Shelly Adapter - genereller Support
-
Da er nun verfügbar ist und auch dokumentiert wurde kann schaun dass ich ihn in den nächste Release reinkonfigurier. Da er eine neue Komponente benutzt könnte es ev. erforderlich sein ein paar Testzyklen zu machen. Pers. ist er mir zu teuer um ihn nur für den Adapter anzuschaffen.
Bitte aboniert das Issue dazu: https://github.com/iobroker-community-adapters/ioBroker.shelly/issues/1228
P.S: Hauptproblem ist zur Zeit dass durch den Einsatz von KI derzeit so viele neue Adapter entstehen dass der notwendige Review massiv Zeit bindet. Das ist nur eine INfo und keine Kritik an irgendwem - wir sind dankbar über jeden der seien Zeit für die Entwicklung eines Adapters einsetzt.
Ich hoffe aber ab nächster Woche auch wieder mal Zeit für Adapterentwiclung frei zu bekommen...
Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
Support Repositoryverwaltung.Wer 'nen Kaffee spendieren will: https://paypal.me
-
Da er nun verfügbar ist und auch dokumentiert wurde kann schaun dass ich ihn in den nächste Release reinkonfigurier. Da er eine neue Komponente benutzt könnte es ev. erforderlich sein ein paar Testzyklen zu machen. Pers. ist er mir zu teuer um ihn nur für den Adapter anzuschaffen.
Bitte aboniert das Issue dazu: https://github.com/iobroker-community-adapters/ioBroker.shelly/issues/1228
P.S: Hauptproblem ist zur Zeit dass durch den Einsatz von KI derzeit so viele neue Adapter entstehen dass der notwendige Review massiv Zeit bindet. Das ist nur eine INfo und keine Kritik an irgendwem - wir sind dankbar über jeden der seien Zeit für die Entwicklung eines Adapters einsetzt.
Ich hoffe aber ab nächster Woche auch wieder mal Zeit für Adapterentwiclung frei zu bekommen...
Da er nun verfügbar ist und auch dokumentiert wurde kann schaun dass ich in den nächste Release reinkonfigurier. Da er eine neue Komponente benutzt könnte es ev. erforderlich sein ein paar Testzyklen zu machen. Pers. ist er mir zu teuer um ihn nur für den Adapter anzuschaffen.
Bitte aboniert das Issue dazu: https://github.com/iobroker-community-adapters/ioBroker.shelly/issues/1228
Vielen Dank!!!
-
Ich habe den Shelly-Adapter 10.6.1 installiert. Der Adapter wird nicht grün, er zeigt ein gelbes Dreieck mit Ausrufezeichen an.
Im Log finde ich jedoch den Eintrag, dass der Adapter ohne Fehler gestartet ist: "Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0)"
Ich bin ratlos.
Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..
-
Ich habe den Shelly-Adapter 10.6.1 installiert. Der Adapter wird nicht grün, er zeigt ein gelbes Dreieck mit Ausrufezeichen an.
Im Log finde ich jedoch den Eintrag, dass der Adapter ohne Fehler gestartet ist: "Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0)"
Ich bin ratlos.
-
Zeit shelly.0 2026-04-26 22:08:10.284 info Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0) shelly.0 2026-04-26 22:08:10.221 info starting. Version 10.6.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v22.22.1, js-controller: 7.0.7 host.iobroker 2026-04-26 22:08:09.678 info instance system.adapter.shelly.0 in version "10.6.1" started with pid 158752 host.iobroker 2026-04-26 22:08:06.558 info instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) shelly.0 2026-04-26 22:08:06.532 info terminating host.iobroker 2026-04-26 22:08:06.072 info stopInstance system.adapter.shelly.0 send kill signal shelly.0 2026-04-26 22:08:06.039 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason shelly.0 2026-04-26 22:08:06.038 info terminating shelly.0 2026-04-26 22:08:06.031 info Got terminate signal TERMINATE_YOURSELF host.iobroker 2026-04-26 22:08:06.029 info stopInstance system.adapter.shelly.0 (force=false, process=true)Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..
-
Zeit shelly.0 2026-04-26 22:08:10.284 info Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0) shelly.0 2026-04-26 22:08:10.221 info starting. Version 10.6.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v22.22.1, js-controller: 7.0.7 host.iobroker 2026-04-26 22:08:09.678 info instance system.adapter.shelly.0 in version "10.6.1" started with pid 158752 host.iobroker 2026-04-26 22:08:06.558 info instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) shelly.0 2026-04-26 22:08:06.532 info terminating host.iobroker 2026-04-26 22:08:06.072 info stopInstance system.adapter.shelly.0 send kill signal shelly.0 2026-04-26 22:08:06.039 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason shelly.0 2026-04-26 22:08:06.038 info terminating shelly.0 2026-04-26 22:08:06.031 info Got terminate signal TERMINATE_YOURSELF host.iobroker 2026-04-26 22:08:06.029 info stopInstance system.adapter.shelly.0 (force=false, process=true)Bitte das richtige Log aus
iob logsverwenden und nicht das Ding aus dem Admin. Das ist furchtbar formatiert und chronologisch falsch herum.
Und wie immer: System auf Stand bringen.
-
Bitte das richtige Log aus
iob logsverwenden und nicht das Ding aus dem Admin. Das ist furchtbar formatiert und chronologisch falsch herum.
Und wie immer: System auf Stand bringen.
-
Ich habe leider kein ssh Zugriff auf diese ioBroker Installation. Der ioBroker läuft in einem Docker und ist nur über VPN zugänglich.
Zugriff via Terminal ist das wichtigste überhaupt.
-
Zugriff via Terminal ist das wichtigste überhaupt.
Da gebe ich dir natürlich recht. Es handelt sich bei der Installation für ein Familienmitglied. Dann müssen man halt vor Ort tätig werden und ich kann nichts weiter tun.
Stopp!
Ich installiere einmal eine Instanz bei mir auf meinem Pi 5 installiert. Hier sollte ich jedoch iob logs ausführen können. Ich melde mich anschließend.
Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..
-
Da gebe ich dir natürlich recht. Es handelt sich bei der Installation für ein Familienmitglied. Dann müssen man halt vor Ort tätig werden und ich kann nichts weiter tun.
Stopp!
Ich installiere einmal eine Instanz bei mir auf meinem Pi 5 installiert. Hier sollte ich jedoch iob logs ausführen können. Ich melde mich anschließend.
-
Wie ich schrieb: Ich richte einem entfernt wohnenden Familienmitglied ein System ein.
Also auch bei mir funktioniert das Ganze auch nicht. Hier das gewünschte Log ..
pi@Pi5:~ $ iob logs 2026-04-26 22:07:18.801 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1408124887 2026-04-26 22:07:19.070 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004c01490148005e0020a4ba0015001200130000031a00000000000009020402a51e9a6e000080fe000000ff00004000042cde42 2026-04-26 22:07:19.328 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:07:39.116 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:07:38Z&rnr=22295&hash=0f84a79321b012b9b340a616626ad57a658afbeed84452535f2cb737f4e125e3 2026-04-26 22:07:42.112 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:07:41Z&rnr=49516&hash=daeb2499a5bf77cf7f430ce2d20e00ce15de33008d37ab1f9e45e656caa2186a 2026-04-26 22:08:18.817 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1409124917 2026-04-26 22:08:19.085 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004c01490148005e0021a4ba0015001200130000031a00000000000009020402a51e9a6e000080fe000000ff00004000042cd9ff 2026-04-26 22:08:19.344 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:08:39.115 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:08:38Z&rnr=36501&hash=da131b9bf3e7743f2990087273ca926243a28ea6e6713f133e4623f71209a304 2026-04-26 22:08:42.111 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:08:41Z&rnr=23697&hash=5c622298d6889ef888b570312e5b5a85e08823fdd85dfce2c76ae412dd65a879 2026-04-26 22:09:18.812 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a140a1249e7 2026-04-26 22:09:19.081 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004c01490148005e0020a4ba0015001200130000031a00000000000009020402a51e9a6e000080ff000000ff00004000042cdabe 2026-04-26 22:09:19.339 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:09:39.118 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:09:38Z&rnr=40130&hash=e17e585254ca1728a6211c148d9e369d913986a60018336412a50714045c7779 2026-04-26 22:09:42.111 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:09:41Z&rnr=53523&hash=fb2b190182bb4f43f7d85d472ac1152082f31f3850d73ec8b5e72b457ef7ade3 2026-04-26 22:10:18.807 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a140b124877 2026-04-26 22:10:19.076 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004b014a0148005e001fa4ba0015001200130000031a00000000000009020402a51e9a6e000080ff000000ff00004000042c36e2 2026-04-26 22:10:19.334 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:10:39.116 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:10:38Z&rnr=201&hash=8fcd134c501102beaecda5144ed22355855f05bb543cd6c33d56e83634b8a32a 2026-04-26 22:10:42.112 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:10:41Z&rnr=14307&hash=d684df03c7d886db254858fd2c98d543ea18fe4d269a239af201b586e63eb981 2026-04-26 22:11:18.802 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a140c124a47 2026-04-26 22:11:19.070 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004b014a0148005e001ea4c40015001200130000031a00000000000009020402a51e9a6e000080ff000000ff00004000042c86d4 2026-04-26 22:11:19.329 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:11:39.120 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:11:38Z&rnr=60096&hash=7a629e569426b9468492d0e3d6e801dbab11ed3399cf9cd31a67236d15cd4ba5 2026-04-26 22:11:42.112 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:11:41Z&rnr=5927&hash=7d1730f2894887b8a07b424d346d9937f3bce0d1454ac8525bd833a3ee531012 2026-04-26 22:12:18.817 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a140d124bd7 2026-04-26 22:12:19.086 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004b014a0148005e001ea4c40015001200130000031a00000000000009020402a51e9a6e000080ff000000ff00004000042c86d4 2026-04-26 22:12:19.345 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:12:39.121 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:12:38Z&rnr=57338&hash=ef9ce8256bf0e2dd5250f1bf4fd608f1ea6dcfcd38eae32daff6b166dfefcd7d 2026-04-26 22:12:42.111 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:12:41Z&rnr=4315&hash=4611fd287137924deeaf451b7d460a4be9801b45894bd7cd15976b9a193720aa 2026-04-26 22:13:18.812 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a140e124b27 2026-04-26 22:13:19.081 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004b014a0148005e001ca4ce0015001200130000031a00000000000009020402a51e9a6e000080ff000000ff00004000042cd496 2026-04-26 22:13:19.339 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:13:39.124 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:13:38Z&rnr=54225&hash=327ce9eba7135c97700e941d6f9373ee06ad0b4fd6267b54884760c7599d4344 2026-04-26 22:13:42.218 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:13:41Z&rnr=57055&hash=93814fd5609121b7712fe5ce3b90a402c10b43b9d13d5f6cdb4cde4af5daeaef 2026-04-26 22:14:18.807 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a140f124ab7 2026-04-26 22:14:19.076 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004a014a0148005e001ba4d80015001200130000031a00000000000009020402a51e9a6e00008100000000ff00004000042c8bb4 2026-04-26 22:14:19.334 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:14:39.122 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:14:38Z&rnr=3410&hash=a2096f2f26896a93c4ee4661933f79cd4adaeaf19406a62e4736ba2d0c5eaa7e 2026-04-26 22:14:42.112 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:14:41Z&rnr=12745&hash=df4bad75ae7998d0972d4a32039d80521edcee8c89f6d8a325bad749efed54b9 2026-04-26 22:15:18.822 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1410124287 2026-04-26 22:15:19.091 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004a014a0148005e001ba4d80015001200130000031a00000000000009020402a51e9a6e00008100000000ff00004000042c8bb4 2026-04-26 22:15:19.350 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:15:24.011 - info: host.Pi5 instance system.adapter.dwd.0 in version "2.8.5" started with pid 1921713 2026-04-26 22:15:25.164 - info: dwd.0 (1921713) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v20.19.5, js-controller: 7.0.7 2026-04-26 22:15:25.573 - info: dwd.0 (1921713) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2026-04-26 22:15:26.083 - info: host.Pi5 instance system.adapter.dwd.0 having pid 1921713 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2026-04-26 22:15:39.116 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:15:38Z&rnr=39260&hash=d511c04a6d691ff3796c9642951b8410690b73eeeaf8bf9f0b4a755e658c78a6 2026-04-26 22:15:42.111 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:15:41Z&rnr=1272&hash=86d494e9561c1e1e403744b89d9ce943bd827f973faa9d0d6f82f04b261b1bfe 2026-04-26 22:16:18.817 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1411124317 2026-04-26 22:16:19.086 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004a014a0148005e001aa4e20015001200130000031a00000000000009020402a5469a6e00008100000000ff00004000042cc3a3 2026-04-26 22:16:19.345 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:16:39.116 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:16:38Z&rnr=46877&hash=66a693988dbc0cc5a460dd39197496667b841182d0a6194a059598d760f50d19 2026-04-26 22:16:42.111 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:16:41Z&rnr=27710&hash=bd697f6328a0ec2a1c9295c7735804eee247cc9a4d16aaf372cc45b133ea7483 2026-04-26 22:17:18.812 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a14121243e7 2026-04-26 22:17:19.081 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004a014a0148005e001aa4e20015001200130000031a00000000000009020402a5469a6e00008100000000ff00004000042cc3a3 2026-04-26 22:17:19.340 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:17:39.117 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:17:38Z&rnr=2072&hash=faaa5b48394fae8475f69963de80a6f8cf1e5b529bd5e949b9919524b0b86707 2026-04-26 22:17:42.113 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:17:41Z&rnr=49852&hash=700cef37dc50de38a48a99d34cdb5c0e8531f9516d21d90862d13af367cdb5b1 2026-04-26 22:18:18.807 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1413124277 2026-04-26 22:18:19.076 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004a014a0148005e001aa4e20015001200130000031a00000000000009020402a5469a6e00008100000000ff00004000042cc3a3 2026-04-26 22:18:19.335 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:18:39.117 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:18:38Z&rnr=29548&hash=27e25a3e7cddea73449f1a96516de1c6b9363ee8d94c24920e1c4fbdf950a4ce 2026-04-26 22:18:42.113 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:18:41Z&rnr=35757&hash=9a6e05d2e07870095d17e90162358e2051c0749509e10e0b2e1812a6d58ad576 2026-04-26 22:19:18.823 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1414124047 2026-04-26 22:19:19.092 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 0103320049014a0148005e0019a4e20015001200130000031a00000000000009020402a5469a6e00008101000000ff00004000042cbaaf 2026-04-26 22:19:19.371 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:19:39.116 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:19:38Z&rnr=32245&hash=5abb137adc6a55591ad6a85e29b8fb908dc72fd75647a7b44c6cd197912bd9a7 2026-04-26 22:19:42.115 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:19:41Z&rnr=49609&hash=82f9622a07472d8a7a64951407cba05a31c397fe3b54047c2bed52c6a617400a 2026-04-26 22:20:00.956 - info: host.Pi5 iobroker add shelly auto --host Pi5 --debug 2026-04-26 22:20:01.916 - info: host.Pi5 iobroker host.Pi5 create instance shelly 2026-04-26 22:20:01.922 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.alive created 2026-04-26 22:20:01.925 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.connected created 2026-04-26 22:20:01.930 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.compactMode created 2026-04-26 22:20:01.937 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.cpu created 2026-04-26 22:20:01.952 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.cputime created 2026-04-26 22:20:01.955 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.memHeapUsed created 2026-04-26 22:20:01.959 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.memHeapTotal created 2026-04-26 22:20:01.966 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.memRss created 2026-04-26 22:20:01.973 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.uptime created 2026-04-26 22:20:01.977 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.inputCount created 2026-04-26 22:20:01.980 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.outputCount created 2026-04-26 22:20:01.983 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.eventLoopLag created 2026-04-26 22:20:01.987 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.sigKill created 2026-04-26 22:20:01.990 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.logLevel created 2026-04-26 22:20:01.997 - info: host.Pi5 iobroker host.Pi5 object shelly.1 created 2026-04-26 22:20:01.999 - info: host.Pi5 iobroker host.Pi5 object shelly.1.info created 2026-04-26 22:20:02.002 - info: host.Pi5 iobroker host.Pi5 object shelly.1.info.connection created 2026-04-26 22:20:02.004 - info: host.Pi5 iobroker host.Pi5 object shelly.1.info.update created 2026-04-26 22:20:02.008 - info: host.Pi5 iobroker host.Pi5 object shelly.1.info.downloadScripts created 2026-04-26 22:20:02.011 - info: host.Pi5 iobroker host.Pi5 object shelly.1.ble created 2026-04-26 22:20:02.013 - info: host.Pi5 iobroker host.Pi5 Set default value of shelly.1.info.connection: false 2026-04-26 22:20:02.018 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1 created 2026-04-26 22:20:03.029 - info: host.Pi5 iobroker exit 0 2026-04-26 22:20:18.818 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a14151241d7 2026-04-26 22:20:19.087 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 0103320049014a0148005e0019a4e20015001200130000031a00000000000009020402a5469a6e00008101000000ff00004000042cbaaf 2026-04-26 22:20:19.345 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:20:39.152 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:20:38Z&rnr=36945&hash=fd11dd95f392056c32756eca06d5b02eafe85c6a86ad15b158b48486d4e3b242 2026-04-26 22:20:42.115 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:20:41Z&rnr=6592&hash=be9aa0f151734bb606d128b558d7b0f738afeb36508842b28842e0ecd4f316fb 2026-04-26 22:21:09.352 - info: host.Pi5 "system.adapter.shelly.1" enabled 2026-04-26 22:21:10.215 - info: host.Pi5 instance system.adapter.shelly.1 in version "10.6.1" started with pid 1922051 2026-04-26 22:21:11.605 - info: shelly.1 (1922051) starting. Version 10.6.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v20.19.5, js-controller: 7.0.7 2026-04-26 22:21:11.747 - info: shelly.1 (1922051) Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0) 2026-04-26 22:21:18.813 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1416124127 2026-04-26 22:21:19.082 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 0103320049014a0148005e0019a4e20015001200130000031a00000000000009020402a5469a6e00008101000000ff00004000042cbaaf 2026-04-26 22:21:19.340 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:21:39.118 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:21:38Z&rnr=26492&hash=62051390669c23340b7ecdca6845991d360927b1dbf4075d3b44d8a0e63805aa 2026-04-26 22:21:42.113 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:21:41Z&rnr=42639&hash=9cb30c897ee3090452b4e0404018e93474a5a428d2213a2cf6775d4601eb80ef pi@Pi5:~ $Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..
-
Wie ich schrieb: Ich richte einem entfernt wohnenden Familienmitglied ein System ein.
Also auch bei mir funktioniert das Ganze auch nicht. Hier das gewünschte Log ..
pi@Pi5:~ $ iob logs 2026-04-26 22:07:18.801 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1408124887 2026-04-26 22:07:19.070 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004c01490148005e0020a4ba0015001200130000031a00000000000009020402a51e9a6e000080fe000000ff00004000042cde42 2026-04-26 22:07:19.328 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:07:39.116 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:07:38Z&rnr=22295&hash=0f84a79321b012b9b340a616626ad57a658afbeed84452535f2cb737f4e125e3 2026-04-26 22:07:42.112 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:07:41Z&rnr=49516&hash=daeb2499a5bf77cf7f430ce2d20e00ce15de33008d37ab1f9e45e656caa2186a 2026-04-26 22:08:18.817 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1409124917 2026-04-26 22:08:19.085 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004c01490148005e0021a4ba0015001200130000031a00000000000009020402a51e9a6e000080fe000000ff00004000042cd9ff 2026-04-26 22:08:19.344 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:08:39.115 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:08:38Z&rnr=36501&hash=da131b9bf3e7743f2990087273ca926243a28ea6e6713f133e4623f71209a304 2026-04-26 22:08:42.111 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:08:41Z&rnr=23697&hash=5c622298d6889ef888b570312e5b5a85e08823fdd85dfce2c76ae412dd65a879 2026-04-26 22:09:18.812 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a140a1249e7 2026-04-26 22:09:19.081 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004c01490148005e0020a4ba0015001200130000031a00000000000009020402a51e9a6e000080ff000000ff00004000042cdabe 2026-04-26 22:09:19.339 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:09:39.118 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:09:38Z&rnr=40130&hash=e17e585254ca1728a6211c148d9e369d913986a60018336412a50714045c7779 2026-04-26 22:09:42.111 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:09:41Z&rnr=53523&hash=fb2b190182bb4f43f7d85d472ac1152082f31f3850d73ec8b5e72b457ef7ade3 2026-04-26 22:10:18.807 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a140b124877 2026-04-26 22:10:19.076 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004b014a0148005e001fa4ba0015001200130000031a00000000000009020402a51e9a6e000080ff000000ff00004000042c36e2 2026-04-26 22:10:19.334 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:10:39.116 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:10:38Z&rnr=201&hash=8fcd134c501102beaecda5144ed22355855f05bb543cd6c33d56e83634b8a32a 2026-04-26 22:10:42.112 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:10:41Z&rnr=14307&hash=d684df03c7d886db254858fd2c98d543ea18fe4d269a239af201b586e63eb981 2026-04-26 22:11:18.802 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a140c124a47 2026-04-26 22:11:19.070 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004b014a0148005e001ea4c40015001200130000031a00000000000009020402a51e9a6e000080ff000000ff00004000042c86d4 2026-04-26 22:11:19.329 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:11:39.120 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:11:38Z&rnr=60096&hash=7a629e569426b9468492d0e3d6e801dbab11ed3399cf9cd31a67236d15cd4ba5 2026-04-26 22:11:42.112 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:11:41Z&rnr=5927&hash=7d1730f2894887b8a07b424d346d9937f3bce0d1454ac8525bd833a3ee531012 2026-04-26 22:12:18.817 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a140d124bd7 2026-04-26 22:12:19.086 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004b014a0148005e001ea4c40015001200130000031a00000000000009020402a51e9a6e000080ff000000ff00004000042c86d4 2026-04-26 22:12:19.345 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:12:39.121 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:12:38Z&rnr=57338&hash=ef9ce8256bf0e2dd5250f1bf4fd608f1ea6dcfcd38eae32daff6b166dfefcd7d 2026-04-26 22:12:42.111 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:12:41Z&rnr=4315&hash=4611fd287137924deeaf451b7d460a4be9801b45894bd7cd15976b9a193720aa 2026-04-26 22:13:18.812 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a140e124b27 2026-04-26 22:13:19.081 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004b014a0148005e001ca4ce0015001200130000031a00000000000009020402a51e9a6e000080ff000000ff00004000042cd496 2026-04-26 22:13:19.339 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:13:39.124 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:13:38Z&rnr=54225&hash=327ce9eba7135c97700e941d6f9373ee06ad0b4fd6267b54884760c7599d4344 2026-04-26 22:13:42.218 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:13:41Z&rnr=57055&hash=93814fd5609121b7712fe5ce3b90a402c10b43b9d13d5f6cdb4cde4af5daeaef 2026-04-26 22:14:18.807 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a140f124ab7 2026-04-26 22:14:19.076 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004a014a0148005e001ba4d80015001200130000031a00000000000009020402a51e9a6e00008100000000ff00004000042c8bb4 2026-04-26 22:14:19.334 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:14:39.122 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:14:38Z&rnr=3410&hash=a2096f2f26896a93c4ee4661933f79cd4adaeaf19406a62e4736ba2d0c5eaa7e 2026-04-26 22:14:42.112 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:14:41Z&rnr=12745&hash=df4bad75ae7998d0972d4a32039d80521edcee8c89f6d8a325bad749efed54b9 2026-04-26 22:15:18.822 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1410124287 2026-04-26 22:15:19.091 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004a014a0148005e001ba4d80015001200130000031a00000000000009020402a51e9a6e00008100000000ff00004000042c8bb4 2026-04-26 22:15:19.350 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:15:24.011 - info: host.Pi5 instance system.adapter.dwd.0 in version "2.8.5" started with pid 1921713 2026-04-26 22:15:25.164 - info: dwd.0 (1921713) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v20.19.5, js-controller: 7.0.7 2026-04-26 22:15:25.573 - info: dwd.0 (1921713) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2026-04-26 22:15:26.083 - info: host.Pi5 instance system.adapter.dwd.0 having pid 1921713 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2026-04-26 22:15:39.116 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:15:38Z&rnr=39260&hash=d511c04a6d691ff3796c9642951b8410690b73eeeaf8bf9f0b4a755e658c78a6 2026-04-26 22:15:42.111 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:15:41Z&rnr=1272&hash=86d494e9561c1e1e403744b89d9ce943bd827f973faa9d0d6f82f04b261b1bfe 2026-04-26 22:16:18.817 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1411124317 2026-04-26 22:16:19.086 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004a014a0148005e001aa4e20015001200130000031a00000000000009020402a5469a6e00008100000000ff00004000042cc3a3 2026-04-26 22:16:19.345 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:16:39.116 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:16:38Z&rnr=46877&hash=66a693988dbc0cc5a460dd39197496667b841182d0a6194a059598d760f50d19 2026-04-26 22:16:42.111 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:16:41Z&rnr=27710&hash=bd697f6328a0ec2a1c9295c7735804eee247cc9a4d16aaf372cc45b133ea7483 2026-04-26 22:17:18.812 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a14121243e7 2026-04-26 22:17:19.081 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004a014a0148005e001aa4e20015001200130000031a00000000000009020402a5469a6e00008100000000ff00004000042cc3a3 2026-04-26 22:17:19.340 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:17:39.117 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:17:38Z&rnr=2072&hash=faaa5b48394fae8475f69963de80a6f8cf1e5b529bd5e949b9919524b0b86707 2026-04-26 22:17:42.113 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:17:41Z&rnr=49852&hash=700cef37dc50de38a48a99d34cdb5c0e8531f9516d21d90862d13af367cdb5b1 2026-04-26 22:18:18.807 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1413124277 2026-04-26 22:18:19.076 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 010332004a014a0148005e001aa4e20015001200130000031a00000000000009020402a5469a6e00008100000000ff00004000042cc3a3 2026-04-26 22:18:19.335 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:18:39.117 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:18:38Z&rnr=29548&hash=27e25a3e7cddea73449f1a96516de1c6b9363ee8d94c24920e1c4fbdf950a4ce 2026-04-26 22:18:42.113 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:18:41Z&rnr=35757&hash=9a6e05d2e07870095d17e90162358e2051c0749509e10e0b2e1812a6d58ad576 2026-04-26 22:19:18.823 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1414124047 2026-04-26 22:19:19.092 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 0103320049014a0148005e0019a4e20015001200130000031a00000000000009020402a5469a6e00008101000000ff00004000042cbaaf 2026-04-26 22:19:19.371 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:19:39.116 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:19:38Z&rnr=32245&hash=5abb137adc6a55591ad6a85e29b8fb908dc72fd75647a7b44c6cd197912bd9a7 2026-04-26 22:19:42.115 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:19:41Z&rnr=49609&hash=82f9622a07472d8a7a64951407cba05a31c397fe3b54047c2bed52c6a617400a 2026-04-26 22:20:00.956 - info: host.Pi5 iobroker add shelly auto --host Pi5 --debug 2026-04-26 22:20:01.916 - info: host.Pi5 iobroker host.Pi5 create instance shelly 2026-04-26 22:20:01.922 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.alive created 2026-04-26 22:20:01.925 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.connected created 2026-04-26 22:20:01.930 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.compactMode created 2026-04-26 22:20:01.937 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.cpu created 2026-04-26 22:20:01.952 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.cputime created 2026-04-26 22:20:01.955 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.memHeapUsed created 2026-04-26 22:20:01.959 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.memHeapTotal created 2026-04-26 22:20:01.966 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.memRss created 2026-04-26 22:20:01.973 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.uptime created 2026-04-26 22:20:01.977 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.inputCount created 2026-04-26 22:20:01.980 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.outputCount created 2026-04-26 22:20:01.983 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.eventLoopLag created 2026-04-26 22:20:01.987 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.sigKill created 2026-04-26 22:20:01.990 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1.logLevel created 2026-04-26 22:20:01.997 - info: host.Pi5 iobroker host.Pi5 object shelly.1 created 2026-04-26 22:20:01.999 - info: host.Pi5 iobroker host.Pi5 object shelly.1.info created 2026-04-26 22:20:02.002 - info: host.Pi5 iobroker host.Pi5 object shelly.1.info.connection created 2026-04-26 22:20:02.004 - info: host.Pi5 iobroker host.Pi5 object shelly.1.info.update created 2026-04-26 22:20:02.008 - info: host.Pi5 iobroker host.Pi5 object shelly.1.info.downloadScripts created 2026-04-26 22:20:02.011 - info: host.Pi5 iobroker host.Pi5 object shelly.1.ble created 2026-04-26 22:20:02.013 - info: host.Pi5 iobroker host.Pi5 Set default value of shelly.1.info.connection: false 2026-04-26 22:20:02.018 - info: host.Pi5 iobroker host.Pi5 object system.adapter.shelly.1 created 2026-04-26 22:20:03.029 - info: host.Pi5 iobroker exit 0 2026-04-26 22:20:18.818 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a14151241d7 2026-04-26 22:20:19.087 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 0103320049014a0148005e0019a4e20015001200130000031a00000000000009020402a5469a6e00008101000000ff00004000042cbaaf 2026-04-26 22:20:19.345 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:20:39.152 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:20:38Z&rnr=36945&hash=fd11dd95f392056c32756eca06d5b02eafe85c6a86ad15b158b48486d4e3b242 2026-04-26 22:20:42.115 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:20:41Z&rnr=6592&hash=be9aa0f151734bb606d128b558d7b0f738afeb36508842b28842e0ecd4f316fb 2026-04-26 22:21:09.352 - info: host.Pi5 "system.adapter.shelly.1" enabled 2026-04-26 22:21:10.215 - info: host.Pi5 instance system.adapter.shelly.1 in version "10.6.1" started with pid 1922051 2026-04-26 22:21:11.605 - info: shelly.1 (1922051) starting. Version 10.6.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v20.19.5, js-controller: 7.0.7 2026-04-26 22:21:11.747 - info: shelly.1 (1922051) Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0) 2026-04-26 22:21:18.813 - info: bydhvs.0 (1365522) Received, Packet: 1 Data: 0103cc50303330543032305a323230363037313432397878787878031a0313031f00010014020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031f010c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001a041a1416124127 2026-04-26 22:21:19.082 - info: bydhvs.0 (1365522) Received, Packet: 2 Data: 0103320049014a0148005e0019a4e20015001200130000031a00000000000009020402a5469a6e00008101000000ff00004000042cbaaf 2026-04-26 22:21:19.340 - info: bydhvs.0 (1365522) Received, Packet: 3 Data: 01030600140200000010ce 2026-04-26 22:21:39.118 - info: nuki.0 (1363897) Bridge Info requested: http://192.168.4.89:8080/info?ts=2026-04-26T20:21:38Z&rnr=26492&hash=62051390669c23340b7ecdca6845991d360927b1dbf4075d3b44d8a0e63805aa 2026-04-26 22:21:42.113 - info: nuki.0 (1363897) Lock list requested: http://192.168.4.89:8080/list?ts=2026-04-26T20:21:41Z&rnr=42639&hash=9cb30c897ee3090452b4e0404018e93474a5a428d2213a2cf6775d4601eb80ef pi@Pi5:~ $ -
Das werde ich wohl oder übel auf morgen verschieben müssen. Ich morgen früh raus. Danke.
-
Ich habe Node.js 22.22.1 auf dem System. Im Shelly 2PM Gen4 habe ich den Geräteschutz aus, und unter dem Register MQTT die Authentifizierungsdaten für meinen ioBroker im Shelly Adapter eingetragen.
Ich habe gleich zwei Shelly PM2 Gen4 versucht auf diese Weise einzubinden. Offenbar verbindet sich jedoch keiner der Shelly (Firmware 1.7.5) mit dem Adapter im ioBroker. Das Symbol bleibt gelb.
Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..
-
@legro
Wenn da gar nix im Log steht dann hast du wahrscheinlich eine fehlerhafte Einstellung AM SHELLY.
(Oder dein Netzwerk blockiert die Kommunikation)Der Shelly Adapter bleibt gelb wenn kein Gerät verbunden ist.
Bitte prüfe die mqtt Einstellungsseite.
- mqtt am Shelly enabled?
- ip der ioBroker Hosts richtig eingetragen?
- Portnummer richtig eingetragen (der ioBroker Shelly Adapter verwendet per defautl NICHT den mqtt Default) ("Listening on 0.0.0.0:1882")
- Shelly nach jeder Änderung an den mqtt Einstellungen neu gestartet?
-
Ich habe Node.js 22.22.1 auf dem System. Im Shelly 2PM Gen4 habe ich den Geräteschutz aus, und unter dem Register MQTT die Authentifizierungsdaten für meinen ioBroker im Shelly Adapter eingetragen.
Ich habe gleich zwei Shelly PM2 Gen4 versucht auf diese Weise einzubinden. Offenbar verbindet sich jedoch keiner der Shelly (Firmware 1.7.5) mit dem Adapter im ioBroker. Das Symbol bleibt gelb.
Ich habe Node.js 22.22.1 auf dem System.
Aus deinem Log:
2026-04-26 22:21:11.605 - info: shelly.1 (1922051) starting. Version 10.6.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v20.19.5, js-controller: 7.0.7Da wird node v20.19.5 gefunden. Davon abgesehen ist Node.js 22.22.1 auch nicht mehr aktuell. Also Kiste losgelöst vom shelly-Adapter auf Stand bringen.
-
@legro
Wenn da gar nix im Log steht dann hast du wahrscheinlich eine fehlerhafte Einstellung AM SHELLY.
(Oder dein Netzwerk blockiert die Kommunikation)Der Shelly Adapter bleibt gelb wenn kein Gerät verbunden ist.
Bitte prüfe die mqtt Einstellungsseite.
- mqtt am Shelly enabled?
- ip der ioBroker Hosts richtig eingetragen?
- Portnummer richtig eingetragen (der ioBroker Shelly Adapter verwendet per defautl NICHT den mqtt Default) ("Listening on 0.0.0.0:1882")
- Shelly nach jeder Änderung an den mqtt Einstellungen neu gestartet?
Ich habe das alles unzählige Male (neu) eingegeben, überprüft, Reboot durchgeführt, .. Nichts hilft.
Die Verbindung zu den Shellys ist jedoch ziemlich wackelig. Ich muss mehrmals die Eingaben wiederholen, bis sie endlich übernommen werden. Oft nimmt er die Daten erst nach einem Reboot an usw.
Was Node.js betrifft ..
Ich betreue eine weitere ioBroker Installation. Hier funktioniert das Ganze glücklicherweise - obwohl auch hier Node.js 22.22.1 läuft.
Ich bin ziemlich frustriert.
Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..
-
Ich habe das alles unzählige Male (neu) eingegeben, überprüft, Reboot durchgeführt, .. Nichts hilft.
Die Verbindung zu den Shellys ist jedoch ziemlich wackelig. Ich muss mehrmals die Eingaben wiederholen, bis sie endlich übernommen werden. Oft nimmt er die Daten erst nach einem Reboot an usw.
Was Node.js betrifft ..
Ich betreue eine weitere ioBroker Installation. Hier funktioniert das Ganze glücklicherweise - obwohl auch hier Node.js 22.22.1 läuft.
Ich bin ziemlich frustriert.
-
Auf dem oben erwähnten zweiten System (Pi4) komme ich über VPN und SSH auf den Raspberry, dort funktioniert schließlich alles wie gewünscht. Aber an dem System, wo's klemmt, habe ich keine Terminal-Zugang, dort läuft der ioBroker in einem Docker-Container.
Soll losgelöst heißen, dass ich den Shelly-Adapter zuvor runterwerfen soll?
Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden503
Online32.8k
Benutzer82.9k
Themen1.3m
Beiträge