[gelöst] MQTT2 Server und Shelly1 - Topics werden nicht zeitnah aktualisiert

[Dattel01]

Hi zusammen,
ich habe einen Shelly1 an den MQTT2 Server in FHEM angebunden.
Heute habe ich bemerkt, dass bestimmte Topics nicht zeitnah ihre Updates pushen....

Kurze Erklärung:
Die Shellies haben ein Topic "longpush", welche den Content 1 gesetzt bekommen, wenn man den Lichttaster etwa 1s gedrückt hält..
Ich schalte damit im Erdgeschoss alle Geräte aus und aktiviere das Licht im Treppenhaus...Bisher hat das auch super funktioniert. Ich kann leider nicht sagen, seit wann es nicht mehr geht.

Um dem Problem etwas näher zu kommen, habe ich mit mit mqtt-spy auf den mqtt2-Server verbunden und mal geschaut, was so an Content kommt. Wenn ich jetzt den Schalter bediene, dann kommt sauber der Schaltbefehl per MQTT an. Das Topic "Longpush" (und auch noch ein anderes, welches ich gerade nicht im Kopf habe") bekommt das Statusupdate aber erst so ca. 25 Sekunden später mit. Das ist etwas uncool, wenn ich abends am Lichtschalter stehe, und erstmal 25 Sekunden in der Dunkelheit warten muss, bevor FHEM auf den LongPush reagieren kann :-D

Testweise habe ich den Shelly mal mit einem Mosquitto-Server sprechen lassen und hier kommt LongPush direkt nach dem Tastendruck zusammen mit dem Schaltbefehl.

Hat jemand eine Idee?
Wenn es das Thema schon irgendwo gibt, dann "Mea Culpa"... kommt nicht wieder vor...

[rudolfkoenig]

Kannst Du bitte ein "attr mqtt2server verbose 5" Log Mitschnitt vom LongPush hier anhaengen?
Wird 2-mal kurz hintereinander gedrueckter "ShortPush" richtig gemeldet?

[Dattel01]

Hier mal eine Abfolge von Schaltvorgängen am Taster..
Ich habe das Log etwas eingekürzt und die anderen Geräte rausgenommen.
warum ist im Log kein Delay zu erkennen... 

• ein normales Schalten
• 2mal schnelles Schalten
• 2mal LongPush

Code Auswählen Erweitern


2019.06.18 19:11:16 5: PUBLISH: 0#(0)(31)shellies/shelly1-2C812A/relay/0on
2019.06.18 19:11:16 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:on
2019.06.18 19:11:16 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000on
2019.06.18 19:11:16 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/01
2019.06.18 19:11:16 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.18 19:11:16 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.18 19:11:31 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/01
2019.06.18 19:11:31 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.18 19:11:31 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.18 19:11:31 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/00
2019.06.18 19:11:31 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:0
2019.06.18 19:11:31 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0000
2019.06.18 19:11:31 5: PUBLISH: 0$(0)(31)shellies/shelly1-2C812A/relay/0off
2019.06.18 19:11:31 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:off
2019.06.18 19:11:31 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000off
2019.06.18 19:11:31 5: PUBLISH: 0%(0)"shellies/shelly1-2C812A/longpush/00
2019.06.18 19:11:31 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/longpush/0:0
2019.06.18 19:11:31 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/longpush/0\0000
2019.06.18 19:11:33 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/01
2019.06.18 19:11:33 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.18 19:11:33 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.18 19:11:34 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/00
2019.06.18 19:11:34 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:0
2019.06.18 19:11:34 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0000
2019.06.18 19:11:34 5: PUBLISH: 0#(0)(31)shellies/shelly1-2C812A/relay/0on
2019.06.18 19:11:34 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:on
2019.06.18 19:11:34 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000on
2019.06.18 19:11:34 5: PUBLISH: 0%(0)"shellies/shelly1-2C812A/longpush/00
2019.06.18 19:11:34 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/longpush/0:0
2019.06.18 19:11:34 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/longpush/0\0000
2019.06.18 19:11:35 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/01
2019.06.18 19:11:35 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.18 19:11:35 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.18 19:11:35 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/00
2019.06.18 19:11:35 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:0
2019.06.18 19:11:35 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0000
2019.06.18 19:11:35 5: PUBLISH: 0$(0)(31)shellies/shelly1-2C812A/relay/0off
2019.06.18 19:11:35 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:off
2019.06.18 19:11:35 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000off
2019.06.18 19:11:35 5: PUBLISH: 0%(0)"shellies/shelly1-2C812A/longpush/00
2019.06.18 19:11:35 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/longpush/0:0
2019.06.18 19:11:35 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/longpush/0\0000
2019.06.18 19:11:36 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/01
2019.06.18 19:11:36 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.18 19:11:36 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.18 19:11:36 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/00
2019.06.18 19:11:36 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:0
2019.06.18 19:11:36 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0000
2019.06.18 19:11:36 5: PUBLISH: 0#(0)(31)shellies/shelly1-2C812A/relay/0on
2019.06.18 19:11:36 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:on
2019.06.18 19:11:36 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000on
2019.06.18 19:11:36 5: PUBLISH: 0%(0)"shellies/shelly1-2C812A/longpush/00
2019.06.18 19:11:36 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/longpush/0:0
2019.06.18 19:11:36 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/longpush/0\0000
2019.06.18 19:11:37 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/01
2019.06.18 19:11:37 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.18 19:11:37 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.18 19:11:38 5: PUBLISH: 0%(0)"shellies/shelly1-2C812A/longpush/01
2019.06.18 19:11:38 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/longpush/0:1
2019.06.18 19:11:38 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/longpush/0\0001
2019.06.18 19:12:03 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/00
2019.06.18 19:12:03 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:0
2019.06.18 19:12:03 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0000
2019.06.18 19:12:03 5: PUBLISH: 0$(0)(31)shellies/shelly1-2C812A/relay/0off
2019.06.18 19:12:03 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:off
2019.06.18 19:12:03 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000off
2019.06.18 19:12:03 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/01
2019.06.18 19:12:03 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.18 19:12:03 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.18 19:12:03 5: PUBLISH: 0%(0)"shellies/shelly1-2C812A/longpush/01
2019.06.18 19:12:03 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/longpush/0:1
2019.06.18 19:12:03 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/longpush/0\0001
2019.06.18 19:12:28 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:0
2019.06.18 19:12:28 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0000
2019.06.18 19:12:28 5: PUBLISH: 0#(0)(31)shellies/shelly1-2C812A/relay/0on
2019.06.18 19:12:28 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:on
2019.06.18 19:12:28 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000on
2019.06.18 19:12:28 5: PUBLISH: 0#(0)(31)shellies/shelly1-2C812A/relay/0on
2019.06.18 19:12:28 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:on
2019.06.18 19:12:28 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000on
2019.06.18 19:12:28 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/01
2019.06.18 19:12:28 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.18 19:12:28 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.18 19:12:29 5: PUBLISH: 0#(0)(31)shellies/shelly1-2C812A/relay/0on
2019.06.18 19:12:29 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:on
2019.06.18 19:12:29 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000on
2019.06.18 19:12:29 5: PUBLISH: 0"(0)(31)shellies/shelly1-2C812A/input/01
2019.06.18 19:12:29 4: MQTT2_FHEM_Server_192.168.178.222_63739 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.18 19:12:29 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001


[rudolfkoenig]

warum ist im Log kein Delay zu erkennen...

Vermutlich weil das Problem nicht in MQTT2_SERVER ist.
Die Zeile mit "(0)" ist Eingang in MQTT2_SERVER, und die Zeile mit Dispatch ist schon die globale Verteilung, also nicht mehr im Modul.
Ich gehe davon aus, dass MQTT2_DEVICE auch direkt reagiert (mit "attr global verbose 5" sollte eine MQTT2_DEVICE_Parse Zeile sichtbar sein), und das Problem anderswo liegt.

[Dattel01]

leider stehe ich hier mit meinem Latein dumm da und weiß nicht, wo ich gerade ansetzen soll..

Wenn ich mich mit MQTT-Spy auf den mqtt2 Server verbinde dann beobachte ich ja das selbe Verhalten, wie ich es am Schalter erlebe.

-Longpush am Schalter, Licht geht aus -> 25 Sekunden später kommt der notify in FHEM an und somit gehen die notify spezifizierten Lampen an/aus.
-im Mqtt-Spy sehe ich die Änderung auf dem Longpush-Topic ja auch erst nach diesen 25 Sekunden.. Das sonderbare hierbei ist, das der TimeStamp für die "Longpush"-Änderung in mqtt-spy annährend zu dem Tastzeitpunkt passt - nur halt eben 25 Sekunden später erst kommt.

Sobald ich den Shelly aber nicht gegen mqtt2 sondern gegen mosquitto laufen lasse, flattert LongPush dort nahezu "instant" ein..

[rudolfkoenig]

leider stehe ich hier mit meinem Latein dumm da und weiß nicht, wo ich gerade ansetzen soll..

Ich habe es im vorigen Beitrag doch beschrieben: mit "attr global verbose 5"

[Dattel01]

Oh man... Was bin ich ein Holzkopf!!!!!! 

Jetzt habe ich gerade das Log mit Verbose angefertigt und hatte schon einen langen Erklärungstext dazu verfasst, dann fällt mein entzündetes Auge in dem Log tatsächlich selber etwas auf.....

Hier mal mein Notify:

Code Auswählen Erweitern

MQTT2_shelly1_2C812A:longpush_0:.1 {
  fhem("
    set MQTT2_shelly1_2C8CED off;
    set MQTT2_shelly1_2C10F2 off;
    set MQTT2_DVES_5A10BF off;
    set MQTT2_DVES_5E3365 off;
    set HUEbridge_HUEDevice10 off;
    set HUEbridge_HUEDevice11 off;
    set HUEbridge_HUEDevice12 off;
    set HUEbridge_HUEDevice13 off;
    set MQTT2_shelly1_2C7DED off;
    set MQTT2_shelly1_2C13FE on;
  ")
}

Jetzt habe ich hier letzte Woche etwas gebastelt und dabei die HUE-Bridge aus der Steckdose gezogen. Was nicht weiter auffällt, da die HUE-Lampen halt einfach da sind, aber eigentlich sowieso immer mit dem Schalter an der Wand ausgeschaltet werden/sind...

Hab gerade die HUEBridge wieder mit Strom versorgt, und Schwupps funktioniert auch der LongPush wieder wunderbar.....

Aber was hat die HUE mit dem MQTT zu tun.... und vorallem, warum funktioniert das Ganze mit Mosquitto und mit MQTT2 nicht.. Blockiert die vergebliche HUE-Anfrage hier so krass das FHEM-System?

Vielen Dank für's auf die Lösung stoßen :-D

[rudolfkoenig]

warum funktioniert das Ganze mit Mosquitto und mit MQTT2 nicht.

Faererweise muesstest du mosquitto mit FHEM mit nur einer global und einer MQTT2_SERVER Instanz vergleichen.

Blockiert die vergebliche HUE-Anfrage hier so krass das FHEM-System?

Bisher war ich der Ansicht, dass das nicht der Fall ist.
Ich wuerde mich freuen, wenn ich ein "attr global verbose 5" Mitschnitt des blockierten Vorgangs sehen koennte.

[Dattel01]

Das Log will ich dir natürlich nicht vorenthalten... ich habe ein paar irrelevante Sachen gekürzt (Telegram-Polls,TV, Hifi) damit es etwas übersichtlicher ist...

2019.06.19 10:44:01 bis 2019.06.19 10:44:26 -> das sind genau meine 25 Sekunden Verzögerung

Code Auswählen Erweitern

2019.06.19 10:43:52 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.19 10:43:52 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.19 10:43:52 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/input/0 => input0
2019.06.19 10:43:52 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is input0: 1
2019.06.19 10:43:52 5: createNotifyHash
2019.06.19 10:43:52 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:52 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:0
2019.06.19 10:43:52 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0000
2019.06.19 10:43:52 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/input/0 => input0
2019.06.19 10:43:52 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is input0: 0
2019.06.19 10:43:52 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:52 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:on
2019.06.19 10:43:52 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000on
2019.06.19 10:43:52 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/relay/0 => relay0
2019.06.19 10:43:52 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/relay/0 => state
2019.06.19 10:43:52 5: Starting notify loop for MQTT2_shelly1_2C812A, 2 event(s), first is relay0: on
2019.06.19 10:43:52 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:52 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/longpush/0:0
2019.06.19 10:43:52 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/longpush/0\0000
2019.06.19 10:43:52 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/longpush/0 => longpush_0
2019.06.19 10:43:52 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is longpush_0: 0
2019.06.19 10:43:52 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:54 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.19 10:43:54 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.19 10:43:54 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/input/0 => input0
2019.06.19 10:43:54 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is input0: 1
2019.06.19 10:43:54 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:54 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:0
2019.06.19 10:43:54 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0000
2019.06.19 10:43:54 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/input/0 => input0
2019.06.19 10:43:54 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is input0: 0
2019.06.19 10:43:54 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:54 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:off
2019.06.19 10:43:54 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000off
2019.06.19 10:43:54 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/relay/0 => relay0
2019.06.19 10:43:54 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/relay/0 => state
2019.06.19 10:43:54 5: Starting notify loop for MQTT2_shelly1_2C812A, 2 event(s), first is relay0: off
2019.06.19 10:43:54 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:54 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/longpush/0:0
2019.06.19 10:43:54 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/longpush/0\0000
2019.06.19 10:43:54 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/longpush/0 => longpush_0
2019.06.19 10:43:54 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is longpush_0: 0
2019.06.19 10:43:54 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:56 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.19 10:43:56 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.19 10:43:56 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/input/0 => input0
2019.06.19 10:43:56 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is input0: 1
2019.06.19 10:43:56 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:57 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:0
2019.06.19 10:43:57 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0000
2019.06.19 10:43:57 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/input/0 => input0
2019.06.19 10:43:57 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is input0: 0
2019.06.19 10:43:57 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:57 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:on
2019.06.19 10:43:57 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000on
2019.06.19 10:43:57 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/relay/0 => relay0
2019.06.19 10:43:57 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/relay/0 => state
2019.06.19 10:43:57 5: Starting notify loop for MQTT2_shelly1_2C812A, 2 event(s), first is relay0: on
2019.06.19 10:43:57 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:57 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/longpush/0:0
2019.06.19 10:43:57 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/longpush/0\0000
2019.06.19 10:43:57 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/longpush/0 => longpush_0
2019.06.19 10:43:57 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is longpush_0: 0
2019.06.19 10:43:57 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:57 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.19 10:43:57 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.19 10:43:57 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/input/0 => input0
2019.06.19 10:43:57 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is input0: 1
2019.06.19 10:43:57 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:57 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:0
2019.06.19 10:43:57 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0000
2019.06.19 10:43:57 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/input/0 => input0
2019.06.19 10:43:57 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is input0: 0
2019.06.19 10:43:57 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:57 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:off
2019.06.19 10:43:57 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000off
2019.06.19 10:43:57 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/relay/0 => relay0
2019.06.19 10:43:57 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/relay/0 => state
2019.06.19 10:43:57 5: Starting notify loop for MQTT2_shelly1_2C812A, 2 event(s), first is relay0: off
2019.06.19 10:43:57 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:43:57 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/longpush/0:0
2019.06.19 10:43:57 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/longpush/0\0000
2019.06.19 10:43:57 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/longpush/0 => longpush_0
2019.06.19 10:43:57 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is longpush_0: 0
2019.06.19 10:43:57 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:44:00 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.19 10:44:00 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.19 10:44:00 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/input/0 => input0
2019.06.19 10:44:00 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is input0: 1
2019.06.19 10:44:00 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:44:01 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/longpush/0:1
2019.06.19 10:44:01 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/longpush/0\0001
2019.06.19 10:44:01 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/longpush/0 => longpush_0
2019.06.19 10:44:01 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is longpush_0: 1
2019.06.19 10:44:01 5: Triggering MQTT2_shelly1_2C812A_notify_1
2019.06.19 10:44:01 4: MQTT2_shelly1_2C812A_notify_1 exec {
  fhem("
    set MQTT2_shelly1_2C8CED off;;
    set MQTT2_shelly1_2C10F2 off;;
    set MQTT2_DVES_5A10BF off;;
    set MQTT2_DVES_5E3365 off;;
    set HUEbridge_HUEDevice10 off;;
    set HUEbridge_HUEDevice11 off;;
    set HUEbridge_HUEDevice12 off;;
    set HUEbridge_HUEDevice13 off;;
    set MQTT2_shelly1_2C7DED off;;
    set MQTT2_shelly1_2C13FE on;;
  ")
}
2019.06.19 10:44:01 5: Cmd: >{
  fhem("
    set MQTT2_shelly1_2C8CED off;
    set MQTT2_shelly1_2C10F2 off;
    set MQTT2_DVES_5A10BF off;
    set MQTT2_DVES_5E3365 off;
    set HUEbridge_HUEDevice10 off;
    set HUEbridge_HUEDevice11 off;
    set HUEbridge_HUEDevice12 off;
    set HUEbridge_HUEDevice13 off;
    set MQTT2_shelly1_2C7DED off;
    set MQTT2_shelly1_2C13FE on;
  ")
}<
2019.06.19 10:44:01 5: Cmd: >set MQTT2_shelly1_2C8CED off<
2019.06.19 10:44:01 5: MQTT2_FHEM_Server: PUBLISH shellies/shelly1-2C8CED/relay/0/command off
2019.06.19 10:44:01 5: MQTT2_FHEM_Server_192.168.178.221_62932 shelly1-2C8CED => shellies/shelly1-2C8CED/relay/0/command:off
2019.06.19 10:44:01 5: Starting notify loop for MQTT2_shelly1_2C8CED, 1 event(s), first is off
2019.06.19 10:44:01 5: End notify loop for MQTT2_shelly1_2C8CED
2019.06.19 10:44:01 5: Cmd: >set MQTT2_shelly1_2C10F2 off<
2019.06.19 10:44:01 5: MQTT2_FHEM_Server: PUBLISH shellies/shelly1-2C10F2/relay/0/command off
2019.06.19 10:44:01 5: MQTT2_FHEM_Server_192.168.178.224_21358 shelly1-2C10F2 => shellies/shelly1-2C10F2/relay/0/command:off
2019.06.19 10:44:01 5: Starting notify loop for MQTT2_shelly1_2C10F2, 1 event(s), first is off
2019.06.19 10:44:01 5: End notify loop for MQTT2_shelly1_2C10F2
2019.06.19 10:44:01 5: Cmd: >set MQTT2_DVES_5A10BF off<
2019.06.19 10:44:01 5: MQTT2_FHEM_Server: PUBLISH cmnd/Gosund_Socket_2/POWER1 0
2019.06.19 10:44:01 5: MQTT2_FHEM_Server_192.168.178.214_50147 DVES_5A10BF => cmnd/Gosund_Socket_2/POWER1:0
2019.06.19 10:44:01 5: Starting notify loop for MQTT2_DVES_5A10BF, 1 event(s), first is set_off
2019.06.19 10:44:01 5: End notify loop for MQTT2_DVES_5A10BF
2019.06.19 10:44:01 5: Cmd: >set MQTT2_DVES_5E3365 off<
2019.06.19 10:44:01 5: MQTT2_FHEM_Server: PUBLISH cmnd/Gosund_Socket_3/POWER1 0
2019.06.19 10:44:01 5: MQTT2_FHEM_Server_192.168.178.215_49570 DVES_5E3365 => cmnd/Gosund_Socket_3/POWER1:0
2019.06.19 10:44:01 5: Starting notify loop for MQTT2_DVES_5E3365, 1 event(s), first is set_off
2019.06.19 10:44:01 5: End notify loop for MQTT2_DVES_5E3365
2019.06.19 10:44:01 5: Cmd: >set HUEbridge_HUEDevice10 off<
2019.06.19 10:44:01 4: using HUEBridge_HTTP_Request: PUT lights/10/state
2019.06.19 10:44:04 1: HUEBridge_HTTP_Request http://192.168.178.12/api/########################################/lights/10/state: Can't connect to http://192.168.178.12:80
2019.06.19 10:44:04 3: HUEBridge_Call: failed, retrying
2019.06.19 10:44:04 4: using HUEBridge_HTTP_Request: PUT lights/10/state
2019.06.19 10:44:08 1: HUEBridge_HTTP_Request http://192.168.178.12/api/########################################/lights/10/state: Can't connect to http://192.168.178.12:80
2019.06.19 10:44:08 3: HUEBridge_Call: failed, retrying
2019.06.19 10:44:08 3: HUEBridge_Call: failed
2019.06.19 10:44:08 5: Cmd: >set HUEbridge_HUEDevice11 off<
2019.06.19 10:44:08 4: using HUEBridge_HTTP_Request: PUT lights/11/state
2019.06.19 10:44:11 1: HUEBridge_HTTP_Request http://192.168.178.12/api/########################################/lights/11/state: Can't connect to http://192.168.178.12:80
2019.06.19 10:44:11 3: HUEBridge_Call: failed, retrying
2019.06.19 10:44:11 4: using HUEBridge_HTTP_Request: PUT lights/11/state
2019.06.19 10:44:14 1: HUEBridge_HTTP_Request http://192.168.178.12/api/########################################/lights/11/state: Can't connect to http://192.168.178.12:80
2019.06.19 10:44:14 3: HUEBridge_Call: failed, retrying
2019.06.19 10:44:14 3: HUEBridge_Call: failed
2019.06.19 10:44:14 5: Cmd: >set HUEbridge_HUEDevice12 off<
2019.06.19 10:44:14 4: using HUEBridge_HTTP_Request: PUT lights/12/state
2019.06.19 10:44:17 1: HUEBridge_HTTP_Request http://192.168.178.12/api/########################################/lights/12/state: Can't connect to http://192.168.178.12:80
2019.06.19 10:44:17 3: HUEBridge_Call: failed, retrying
2019.06.19 10:44:17 4: using HUEBridge_HTTP_Request: PUT lights/12/state
2019.06.19 10:44:20 1: HUEBridge_HTTP_Request http://192.168.178.12/api/########################################/lights/12/state: Can't connect to http://192.168.178.12:80
2019.06.19 10:44:20 3: HUEBridge_Call: failed, retrying
2019.06.19 10:44:20 3: HUEBridge_Call: failed
2019.06.19 10:44:20 5: Cmd: >set HUEbridge_HUEDevice13 off<
2019.06.19 10:44:20 4: using HUEBridge_HTTP_Request: PUT lights/13/state
2019.06.19 10:44:23 1: HUEBridge_HTTP_Request http://192.168.178.12/api/########################################/lights/13/state: Can't connect to http://192.168.178.12:80
2019.06.19 10:44:23 3: HUEBridge_Call: failed, retrying
2019.06.19 10:44:23 4: using HUEBridge_HTTP_Request: PUT lights/13/state
2019.06.19 10:44:26 1: HUEBridge_HTTP_Request http://192.168.178.12/api/########################################/lights/13/state: Can't connect to http://192.168.178.12:80
2019.06.19 10:44:26 3: HUEBridge_Call: failed, retrying
2019.06.19 10:44:26 3: HUEBridge_Call: failed
2019.06.19 10:44:26 5: Cmd: >set MQTT2_shelly1_2C7DED off<
2019.06.19 10:44:26 5: MQTT2_FHEM_Server: PUBLISH shellies/shelly1-2C7DED/relay/0/command off
2019.06.19 10:44:26 5: MQTT2_FHEM_Server_192.168.178.225_47593 shelly1-2C7DED => shellies/shelly1-2C7DED/relay/0/command:off
2019.06.19 10:44:26 5: Starting notify loop for MQTT2_shelly1_2C7DED, 1 event(s), first is off
2019.06.19 10:44:26 5: End notify loop for MQTT2_shelly1_2C7DED
2019.06.19 10:44:26 5: Cmd: >set MQTT2_shelly1_2C13FE on<
2019.06.19 10:44:26 5: MQTT2_FHEM_Server: PUBLISH shellies/shelly1-2C13FE/relay/0/command on
2019.06.19 10:44:26 5: MQTT2_FHEM_Server_192.168.178.223_29435 shelly1-2C13FE => shellies/shelly1-2C13FE/relay/0/command:on
2019.06.19 10:44:26 5: Starting notify loop for MQTT2_shelly1_2C13FE, 1 event(s), first is on
2019.06.19 10:44:26 5: End notify loop for MQTT2_shelly1_2C13FE
2019.06.19 10:44:26 5: Cmd: ><
2019.06.19 10:44:26 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:44:26 5: MQTT mqttBroker message sent: PingReq/at-most-once
2019.06.19 10:44:26 5: SW: c000
2019.06.19 10:44:26 3: MQTT2_FHEM_Server: MQTT2_FHEM_Server_192.168.178.215_49570/DVES_5E3365 left us (keepalive check)
2019.06.19 10:44:26 5: Starting notify loop for MQTT2_FHEM_Server, 1 event(s), first is nrclients: 8
2019.06.19 10:44:26 5: End notify loop for MQTT2_FHEM_Server
2019.06.19 10:44:26 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000DVES_5E3365\000tele/Gosund_Socket_3/LWT\000Offline
2019.06.19 10:44:26 4: MQTT2_DEVICE_Parse: MQTT2_DVES_5E3365 tele/Gosund_Socket_3/LWT => LWT
2019.06.19 10:44:26 5: Starting notify loop for MQTT2_DVES_5E3365, 1 event(s), first is LWT: Offline
2019.06.19 10:44:26 5: End notify loop for MQTT2_DVES_5E3365
2019.06.19 10:44:26 3: MQTT2_FHEM_Server: MQTT2_FHEM_Server_192.168.178.214_50147/DVES_5A10BF left us (keepalive check)
2019.06.19 10:44:26 5: Starting notify loop for MQTT2_FHEM_Server, 1 event(s), first is nrclients: 7
2019.06.19 10:44:26 5: End notify loop for MQTT2_FHEM_Server
2019.06.19 10:44:26 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000DVES_5A10BF\000tele/Gosund_Socket_2/LWT\000Offline
2019.06.19 10:44:26 4: MQTT2_DEVICE_Parse: MQTT2_DVES_5A10BF tele/Gosund_Socket_2/LWT => LWT
2019.06.19 10:44:26 5: Starting notify loop for MQTT2_DVES_5A10BF, 1 event(s), first is LWT: Offline
2019.06.19 10:44:26 5: End notify loop for MQTT2_DVES_5A10BF
2019.06.19 10:44:26 3: MQTT2_FHEM_Server: MQTT2_FHEM_Server_192.168.178.210_11338/DVES_93D20A left us (keepalive check)
2019.06.19 10:44:26 5: Starting notify loop for MQTT2_FHEM_Server, 1 event(s), first is nrclients: 6
2019.06.19 10:44:26 5: End notify loop for MQTT2_FHEM_Server
2019.06.19 10:44:26 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000DVES_93D20A\000tele/Sonoff_Switch_1/LWT\000Offline
2019.06.19 10:44:26 4: MQTT2_DEVICE_Parse: MQTT2_DVES_93D20A tele/Sonoff_Switch_1/LWT => LWT
2019.06.19 10:44:26 5: Starting notify loop for MQTT2_DVES_93D20A, 1 event(s), first is LWT: Offline
2019.06.19 10:44:26 5: End notify loop for MQTT2_DVES_93D20A
2019.06.19 10:44:26 4: MQTT2_FHEM_Server_192.168.178.223_29435 shelly1-2C13FE PUBLISH shellies/shelly1-2C13FE/relay/0:off
2019.06.19 10:44:26 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C13FE\000shellies/shelly1-2C13FE/relay/0\000off
2019.06.19 10:44:26 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C13FE shellies/shelly1-2C13FE/relay/0 => relay0
2019.06.19 10:44:26 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C13FE shellies/shelly1-2C13FE/relay/0 => state
2019.06.19 10:44:26 5: Starting notify loop for MQTT2_shelly1_2C13FE, 2 event(s), first is relay0: off
2019.06.19 10:44:26 5: End notify loop for MQTT2_shelly1_2C13FE
2019.06.19 10:44:26 4: MQTT2_FHEM_Server_192.168.178.223_29435 shelly1-2C13FE PUBLISH shellies/shelly1-2C13FE/input/0:0
2019.06.19 10:44:26 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C13FE\000shellies/shelly1-2C13FE/input/0\0000
2019.06.19 10:44:26 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C13FE shellies/shelly1-2C13FE/input/0 => input0
2019.06.19 10:44:26 5: Starting notify loop for MQTT2_shelly1_2C13FE, 1 event(s), first is input0: 0
2019.06.19 10:44:26 5: End notify loop for MQTT2_shelly1_2C13FE
2019.06.19 10:44:26 4: MQTT2_FHEM_Server_192.168.178.224_21358 shelly1-2C10F2 PUBLISH shellies/shelly1-2C10F2/relay/0:off
2019.06.19 10:44:26 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C10F2\000shellies/shelly1-2C10F2/relay/0\000off
2019.06.19 10:44:26 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C10F2 shellies/shelly1-2C10F2/relay/0 => state
2019.06.19 10:44:26 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C10F2 shellies/shelly1-2C10F2/relay/0 => relay0
2019.06.19 10:44:26 5: Starting notify loop for MQTT2_shelly1_2C10F2, 2 event(s), first is off
2019.06.19 10:44:26 5: End notify loop for MQTT2_shelly1_2C10F2
2019.06.19 10:44:26 4: MQTT2_FHEM_Server_192.168.178.224_21358 shelly1-2C10F2 PUBLISH shellies/shelly1-2C10F2/input/0:1
2019.06.19 10:44:26 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C10F2\000shellies/shelly1-2C10F2/input/0\0001
2019.06.19 10:44:26 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C10F2 shellies/shelly1-2C10F2/input/0 => input0
2019.06.19 10:44:26 5: Starting notify loop for MQTT2_shelly1_2C10F2, 1 event(s), first is input0: 1
2019.06.19 10:44:26 5: End notify loop for MQTT2_shelly1_2C10F2
2019.06.19 10:44:26 4: MQTT2_FHEM_Server_192.168.178.225_47593 shelly1-2C7DED PUBLISH shellies/shelly1-2C7DED/relay/0:off
2019.06.19 10:44:26 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C7DED\000shellies/shelly1-2C7DED/relay/0\000off
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C7DED shellies/shelly1-2C7DED/relay/0 => state
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C7DED shellies/shelly1-2C7DED/relay/0 => relay0
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_shelly1_2C7DED, 2 event(s), first is off
2019.06.19 10:44:27 5: End notify loop for MQTT2_shelly1_2C7DED
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.225_47593 shelly1-2C7DED PUBLISH shellies/shelly1-2C7DED/input/0:0
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C7DED\000shellies/shelly1-2C7DED/input/0\0000
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C7DED shellies/shelly1-2C7DED/input/0 => input0
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_shelly1_2C7DED, 1 event(s), first is input0: 0
2019.06.19 10:44:27 5: End notify loop for MQTT2_shelly1_2C7DED
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.226_6095 shelly1-2C0C17 PUBLISH shellies/shelly1-2C0C17/relay/0:off
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C0C17\000shellies/shelly1-2C0C17/relay/0\000off
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C0C17 shellies/shelly1-2C0C17/relay/0 => relay0
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C0C17 shellies/shelly1-2C0C17/relay/0 => state
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_shelly1_2C0C17, 2 event(s), first is relay0: off
2019.06.19 10:44:27 5: End notify loop for MQTT2_shelly1_2C0C17
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.226_6095 shelly1-2C0C17 PUBLISH shellies/shelly1-2C0C17/input/0:1
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C0C17\000shellies/shelly1-2C0C17/input/0\0001
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C0C17 shellies/shelly1-2C0C17/input/0 => input0
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_shelly1_2C0C17, 1 event(s), first is input0: 1
2019.06.19 10:44:27 5: End notify loop for MQTT2_shelly1_2C0C17
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:0
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0000
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/input/0 => input0
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is input0: 0
2019.06.19 10:44:27 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:on
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000on
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/relay/0 => relay0
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/relay/0 => state
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_shelly1_2C812A, 2 event(s), first is relay0: on
2019.06.19 10:44:27 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/relay/0:on
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/relay/0\000on
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/relay/0 => relay0
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/relay/0 => state
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_shelly1_2C812A, 2 event(s), first is relay0: on
2019.06.19 10:44:27 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.222_63750 shelly1-2C812A PUBLISH shellies/shelly1-2C812A/input/0:1
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C812A\000shellies/shelly1-2C812A/input/0\0001
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C812A shellies/shelly1-2C812A/input/0 => input0
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_shelly1_2C812A, 1 event(s), first is input0: 1
2019.06.19 10:44:27 5: End notify loop for MQTT2_shelly1_2C812A
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.221_62932 shelly1-2C8CED PUBLISH shellies/shelly1-2C8CED/relay/0:off
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C8CED\000shellies/shelly1-2C8CED/relay/0\000off
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C8CED shellies/shelly1-2C8CED/relay/0 => relay0
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C8CED shellies/shelly1-2C8CED/relay/0 => state
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_shelly1_2C8CED, 2 event(s), first is relay0: off
2019.06.19 10:44:27 5: End notify loop for MQTT2_shelly1_2C8CED
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.221_62932 shelly1-2C8CED PUBLISH shellies/shelly1-2C8CED/input/0:1
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C8CED\000shellies/shelly1-2C8CED/input/0\0001
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C8CED shellies/shelly1-2C8CED/input/0 => input0
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_shelly1_2C8CED, 1 event(s), first is input0: 1
2019.06.19 10:44:27 5: End notify loop for MQTT2_shelly1_2C8CED
2019.06.19 10:44:27 5: MQTT mqttBroker message received: PingResp/at-most-once
2019.06.19 10:44:27 5: Starting notify loop for mqttBroker, 1 event(s), first is connection: active
2019.06.19 10:44:27 5: End notify loop for mqttBroker
2019.06.19 10:44:27 5: Starting notify loop for SD_WS07_T_2, 2 event(s), first is T: 39.8
2019.06.19 10:44:27 5: End notify loop for SD_WS07_T_2
2019.06.19 10:44:27 4: Connection accepted from MQTT2_FHEM_Server_192.168.178.214_50148
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_FHEM_Server, 1 event(s), first is nrclients: 7
2019.06.19 10:44:27 5: End notify loop for MQTT2_FHEM_Server
2019.06.19 10:44:27 4: Connection accepted from MQTT2_FHEM_Server_192.168.178.210_11803
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_FHEM_Server, 1 event(s), first is nrclients: 8
2019.06.19 10:44:27 5: End notify loop for MQTT2_FHEM_Server
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.214_50148 DVES_5A10BF CONNECT V:4 keepAlive:10 LWT:tele/Gosund_Socket_2/LWT:Offline usr:mqttuser
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.223_29435 shelly1-2C13FE PUBLISH shellies/shelly1-2C13FE/relay/0:on
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000shelly1_2C13FE\000shellies/shelly1-2C13FE/relay/0\000on
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C13FE shellies/shelly1-2C13FE/relay/0 => relay0
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_shelly1_2C13FE shellies/shelly1-2C13FE/relay/0 => state
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_shelly1_2C13FE, 2 event(s), first is relay0: on
2019.06.19 10:44:27 5: End notify loop for MQTT2_shelly1_2C13FE
2019.06.19 10:44:27 4: Connection accepted from MQTT2_FHEM_Server_192.168.178.215_49571
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_FHEM_Server, 1 event(s), first is nrclients: 9
2019.06.19 10:44:27 5: End notify loop for MQTT2_FHEM_Server
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.210_11803 DVES_93D20A CONNECT V:4 keepAlive:10 LWT:tele/Sonoff_Switch_1/LWT:Offline usr:mqttuser
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.215_49571 DVES_5E3365 CONNECT V:4 keepAlive:10 LWT:tele/Gosund_Socket_3/LWT:Offline usr:mqttuser
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.210_11803 DVES_93D20A PUBLISH tele/Sonoff_Switch_1/LWT:Online
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000DVES_93D20A\000tele/Sonoff_Switch_1/LWT\000Online
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_DVES_93D20A tele/Sonoff_Switch_1/LWT => LWT
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_DVES_93D20A, 1 event(s), first is LWT: Online
2019.06.19 10:44:27 5: End notify loop for MQTT2_DVES_93D20A
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.210_11803 DVES_93D20A PUBLISH cmnd/Sonoff_Switch_1/POWER:
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000DVES_93D20A\000cmnd/Sonoff_Switch_1/POWER\000
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.210_11803 DVES_93D20A SUBSCRIBE
2019.06.19 10:44:27 4:   topic:cmnd/Sonoff_Switch_1/# qos:0
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.210_11803 DVES_93D20A SUBSCRIBE
2019.06.19 10:44:27 4:   topic:cmnd/sonoffs/# qos:0
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.210_11803 DVES_93D20A SUBSCRIBE
2019.06.19 10:44:27 4:   topic:cmnd/DVES_93D20A_fb/# qos:0
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.214_50148 DVES_5A10BF PUBLISH tele/Gosund_Socket_2/LWT:Online
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000DVES_5A10BF\000tele/Gosund_Socket_2/LWT\000Online
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_DVES_5A10BF tele/Gosund_Socket_2/LWT => LWT
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_DVES_5A10BF, 1 event(s), first is LWT: Online
2019.06.19 10:44:27 5: End notify loop for MQTT2_DVES_5A10BF
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.214_50148 DVES_5A10BF PUBLISH cmnd/Gosund_Socket_2/POWER:
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000DVES_5A10BF\000cmnd/Gosund_Socket_2/POWER\000
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.214_50148 DVES_5A10BF SUBSCRIBE
2019.06.19 10:44:27 4:   topic:cmnd/Gosund_Socket_2/# qos:0
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.214_50148 DVES_5A10BF SUBSCRIBE
2019.06.19 10:44:27 4:   topic:cmnd/sonoffs/# qos:0
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.214_50148 DVES_5A10BF SUBSCRIBE
2019.06.19 10:44:27 4:   topic:cmnd/DVES_5A10BF_fb/# qos:0
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.215_49571 DVES_5E3365 PUBLISH tele/Gosund_Socket_3/LWT:Online
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000DVES_5E3365\000tele/Gosund_Socket_3/LWT\000Online
2019.06.19 10:44:27 4: MQTT2_DEVICE_Parse: MQTT2_DVES_5E3365 tele/Gosund_Socket_3/LWT => LWT
2019.06.19 10:44:27 5: Starting notify loop for MQTT2_DVES_5E3365, 1 event(s), first is LWT: Online
2019.06.19 10:44:27 5: End notify loop for MQTT2_DVES_5E3365
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.215_49571 DVES_5E3365 PUBLISH cmnd/Gosund_Socket_3/POWER:
2019.06.19 10:44:27 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000DVES_5E3365\000cmnd/Gosund_Socket_3/POWER\000
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.215_49571 DVES_5E3365 SUBSCRIBE
2019.06.19 10:44:27 4:   topic:cmnd/Gosund_Socket_3/# qos:0
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.215_49571 DVES_5E3365 SUBSCRIBE
2019.06.19 10:44:27 4:   topic:cmnd/sonoffs/# qos:0
2019.06.19 10:44:27 4: MQTT2_FHEM_Server_192.168.178.215_49571 DVES_5E3365 SUBSCRIBE
2019.06.19 10:44:27 4:   topic:cmnd/DVES_5E3365_fb/# qos:0


[rudolfkoenig]

Das HUEBridge Modul blockiert leider beim Verbindungsaufbau FHEM.
Man koennte es dem Modulauthor naheliegen, auf die nicht blockierende FHEM Funktion umzusteigen

[Dattel01]

Soll ich dem Kollegen mal eine PM mit einem Link auf diesen Thread zukommen lassen?

[rudolfkoenig]

Gerne.

[Dattel01]

ist erledigt.... Vielen Dank schon mal für den Support an dieser Stelle.

[justme1968]

wenn man das dafür vorgesehene attribut httpUtils auf 1 setzt werden (fast) alle anfragen/kommandos an die bridge nicht blockierend abgesetzt.

httpUtils
0 -> use HttpUtils_BlockingGet
1 -> use HttpUtils_NonblockingGet
not set -> use old module specific implementation

pollDevices
1 -> the bridge will poll all lights in one go instead of each device polling itself independently
2 -> the bridge will poll all devices in one go instead of each device polling itself independently
default is 1.

[Dattel01]

Top!....
und wieder mal RTFM 
Schnelle und funktionierende Antwort... Herzlichen Dank....