[gelöst] MQTT Modul steigt aus mit Fehler: decode_string: insufficient data

essera · 11 Februar 2019, 21:57:29

Ich habe seit einigen Wochen auf meinem Testsystem den MQTT2 Server im Einsatz mit einer Verbindung zum Zigbee2MQTT Gateway. (FHEM als Docker und Zigbee2MQTT auch als Docker)
Diverse Zigbee Geräte und Tasmota Geräte liefen hier sehr stabil nebeneinander. Dabei habe ich die fortwährende Weiterentwicklung der MQTT2 Devices selber testen können.
Sehr schön soweit.
Ich habe dann gestern ein Update von Fhem gemacht (letztes Update war vor ca. 2 Wochen ).
Dann nahm das Unheil seinen Lauf. Seit dem verabschiedet sich FHEM in eine Dauer Restart Loop:

Code Auswählen


2019.02.10 22:34:06.438 1: Including fhem.cfg
2019.02.10 22:34:08.741 3: WEB: port 8083 opened
2019.02.10 22:34:08.846 2: eventTypes: loaded 593 events from ./log/eventTypes.txt
2019.02.10 22:34:08.876 3: telnetPort: port 7072 opened
2019.02.10 22:34:08.891 3: MQTT2_FHEM_Server: port 1883 opened
2019.02.10 22:34:09.281 1: Including ./log/fhem.save
2019.02.10 22:34:09.329 1: ./log/fhem.save: Please define SVG_FileLog_MQTT2_zigbee_0x00158d0002327a09_1 first

2019.02.10 22:34:09.332 3: Opening MQTT device 192.168.178.137:1883
2019.02.10 22:34:09.346 3: MQTT device opened
2019.02.10 22:34:09.347 1: usb create starting
2019.02.10 22:34:09.612 1: usb create end
2019.02.10 22:34:09.614 0: Featurelevel: 5.9
2019.02.10 22:34:09.614 0: Server started with 48 defined entities (fhem.pl:18497/2019-02-05 perl:5.024001 os:linux user:fhem pid:5632)
2019.02.10 22:34:09.733 4: MQTT2_DEVICE_Parse: test_hue zigbee2mqtt/0x0017880102784501 => { json2nameValue($EVENT) }
decode_string: insufficient data at /usr/local/share/perl/5.24.1/Net/MQTT/Message/Publish.pm line 36.
2019.02.10 22:34:21.172 1: Including fhem.cfg
2019.02.10 22:34:21.547 3: WEB: port 8083 opened
2019.02.10 22:34:21.646 2: eventTypes: loaded 593 events from ./log/eventTypes.txt
2019.02.10 22:34:21.675 3: telnetPort: port 7072 opened
2019.02.10 22:34:21.693 3: MQTT2_FHEM_Server: port 1883 opened
2019.02.10 22:34:22.109 1: Including ./log/fhem.save
2019.02.10 22:34:22.160 1: ./log/fhem.save: Please define SVG_FileLog_MQTT2_zigbee_0x00158d0002327a09_1 first

2019.02.10 22:34:22.163 3: Opening MQTT device 192.168.178.137:1883
2019.02.10 22:34:22.177 3: MQTT device opened
2019.02.10 22:34:22.179 1: usb create starting
2019.02.10 22:34:22.447 1: usb create end
2019.02.10 22:34:22.449 0: Featurelevel: 5.9
2019.02.10 22:34:22.449 0: Server started with 48 defined entities (fhem.pl:18497/2019-02-05 perl:5.024001 os:linux user:fhem pid:5729)
2019.02.10 22:34:22.639 4: MQTT2_DEVICE_Parse: test_hue zigbee2mqtt/0x0017880102784501 => { json2nameValue($EVENT) }
decode_string: insufficient data at /usr/local/share/perl/5.24.1/Net/MQTT/Message/Publish.pm line 36.
2019.02.10 22:34:34.168 1: Including fhem.cfg
2019.02.10 22:34:34.506 3: WEB: port 8083 opened
2019.02.10 22:34:34.601 2: eventTypes: loaded 593 events from ./log/eventTypes.txt
2019.02.10 22:34:34.626 3: telnetPort: port 7072 opened
2019.02.10 22:34:34.644 3: MQTT2_FHEM_Server: port 1883 opened
2019.02.10 22:34:35.045 1: Including ./log/fhem.save
2019.02.10 22:34:35.094 1: ./log/fhem.save: Please define SVG_FileLog_MQTT2_zigbee_0x00158d0002327a09_1 first

2019.02.10 22:34:35.097 3: Opening MQTT device 192.168.178.137:1883
2019.02.10 22:34:35.111 3: MQTT device opened
2019.02.10 22:34:35.112 1: usb create starting
2019.02.10 22:34:35.368 1: usb create end
2019.02.10 22:34:35.370 0: Featurelevel: 5.9
2019.02.10 22:34:35.370 0: Server started with 48 defined entities (fhem.pl:18497/2019-02-05 perl:5.024001 os:linux user:fhem pid:5878)
2019.02.10 22:34:35.509 4: MQTT2_DEVICE_Parse: test_hue zigbee2mqtt/0x0017880102784501 => { json2nameValue($EVENT) }
decode_string: insufficient data at /usr/local/share/perl/5.24.1/Net/MQTT/Message/Publish.pm line 36.

Das LOG mit Einstellung MQTT2_Server Verbose auf 5:

Code Auswählen


