Tester für Zigbee Adapter 2.0.x gesucht
-
@homoran Das ist Absicht. Succcess heisst das er erfolg hatte.
-
@asgothian sagte in Tester für Zigbee Adapter 2.0.x gesucht:
@homoran Das ist Absicht. Succcess heisst das er erfolg hatte.
dann ist aber
Errorin der Titelleiste fehl am Platz -
@homoran Jo. wird in der latest 2.0.5 weg sein
-
Hallo,
ich habe von einem USB-Zigbee-Adapter CC2531 auf einen SLZB-06 Adapter umgestellt, der über WLAN laufen soll. Leider bekomme ich das unter meinem Zigbee Adapter nicht zum Laufen. Über USB bekomme ich den Adapter auch nicht zum Laufen.Ich habe den Adapter bereits mehrfach gelöscht und neu eingerichtet. Das alte zigbee.0 Verzeichnis habe ich auch gelöscht. Neue FW-Updates für den SLZB-06 habe ich auch eingespielt.
Folgende Einstellungen habe ich im Adapter gesetzt:
Die Log-Datei für die Instanz sieht wie folgt aus:
2025-03-20 11:48:33.507 - warn: fullybrowser.0 (67164) [REST] 192.168.178.152: Sending command get axiosGetDevicesInfo failed: No response 2025-03-20 11:48:34.254 - info: host.iobroker instance system.adapter.zigbee.0 in version "2.0.4" started with pid 68617 2025-03-20 11:48:35.902 - debug: zigbee.0 (68617) Redis Objects: Use Redis connection: 127.0.0.1:9001 2025-03-20 11:48:35.935 - debug: zigbee.0 (68617) Objects client ready ... initialize now 2025-03-20 11:48:35.979 - debug: zigbee.0 (68617) Objects create System PubSub Client 2025-03-20 11:48:35.980 - debug: zigbee.0 (68617) Objects create User PubSub Client 2025-03-20 11:48:36.017 - debug: zigbee.0 (68617) Objects client initialize lua scripts 2025-03-20 11:48:36.033 - debug: zigbee.0 (68617) Objects connected to redis: 127.0.0.1:9001 2025-03-20 11:48:36.062 - debug: zigbee.0 (68617) Redis States: Use Redis connection: 127.0.0.1:9000 2025-03-20 11:48:36.115 - debug: zigbee.0 (68617) States create System PubSub Client 2025-03-20 11:48:36.116 - debug: zigbee.0 (68617) States create User PubSub Client 2025-03-20 11:48:36.168 - debug: zigbee.0 (68617) States connected to redis: 127.0.0.1:9000 2025-03-20 11:48:36.198 - debug: zigbee.0 (68617) Plugin sentry Initialize Plugin (enabled=true) 2025-03-20 11:48:36.443 - info: zigbee.0 (68617) starting. Version 2.0.4 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.18.0, js-controller: 7.0.6 2025-03-20 11:48:36.453 - info: zigbee.0 (68617) init localConfig 2025-03-20 11:48:36.458 - error: zigbee.0 (68617) 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-03-20 11:48:36.458 - error: zigbee.0 (68617) unhandled promise rejection: Cannot read properties of undefined (reading 'map') 2025-03-20 11:48:36.520 - error: zigbee.0 (68617) TypeError: Cannot read properties of undefined (reading 'map') at ZigbeeController.ByteArrayToString (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:81:21) at ZigbeeController.configure (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:126:55) at Zigbee.onReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:216:27) at Zigbee. (/opt/iobroker/node_modules/iobroker.zigbee/main.js:70:37) at Zigbee.emit (node:events:531:35) at Zigbee.emit (node:domain:488:12) at Zigbee._callReadyHandler (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11727:18) at Zigbee._initAdapter (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11706:18) 2025-03-20 11:48:36.520 - error: zigbee.0 (68617) Cannot read properties of undefined (reading 'map') 2025-03-20 11:48:36.530 - info: zigbee.0 (68617) cleaned everything up... 2025-03-20 11:48:36.531 - info: zigbee.0 (68617) local config saved 2025-03-20 11:48:36.531 - info: zigbee.0 (68617) Saved local configuration data 2025-03-20 11:48:36.532 - info: zigbee.0 (68617) terminating 2025-03-20 11:48:36.532 - debug: zigbee.0 (68617) Plugin sentry destroyed 2025-03-20 11:48:36.532 - warn: zigbee.0 (68617) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-03-20 11:48:36.533 - error: zigbee.0 (68617) unable to call extension Method stop: Cannot read properties of undefined (reading 'database') 2025-03-20 11:48:36.534 - error: zigbee.0 (68617) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:668:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:643:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1111:17) 2025-03-20 11:48:36.534 - warn: zigbee.0 (68617) Failed to stop zigbee during startup 2025-03-20 11:48:36.535 - info: zigbee.0 (68617) terminating 2025-03-20 11:48:36.535 - error: zigbee.0 (68617) 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-03-20 11:48:36.535 - error: zigbee.0 (68617) unhandled promise rejection: Cannot read properties of undefined (reading 'database') 2025-03-20 11:48:36.535 - error: zigbee.0 (68617) TypeError: Cannot read properties of undefined (reading 'database') at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:343:27) at DeviceEvent.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:30:25) at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:329:54) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:636:24) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1111:41) at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-03-20 11:48:36.536 - error: zigbee.0 (68617) Cannot read properties of undefined (reading 'database') 2025-03-20 11:48:37.034 - info: zigbee.0 (68617) terminating 2025-03-20 11:48:37.147 - error: host.iobroker 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-03-20 11:48:37.147 - error: host.iobroker Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'map') 2025-03-20 11:48:37.147 - error: host.iobroker Caught by controller[1]: at ZigbeeController.ByteArrayToString (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:81:21) 2025-03-20 11:48:37.147 - error: host.iobroker Caught by controller[1]: at ZigbeeController.configure (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:126:55) 2025-03-20 11:48:37.147 - error: host.iobroker Caught by controller[1]: at Zigbee.onReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:216:27) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[1]: at Zigbee. (/opt/iobroker/node_modules/iobroker.zigbee/main.js:70:37) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[1]: at Zigbee.emit (node:events:531:35) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[1]: at Zigbee.emit (node:domain:488:12) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[1]: at Zigbee._callReadyHandler (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11727:18) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[1]: at Zigbee._initAdapter (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11706:18) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[2]: 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-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: TypeError: Cannot read properties of undefined (reading 'database') 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:343:27) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: at DeviceEvent.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:30:25) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:329:54) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:636:24) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1111:41) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-03-20 11:48:37.148 - error: host.iobroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-03-20 11:48:37.148 - info: host.iobroker Restart adapter system.adapter.zigbee.0 because enabledMOD-EDIT: Code in code-tags gesetzt!
Chat-GPT hat viele Vorschläge gemacht, konnte aber letztendlich nicht weiterhelfen.
Habt ihr eine Idee, was ich noch tun kann?!
VG Thorsten
-
@thokai16 Versuche: 1. Adapter löschen,2.Ordner Zigbee.0 unter iobroker/iobroker-data löschen. Adapter neu installieren PAN-ID und Erweiterte PAN-ID ändern (egal auf was). tcp://..... als Com-Anschlussname. Speichern und dann Adapter starten. mit 2.x Version habe ich noch nicht probiert. Auf 1.10.14 läuft alles
-
@thokai16 sagte in Tester für Zigbee Adapter 2.0.x gesucht:
Hallo,
ich habe von einem USB-Zigbee-Adapter CC2531 auf einen SLZB-06 Adapter umgestellt, der über WLAN laufen soll. Leider bekomme ich das unter meinem Zigbee Adapter nicht zum Laufen. Über USB bekomme ich den Adapter auch nicht zum Laufen.Ich habe den Adapter bereits mehrfach gelöscht und neu eingerichtet. Das alte zigbee.0 Verzeichnis habe ich auch gelöscht. Neue FW-Updates für den SLZB-06 habe ich auch eingespielt.
Folgende Einstellungen habe ich im Adapter gesetzt:
Die Log-Datei für die Instanz sieht wie folgt aus:
2025-03-20 11:48:33.507 - warn: fullybrowser.0 (67164) [REST] 192.168.178.152: Sending command get axiosGetDevicesInfo failed: No response 2025-03-20 11:48:34.254 - info: host.iobroker instance system.adapter.zigbee.0 in version "2.0.4" started with pid 68617 2025-03-20 11:48:35.902 - debug: zigbee.0 (68617) Redis Objects: Use Redis connection: 127.0.0.1:9001 2025-03-20 11:48:35.935 - debug: zigbee.0 (68617) Objects client ready ... initialize now 2025-03-20 11:48:35.979 - debug: zigbee.0 (68617) Objects create System PubSub Client 2025-03-20 11:48:35.980 - debug: zigbee.0 (68617) Objects create User PubSub Client 2025-03-20 11:48:36.017 - debug: zigbee.0 (68617) Objects client initialize lua scripts 2025-03-20 11:48:36.033 - debug: zigbee.0 (68617) Objects connected to redis: 127.0.0.1:9001 2025-03-20 11:48:36.062 - debug: zigbee.0 (68617) Redis States: Use Redis connection: 127.0.0.1:9000 2025-03-20 11:48:36.115 - debug: zigbee.0 (68617) States create System PubSub Client 2025-03-20 11:48:36.116 - debug: zigbee.0 (68617) States create User PubSub Client 2025-03-20 11:48:36.168 - debug: zigbee.0 (68617) States connected to redis: 127.0.0.1:9000 2025-03-20 11:48:36.198 - debug: zigbee.0 (68617) Plugin sentry Initialize Plugin (enabled=true) 2025-03-20 11:48:36.443 - info: zigbee.0 (68617) starting. Version 2.0.4 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.18.0, js-controller: 7.0.6 2025-03-20 11:48:36.453 - info: zigbee.0 (68617) init localConfig 2025-03-20 11:48:36.458 - error: zigbee.0 (68617) 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-03-20 11:48:36.458 - error: zigbee.0 (68617) unhandled promise rejection: Cannot read properties of undefined (reading 'map') 2025-03-20 11:48:36.520 - error: zigbee.0 (68617) TypeError: Cannot read properties of undefined (reading 'map') at ZigbeeController.ByteArrayToString (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:81:21) at ZigbeeController.configure (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:126:55) at Zigbee.onReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:216:27) at Zigbee. (/opt/iobroker/node_modules/iobroker.zigbee/main.js:70:37) at Zigbee.emit (node:events:531:35) at Zigbee.emit (node:domain:488:12) at Zigbee._callReadyHandler (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11727:18) at Zigbee._initAdapter (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11706:18) 2025-03-20 11:48:36.520 - error: zigbee.0 (68617) Cannot read properties of undefined (reading 'map') 2025-03-20 11:48:36.530 - info: zigbee.0 (68617) cleaned everything up... 2025-03-20 11:48:36.531 - info: zigbee.0 (68617) local config saved 2025-03-20 11:48:36.531 - info: zigbee.0 (68617) Saved local configuration data 2025-03-20 11:48:36.532 - info: zigbee.0 (68617) terminating 2025-03-20 11:48:36.532 - debug: zigbee.0 (68617) Plugin sentry destroyed 2025-03-20 11:48:36.532 - warn: zigbee.0 (68617) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-03-20 11:48:36.533 - error: zigbee.0 (68617) unable to call extension Method stop: Cannot read properties of undefined (reading 'database') 2025-03-20 11:48:36.534 - error: zigbee.0 (68617) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:668:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:643:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1111:17) 2025-03-20 11:48:36.534 - warn: zigbee.0 (68617) Failed to stop zigbee during startup 2025-03-20 11:48:36.535 - info: zigbee.0 (68617) terminating 2025-03-20 11:48:36.535 - error: zigbee.0 (68617) 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-03-20 11:48:36.535 - error: zigbee.0 (68617) unhandled promise rejection: Cannot read properties of undefined (reading 'database') 2025-03-20 11:48:36.535 - error: zigbee.0 (68617) TypeError: Cannot read properties of undefined (reading 'database') at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:343:27) at DeviceEvent.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:30:25) at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:329:54) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:636:24) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1111:41) at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-03-20 11:48:36.536 - error: zigbee.0 (68617) Cannot read properties of undefined (reading 'database') 2025-03-20 11:48:37.034 - info: zigbee.0 (68617) terminating 2025-03-20 11:48:37.147 - error: host.iobroker 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-03-20 11:48:37.147 - error: host.iobroker Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'map') 2025-03-20 11:48:37.147 - error: host.iobroker Caught by controller[1]: at ZigbeeController.ByteArrayToString (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:81:21) 2025-03-20 11:48:37.147 - error: host.iobroker Caught by controller[1]: at ZigbeeController.configure (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:126:55) 2025-03-20 11:48:37.147 - error: host.iobroker Caught by controller[1]: at Zigbee.onReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:216:27) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[1]: at Zigbee. (/opt/iobroker/node_modules/iobroker.zigbee/main.js:70:37) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[1]: at Zigbee.emit (node:events:531:35) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[1]: at Zigbee.emit (node:domain:488:12) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[1]: at Zigbee._callReadyHandler (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11727:18) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[1]: at Zigbee._initAdapter (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11706:18) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[2]: 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-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: TypeError: Cannot read properties of undefined (reading 'database') 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:343:27) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: at DeviceEvent.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:30:25) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:329:54) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:636:24) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1111:41) 2025-03-20 11:48:37.148 - error: host.iobroker Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-03-20 11:48:37.148 - error: host.iobroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-03-20 11:48:37.148 - info: host.iobroker Restart adapter system.adapter.zigbee.0 because enabledMOD-EDIT: Code in code-tags gesetzt!
Chat-GPT hat viele Vorschläge gemacht, konnte aber letztendlich nicht weiterhelfen.
Habt ihr eine Idee, was ich noch tun kann?!
VG Thorsten
Installier bitte den Adapter von Github (siehe Bild), und starte dann nochmal - dann bekommst Du Informationen darüber was nicht passt.
A.
-
Hab ich so gemacht. Folgender Log:
2025-03-20 14:34:24.012 - info: host.iobroker instance system.adapter.zigbee.0 in version "2.0.4" (non-npm: ioBroker/ioBroker.zigbee) started with pid 73487 2025-03-20 14:34:24.799 - debug: zigbee.0 (73487) Redis Objects: Use Redis connection: 127.0.0.1:9001 2025-03-20 14:34:24.825 - debug: zigbee.0 (73487) Objects client ready ... initialize now 2025-03-20 14:34:24.867 - debug: zigbee.0 (73487) Objects create System PubSub Client 2025-03-20 14:34:24.868 - debug: zigbee.0 (73487) Objects create User PubSub Client 2025-03-20 14:34:24.912 - debug: zigbee.0 (73487) Objects client initialize lua scripts 2025-03-20 14:34:24.916 - debug: zigbee.0 (73487) Objects connected to redis: 127.0.0.1:9001 2025-03-20 14:34:24.937 - debug: zigbee.0 (73487) Redis States: Use Redis connection: 127.0.0.1:9000 2025-03-20 14:34:24.995 - debug: zigbee.0 (73487) States create System PubSub Client 2025-03-20 14:34:24.997 - debug: zigbee.0 (73487) States create User PubSub Client 2025-03-20 14:34:25.073 - debug: zigbee.0 (73487) States connected to redis: 127.0.0.1:9000 2025-03-20 14:34:25.127 - debug: zigbee.0 (73487) Plugin sentry Initialize Plugin (enabled=true) 2025-03-20 14:34:25.364 - info: zigbee.0 (73487) starting. Version 2.0.4 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.18.0, js-controller: 7.0.6 2025-03-20 14:34:25.373 - info: zigbee.0 (73487) init localConfig 2025-03-20 14:34:25.376 - info: zigbee.0 (73487) --> transmitPower : normal 2025-03-20 14:34:25.382 - info: zigbee.0 (73487) --- creating device debug --- 2025-03-20 14:34:25.382 - info: zigbee.0 (73487) Starting Adapter npm ... 2025-03-20 14:34:25.408 - debug: zigbee.0 (73487) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2025_03_20-14_34_25.tar.gz success 2025-03-20 14:34:25.408 - info: zigbee.0 (73487) Installed Version: ioBroker/ioBroker.zigbee (Converters 23.6.0 Herdsman 3.4.3) 2025-03-20 14:34:25.409 - debug: zigbee.0 (73487) Starting zigbee-herdsman... 2025-03-20 14:34:25.409 - info: zigbee.0 (73487) Starting Zigbee-Herdsman 2025-03-20 14:34:27.021 - warn: zigbee.0 (73487) Network parameters in Config : panID=2345 channel=11 extendedPanID=3513dededededede 2025-03-20 14:34:27.022 - warn: zigbee.0 (73487) Network parameters on Coordinator: panID=2345 channel=11 extendedPanID=33f2df31004b1200 2025-03-20 14:34:27.166 - error: zigbee.0 (73487) Starting zigbee-herdsman problem : startup failed - configuration-adapter mismatch - see logs above for more information 2025-03-20 14:34:27.166 - error: zigbee.0 (73487) 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-03-20 14:34:27.166 - error: zigbee.0 (73487) unhandled promise rejection: undefined 2025-03-20 14:34:27.167 - error: zigbee.0 (73487) undefined 2025-03-20 14:34:27.180 - info: zigbee.0 (73487) cleaned everything up... 2025-03-20 14:34:27.180 - info: zigbee.0 (73487) local config saved 2025-03-20 14:34:27.180 - info: zigbee.0 (73487) Saved local configuration data 2025-03-20 14:34:27.181 - info: zigbee.0 (73487) terminating 2025-03-20 14:34:27.181 - debug: zigbee.0 (73487) Plugin sentry destroyed 2025-03-20 14:34:27.181 - warn: zigbee.0 (73487) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-03-20 14:34:27.183 - error: zigbee.0 (73487) 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:319: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:1032:17) 2025-03-20 14:34:27.217 - info: zigbee.0 (73487) terminating 2025-03-20 14:34:27.683 - info: zigbee.0 (73487) terminating 2025-03-20 14:34:27.770 - error: host.iobroker Caught by controller[0]: [2025-03-20T13:34:26.975Z] zh:adapter:zstack:manager: Configuration is not consistent with adapter state/backup! 2025-03-20 14:34:27.770 - error: host.iobroker Caught by controller[1]: [2025-03-20T13:34:26.976Z] zh:adapter:zstack:manager: - PAN ID: configured=2345, adapter=2345 2025-03-20 14:34:27.770 - error: host.iobroker Caught by controller[1]: [2025-03-20T13:34:26.976Z] zh:adapter:zstack:manager: - Extended PAN ID: configured=3412dddddddddddd, adapter=00124b0031dff233 2025-03-20 14:34:27.770 - error: host.iobroker Caught by controller[1]: [2025-03-20T13:34:26.976Z] zh:adapter:zstack:manager: - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d 2025-03-20 14:34:27.770 - error: host.iobroker Caught by controller[1]: [2025-03-20T13:34:26.977Z] zh:adapter:zstack:manager: - Channel List: configured=11, adapter=11 2025-03-20 14:34:27.771 - error: host.iobroker Caught by controller[1]: [2025-03-20T13:34:26.977Z] zh:adapter:zstack:manager: Please update configuration to prevent further issues. 2025-03-20 14:34:27.771 - error: host.iobroker Caught by controller[1]: [2025-03-20T13:34:26.977Z] zh:adapter:zstack:manager: If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json. 2025-03-20 14:34:27.771 - error: host.iobroker Caught by controller[1]: [2025-03-20T13:34:26.977Z] zh:adapter:zstack:manager: Re-commissioning your network will require re-pairing of all devices! 2025-03-20 14:34:27.771 - error: host.iobroker Caught by controller[2]: 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-03-20 14:34:27.771 - error: host.iobroker Caught by controller[3]: Error herdsman start 2025-03-20 14:34:27.771 - error: host.iobroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-03-20 14:34:27.771 - info: host.iobroker Restart adapter system.adapter.zigbee.0 because enabled 2025-03-20 14:34:27.771 - warn: host.iobroker Do not restart adapter system.adapter.zigbee.0 because restart loop detected 2025-03-20 14:34:36.902 - warn: fullybrowser.0 (72611) [REST] 192.168.178.152: Sending command get axiosGetDevicesInfo failed: No response 2025-03-20 14:35:00.001 - info: sun2000.0 (72847) Open Connection... 2025-03-20 14:35:09.002 - info: sun2000.0 (72847) Connected Modbus TCP to 192.168.178.113:5200 -
@thokai16 sagte in Tester für Zigbee Adapter 2.0.x gesucht:
2025-03-20 14:34:27.021 - warn: zigbee.0 (73487) Network parameters in Config : panID=2345 channel=11 extendedPanID=3513dededededede
2025-03-20 14:34:27.022 - warn: zigbee.0 (73487) Network parameters on Coordinator: panID=2345 channel=11 extendedPanID=33f2df31004b1200 -
@sphinx_sat said in Tester für Zigbee Adapter 2.0.x gesucht:
@thokai16 Versuche: 1. Adapter löschen,2.Ordner Zigbee.0 unter iobroker/iobroker-data löschen. Adapter neu installieren PAN-ID und Erweiterte PAN-ID ändern (egal auf was). tcp://..... als Com-Anschlussname. Speichern und dann Adapter starten. mit 2.x Version habe ich noch nicht probiert. Auf 1.10.14 läuft alles
Hat leider keinen Erfolg gebracht. Hab es auch mit Version 1.x probiert.
-
@thokai16 Da steht was nicht ok ist- sogar 2 mal:
Network parameters in Config. : panID=2345 channel=11 extendedPanID=3513dededededede Network parameters on Coordinator: panID=2345 channel=11 extendedPanID=33f2df31004b1200 Configuration is not consistent with adapter state/backup! Extended PAN ID: configured=3412dddddddddddd, adapter=00124b0031dff233Korrigier bitte die PanID in deiner Konfiguration
A.
-
Vielen Dank für die Hilfe. Das war die Lösung.
-
@thokai16 Könntest Du bitte mir den Github-Link hier posten? über den Du installiert hast. Vielen Dank
-
@sphinx_sat sagte in Tester für Zigbee Adapter 2.0.x gesucht:
@thokai16 Könntest Du bitte mir den Github-Link hier posten? über den Du installiert hast. Vielen Dank
Keinen GitHub link.
Installation von hier:
-
@asgothian so bin jetzt auch dabei, vorhin die v 2.0.4 runtergeladen.
Hat alles super geklappt musste nur ein paar Datenpunkte ändern der Lichtsensoren und ein paar Schalter. Läuft super mit dem CZC Zigbee Coordinator.
Hast einen super Job hingelegt. Vielen Dank für deine unermüdliche Hilfe und Arbeit.
Herzliche Grüße
Fabio -
@asgothian es wird 2.0.4 installiert. ich dachte die letzte Version ist 2.0.5
-
@sphinx_sat Es ist die 2.0.5 RC4. Intern wird sie noch als 2.0.4 gelabeled, damit wir nicht für reine Git-Versionen die Nummer hochziehen müssen.
A.
-
@asgothian Vielen Dank. Hat alles funktioniert. Eine Frage - kann man die Auswertung vom PAN-ID und Erw. PAN-ID im Log immer sehen? Das ist sehr hilfreich
-
@sphinx_sat sagte in Tester für Zigbee Adapter 2.0.x gesucht:
@asgothian Vielen Dank. Hat alles funktioniert. Eine Frage - kann man die Auswertung vom PAN-ID und Erw. PAN-ID im Log immer sehen? Das ist sehr hilfreich
Das musst du genauer erklären. Warum ist diese Auswertung hilfreich wenn alles nach Plan läuft ?
A.
-
@sphinx_sat also wenn da was nicht passt, steht das immer im Log beim Adapter-Start, und ggf. auch was man tun muss (z.B. bei einem Wechsel der IDs muss eine Backupdatei gelöscht werden - das steht dann da so auch).
Aber bitte immer genau lesen und Bedenken wie das zu dem passt was man gerade vor hatte oder gemacht hat. Zum Beispiel des Löschens der Datei: Wenn man die gar nicht ändert wollte kann man auch wieder die richtige im Adapter eintragen und es passt wieder. -
@asgothian Ich hatte das schon mehrmals mit POE Zigbee, dass die Standardeinstellungen der PAN-ID und Erw. PAN-ID nicht gestimmt haben und deswegen viele Fehlermeldungen kommen. Bei ver. 1.10.14 habe durch löschen zigbee.0 Ordner, NVRAM, Neuinstallation des Adaptes, es doch zum Laufen hinbekommen. Aber in LOG habe ich noch nie die Angaben vom PAN-ID und Erw. PAN-ID vom Coordinator gesehen.
