[gelöst]SONOFF ZigBee 3.0 wird n. in Zigbee eingebunden
-
- du musst unbedingt die panID anpassen - die ist so nicht gut. (16 stellige zahl, nicht 16 mal D
- mach bitte folgendes:
— zigbee Adapter anhalten
— iobroker log löschen
— zigbee Adapter starten
— 120 Sekunden (plus/minus ein paar Sekunden ) warten.
— log herunter laden
— das herunter geladene log hier in code-tags posten.
A.
-
@asgothian
Hallo,
hier die Ausgabe vom log.2025-05-22 22:05:30.312 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 in version "2.0.5" started with pid 13269 2025-05-22 22:05:34.282 - info: zigbee.0 (13269) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.2, js-controller: 7.0.6 2025-05-22 22:05:34.312 - info: zigbee.0 (13269) init localConfig 2025-05-22 22:05:34.323 - info: zigbee.0 (13269) --> transmitPower : normal 2025-05-22 22:05:34.339 - info: zigbee.0 (13269) delete old Backup files. keep only last 10 2025-05-22 22:05:34.344 - info: zigbee.0 (13269) --- creating device debug --- 2025-05-22 22:05:34.346 - info: zigbee.0 (13269) Starting Adapter npm ... 2025-05-22 22:05:34.404 - info: zigbee.0 (13269) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2) 2025-05-22 22:05:34.406 - info: zigbee.0 (13269) Starting Zigbee-Herdsman 2025-05-22 22:05:48.281 - info: host.raspberrypi64bitbookworm "system.adapter.zigbee.0" disabled 2025-05-22 22:05:48.286 - info: host.raspberrypi64bitbookworm stopInstance system.adapter.zigbee.0 (force=false, process=true) 2025-05-22 22:05:48.294 - info: zigbee.0 (13269) Got terminate signal TERMINATE_YOURSELF 2025-05-22 22:05:48.298 - info: zigbee.0 (13269) cleaned everything up... 2025-05-22 22:05:48.299 - info: zigbee.0 (13269) local config saved 2025-05-22 22:05:48.301 - info: zigbee.0 (13269) Saved local configuration data 2025-05-22 22:05:48.302 - info: zigbee.0 (13269) terminating 2025-05-22 22:05:48.304 - info: zigbee.0 (13269) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-05-22 22:05:48.405 - error: zigbee.0 (13269) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17) 2025-05-22 22:05:48.416 - info: zigbee.0 (13269) terminating 2025-05-22 22:05:48.452 - info: host.raspberrypi64bitbookworm stopInstance system.adapter.zigbee.0 send kill signal 2025-05-22 22:05:48.806 - info: zigbee.0 (13269) terminating 2025-05-22 22:05:48.982 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-05-22 22:12:25.154 - info: admin.0 (687) ==> Connected system.user.admin from ::ffff:192.168.178.102 2025-05-22 22:17:25.242 - info: admin.0 (687) <== Disconnect system.user.admin from ::ffff:192.168.178.102 2025-05-22 22:18:55.896 - info: host.raspberrypi64bitbookworm "system.adapter.zigbee.0" enabled 2025-05-22 22:18:57.325 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 in version "2.0.5" started with pid 14090 2025-05-22 22:19:01.371 - info: zigbee.0 (14090) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.2, js-controller: 7.0.6 2025-05-22 22:19:01.402 - info: zigbee.0 (14090) init localConfig 2025-05-22 22:19:01.412 - info: zigbee.0 (14090) --> transmitPower : normal 2025-05-22 22:19:01.429 - info: zigbee.0 (14090) delete old Backup files. keep only last 10 2025-05-22 22:19:01.433 - info: zigbee.0 (14090) --- creating device debug --- 2025-05-22 22:19:01.436 - info: zigbee.0 (14090) Starting Adapter npm ... 2025-05-22 22:19:01.492 - info: zigbee.0 (14090) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2) 2025-05-22 22:19:01.494 - info: zigbee.0 (14090) Starting Zigbee-Herdsman 2025-05-22 22:19:24.177 - info: admin.0 (687) ==> Connected system.user.admin from ::ffff:192.168.178.102 2025-05-22 22:19:24.473 - error: zigbee.0 (14090) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-05-22 22:19:24.475 - error: zigbee.0 (14090) unhandled promise rejection: Cannot read properties of undefined (reading 'CleanupRequired') 2025-05-22 22:19:24.804 - error: zigbee.0 (14090) TypeError: Cannot read properties of undefined (reading 'CleanupRequired') at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:155:97) at Zigbee. (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:20:48) at Zigbee.emit (node:events:536:35) at Zigbee.emit (node:domain:489:12) at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:10953:34) at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:368:37) at processImmediate (node:internal/timers:483:21) 2025-05-22 22:19:24.805 - error: zigbee.0 (14090) Cannot read properties of undefined (reading 'CleanupRequired') 2025-05-22 22:19:24.865 - info: zigbee.0 (14090) cleaned everything up... 2025-05-22 22:19:24.866 - info: zigbee.0 (14090) local config saved 2025-05-22 22:19:24.868 - info: zigbee.0 (14090) Saved local configuration data 2025-05-22 22:19:24.869 - info: zigbee.0 (14090) terminating 2025-05-22 22:19:24.873 - warn: zigbee.0 (14090) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-05-22 22:19:24.920 - error: zigbee.0 (14090) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17) 2025-05-22 22:19:24.927 - info: zigbee.0 (14090) terminating 2025-05-22 22:19:25.007 - info: zigbee.0 (14090) List of port: [{"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"2e3882639474ef11b58fd08c8fcc3fa0","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_2e3882639474ef11b58fd08c8fcc3fa0-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"}] 2025-05-22 22:19:25.382 - info: zigbee.0 (14090) terminating 2025-05-22 22:19:25.562 - error: host.raspberrypi64bitbookworm Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: TypeError: Cannot read properties of undefined (reading 'CleanupRequired') 2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:155:97) 2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Zigbee. (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:20:48) 2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Zigbee.emit (node:events:536:35) 2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Zigbee.emit (node:domain:489:12) 2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:10953:34) 2025-05-22 22:19:25.564 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:368:37) 2025-05-22 22:19:25.564 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at processImmediate (node:internal/timers:483:21) 2025-05-22 22:19:25.564 - error: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-05-22 22:19:25.564 - info: host.raspberrypi64bitbookworm Restart adapter system.adapter.zigbee.0 because enabled 2025-05-22 22:19:56.435 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 in version "2.0.5" started with pid 14168 2025-05-22 22:20:00.397 - info: zigbee.0 (14168) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.2, js-controller: 7.0.6 2025-05-22 22:20:00.428 - info: zigbee.0 (14168) init localConfig 2025-05-22 22:20:00.441 - info: zigbee.0 (14168) --> transmitPower : normal 2025-05-22 22:20:00.460 - info: zigbee.0 (14168) delete old Backup files. keep only last 10 2025-05-22 22:20:00.465 - info: zigbee.0 (14168) --- creating device debug --- 2025-05-22 22:20:00.467 - info: zigbee.0 (14168) Starting Adapter npm ... 2025-05-22 22:20:00.542 - info: zigbee.0 (14168) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2) 2025-05-22 22:20:00.544 - info: zigbee.0 (14168) Starting Zigbee-Herdsman 2025-05-22 22:20:26.959 - info: zigbee.0 (14168) Unable to obtain herdsman settings 2025-05-22 22:20:27.179 - error: zigbee.0 (14168) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) 2025-05-22 22:20:27.181 - error: zigbee.0 (14168) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-05-22 22:20:27.182 - error: zigbee.0 (14168) unhandled promise rejection: undefined 2025-05-22 22:20:27.183 - error: zigbee.0 (14168) undefined 2025-05-22 22:20:27.240 - info: zigbee.0 (14168) cleaned everything up... 2025-05-22 22:20:27.241 - info: zigbee.0 (14168) local config saved 2025-05-22 22:20:27.243 - info: zigbee.0 (14168) Saved local configuration data 2025-05-22 22:20:27.244 - info: zigbee.0 (14168) terminating 2025-05-22 22:20:27.247 - warn: zigbee.0 (14168) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-05-22 22:20:27.256 - error: zigbee.0 (14168) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17) 2025-05-22 22:20:27.263 - info: zigbee.0 (14168) terminating 2025-05-22 22:20:27.749 - info: zigbee.0 (14168) terminating 2025-05-22 22:20:27.965 - error: host.raspberrypi64bitbookworm Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2025-05-22 22:20:27.966 - error: host.raspberrypi64bitbookworm Caught by controller[1]: Error herdsman start 2025-05-22 22:20:27.967 - error: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-05-22 22:20:27.967 - info: host.raspberrypi64bitbookworm Restart adapter system.adapter.zigbee.0 because enabled 2025-05-22 22:20:58.998 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 in version "2.0.5" started with pid 14246 2025-05-22 22:20:59.706 - info: admin.0 (687) <== Disconnect system.user.admin from ::ffff:192.168.178.102 2025-05-22 22:21:03.058 - info: zigbee.0 (14246) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.2, js-controller: 7.0.6 2025-05-22 22:21:03.090 - info: zigbee.0 (14246) init localConfig 2025-05-22 22:21:03.100 - info: zigbee.0 (14246) --> transmitPower : normal 2025-05-22 22:21:03.116 - info: zigbee.0 (14246) delete old Backup files. keep only last 10 2025-05-22 22:21:03.122 - info: zigbee.0 (14246) --- creating device debug --- 2025-05-22 22:21:03.123 - info: zigbee.0 (14246) Starting Adapter npm ... 2025-05-22 22:21:03.181 - info: zigbee.0 (14246) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2) 2025-05-22 22:21:03.184 - info: zigbee.0 (14246) Starting Zigbee-Herdsman 2025-05-22 22:21:29.603 - info: zigbee.0 (14246) Unable to obtain herdsman settings 2025-05-22 22:21:29.785 - error: zigbee.0 (14246) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) 2025-05-22 22:21:29.788 - error: zigbee.0 (14246) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-05-22 22:21:29.789 - error: zigbee.0 (14246) unhandled promise rejection: undefined 2025-05-22 22:21:29.790 - error: zigbee.0 (14246) undefined 2025-05-22 22:21:29.852 - info: zigbee.0 (14246) cleaned everything up... 2025-05-22 22:21:29.854 - info: zigbee.0 (14246) local config saved 2025-05-22 22:21:29.856 - info: zigbee.0 (14246) Saved local configuration data 2025-05-22 22:21:29.857 - info: zigbee.0 (14246) terminating 2025-05-22 22:21:29.859 - warn: zigbee.0 (14246) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-05-22 22:21:29.867 - error: zigbee.0 (14246) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17) 2025-05-22 22:21:29.875 - info: zigbee.0 (14246) terminating 2025-05-22 22:21:30.363 - info: zigbee.0 (14246) terminating 2025-05-22 22:21:30.561 - error: host.raspberrypi64bitbookworm Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2025-05-22 22:21:30.562 - error: host.raspberrypi64bitbookworm Caught by controller[0]: Error herdsman start 2025-05-22 22:21:30.563 - error: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-05-22 22:21:30.563 - info: host.raspberrypi64bitbookworm Restart adapter system.adapter.zigbee.0 because enabled 2025-05-22 22:21:30.563 - warn: host.raspberrypi64bitbookworm Do not restart adapter system.adapter.zigbee.0 because restart loop detectedDie pan id habe ich geändert: 1437834385923494
@högi So ich habe jetzt noch folgendes probiert.
1.) aktuelle Firmware auf den Sonoff coordinator aufgespielt.
2.) Kpl neu raspberry pi os lite (64bit) Debian Bookworm aufgesetzt und
Iobroker mit : curl -sSLf https://iobroker.net/install.sh | bash -
installiert.
3.) Zigbee Adapter 2.0.5 installiert.
4.) Coordinator wird unter /dev/serial/by-id angezeigt:
usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_2e3882639474ef11b58fd08c8fcc3fa0-if00-port0
5.)Pan ID 16 stellig vergeben.
6.) Zigbee Adapter Version 2.0.4 probiert.
7.) USB 0,5 m Verlängerung benutzt
8.)Raspberry USB 2.0 und USB 3.0 benutzt.Alles hat nichts geholfen. Instanz bleibt rot.
Bin mit meinem Latein am Ende.
-
@högi du musst schon systematisch vorgehen. Bei dem geposteten Log ist dieser Eintrag entscheidend:
2025-05-22 22:21:29.785 - error: zigbee.0 (14246) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)Dieses bedeutet das
- die serielle Schnittstelle geöffnet wurde (erfolgreich)
- keine Kommunikation zur Firmware entsteht.
Genau das musst du dir bei den einzelnen Versuchen anschauen.
Bevor du da aber loslegst, bitte noch einmal verifizieren :
Bitte noch einmal verifizieren - hast du einen Sonoff Dongle P oder Dongle E (steht auf dem Gerät selber drauf.
A.
-
@asgothian Ich habe den Sonoff Dongle P
-
@högi sagte in SONOFF ZigBee 3.0 wird nicht in Iobroker Zigbee eingebunden:
@asgothian Ich habe den Sonoff Dongle P
und welche Firmware hast du da aufgespielt.. zeigmal den link
-
@arteck
Über diesen link:https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20240710.zipUnd nach dieser Anleitung die Firmware aufgespielt:
https://haus-automatisierung.com/hardware/sonoff/2022/01/11/sonoff-zigbee-usb-dongle-plus.html -
@Högi
das der Zigbee-Stick in Verbindung mit der pivccu3 nicht gefunden wurde, hat ich auch schon.
Bei mir hat der CUx-Daemon von der pivccu3 die USB-Schnittstelle für den Zigbee-Stick blockiert.
Dies kann man verhindern, wenn man in der Pivccu3-Oberfläche in der Systemsteuerung unter CUx-Daemon das Setup anwählt und dort am Ende folgenden Eintrag ergänzt:TTYASSIGN=ttyACM0:NC
und das Setup dann speichert.
Danach alles neu starten.
Ich hoffe es hilft. -
@walter-weiss Ich habe das auch probiert und es hat sich nichts geändert.
Hatte ja mal testweise System nur mit Iobroker aufgesetzt und der Stick ließ sich
auch nicht einbinden.
Ich habe den Stick über Amazon gekauft und in den Rezessionen gelesen, das
auch defekte Sticks auch ausgeliefert wurden.
Bekomme Montag einen neuen Stick.
Dann bin ich gespannt. -
@högi
So Problem gelöst und danke an Walter Weiss.
Das mit dem CUx-Daemon von der pivccu3 hat mich zur Lösung geführt.
Aber zuvor, der erste Sonoff coordinator war wirklich kaputt.Nach dem ich den neuen Sonoff Stick in die Zigbee Instanz einbinden wollte war die Enttäuschung groß und ich wollte schon allen hinschmeißen.
Als ich aber den CUx-Daemon von der pivccu3 gestoppt habe, siehe da
den Zigbee Adapter wurde grün.Danach habe ich TTYASSIGN=ttyACM0:NC im CUx-Daemon eingetragen
aber das hat auch nicht funktioniert.
Danach TTYASSIGN=ttyttyUSB0 :NC eingetragen und alles läuft reibungslos.
Mein Gott schwere GeburtDanke an Alle
-
@högi
Entschuldigung, ich hätte noch darauf hinweisen sollen, dass auf unterschiedlichen Systemen die USB-Schnittstellen unterschiedlich benannt werden. ich poste nicht so oft. Aber wieder was dazugelernt. Aber schön dass es geklappt hat.
