NEWS
Zigbee Adapter startet nicht, Cannot read properties
Error/Bug
30
Beiträge
3
Kommentatoren
2.1k
Aufrufe
2
Watching
-
Ja, phoscon ist im Moment down.
Hat aber mit dem zigbee-Adapter nichts zu tun, würde ich sagen. -
@thomas-braun
Hatte gestern noch funktioniert meine ich.
Bullseye gehe ich jetzt an.@simono sagte in Zigbee Adapter startet nicht, Cannot read properties:
Hatte gestern noch funktioniert meine ich.
Ja, ist heute Vormittag aus dem Gleis gesprungen.
-
@simono sagte in Zigbee Adapter startet nicht, Cannot read properties:
Hatte gestern noch funktioniert meine ich.
Ja, ist heute Vormittag aus dem Gleis gesprungen.
So, Bullseye ist drauf. Das Problem mit dem Zigbee-Adapter bleibt leider.
======================= SUMMARY ======================= v.2023-04-02 Operatingsystem: Raspbian GNU/Linux 11 (bullseye) Kernel: 6.1.21-v8+ Installation: Native Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v18.15.0 /usr/bin/node v18.15.0 /usr/bin/npm 9.5.0 /usr/bin/npx 9.5.0 Recommended versions are nodejs 18.x.y and npm 9.x.y MEMORY: total used free shared buff/cache available Mem: 3.8G 1.0G 2.1G 0.0K 718M 2.7G Swap: 99M 0B 99M Total: 3.9G 1.0G 2.2G Active iob-Instances: 25 Active repo(s): stable ioBroker Core: js-controller 4.0.24 admin 6.3.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: redis Status admin and web instance: + system.adapter.admin.0 : admin : pi4 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : pi4 - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 14105 States: 10574 Size of iob-Database: 14M /opt/iobroker/iobroker-data/objects.jsonl 13M /opt/iobroker/iobroker-data/objects.json.migrated 13M /opt/iobroker/iobroker-data/objects.json.bak.migrated 1.8M /opt/iobroker/iobroker-data/2021-10-30_23-12_objects.json.gz 3.5M /opt/iobroker/iobroker-data/states.json 540K /opt/iobroker/iobroker-data/2020-01-15_14-00_states.json.gz =================== END OF SUMMARY ==================== -
So, Bullseye ist drauf. Das Problem mit dem Zigbee-Adapter bleibt leider.
======================= SUMMARY ======================= v.2023-04-02 Operatingsystem: Raspbian GNU/Linux 11 (bullseye) Kernel: 6.1.21-v8+ Installation: Native Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v18.15.0 /usr/bin/node v18.15.0 /usr/bin/npm 9.5.0 /usr/bin/npx 9.5.0 Recommended versions are nodejs 18.x.y and npm 9.x.y MEMORY: total used free shared buff/cache available Mem: 3.8G 1.0G 2.1G 0.0K 718M 2.7G Swap: 99M 0B 99M Total: 3.9G 1.0G 2.2G Active iob-Instances: 25 Active repo(s): stable ioBroker Core: js-controller 4.0.24 admin 6.3.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: redis Status admin and web instance: + system.adapter.admin.0 : admin : pi4 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : pi4 - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 14105 States: 10574 Size of iob-Database: 14M /opt/iobroker/iobroker-data/objects.jsonl 13M /opt/iobroker/iobroker-data/objects.json.migrated 13M /opt/iobroker/iobroker-data/objects.json.bak.migrated 1.8M /opt/iobroker/iobroker-data/2021-10-30_23-12_objects.json.gz 3.5M /opt/iobroker/iobroker-data/states.json 540K /opt/iobroker/iobroker-data/2020-01-15_14-00_states.json.gz =================== END OF SUMMARY ====================So, und es geht weiter mit den Problemen, durch Bullseye habe ich mir jetzt meine PiVCCU3 zerschossen. Liegt evtl daran, dass das ein 32bit Image war und Bullseye 64bit!?
Gibt es dazu einen Workaround? Oder bleibt nur komplett neu zu installieren? -
So, und es geht weiter mit den Problemen, durch Bullseye habe ich mir jetzt meine PiVCCU3 zerschossen. Liegt evtl daran, dass das ein 32bit Image war und Bullseye 64bit!?
Gibt es dazu einen Workaround? Oder bleibt nur komplett neu zu installieren?@simono sagte in Zigbee Adapter startet nicht, Cannot read properties:
Bullseye habe ich mir jetzt meine PiVCCU3 zerschossen. Liegt evtl daran, dass das ein 32bit Image war und Bullseye 64bit!?
Die Prozessor-Architekturen müssen zueinander passen. Soweit ich das weiß wird pivccu3 gegen den aktuellen Kernel gebaut.
-
@simono sagte in Zigbee Adapter startet nicht, Cannot read properties:
Bullseye habe ich mir jetzt meine PiVCCU3 zerschossen. Liegt evtl daran, dass das ein 32bit Image war und Bullseye 64bit!?
Die Prozessor-Architekturen müssen zueinander passen. Soweit ich das weiß wird pivccu3 gegen den aktuellen Kernel gebaut.
-
@thomas-braun
Entschuldigung, bin wieder zu ungenau.
Habe das Homematic IP Funkmodul für Raspberry Pi HM-MOD-RPI-PCB. Und das All-in-One Image für Raspberry Pi4 – piVCCU3. Lief mit Buster bisher problemlos.@simono sagte in Zigbee Adapter startet nicht, Cannot read properties:
Lief mit Buster bisher problemlos.
Läuft auch mit Bullseye problemlos.
-
@simono sagte in Zigbee Adapter startet nicht, Cannot read properties:
Lief mit Buster bisher problemlos.
Läuft auch mit Bullseye problemlos.
Wie gesagt nach dem Update leider nichtmehr.
pi@pi4:~ $ systemctl start pivccu.service ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Legitimierung ist zum Starten von »pivccu.service« notwendig. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === Job for pivccu.service failed because the service did not take the steps required by its unit configuration. See "systemctl status pivccu.service" and "journalctl -xe" for details. pi@pi4:~ $ systemctl status pivccu.service ● pivccu.service - piVCCU Loaded: loaded (/lib/systemd/system/pivccu.service; enabled; vendor preset: enabled) Active: failed (Result: protocol) since Sat 2023-04-08 13:07:07 CEST; 8s ago Process: 8422 ExecStart=/var/lib/piVCCU3/start_container.sh (code=exited, status=0/SUCCESS) CPU: 32ms Apr 08 13:07:07 pi4 systemd[1]: Starting piVCCU... Apr 08 13:07:07 pi4 start_container.sh[8425]: modprobe: FATAL: Module eq3_char_loop not found in directory /lib/modules/6.1.21-v8+ Apr 08 13:07:07 pi4 systemd[1]: pivccu.service: Can't open PID file /run/pivccu3.pid (yet?) after start: Operation not permitted Apr 08 13:07:07 pi4 systemd[1]: pivccu.service: Failed with result 'protocol'. Apr 08 13:07:07 pi4 systemd[1]: Failed to start piVCCU. pi@pi4:~ $ -
Wie gesagt nach dem Update leider nichtmehr.
pi@pi4:~ $ systemctl start pivccu.service ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Legitimierung ist zum Starten von »pivccu.service« notwendig. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === Job for pivccu.service failed because the service did not take the steps required by its unit configuration. See "systemctl status pivccu.service" and "journalctl -xe" for details. pi@pi4:~ $ systemctl status pivccu.service ● pivccu.service - piVCCU Loaded: loaded (/lib/systemd/system/pivccu.service; enabled; vendor preset: enabled) Active: failed (Result: protocol) since Sat 2023-04-08 13:07:07 CEST; 8s ago Process: 8422 ExecStart=/var/lib/piVCCU3/start_container.sh (code=exited, status=0/SUCCESS) CPU: 32ms Apr 08 13:07:07 pi4 systemd[1]: Starting piVCCU... Apr 08 13:07:07 pi4 start_container.sh[8425]: modprobe: FATAL: Module eq3_char_loop not found in directory /lib/modules/6.1.21-v8+ Apr 08 13:07:07 pi4 systemd[1]: pivccu.service: Can't open PID file /run/pivccu3.pid (yet?) after start: Operation not permitted Apr 08 13:07:07 pi4 systemd[1]: pivccu.service: Failed with result 'protocol'. Apr 08 13:07:07 pi4 systemd[1]: Failed to start piVCCU. pi@pi4:~ $@simono sagte in Zigbee Adapter startet nicht, Cannot read properties:
nach dem Update
Und wie hast du das gemacht?
Pivccu muss ggf. neugebaut werden, wenn da kein passendes Kernelmodul bereit gestellt wird.
Ich kenne piVCCU aber nicht gut genug um zu sagen wie das gemacht wird. -
@simono sagte in Zigbee Adapter startet nicht, Cannot read properties:
nach dem Update
Und wie hast du das gemacht?
Pivccu muss ggf. neugebaut werden, wenn da kein passendes Kernelmodul bereit gestellt wird.
Ich kenne piVCCU aber nicht gut genug um zu sagen wie das gemacht wird.@thomas-braun
nach der Anleitung:
https://linuxnews.de/2021/11/16/raspberry-pi-os-auf-bullseye-aktualisieren/pi@pi4:~ $ sudo pivccu-info piVCCU version: 3.67.10-78 Kernel modules: Not available Raw UART dev: Not available Rasp.Pi UART: Assigned to GPIO pins HMRF Hardware: unknown HMIP Hardware: unknown State: STOPPED pi@pi4:~ $ -
@thomas-braun
nach der Anleitung:
https://linuxnews.de/2021/11/16/raspberry-pi-os-auf-bullseye-aktualisieren/pi@pi4:~ $ sudo pivccu-info piVCCU version: 3.67.10-78 Kernel modules: Not available Raw UART dev: Not available Rasp.Pi UART: Assigned to GPIO pins HMRF Hardware: unknown HMIP Hardware: unknown State: STOPPED pi@pi4:~ $ -
@thomas-braun
nach der Anleitung:
https://linuxnews.de/2021/11/16/raspberry-pi-os-auf-bullseye-aktualisieren/pi@pi4:~ $ sudo pivccu-info piVCCU version: 3.67.10-78 Kernel modules: Not available Raw UART dev: Not available Rasp.Pi UART: Assigned to GPIO pins HMRF Hardware: unknown HMIP Hardware: unknown State: STOPPED pi@pi4:~ $Die Anleitung ist Quatsch.
Nie rpi-update für sowas verwenden. -
Die Anleitung ist Quatsch.
Nie rpi-update für sowas verwenden. -
@thomas-braun
Ok, habe nichts anderes gefunden für ein Update. Steht überallsudo rpi-update@simono
Dann steht es überall falsch.
Ich hab das auch mal dokumentiert, aber ohne den Quark mit rpi-update. Schau durch meine Themen durch. -
@simono
Dann steht es überall falsch.
Ich hab das auch mal dokumentiert, aber ohne den Quark mit rpi-update. Schau durch meine Themen durch.@thomas-braun
Meine Güte, habe deinen "kleinen Werkzeugkasten" gefühlt schon 1000x gebraucht (Danke dafür), aber das mit dem Upgrade habe ich leider übersehen. Nur bei Google gesucht und nicht über dich.
Kann ich das ganze nochmal irgendwie zurück rollen oder sollte ich deiner Meinung nach ein komplett neues Image aufspielen? -
@thomas-braun
Meine Güte, habe deinen "kleinen Werkzeugkasten" gefühlt schon 1000x gebraucht (Danke dafür), aber das mit dem Upgrade habe ich leider übersehen. Nur bei Google gesucht und nicht über dich.
Kann ich das ganze nochmal irgendwie zurück rollen oder sollte ich deiner Meinung nach ein komplett neues Image aufspielen?@simono sagte in Zigbee Adapter startet nicht, Cannot read properties:
aber das mit dem Upgrade habe ich leider übersehen
Ich glaube das steht da auch gar nicht drin. Es gibt jedenfalls ein separates Thema dafür.
-
@thomas-braun
Meine Güte, habe deinen "kleinen Werkzeugkasten" gefühlt schon 1000x gebraucht (Danke dafür), aber das mit dem Upgrade habe ich leider übersehen. Nur bei Google gesucht und nicht über dich.
Kann ich das ganze nochmal irgendwie zurück rollen oder sollte ich deiner Meinung nach ein komplett neues Image aufspielen?@simono sagte in Zigbee Adapter startet nicht, Cannot read properties:
Kann ich das ganze nochmal irgendwie zurück rollen oder sollte ich deiner Meinung nach ein komplett neues Image aufspielen?
Ich glaube, ich würde das komplett neuaufsetzen. Was genau rpi-update da macht hab ich mir noch nie angesehen, es knallt aber am Paketmanager vorbei da Kernel und Firmwares auf das System. Beißt sich dann mit regulären Upgrade via apt full-upgrade. Wie gesehen...
-
@simono sagte in Zigbee Adapter startet nicht, Cannot read properties:
aber das mit dem Upgrade habe ich leider übersehen
Ich glaube das steht da auch gar nicht drin. Es gibt jedenfalls ein separates Thema dafür.
@thomas-braun
Steht nicht im Werkzeugkasten, aber habe es ziemlich direkt unter deinem Themen gefunden. Leider steht du bei der Googlesuche nicht weit oben. -
@simono sagte in Zigbee Adapter startet nicht, Cannot read properties:
Kann ich das ganze nochmal irgendwie zurück rollen oder sollte ich deiner Meinung nach ein komplett neues Image aufspielen?
Ich glaube, ich würde das komplett neuaufsetzen. Was genau rpi-update da macht hab ich mir noch nie angesehen, es knallt aber am Paketmanager vorbei da Kernel und Firmwares auf das System. Beißt sich dann mit regulären Upgrade via apt full-upgrade. Wie gesehen...
@thomas-braun
Dann werde ich das so machen, melde mich dann nochmal wie das ganze mit zigbee ausgegangen ist. Dauert aber noch ein paar Tage. Danke für deine Hilfe. -
Ich habe es jetzt geschafft mir alles neu zu installieren und auch der Zigbee-Adapter lief direkt. Nur mit Shelly 6.3.1 gibt es Probleme.
Falls es jemanden interessieren sollte oder jemand Tipps hat wie man es besser machen könnte, hier eine kurze Zusammenfassung was ich gemacht habe (lief nicht alles problemlos):- Neustes Raspberry Lite installieren.
- Homatic installieren: https://github.com/alexreinert/piVCCU.
- Iobroker Backup mit Backitup local einspielen (https://www.youtube.com/watch?v=71G87dqFQXA).
- Falls Iobroker nicht mehr starten sollte:
sudo apt-get install redis-server- Auf CCU Firewall-Einstellungen ändern:
- Backup auf Homematic (oder Homematic -> Einstellungen -> Systemsteuerung -> Sicherheit).
- Vis Adapter kann nicht zurückgespielt werden:
o Cd /opt/iobroker
o npm i iobroker.vis@1.4.6
o iobroker update
o iobroker upgrade - Zigbee Einstellungen:
o /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2130751-if00
o Typ: Deconz/Conbee
o PAN ID ändern<> - Shelly Adapter 6.3.1 nach ca 2min nicht mehr erreichbar. Downgrade auf 6.3.0 -> läuft.
2023-04-17 20:49:16.392 - error: shelly.0 (1888371) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12) 2023-04-17 20:49:16.392 - error: shelly.0 (1888371) DB closed 2023-04-17 20:49:16.514 - info: host.ioboker iobroker upload [12] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/en/translations.json i18n/en/translations.json application/json 2023-04-17 20:49:16.527 - info: host.ioboker iobroker upload [11] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/es/translations.json i18n/es/translations.json application/json 2023-04-17 20:49:16.752 - info: host.ioboker instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-04-17 20:49:16.753 - info: host.ioboker iobroker upload [10] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/fr/translations.json i18n/fr/translations.json application/json 2023-04-17 20:49:16.766 - info: host.ioboker iobroker upload [9] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/it/translations.json i18n/it/translations.json application/json 2023-04-17 20:49:16.775 - info: host.ioboker iobroker upload [8] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/nl/translations.json i18n/nl/translations.json application/json 2023-04-17 20:49:16.786 - info: host.ioboker iobroker upload [7] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/pl/translations.json i18n/pl/translations.json application/json 2023-04-17 20:49:16.795 - info: host.ioboker iobroker upload [6] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/pt/translations.json i18n/pt/translations.json application/json 2023-04-17 20:49:16.806 - info: host.ioboker iobroker upload [5] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/ru/translations.json i18n/ru/translations.json application/json 2023-04-17 20:49:16.816 - info: host.ioboker iobroker upload [4] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/uk/translations.json i18n/uk/translations.json application/json 2023-04-17 20:49:16.827 - info: host.ioboker iobroker upload [3] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json 2023-04-17 20:49:16.836 - info: host.ioboker iobroker upload [2] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/jsonConfig.json jsonConfig.json application/json 2023-04-17 20:49:16.846 - info: host.ioboker iobroker upload [1] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/shelly.png shelly.png image/png 2023-04-17 20:49:16.857 - info: host.ioboker iobroker upload [0] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/words.js words.js application/javascript 2023-04-17 20:49:17.894 - info: host.ioboker iobroker exit 0 2023-04-17 20:49:19.010 - info: host.ioboker instance system.adapter.shelly.0 started with pid 1917663 2023-04-17 20:49:20.991 - debug: shelly.0 (1917663) Redis Objects: Use Redis connection: 127.0.0.1:9001 2023-04-17 20:49:21.075 - debug: shelly.0 (1917663) Objects client ready ... initialize now 2023-04-17 20:49:21.081 - debug: shelly.0 (1917663) Objects create System PubSub Client 2023-04-17 20:49:21.084 - debug: shelly.0 (1917663) Objects create User PubSub Client 2023-04-17 20:49:21.217 - debug: shelly.0 (1917663) Objects client initialize lua scripts 2023-04-17 20:49:21.227 - debug: shelly.0 (1917663) Objects connected to redis: 127.0.0.1:9001 2023-04-17 20:49:21.300 - debug: shelly.0 (1917663) Redis States: Use Redis connection: 127.0.0.1:6379 2023-04-17 20:49:21.311 - debug: shelly.0 (1917663) States create System PubSub Client 2023-04-17 20:49:21.313 - debug: shelly.0 (1917663) States create User PubSub Client 2023-04-17 20:49:21.330 - debug: shelly.0 (1917663) States connected to redis: 127.0.0.1:6379 2023-04-17 20:49:21.388 - debug: shelly.0 (1917663) Plugin sentry Initialize Plugin (enabled=true) 2023-04-17 20:49:21.398 - info: shelly.0 (1917663) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2023-04-17 20:49:21.672 - info: shelly.0 (1917663) starting. Version 6.3.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v18.16.0, js-controller: 4.0.24 2023-04-17 20:49:22.064 - info: shelly.0 (1917663) Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0) 2023-04-17 20:49:22.072 - debug: shelly.0 (1917663) [MQTT Server] Started listener on 0.0.0.0:1882 2023-04-17 20:49:22.121 - debug: shelly.0 (1917663) [onlineCheck] Checking SHDM-1#D48060#1 on 192.168.171.100:80 2023-04-17 20:49:22.125 - debug: shelly.0 (1917663) [onlineCheck] Checking SHDM-1#F3D318#1 on 192.168.171.104:80 2023-04-17 20:49:22.128 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#3494546A3BD6#1 on 192.168.171.116:80 2023-04-17 20:49:22.133 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#3494546A89E4#1 on 192.168.171.115:80 2023-04-17 20:49:22.138 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#98F4ABD0B5D1#1 on 192.168.171.110:80 2023-04-17 20:49:22.143 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#C45BBE6AEA36#1 on 192.168.171.122:80 2023-04-17 20:49:22.147 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#C45BBE6BA0EA#1 on 192.168.171.123:80 2023-04-17 20:49:22.151 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#E09806AA5B3B#1 on 192.168.171.111:80 2023-04-17 20:49:22.155 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-25#E8DB84A23889#1 on 192.168.171.135:80 2023-04-17 20:49:22.282 - debug: shelly.0 (1917663) [MQTT Server] New connection from 192.168.178.30 2023-04-17 20:49:22.308 - debug: shelly.0 (1917663) [MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":99,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":false,"qos":0,"topic":"shellies/shellydimmer-F3D318/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellydimmer-F3D318","username":"MQTT","password":{"type":"Buffer","data":[73,79,83,104,101,108,108,121,56,50]}} 2023-04-17 20:50:06.330 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.100 (shellydimmer / shellydimmer-D48060 / SHDM-1#D48060#1) - topic: shellies/shellydimmer-D48060/light/0/energy, qos: 0, payload: 52390 2023-04-17 20:50:07.680 - debug: shelly.0 (1917663) [httpIoBrokerState] HTTP request error for 192.168.171.100 (shellydimmer / shellydimmer-D48060 / SHDM-1#D48060#1) "/status": Error: connect ENETUNREACH 192.168.171.100:80 2023-04-17 20:50:07.684 - debug: shelly.0 (1917663) [httpIoBrokerState] HTTP request error for 192.168.171.123 (shelly1 / shelly1-C45BBE6BA0EA / SHSW-1#C45BBE6BA0EA#1) "/settings/ext_temperature/1": Error: connect ENETUNREACH 192.168.171.123:80 2023-04-17 20:50:07.688 - debug: shelly.0 (1917663) [httpIoBrokerState] HTTP request error for 192.168.171.111 (shelly1 / shelly1-E09806AA5B3B / SHSW-1#E09806AA5B3B#1) "/settings/ext_temperature/2": Error: connect ENETUNREACH 192.168.171.111:80 2023-04-17 20:50:07.704 - debug: shelly.0 (1917663) [httpIoBrokerState] HTTP request error for 192.168.171.123 (shelly1 / shelly1-C45BBE6BA0EA / SHSW-1#C45BBE6BA0EA#1) "/settings/ext_temperature/2": Error: connect ENETUNREACH 192.168.171.123:80 2023-04-17 20:50:07.680 - debug: shelly.0 (1917663) [httpIoBrokerState] HTTP request error for 192.168.171.100 (shellydimmer / shellydimmer-D48060 / SHDM-1#D48060#1) "/status": Error: connect ENETUNREACH 192.168.171.100:80 2023-04-17 20:50:07.684 - debug: shelly.0 (1917663) [httpIoBrokerState] HTTP request error for 192.168.171.123 (shelly1 / shelly1-C45BBE6BA0EA / SHSW-1#C45BBE6BA0EA#1) "/settings/ext_temperature/1": Error: connect ENETUNREACH 192.168.171.123:80 2023-04-17 20:50:07.688 - debug: shelly.0 (1917663) [httpIoBrokerState] HTTP request error for 192.168.171.111 (shelly1 / shelly1-E09806AA5B3B / SHSW-1#E09806AA5B3B#1) "/settings/ext_temperature/2": Error: connect ENETUNREACH 192.168.171.111:80 2023-04-17 20:50:07.704 - debug: shelly.0 (1917663) [httpIoBrokerState] HTTP request error for 192.168.171.123 (shelly1 / shelly1-C45BBE6BA0EA / SHSW-1#C45BBE6BA0EA#1) "/settings/ext_temperature/2": Error: connect ENETUNREACH 192.168.171.123:80 2023-04-17 20:50:08.704 - debug: shelly.0 (1917663) [httpIoBrokerState] HTTP request error for 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) "/status": Error: connect ENETUNREACH 192.168.171.104:80 2023-04-17 20:50:13.605 - info: javascript.0 (6247) script.js.Telegram.TelegramMenue: Whz Wandlampe 2023-04-17 20:50:13.690 - debug: shelly.0 (1917663) [onStateChange] "shelly.0.SHDM-1#F3D318#1.lights.Switch" state changed: {"val":true,"ack":false,"ts":1681757413688,"q":0,"from":"system.adapter.linkeddevices.0","user":"system.user.admin","lc":1681757413688} - forwarding to objectHelper 2023-04-17 20:50:13.692 - debug: shelly.0 (1917663) [mqtt controlFunction] Executing state.mqtt.mqtt_cmd_funct of state SHDM-1#F3D318#1.lights.Switch for 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) with value: true -> on 2023-04-17 20:50:13.694 - debug: shelly.0 (1917663) [MQTT] Send state to 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) with QoS 0: shellies/shellydimmer-F3D318/light/0/command = on (2) 2023-04-17 20:50:13.830 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0, qos: 0, payload: on 2023-04-17 20:50:13.833 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/status, qos: 0, payload: {"ison":true,"source":"mqtt","has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"mode":"white","brightness":70,"transition":0} 2023-04-17 20:50:13.834 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/light/0/status -> state: SHDM-1#F3D318#1.lights.Switch, value: true 2023-04-17 20:50:13.836 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/temperature, qos: 0, payload: 39.74 2023-04-17 20:50:13.838 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/temperature -> state: SHDM-1#F3D318#1.temperatureC, value: 39.74 2023-04-17 20:50:13.839 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/temperature_f, qos: 0, payload: 103.53 2023-04-17 20:50:13.841 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/temperature_f -> state: SHDM-1#F3D318#1.temperatureF, value: 103.53 2023-04-17 20:50:13.842 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/overtemperature, qos: 0, payload: 0 2023-04-17 20:50:13.844 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/overpower, qos: 0, payload: 0 2023-04-17 20:50:13.846 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/loaderror, qos: 0, payload: 0 2023-04-17 20:50:13.605 - info: javascript.0 (6247) script.js.Telegram.TelegramMenue: Whz Wandlampe 2023-04-17 20:50:13.690 - debug: shelly.0 (1917663) [onStateChange] "shelly.0.SHDM-1#F3D318#1.lights.Switch" state changed: {"val":true,"ack":false,"ts":1681757413688,"q":0,"from":"system.adapter.linkeddevices.0","user":"system.user.admin","lc":1681757413688} - forwarding to objectHelper 2023-04-17 20:50:13.692 - debug: shelly.0 (1917663) [mqtt controlFunction] Executing state.mqtt.mqtt_cmd_funct of state SHDM-1#F3D318#1.lights.Switch for 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) with value: true -> on 2023-04-17 20:50:13.694 - debug: shelly.0 (1917663) [MQTT] Send state to 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) with QoS 0: shellies/shellydimmer-F3D318/light/0/command = on (2) 2023-04-17 20:50:13.830 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0, qos: 0, payload: on 2023-04-17 20:50:13.833 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/status, qos: 0, payload: {"ison":true,"source":"mqtt","has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"mode":"white","brightness":70,"transition":0} 2023-04-17 20:50:13.834 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/light/0/status -> state: SHDM-1#F3D318#1.lights.Switch, value: true 2023-04-17 20:50:13.836 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/temperature, qos: 0, payload: 39.74 2023-04-17 20:50:13.838 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/temperature -> state: SHDM-1#F3D318#1.temperatureC, value: 39.74 2023-04-17 20:50:13.839 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/temperature_f, qos: 0, payload: 103.53 2023-04-17 20:50:13.841 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/temperature_f -> state: SHDM-1#F3D318#1.temperatureF, value: 103.53 2023-04-17 20:50:13.842 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/overtemperature, qos: 0, payload: 0 2023-04-17 20:50:13.844 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/overpower, qos: 0, payload: 0 2023-04-17 20:50:13.846 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/loaderror, qos: 0, payload: 0 2023-04-17 20:50:14.430 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/power, qos: 0, payload: 9.89 2023-04-17 20:50:14.431 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/light/0/power -> state: SHDM-1#F3D318#1.lights.Power, value: 9.89 2023-04-17 20:50:14.433 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/energy, qos: 0, payload: 1291 2023-04-17 20:50:14.430 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/power, qos: 0, payload: 9.89 2023-04-17 20:50:14.431 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/light/0/power -> state: SHDM-1#F3D318#1.lights.Power, value: 9.89 2023-04-17 20:50:14.433 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/energy, qos: 0, payload: 1291 2023-04-17 20:50:20.249 - info: javascript.0 (6247) script.js.Telegram.TelegramMenue: Whz Wandlampe 2023-04-17 20:50:20.323 - debug: shelly.0 (1917663) [onStateChange] "shelly.0.SHDM-1#F3D318#1.lights.Switch" state changed: {"val":false,"ack":false,"ts":1681757420321,"q":0,"from":"system.adapter.linkeddevices.0","user":"system.user.admin","lc":1681757420321} - forwarding to objectHelper 2023-04-17 20:50:20.328 - debug: shelly.0 (1917663) [mqtt controlFunction] Executing state.mqtt.mqtt_cmd_funct of state SHDM-1#F3D318#1.lights.Switch for 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) with value: false -> off 2023-04-17 20:50:20.328 - debug: shelly.0 (1917663) [MQTT] Send state to 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) with QoS 0: shellies/shellydimmer-F3D318/light/0/command = off (3) 2023-04-17 20:50:20.448 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0, qos: 0, payload: off 2023-04-17 20:50:20.450 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/status, qos: 0, payload: {"ison":false,"source":"mqtt","has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"mode":"white","brightness":70,"transition":0} 2023-04-17 20:50:20.451 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/light/0/status -> state: SHDM-1#F3D318#1.lights.Switch, value: false 2023-04-17 20:50:20.453 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/temperature, qos: 0, payload: 39.80 2023-04-17 20:50:20.454 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/temperature -> state: SHDM-1#F3D318#1.temperatureC, value: 39.8 2023-04-17 20:50:20.455 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/temperature_f, qos: 0, payload: 103.65 2023-04-17 20:50:20.456 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/temperature_f -> state: SHDM-1#F3D318#1.temperatureF, value: 103.65 2023-04-17 20:50:20.457 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/overtemperature, qos: 0, payload: 0 2023-04-17 20:50:20.459 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/overpower, qos: 0, payload: 0 2023-04-17 20:50:20.460 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/loaderror, qos: 0, payload: 0 2023-04-17 20:50:20.249 - info: javascript.0 (6247) script.js.Telegram.TelegramMenue: Whz Wandlampe 2023-04-17 20:50:20.323 - debug: shelly.0 (1917663) [onStateChange] "shelly.0.SHDM-1#F3D318#1.lights.Switch" state changed: {"val":false,"ack":false,"ts":1681757420321,"q":0,"from":"system.adapter.linkeddevices.0","user":"system.user.admin","lc":1681757420321} - forwarding to objectHelper 2023-04-17 20:50:20.328 - debug: shelly.0 (1917663) [mqtt controlFunction] Executing state.mqtt.mqtt_cmd_funct of state SHDM-1#F3D318#1.lights.Switch for 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) with value: false -> off 2023-04-17 20:50:20.328 - debug: shelly.0 (1917663) [MQTT] Send state to 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) with QoS 0: shellies/shellydimmer-F3D318/light/0/command = off (3) 2023-04-17 20:50:20.448 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0, qos: 0, payload: off 2023-04-17 20:50:20.450 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/status, qos: 0, payload: {"ison":false,"source":"mqtt","has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"mode":"white","brightness":70,"transition":0} 2023-04-17 20:50:20.451 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/light/0/status -> state: SHDM-1#F3D318#1.lights.Switch, value: false 2023-04-17 20:50:20.453 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/temperature, qos: 0, payload: 39.80 2023-04-17 20:50:20.454 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/temperature -> state: SHDM-1#F3D318#1.temperatureC, value: 39.8 2023-04-17 20:50:20.455 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/temperature_f, qos: 0, payload: 103.65 2023-04-17 20:50:20.456 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/temperature_f -> state: SHDM-1#F3D318#1.temperatureF, value: 103.65 2023-04-17 20:50:20.457 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/overtemperature, qos: 0, payload: 0 2023-04-17 20:50:20.459 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/overpower, qos: 0, payload: 0 2023-04-17 20:50:20.460 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/loaderror, qos: 0, payload: 0 2023-04-17 20:50:22.228 - debug: shelly.0 (1917663) [onlineCheck] Checking SHDM-1#D48060#1 on 192.168.171.100:80 2023-04-17 20:50:22.231 - debug: shelly.0 (1917663) [onlineCheck] Checking SHDM-1#F3D318#1 on 192.168.171.104:80 2023-04-17 20:50:22.233 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#3494546A3BD6#1 on 192.168.171.116:80 2023-04-17 20:50:22.236 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#3494546A89E4#1 on 192.168.171.115:80 2023-04-17 20:50:22.239 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#98F4ABD0B5D1#1 on 192.168.171.110:80 2023-04-17 20:50:22.242 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#C45BBE6AEA36#1 on 192.168.171.122:80 2023-04-17 20:50:22.244 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#C45BBE6BA0EA#1 on 192.168.171.123:80 2023-04-17 20:50:22.247 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#E09806AA5B3B#1 on 192.168.171.111:80 2023-04-17 20:50:22.250 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHDM-1#D48060#1: false 2023-04-17 20:50:22.251 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-25#E8DB84A23889#1 on 192.168.171.135:80 2023-04-17 20:50:22.256 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHDM-1#F3D318#1: false 2023-04-17 20:50:22.257 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-1#3494546A3BD6#1: false 2023-04-17 20:50:22.275 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-1#3494546A89E4#1: false 2023-04-17 20:50:22.276 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-1#98F4ABD0B5D1#1: false 2023-04-17 20:50:22.280 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-1#C45BBE6AEA36#1: false 2023-04-17 20:50:22.281 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-1#C45BBE6BA0EA#1: false 2023-04-17 20:50:22.287 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-1#E09806AA5B3B#1: false 2023-04-17 20:50:22.291 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-25#E8DB84A23889#1: false 2023-04-17 20:50:22.431 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/power, qos: 0, payload: 8.81 2023-04-17 20:50:22.433 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/light/0/power -> state: SHDM-1#F3D318#1.lights.Power, value: 8.81 2023-04-17 20:50:22.435 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/energy, qos: 0, payload: 1291 2023-04-17 20:50:22.462 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#98F4ABD0B5D1#1","SHDM-1#F3D318#1","SHSW-1#E09806AA5B3B#1","SHSW-1#C45BBE6BA0EA#1","SHSW-1#3494546A89E4#1","SHSW-25#E8DB84A23889#1","SHSW-1#3494546A3BD6#1","SHSW-1#C45BBE6AEA36#1"] 2023-04-17 20:50:22.789 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#98F4ABD0B5D1#1","SHSW-1#E09806AA5B3B#1","SHSW-1#C45BBE6BA0EA#1","SHSW-1#3494546A89E4#1","SHSW-25#E8DB84A23889#1","SHSW-1#3494546A3BD6#1","SHSW-1#C45BBE6AEA36#1"] 2023-04-17 20:50:22.799 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#98F4ABD0B5D1#1","SHSW-1#E09806AA5B3B#1","SHSW-1#C45BBE6BA0EA#1","SHSW-1#3494546A89E4#1","SHSW-25#E8DB84A23889#1","SHSW-1#C45BBE6AEA36#1"] 2023-04-17 20:50:22.802 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#98F4ABD0B5D1#1","SHSW-1#E09806AA5B3B#1","SHSW-1#C45BBE6BA0EA#1","SHSW-25#E8DB84A23889#1","SHSW-1#C45BBE6AEA36#1"] 2023-04-17 20:50:22.802 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#E09806AA5B3B#1","SHSW-1#C45BBE6BA0EA#1","SHSW-25#E8DB84A23889#1","SHSW-1#C45BBE6AEA36#1"] 2023-04-17 20:50:22.803 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#E09806AA5B3B#1","SHSW-1#C45BBE6BA0EA#1","SHSW-25#E8DB84A23889#1"] 2023-04-17 20:50:22.803 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#E09806AA5B3B#1","SHSW-25#E8DB84A23889#1"] 2023-04-17 20:50:22.804 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-25#E8DB84A23889#1"] 2023-04-17 20:50:22.804 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: [] 2023-04-17 20:50:22.228 - debug: shelly.0 (1917663) [onlineCheck] Checking SHDM-1#D48060#1 on 192.168.171.100:80 2023-04-17 20:50:22.231 - debug: shelly.0 (1917663) [onlineCheck] Checking SHDM-1#F3D318#1 on 192.168.171.104:80 2023-04-17 20:50:22.233 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#3494546A3BD6#1 on 192.168.171.116:80 2023-04-17 20:50:22.236 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#3494546A89E4#1 on 192.168.171.115:80 2023-04-17 20:50:22.239 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#98F4ABD0B5D1#1 on 192.168.171.110:80 2023-04-17 20:50:22.242 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#C45BBE6AEA36#1 on 192.168.171.122:80 2023-04-17 20:50:22.244 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#C45BBE6BA0EA#1 on 192.168.171.123:80 2023-04-17 20:50:22.247 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-1#E09806AA5B3B#1 on 192.168.171.111:80 2023-04-17 20:50:22.250 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHDM-1#D48060#1: false 2023-04-17 20:50:22.251 - debug: shelly.0 (1917663) [onlineCheck] Checking SHSW-25#E8DB84A23889#1 on 192.168.171.135:80 2023-04-17 20:50:22.256 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHDM-1#F3D318#1: false 2023-04-17 20:50:22.257 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-1#3494546A3BD6#1: false 2023-04-17 20:50:22.275 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-1#3494546A89E4#1: false 2023-04-17 20:50:22.276 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-1#98F4ABD0B5D1#1: false 2023-04-17 20:50:22.280 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-1#C45BBE6AEA36#1: false 2023-04-17 20:50:22.281 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-1#C45BBE6BA0EA#1: false 2023-04-17 20:50:22.287 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-1#E09806AA5B3B#1: false 2023-04-17 20:50:22.291 - debug: shelly.0 (1917663) [deviceStatusUpdate] SHSW-25#E8DB84A23889#1: false 2023-04-17 20:50:22.431 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/power, qos: 0, payload: 8.81 2023-04-17 20:50:22.433 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/light/0/power -> state: SHDM-1#F3D318#1.lights.Power, value: 8.81 2023-04-17 20:50:22.435 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/energy, qos: 0, payload: 1291 2023-04-17 20:50:22.462 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#98F4ABD0B5D1#1","SHDM-1#F3D318#1","SHSW-1#E09806AA5B3B#1","SHSW-1#C45BBE6BA0EA#1","SHSW-1#3494546A89E4#1","SHSW-25#E8DB84A23889#1","SHSW-1#3494546A3BD6#1","SHSW-1#C45BBE6AEA36#1"] 2023-04-17 20:50:22.789 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#98F4ABD0B5D1#1","SHSW-1#E09806AA5B3B#1","SHSW-1#C45BBE6BA0EA#1","SHSW-1#3494546A89E4#1","SHSW-25#E8DB84A23889#1","SHSW-1#3494546A3BD6#1","SHSW-1#C45BBE6AEA36#1"] 2023-04-17 20:50:22.799 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#98F4ABD0B5D1#1","SHSW-1#E09806AA5B3B#1","SHSW-1#C45BBE6BA0EA#1","SHSW-1#3494546A89E4#1","SHSW-25#E8DB84A23889#1","SHSW-1#C45BBE6AEA36#1"] 2023-04-17 20:50:22.802 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#98F4ABD0B5D1#1","SHSW-1#E09806AA5B3B#1","SHSW-1#C45BBE6BA0EA#1","SHSW-25#E8DB84A23889#1","SHSW-1#C45BBE6AEA36#1"] 2023-04-17 20:50:22.802 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#E09806AA5B3B#1","SHSW-1#C45BBE6BA0EA#1","SHSW-25#E8DB84A23889#1","SHSW-1#C45BBE6AEA36#1"] 2023-04-17 20:50:22.803 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#E09806AA5B3B#1","SHSW-1#C45BBE6BA0EA#1","SHSW-25#E8DB84A23889#1"] 2023-04-17 20:50:22.803 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-1#E09806AA5B3B#1","SHSW-25#E8DB84A23889#1"] 2023-04-17 20:50:22.804 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: ["SHSW-25#E8DB84A23889#1"] 2023-04-17 20:50:22.804 - debug: shelly.0 (1917663) [deviceStatusUpdate] Online devices: [] 2023-04-17 20:50:24.431 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/power, qos: 0, payload: 0.00 2023-04-17 20:50:24.432 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/light/0/power -> state: SHDM-1#F3D318#1.lights.Power, value: 0 2023-04-17 20:50:24.433 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/energy, qos: 0, payload: 1291 2023-04-17 20:50:24.431 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/power, qos: 0, payload: 0.00 2023-04-17 20:50:24.432 - debug: shelly.0 (1917663) [MQTT] State change 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1): shellies/shellydimmer-F3D318/light/0/power -> state: SHDM-1#F3D318#1.lights.Power, value: 0 2023-04-17 20:50:24.433 - debug: shelly.0 (1917663) [MQTT] Publish: 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) - topic: shellies/shellydimmer-F3D318/light/0/energy, qos: 0, payload: 1291 2023-04-17 20:50:29.903 - info: javascript.0 (6247) script.js.Telegram.TelegramMenue: Whz Wandlampe 2023-04-17 20:50:29.968 - debug: shelly.0 (1917663) [onStateChange] "shelly.0.SHDM-1#F3D318#1.lights.Switch" state changed: {"val":true,"ack":false,"ts":1681757429966,"q":0,"from":"system.adapter.linkeddevices.0","user":"system.user.admin","lc":1681757429966} - forwarding to objectHelper 2023-04-17 20:50:29.969 - warn: shelly.0 (1917663) [mqtt controlFunction] Unable to perform request - device 192.168.171.104 (shellydimmer / shellydimmer-F3D318 / SHDM-1#F3D318#1) is offline
Support us
573
Online32.7k
Benutzer82.4k
Themen1.3m
Beiträge