2019.02.11 20:50:51.136 1: Including fhem.cfg
2019.02.11 20:50:51.599 3: WEB: port 8083 opened
2019.02.11 20:50:51.711 2: eventTypes: loaded 596 events from ./log/eventTypes.txt
2019.02.11 20:50:51.742 3: telnetPort: port 7072 opened
2019.02.11 20:50:51.763 3: MQTT2_FHEM_Server: port 1883 opened
2019.02.11 20:50:52.299 1: Including ./log/fhem.save
2019.02.11 20:50:52.353 3: Opening MQTT device 192.168.178.137:1883
2019.02.11 20:50:52.369 3: MQTT device opened
2019.02.11 20:50:52.370 1: usb create starting
2019.02.11 20:50:52.617 1: usb create end
2019.02.11 20:50:52.619 0: Featurelevel: 5.9
2019.02.11 20:50:52.619 0: Server started with 50 defined entities (fhem.pl:18497/2019-02-05 perl:5.024001 os:linux user:fhem pid:92)
2019.02.11 20:50:52.626 4: Connection accepted from MQTT2_FHEM_Server_172.17.0.1_45018
2019.02.11 20:50:52.629 5: CONNECT: (16)(25)(0)(6)MQIsdp(3)(2)(0)<(0)(11)NetMQTTpm92
2019.02.11 20:50:52.629 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 CONNECT V:3 keepAlive:60
2019.02.11 20:50:52.629 5: PINGREQ: (192)(0)
2019.02.11 20:50:52.629 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PINGREQ
2019.02.11 20:50:52.660 5: SUBSCRIBE: (130)A(0)(1)(0)(30)zigbee2mqtt/0x00158d0002327a09(0)(0)(27)xiaomi/0x00158d0002327a09/#(0)
2019.02.11 20:50:52.660 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 SUBSCRIBE
2019.02.11 20:50:52.660 4:   topic:zigbee2mqtt/0x00158d0002327a09 qos:0
2019.02.11 20:50:52.660 4:   topic:xiaomi/0x00158d0002327a09/# qos:0
2019.02.11 20:50:52.661 5: SUBSCRIBE: (130)A(0)(2)(0)(30)zigbee2mqtt/0x00158d000257d9f9(0)(0)(27)xiaomi/0x00158d000257d9f9/#(0)
2019.02.11 20:50:52.661 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 SUBSCRIBE
2019.02.11 20:50:52.661 4:   topic:zigbee2mqtt/0x00158d000257d9f9 qos:0
2019.02.11 20:50:52.661 4:   topic:xiaomi/0x00158d000257d9f9/# qos:0
2019.02.11 20:50:52.661 5: SUBSCRIBE: (130)A(0)(3)(0)(30)zigbee2mqtt/0x00158d0002a23f1d(0)(0)(27)xiaomi/0x00158d0002a23f1d/#(0)
2019.02.11 20:50:52.662 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 SUBSCRIBE
2019.02.11 20:50:52.662 4:   topic:zigbee2mqtt/0x00158d0002a23f1d qos:0
2019.02.11 20:50:52.662 4:   topic:xiaomi/0x00158d0002a23f1d/# qos:0
2019.02.11 20:50:52.662 5: SUBSCRIBE: (130)A(0)(4)(0)(30)zigbee2mqtt/0x0017880102784501(0)(0)(27)xiaomi/0x0017880102784501/#(0)
2019.02.11 20:50:52.662 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 SUBSCRIBE
2019.02.11 20:50:52.662 4:   topic:zigbee2mqtt/0x0017880102784501 qos:0
2019.02.11 20:50:52.663 4:   topic:xiaomi/0x0017880102784501/# qos:0
2019.02.11 20:50:52.663 5: SUBSCRIBE: (130)@(0)(5)(0)(18)zigbee2mqtt/bridge(0)(0)(15)xiaomi/bridge/#(0)(0)(20)zigbee2mqtt/bridge/#(0)
2019.02.11 20:50:52.663 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 SUBSCRIBE
2019.02.11 20:50:52.663 4:   topic:zigbee2mqtt/bridge qos:0
2019.02.11 20:50:52.663 4:   topic:xiaomi/bridge/# qos:0
2019.02.11 20:50:52.663 4:   topic:zigbee2mqtt/bridge/# qos:0
2019.02.11 20:50:52.664 5: SUBSCRIBE: (138)A(0)(2)(0)(30)zigbee2mqtt/0x00158d000257d9f9(0)(0)(27)xiaomi/0x00158d000257d9f9/#(0)
2019.02.11 20:50:52.664 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 SUBSCRIBE
2019.02.11 20:50:52.664 4:   topic:zigbee2mqtt/0x00158d000257d9f9 qos:0
2019.02.11 20:50:52.664 4:   topic:xiaomi/0x00158d000257d9f9/# qos:0
2019.02.11 20:50:52.664 5: SUBSCRIBE: (138)@(0)(5)(0)(18)zigbee2mqtt/bridge(0)(0)(15)xiaomi/bridge/#(0)(0)(20)zigbee2mqtt/bridge/#(0)
2019.02.11 20:50:52.665 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 SUBSCRIBE
2019.02.11 20:50:52.665 4:   topic:zigbee2mqtt/bridge qos:0
2019.02.11 20:50:52.665 4:   topic:xiaomi/bridge/# qos:0
2019.02.11 20:50:52.665 4:   topic:zigbee2mqtt/bridge/# qos:0
2019.02.11 20:50:52.665 5: SUBSCRIBE: (138)A(0)(1)(0)(30)zigbee2mqtt/0x00158d0002327a09(0)(0)(27)xiaomi/0x00158d0002327a09/#(0)
2019.02.11 20:50:52.665 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 SUBSCRIBE
2019.02.11 20:50:52.666 4:   topic:zigbee2mqtt/0x00158d0002327a09 qos:0
2019.02.11 20:50:52.666 4:   topic:xiaomi/0x00158d0002327a09/# qos:0
2019.02.11 20:50:52.666 5: SUBSCRIBE: (138)A(0)(4)(0)(30)zigbee2mqtt/0x0017880102784501(0)(0)(27)xiaomi/0x0017880102784501/#(0)
2019.02.11 20:50:52.666 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 SUBSCRIBE
2019.02.11 20:50:52.666 4:   topic:zigbee2mqtt/0x0017880102784501 qos:0
2019.02.11 20:50:52.666 4:   topic:xiaomi/0x0017880102784501/# qos:0
2019.02.11 20:50:52.667 5: SUBSCRIBE: (138)A(0)(3)(0)(30)zigbee2mqtt/0x00158d0002a23f1d(0)(0)(27)xiaomi/0x00158d0002a23f1d/#(0)
2019.02.11 20:50:52.667 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 SUBSCRIBE
2019.02.11 20:50:52.667 4:   topic:zigbee2mqtt/0x00158d0002a23f1d qos:0
2019.02.11 20:50:52.667 4:   topic:xiaomi/0x00158d0002a23f1d/# qos:0
2019.02.11 20:50:53.661 5: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 => zigbee2mqtt/bridge/state:online
2019.02.11 20:50:53.663 5: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 => zigbee2mqtt/bridge/config:{"log_level":"debug","permit_join":false}
2019.02.11 20:50:54.067 5: PUBLISH: 2%(0)!zigbee2mqtt/bridge/config/devices(0)(6)
2019.02.11 20:50:54.068 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PUBLISH zigbee2mqtt/bridge/config/devices:
2019.02.11 20:50:54.068 5: MQTT2_FHEM_Server: dispatch autocreate\000NetMQTTpm92\000zigbee2mqtt/bridge/config/devices\000
2019.02.11 20:50:54.153 5: PUBLISH: 2!(0)(29)xiaomi/cmnd/bridge/getDevices(0)(7)
2019.02.11 20:50:54.154 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PUBLISH xiaomi/cmnd/bridge/getDevices:
2019.02.11 20:50:54.154 5: MQTT2_FHEM_Server: dispatch autocreate\000NetMQTTpm92\000xiaomi/cmnd/bridge/getDevices\000
2019.02.11 20:50:58.124 2: AttrTemplates: got 53 entries
2019.02.11 20:50:58.750 4: Connection accepted from MQTT2_FHEM_Server_192.168.178.120_20906
2019.02.11 20:50:58.753 5: CONNECT: (16)W(0)(4)MQTT(4)(238)(0)(15)(0)(11)DVES_79CFCA(0)(31)/SmartHome/az/sonoff42/tele/LWT(0)(7)offline(0)(9)DVES_USER(0)(9)DVES_PASS
2019.02.11 20:50:58.758 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA CONNECT V:4 keepAlive:15 LWT:/SmartHome/az/sonoff42/tele/LWT:offline usr:DVES_USER
2019.02.11 20:50:58.771 5: PUBLISH: 1'(0)(31)/SmartHome/az/sonoff42/tele/LWTonline
2019.02.11 20:50:58.771 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PUBLISH /SmartHome/az/sonoff42/tele/LWT:online
2019.02.11 20:50:58.772 5: MQTT2_FHEM_Server: dispatch autocreate\000DVES_79CFCA\000/SmartHome/az/sonoff42/tele/LWT\000online
2019.02.11 20:50:58.817 5: PUBLISH: 0#(0)!/SmartHome/az/sonoff42/cmnd/POWER
2019.02.11 20:50:58.818 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PUBLISH /SmartHome/az/sonoff42/cmnd/POWER:
2019.02.11 20:50:58.818 5: MQTT2_FHEM_Server: dispatch autocreate\000DVES_79CFCA\000/SmartHome/az/sonoff42/cmnd/POWER\000
2019.02.11 20:50:58.823 5: SUBSCRIBE: (130)"(0)(2)(0)(29)/SmartHome/az/sonoff42/cmnd/#(0)
2019.02.11 20:50:58.823 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA SUBSCRIBE
2019.02.11 20:50:58.824 4:   topic:/SmartHome/az/sonoff42/cmnd/# qos:0
2019.02.11 20:50:58.824 5: SUBSCRIBE: (130)!(0)(3)(0)(28)/SmartHome/az/sonoffs/cmnd/#(0)
2019.02.11 20:50:58.824 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA SUBSCRIBE
2019.02.11 20:50:58.824 4:   topic:/SmartHome/az/sonoffs/cmnd/# qos:0
2019.02.11 20:50:58.825 5: SUBSCRIBE: (130)(23)(0)(4)(0)(18)cmnd/DVES_79CFCA/#(0)
2019.02.11 20:50:58.825 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA SUBSCRIBE
2019.02.11 20:50:58.825 4:   topic:cmnd/DVES_79CFCA/# qos:0
2019.02.11 20:51:13.777 5: PINGREQ: (192)(0)
2019.02.11 20:51:13.778 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:51:28.749 5: PUBLISH: 0(185)(1)(0)!/SmartHome/az/sonoff42/tele/STATE{"Time":"2019-02-11T20:51:28","Uptime":"28T03:04:20","Vcc":3.423,"POWER":"ON","Wifi":{"AP":1,"SSId":"Turbonet","RSSI":52,"APMac":"34:81:C4:E1:99:7A"}}
2019.02.11 20:51:28.749 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PUBLISH /SmartHome/az/sonoff42/tele/STATE:{"Time":"2019-02-11T20:51:28","Uptime":"28T03:04:20","Vcc":3.423,"POWER":"ON","Wifi":{"AP":1,"SSId":"Turbonet","RSSI":52,"APMac":"34:81:C4:E1:99:7A"}}
2019.02.11 20:51:28.750 5: MQTT2_FHEM_Server: dispatch autocreate\000DVES_79CFCA\000/SmartHome/az/sonoff42/tele/STATE\000{"Time":"2019-02-11T20:51:28","Uptime":"28T03:04:20","Vcc":3.423,"POWER":"ON","Wifi":{"AP":1,"SSId":"Turbonet","RSSI":52,"APMac":"34:81:C4:E1:99:7A"}}
2019.02.11 20:51:28.799 5: PINGREQ: (192)(0)
2019.02.11 20:51:28.799 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:51:43.786 5: PINGREQ: (192)(0)
2019.02.11 20:51:43.786 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:51:52.372 5: PINGREQ: (192)(0)
2019.02.11 20:51:52.373 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PINGREQ
2019.02.11 20:51:58.786 5: PINGREQ: (192)(0)
2019.02.11 20:51:58.786 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:52:13.787 5: PINGREQ: (192)(0)
2019.02.11 20:52:13.788 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:52:28.788 5: PINGREQ: (192)(0)
2019.02.11 20:52:28.789 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:52:43.791 5: PINGREQ: (192)(0)
2019.02.11 20:52:43.791 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:52:52.377 5: PINGREQ: (192)(0)
2019.02.11 20:52:52.378 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PINGREQ
2019.02.11 20:52:58.790 5: PINGREQ: (192)(0)
2019.02.11 20:52:58.796 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:53:13.794 5: PINGREQ: (192)(0)
2019.02.11 20:53:13.794 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:53:28.792 5: PINGREQ: (192)(0)
2019.02.11 20:53:28.793 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:53:43.794 5: PINGREQ: (192)(0)
2019.02.11 20:53:43.795 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:53:52.382 5: PINGREQ: (192)(0)
2019.02.11 20:53:52.382 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PINGREQ
2019.02.11 20:53:58.795 5: PINGREQ: (192)(0)
2019.02.11 20:53:58.796 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:54:13.798 5: PINGREQ: (192)(0)
2019.02.11 20:54:13.799 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:54:28.797 5: PINGREQ: (192)(0)
2019.02.11 20:54:28.798 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:54:43.802 5: PINGREQ: (192)(0)
2019.02.11 20:54:43.802 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:54:52.386 5: PINGREQ: (192)(0)
2019.02.11 20:54:52.387 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PINGREQ
2019.02.11 20:54:58.800 5: PINGREQ: (192)(0)
2019.02.11 20:54:58.800 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:55:13.802 5: PINGREQ: (192)(0)
2019.02.11 20:55:13.803 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:55:28.804 5: PINGREQ: (192)(0)
2019.02.11 20:55:28.805 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:55:43.803 5: PINGREQ: (192)(0)
2019.02.11 20:55:43.804 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:55:52.391 5: PINGREQ: (192)(0)
2019.02.11 20:55:52.391 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PINGREQ
2019.02.11 20:55:58.813 5: PINGREQ: (192)(0)
2019.02.11 20:55:58.814 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:56:13.807 5: PINGREQ: (192)(0)
2019.02.11 20:56:13.808 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:56:28.752 5: PUBLISH: 0(185)(1)(0)!/SmartHome/az/sonoff42/tele/STATE{"Time":"2019-02-11T20:56:28","Uptime":"28T03:09:20","Vcc":3.423,"POWER":"ON","Wifi":{"AP":1,"SSId":"Turbonet","RSSI":50,"APMac":"34:81:C4:E1:99:7A"}}
2019.02.11 20:56:28.753 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PUBLISH /SmartHome/az/sonoff42/tele/STATE:{"Time":"2019-02-11T20:56:28","Uptime":"28T03:09:20","Vcc":3.423,"POWER":"ON","Wifi":{"AP":1,"SSId":"Turbonet","RSSI":50,"APMac":"34:81:C4:E1:99:7A"}}
2019.02.11 20:56:28.755 5: MQTT2_FHEM_Server: dispatch autocreate\000DVES_79CFCA\000/SmartHome/az/sonoff42/tele/STATE\000{"Time":"2019-02-11T20:56:28","Uptime":"28T03:09:20","Vcc":3.423,"POWER":"ON","Wifi":{"AP":1,"SSId":"Turbonet","RSSI":50,"APMac":"34:81:C4:E1:99:7A"}}
2019.02.11 20:56:28.816 5: PINGREQ: (192)(0)
2019.02.11 20:56:28.816 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:56:43.822 5: PINGREQ: (192)(0)
2019.02.11 20:56:43.823 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:56:52.396 5: PINGREQ: (192)(0)
2019.02.11 20:56:52.397 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PINGREQ
2019.02.11 20:56:58.820 5: PINGREQ: (192)(0)
2019.02.11 20:56:58.821 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:57:13.820 5: PINGREQ: (192)(0)
2019.02.11 20:57:13.821 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:57:28.822 5: PINGREQ: (192)(0)
2019.02.11 20:57:28.823 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:57:43.823 5: PINGREQ: (192)(0)
2019.02.11 20:57:43.824 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:57:52.401 5: PINGREQ: (192)(0)
2019.02.11 20:57:52.401 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PINGREQ
2019.02.11 20:57:58.827 5: PINGREQ: (192)(0)
2019.02.11 20:57:58.827 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:58:13.831 5: PINGREQ: (192)(0)
2019.02.11 20:58:13.831 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:58:28.831 5: PINGREQ: (192)(0)
2019.02.11 20:58:28.831 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:58:43.832 5: PINGREQ: (192)(0)
2019.02.11 20:58:43.833 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:58:44.517 3: FHEMWEB WEB CSRF error: csrf_133672305740767 ne csrf_196506342915847 for client WEB_192.168.178.107_62513 / command set test_hue off. For details see the csrfToken FHEMWEB attribute.
2019.02.11 20:58:44.531 5: MQTT2_FHEM_Server: PUBLISH zigbee2mqtt/0x0017880102784501/set {"state":"OFF"}
2019.02.11 20:58:46.806 5: MQTT2_FHEM_Server: PUBLISH zigbee2mqtt/0x0017880102784501/set {"state":"ON"}
2019.02.11 20:58:52.402 5: PINGREQ: (192)(0)
2019.02.11 20:58:52.402 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PINGREQ
2019.02.11 20:58:58.829 5: PINGREQ: (192)(0)
2019.02.11 20:58:58.830 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:59:13.834 5: PINGREQ: (192)(0)
2019.02.11 20:59:13.835 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:59:28.833 5: PINGREQ: (192)(0)
2019.02.11 20:59:28.833 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:59:43.835 5: PINGREQ: (192)(0)
2019.02.11 20:59:43.836 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 20:59:52.407 5: PINGREQ: (192)(0)
2019.02.11 20:59:52.408 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PINGREQ
2019.02.11 20:59:58.835 5: PINGREQ: (192)(0)
2019.02.11 20:59:58.836 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 21:00:13.836 5: PINGREQ: (192)(0)
2019.02.11 21:00:13.837 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 21:00:28.838 5: PINGREQ: (192)(0)
2019.02.11 21:00:28.838 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 21:00:43.840 5: PINGREQ: (192)(0)
2019.02.11 21:00:43.841 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 21:00:52.412 5: PINGREQ: (192)(0)
2019.02.11 21:00:52.412 4: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 PINGREQ
2019.02.11 21:00:58.840 5: PINGREQ: (192)(0)
2019.02.11 21:00:58.840 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 21:01:13.845 5: PINGREQ: (192)(0)
2019.02.11 21:01:13.845 4: MQTT2_FHEM_Server_192.168.178.120_20906 DVES_79CFCA PINGREQ
2019.02.11 21:01:23.041 4: Connection accepted from MQTT2_FHEM_Server_172.17.0.1_45202
2019.02.11 21:01:23.046 5: CONNECT: (16)8(0)(4)MQTT(4)&(0)<(0)(9)zigbee_pi(0)(24)zigbee2mqtt/bridge/state(0)(7)offline
2019.02.11 21:01:23.046 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi CONNECT V:4 keepAlive:60 LWT:zigbee2mqtt/bridge/state:offline
2019.02.11 21:01:23.156 5: PUBLISH: 1 (0)(24)zigbee2mqtt/bridge/stateonline
2019.02.11 21:01:23.156 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi PUBLISH zigbee2mqtt/bridge/state:online
2019.02.11 21:01:23.157 5: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 => zigbee2mqtt/bridge/state:online
2019.02.11 21:01:23.158 5: MQTT2_FHEM_Server: dispatch autocreate\000zigbee_pi\000zigbee2mqtt/bridge/state\000online
2019.02.11 21:01:23.164 5: PUBLISH: 0(131)(1)(0)(30)zigbee2mqtt/0x00158d000273008a{"temperature":21.74,"linkquality":13,"humidity":55.24,"pressure":993,"battery":100,"voltage":3005}
2019.02.11 21:01:23.164 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi PUBLISH zigbee2mqtt/0x00158d000273008a:{"temperature":21.74,"linkquality":13,"humidity":55.24,"pressure":993,"battery":100,"voltage":3005}
2019.02.11 21:01:23.165 5: MQTT2_FHEM_Server: dispatch autocreate\000zigbee_pi\000zigbee2mqtt/0x00158d000273008a\000{"temperature":21.74,"linkquality":13,"humidity":55.24,"pressure":993,"battery":100,"voltage":3005}
2019.02.11 21:01:23.175 5: PUBLISH: 0(181)(1)(0)(30)zigbee2mqtt/0x00158d0002adc401{"angle_x":3,"angle_y":2,"angle_z":86,"angle_x_absolute":87,"angle_y_absolute":88,"linkquality":63,"unknown_data":131072,"battery":97,"voltage":2995}
2019.02.11 21:01:23.176 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi PUBLISH zigbee2mqtt/0x00158d0002adc401:{"angle_x":3,"angle_y":2,"angle_z":86,"angle_x_absolute":87,"angle_y_absolute":88,"linkquality":63,"unknown_data":131072,"battery":97,"voltage":2995}
2019.02.11 21:01:23.177 5: MQTT2_FHEM_Server: dispatch autocreate\000zigbee_pi\000zigbee2mqtt/0x00158d0002adc401\000{"angle_x":3,"angle_y":2,"angle_z":86,"angle_x_absolute":87,"angle_y_absolute":88,"linkquality":63,"unknown_data":131072,"battery":97,"voltage":2995}
2019.02.11 21:01:23.187 5: PUBLISH: 0(154)(1)(0)(30)zigbee2mqtt/0x0017880102784501{"state":"ON","color_temp":206,"color":{"x":0.35,"y":0.332,"saturation":74.8,"hue":261.5},"color_mode":1,"brightness":254}
2019.02.11 21:01:23.187 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi PUBLISH zigbee2mqtt/0x0017880102784501:{"state":"ON","color_temp":206,"color":{"x":0.35,"y":0.332,"saturation":74.8,"hue":261.5},"color_mode":1,"brightness":254}
2019.02.11 21:01:23.188 5: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 => zigbee2mqtt/0x0017880102784501:{"state":"ON","color_temp":206,"color":{"x":0.35,"y":0.332,"saturation":74.8,"hue":261.5},"color_mode":1,"brightness":254}
2019.02.11 21:01:23.188 5: MQTT2_FHEM_Server: dispatch autocreate\000zigbee_pi\000zigbee2mqtt/0x0017880102784501\000{"state":"ON","color_temp":206,"color":{"x":0.35,"y":0.332,"saturation":74.8,"hue":261.5},"color_mode":1,"brightness":254}
2019.02.11 21:01:23.189 4: MQTT2_DEVICE_Parse: test_hue zigbee2mqtt/0x0017880102784501 => { json2nameValue($EVENT) }
2019.02.11 21:01:23.198 5: PUBLISH: 0(129)(1)(0)(30)zigbee2mqtt/0x00158d000238f9b7{"temperature":18.84,"linkquality":63,"humidity":58.4,"pressure":991,"battery":68,"voltage":2945}
2019.02.11 21:01:23.199 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi PUBLISH zigbee2mqtt/0x00158d000238f9b7:{"temperature":18.84,"linkquality":63,"humidity":58.4,"pressure":991,"battery":68,"voltage":2945}
2019.02.11 21:01:23.200 5: MQTT2_FHEM_Server: dispatch autocreate\000zigbee_pi\000zigbee2mqtt/0x00158d000238f9b7\000{"temperature":18.84,"linkquality":63,"humidity":58.4,"pressure":991,"battery":68,"voltage":2945}
2019.02.11 21:01:23.209 5: PUBLISH: 0(130)(1)(0)(30)zigbee2mqtt/0x00158d000238fb9c{"temperature":21.03,"linkquality":36,"humidity":55.91,"pressure":991,"battery":80,"voltage":2965}
2019.02.11 21:01:23.209 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi PUBLISH zigbee2mqtt/0x00158d000238fb9c:{"temperature":21.03,"linkquality":36,"humidity":55.91,"pressure":991,"battery":80,"voltage":2965}
2019.02.11 21:01:23.210 5: MQTT2_FHEM_Server: dispatch autocreate\000zigbee_pi\000zigbee2mqtt/0x00158d000238fb9c\000{"temperature":21.03,"linkquality":36,"humidity":55.91,"pressure":991,"battery":80,"voltage":2965}
2019.02.11 21:01:23.220 5: PUBLISH: 0(130)(1)(0)(30)zigbee2mqtt/0x00158d00023a7fb7{"temperature":20.83,"linkquality":94,"humidity":56.07,"pressure":991,"battery":86,"voltage":2975}
2019.02.11 21:01:23.220 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi PUBLISH zigbee2mqtt/0x00158d00023a7fb7:{"temperature":20.83,"linkquality":94,"humidity":56.07,"pressure":991,"battery":86,"voltage":2975}
2019.02.11 21:01:23.221 5: MQTT2_FHEM_Server: dispatch autocreate\000zigbee_pi\000zigbee2mqtt/0x00158d00023a7fb7\000{"temperature":20.83,"linkquality":94,"humidity":56.07,"pressure":991,"battery":86,"voltage":2975}
2019.02.11 21:01:23.231 5: PUBLISH: 0(184)(1)(0)(30)zigbee2mqtt/0x00158d0002a23f1d{"angle_x":3,"angle_y":-1,"angle_z":-87,"angle_x_absolute":87,"angle_y_absolute":91,"linkquality":47,"unknown_data":393216,"battery":100,"voltage":3015}
2019.02.11 21:01:23.231 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi PUBLISH zigbee2mqtt/0x00158d0002a23f1d:{"angle_x":3,"angle_y":-1,"angle_z":-87,"angle_x_absolute":87,"angle_y_absolute":91,"linkquality":47,"unknown_data":393216,"battery":100,"voltage":3015}
2019.02.11 21:01:23.232 5: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 => zigbee2mqtt/0x00158d0002a23f1d:{"angle_x":3,"angle_y":-1,"angle_z":-87,"angle_x_absolute":87,"angle_y_absolute":91,"linkquality":47,"unknown_data":393216,"battery":100,"voltage":3015}
2019.02.11 21:01:23.232 5: MQTT2_FHEM_Server: dispatch autocreate\000zigbee_pi\000zigbee2mqtt/0x00158d0002a23f1d\000{"angle_x":3,"angle_y":-1,"angle_z":-87,"angle_x_absolute":87,"angle_y_absolute":91,"linkquality":47,"unknown_data":393216,"battery":100,"voltage":3015}
2019.02.11 21:01:23.242 5: PUBLISH: 0o(0)(30)zigbee2mqtt/0x00158d000257d9f9{"illuminance":0,"linkquality":0,"occupancy":false,"battery":91,"voltage":2985}
2019.02.11 21:01:23.242 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi PUBLISH zigbee2mqtt/0x00158d000257d9f9:{"illuminance":0,"linkquality":0,"occupancy":false,"battery":91,"voltage":2985}
2019.02.11 21:01:23.243 5: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 => zigbee2mqtt/0x00158d000257d9f9:{"illuminance":0,"linkquality":0,"occupancy":false,"battery":91,"voltage":2985}
2019.02.11 21:01:23.244 5: MQTT2_FHEM_Server: dispatch autocreate\000zigbee_pi\000zigbee2mqtt/0x00158d000257d9f9\000{"illuminance":0,"linkquality":0,"occupancy":false,"battery":91,"voltage":2985}
2019.02.11 21:01:23.253 5: PUBLISH: 0(129)(1)(0)(30)zigbee2mqtt/0x00158d0002327a09{"temperature":4.87,"linkquality":44,"humidity":86.66,"pressure":991,"battery":74,"voltage":2955}
2019.02.11 21:01:23.254 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi PUBLISH zigbee2mqtt/0x00158d0002327a09:{"temperature":4.87,"linkquality":44,"humidity":86.66,"pressure":991,"battery":74,"voltage":2955}
2019.02.11 21:01:23.254 5: MQTT2_FHEM_Server_172.17.0.1_45018 NetMQTTpm92 => zigbee2mqtt/0x00158d0002327a09:{"temperature":4.87,"linkquality":44,"humidity":86.66,"pressure":991,"battery":74,"voltage":2955}
2019.02.11 21:01:23.255 5: MQTT2_FHEM_Server: dispatch autocreate\000zigbee_pi\000zigbee2mqtt/0x00158d0002327a09\000{"temperature":4.87,"linkquality":44,"humidity":86.66,"pressure":991,"battery":74,"voltage":2955}
2019.02.11 21:01:23.264 5: PUBLISH: 0(129)(1)(0)(30)zigbee2mqtt/0x00158d000232279a{"temperature":18.03,"linkquality":15,"humidity":59.9,"pressure":993,"battery":74,"voltage":2955}
2019.02.11 21:01:23.265 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi PUBLISH zigbee2mqtt/0x00158d000232279a:{"temperature":18.03,"linkquality":15,"humidity":59.9,"pressure":993,"battery":74,"voltage":2955}
2019.02.11 21:01:23.266 5: MQTT2_FHEM_Server: dispatch autocreate\000zigbee_pi\000zigbee2mqtt/0x00158d000232279a\000{"temperature":18.03,"linkquality":15,"humidity":59.9,"pressure":993,"battery":74,"voltage":2955}
2019.02.11 21:01:23.274 5: SUBSCRIBE: (130)(22)M(136)(0)(17)zigbee2mqtt/+/set(0)
2019.02.11 21:01:23.274 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.274 4:   topic:zigbee2mqtt/+/set qos:0
2019.02.11 21:01:23.275 5: SUBSCRIBE: (130)(22)M(137)(0)(17)zigbee2mqtt/+/get(0)
2019.02.11 21:01:23.275 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.275 4:   topic:zigbee2mqtt/+/get qos:0
2019.02.11 21:01:23.275 5: SUBSCRIBE: (130)(24)M(138)(0)(19)zigbee2mqtt/+/+/set(0)
2019.02.11 21:01:23.275 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.276 4:   topic:zigbee2mqtt/+/+/set qos:0
2019.02.11 21:01:23.276 5: SUBSCRIBE: (130)(24)M(139)(0)(19)zigbee2mqtt/+/+/get(0)
2019.02.11 21:01:23.276 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.276 4:   topic:zigbee2mqtt/+/+/get qos:0
2019.02.11 21:01:23.276 5: SUBSCRIBE: (130)(26)M(140)(0)(21)zigbee2mqtt/+/+/+/set(0)
2019.02.11 21:01:23.276 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.277 4:   topic:zigbee2mqtt/+/+/+/set qos:0
2019.02.11 21:01:23.277 5: SUBSCRIBE: (130)(26)M(141)(0)(21)zigbee2mqtt/+/+/+/get(0)
2019.02.11 21:01:23.277 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.277 4:   topic:zigbee2mqtt/+/+/+/get qos:0
2019.02.11 21:01:23.277 5: SUBSCRIBE: (130)(28)M(142)(0)(23)zigbee2mqtt/+/+/+/+/set(0)
2019.02.11 21:01:23.277 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.278 4:   topic:zigbee2mqtt/+/+/+/+/set qos:0
2019.02.11 21:01:23.278 5: SUBSCRIBE: (130)(28)M(143)(0)(23)zigbee2mqtt/+/+/+/+/get(0)
2019.02.11 21:01:23.278 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.278 4:   topic:zigbee2mqtt/+/+/+/+/get qos:0
2019.02.11 21:01:23.278 5: SUBSCRIBE: (130)(30)M(144)(0)(25)zigbee2mqtt/+/+/+/+/+/set(0)
2019.02.11 21:01:23.279 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.279 4:   topic:zigbee2mqtt/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.279 5: SUBSCRIBE: (130)(30)M(145)(0)(25)zigbee2mqtt/+/+/+/+/+/get(0)
2019.02.11 21:01:23.279 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.279 4:   topic:zigbee2mqtt/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.279 5: SUBSCRIBE: (130) M(146)(0)(27)zigbee2mqtt/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.280 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.280 4:   topic:zigbee2mqtt/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.280 5: SUBSCRIBE: (130) M(147)(0)(27)zigbee2mqtt/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.280 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.280 4:   topic:zigbee2mqtt/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.281 5: SUBSCRIBE: (130)"M(148)(0)(29)zigbee2mqtt/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.281 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.281 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.281 5: SUBSCRIBE: (130)"M(149)(0)(29)zigbee2mqtt/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.281 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.281 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.282 5: SUBSCRIBE: (130)$M(150)(0)(31)zigbee2mqtt/+/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.282 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.282 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.282 5: SUBSCRIBE: (130)$M(151)(0)(31)zigbee2mqtt/+/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.282 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.282 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.283 5: SUBSCRIBE: (130)&M(152)(0)!zigbee2mqtt/+/+/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.283 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.283 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.283 5: SUBSCRIBE: (130)&M(153)(0)!zigbee2mqtt/+/+/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.283 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.284 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.285 5: SUBSCRIBE: (130)(M(154)(0)#zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.285 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.285 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.286 5: SUBSCRIBE: (130)(M(155)(0)#zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.286 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.286 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.286 5: SUBSCRIBE: (130)*M(156)(0)%zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.286 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.286 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.287 5: SUBSCRIBE: (130)*M(157)(0)%zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.287 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.287 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.287 5: SUBSCRIBE: (130),M(158)(0)'zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.287 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.287 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.288 5: SUBSCRIBE: (130),M(159)(0)'zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.288 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.288 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.288 5: SUBSCRIBE: (130).M(160)(0))zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.288 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.288 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.289 5: SUBSCRIBE: (130).M(161)(0))zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.289 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.289 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.289 5: SUBSCRIBE: (130)0M(162)(0)+zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.289 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.289 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.290 5: SUBSCRIBE: (130)0M(163)(0)+zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.290 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.290 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.290 5: SUBSCRIBE: (130)2M(164)(0)-zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.290 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.290 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.291 5: SUBSCRIBE: (130)2M(165)(0)-zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.291 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.291 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.291 5: SUBSCRIBE: (130)4M(166)(0)/zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.291 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.291 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.292 5: SUBSCRIBE: (130)4M(167)(0)/zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.292 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.292 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.292 5: SUBSCRIBE: (130)6M(168)(0)1zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.292 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.292 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.292 5: SUBSCRIBE: (130)6M(169)(0)1zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.293 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.293 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.293 5: SUBSCRIBE: (130)8M(170)(0)3zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.293 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.293 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.293 5: SUBSCRIBE: (130)8M(171)(0)3zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.294 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.294 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get qos:0
2019.02.11 21:01:23.294 5: SUBSCRIBE: (130):M(172)(0)5zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set(0)
2019.02.11 21:01:23.294 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.294 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set qos:0
2019.02.11 21:01:23.294 5: SUBSCRIBE: (130):M(173)(0)5zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get(0)
2019.02.11 21:01:23.295 4: MQTT2_FHEM_Server_172.17.0.1_45202 zigbee_pi SUBSCRIBE
2019.02.11 21:01:23.295 4:   topic:zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get qos:0
decode_string: insufficient data at /usr/local/share/perl/5.24.1/Net/MQTT/Message/Publish.pm line 36.
2019.02.11 21:01:35.833 1: Including fhem.cfg

Den Dauerloop kann ich nur unterbinde indem ich das Zigbee2MQTT Gateway herunter fahre.

Da die Updates bisher meistens früher oder später funktioniert haben, habe ich vorher mal kein Backup gemacht

( um auf die vorherige Version zurück zu gehen.
Irgendwelche Ideen woran es liegen könnte oder wo ich noch "nachsehen" kann.

Grüße,
Andreas.

rudolfkoenig · 12 Februar 2019, 08:01:42

Mich verwirrt die Zeile

Zitatdecode_string: insufficient data at /usr/local/share/perl/5.24.1/Net/MQTT/Message/Publish.pm line 36.

da es darauf hinweis, dass neben MQTT2 auch das alte MQTT Modul aktiv ist.
Kannst Du das bitte versuchen zu vermeiden?

Was genau ist das Problem?
Diese Meldung, oder dass die SUBSCRIBE Orgie von zigbee2mqtt nicht aufhoert?
Wenn Letzteres, dann sehe ich im Moment das Problem eher bei zigbee2mqtt.

essera · 12 Februar 2019, 08:46:26

Moin.

Zitat
da es darauf hinweis, dass neben MQTT2 auch das alte MQTT Modul aktiv ist.
Kannst Du das bitte versuchen zu vermeiden?

Wie kann ich das vermeiden ? Kommt das über die Devices vom Typ "MQTT" die ich für das Zigbee2MQTT Gateway definiert habe ?
Dann gehe ich davon aus, dass ich die neu definieren muss mit einem IODev für MQTT2 - werde ich mal versuchen.

Ist halt nur verwunderlich, dass der Fehler (Dauer Neustart vom Fhem) vorher nicht auftrat bis ich das Update am Sonntag gemacht habe....
Aber so ist das nun mal in einem dynamisch sich entwickelnden System

rudolfkoenig · 12 Februar 2019, 09:58:58

ZitatKommt das über die Devices vom Typ "MQTT" die ich für das Zigbee2MQTT Gateway definiert habe ?

Zigbee2mqtt ueber MQTT _und_ MQTT2_SERVER anzubinden klingt abenteuerlich, falls man keine Probleme sucht, wuerde ich sowas vermeiden.

essera · 12 Februar 2019, 13:19:16

Zitat
Zigbee2mqtt ueber MQTT _und_ MQTT2_SERVER anzubinden klingt abenteuerlich, falls man keine Probleme sucht, wuerde ich sowas vermeiden.

OK - Den Hinweis habe ich verstanden. Wo liegt denn mein Denkfehler bzw. was muss ich anders machen ?
MQTT2 Server läuft auf FHEM.

Ich verstehe es so ,dass wenn ich den internen MQTT Server verwende bei den erstellten Devices auch nur IODev´s vom Typ MQTT2 verwenden darf ??
D.h. ich muss die anderen Devices Löschen und unter MQTT2 neu anlegen !?

essera · 12 Februar 2019, 19:08:28

Zitat
Ich verstehe es so ,dass wenn ich den internen MQTT Server verwende bei den erstellten Devices auch nur IODev´s vom Typ MQTT2 verwenden darf ??
D.h. ich muss die anderen Devices Löschen und unter MQTT2 neu anlegen !?

So ... habe alle Device mit MQTT als IODev gelöscht.
Ein neues Device als MQTT2 und IODev MQTT2_Server angelegt und Zigbee2mqtt Gateway neu gestartet.
und ... lüppt - Kein Crash von FHEM mehr und Device lassen sich wieder schalten.

War ein Überbleibsel aus der Beschreibung der Anlage von Kommunikationsdevices im Thread des Zigbee2mqtt Entwicklers Neumann. ( https://forum.fhem.de/index.php/topic,84790.0.html ) Die Beschreibung kennt halt die Möglichkeit des internen FHEM - MQTT Server noch nicht.

Danke Rudi fürs "... auf die Sprünge" bringen.

rudolfkoenig · 12 Februar 2019, 19:48:34

Den MQTT2_SERVER gibt es erst seit August 2018, die meisten Wiki/Blog/etc Beitraege kennen es nicht. Es soll die Anbindung von MQTT Geraeten an FHEM vereinfachen: Es benoetigt keine Installation von weiteren Paketen, es bietet ein autocreate, mit automatisch angelegten Readings, und die restlichen Einstellungen (wie Befehle/setList) kann man meist ueber die attrTemplates setzen.

MQTT ist (wie MQTT2_CLIENT) ein MQTT Client. Diesen kann man vmtl. auch ueber MQTT2_SERVER verwenden, aber das ist ungefaehr so, wie wenn man sich selbst über Telefon anruft.