Neuer ioBroker-Blog online: Monatsrückblick März/April 2026

[hukio]

Gestern wurde plötzlich das log durch Fehlermeldungen des zigbee adapters überschwemmt (logfile > 50 MB). Auch nach Neustart des Adapters ging es weiter. Controller kurz abziehen half auch nicht. Habe dann das letzte backup vom 2 Uhr morgens eingespielt. Zigbee adapter ist grün. Alle Datenpunkte der Geräte in den Objekten, aber kein Gerät hat Verbindung. Wenn ich den Adapter neu starte kommen folgende Fehlermeldungen

2020-11-22 09:05:02.590 - info: host.raspi-3 stopInstance system.adapter.zigbee.0 (force=false, process=true)
2020-11-22 09:05:02.600 - info: host.raspi-3 stopInstance system.adapter.zigbee.0 send kill signal
2020-11-22 09:05:02.601 - info: zigbee.0 (1476) Got terminate signal TERMINATE_YOURSELF
2020-11-22 09:05:02.602 - info: zigbee.0 (1476) cleaned everything up...
2020-11-22 09:05:02.605 - info: zigbee.0 (1476) Zigbee: disabling joining new devices.
2020-11-22 09:05:02.624 - debug: zigbee.0 (1476) Publish available for 0x00158d000312f7cb = false
2020-11-22 09:05:02.886 - info: zigbee.0 (1476) terminating
2020-11-22 09:05:02.888 - info: zigbee.0 (1476) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-11-22 09:05:03.465 - info: host.raspi-3 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-11-22 09:05:05.669 - info: host.raspi-3 instance system.adapter.zigbee.0 started with pid 1502
2020-11-22 09:05:07.143 - debug: zigbee.0 (1502) Redis Objects: Use Redis connection: 127.0.0.1:9001
2020-11-22 09:05:07.193 - debug: zigbee.0 (1502) Objects client ready ... initialize now
2020-11-22 09:05:07.197 - debug: zigbee.0 (1502) Objects create System PubSub Client
2020-11-22 09:05:07.198 - debug: zigbee.0 (1502) Objects create User PubSub Client
2020-11-22 09:05:07.200 - debug: zigbee.0 (1502) Objects client initialize lua scripts
2020-11-22 09:05:07.223 - debug: zigbee.0 (1502) Objects connected to redis: 127.0.0.1:9001
2020-11-22 09:05:07.232 - debug: zigbee.0 (1502) objectDB connected
2020-11-22 09:05:07.235 - debug: zigbee.0 (1502) Redis States: Use Redis connection: 127.0.0.1:6379
2020-11-22 09:05:07.246 - debug: zigbee.0 (1502) States create User PubSub Client
2020-11-22 09:05:07.250 - debug: zigbee.0 (1502) States create System PubSub Client
2020-11-22 09:05:07.263 - debug: zigbee.0 (1502) States connected to redis: 127.0.0.1:6379
2020-11-22 09:05:07.264 - debug: zigbee.0 (1502) statesDB connected
2020-11-22 09:05:08.152 - info: zigbee.0 (1502) starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.19.0, js-controller: 3.1.6
2020-11-22 09:05:08.200 - debug: zigbee.0 (1502) Using zigbee-herdsman with settings: {"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[15],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,11,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-Texas_Instruments_CC2538_USB_CDC-if00","adapter":"zstack"}}
2020-11-22 09:05:08.270 - info: zigbee.0 (1502) Starting Zigbee npm ...
2020-11-22 09:05:08.272 - debug: zigbee.0 (1502) Starting zigbee-herdsman...
2020-11-22 09:05:08.472 - debug: zigbee.0 (1502) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2020_11_22-09_05_08.tar.gz success
2020-11-22 09:05:10.262 - debug: zigbee.0 (1502) zigbee-herdsman started
2020-11-22 09:05:10.263 - info: zigbee.0 (1502) Coordinator firmware version: {"type":"zStack30x","meta":{"transportrev":2,"product":2,"majorrel":2,"minorrel":7,"maintrel":2,"revision":20200211}}
2020-11-22 09:05:10.267 - debug: zigbee.0 (1502) Zigbee network parameters: {"panID":6754,"extendedPanID":"0x00124b001940be8c","channel":15}
2020-11-22 09:05:10.268 - info: zigbee.0 (1502) Disable LED
2020-11-22 09:05:10.272 - info: zigbee.0 (1502) --> transmitPower : high
2020-11-22 09:05:10.280 - info: zigbee.0 (1502) Currently 6 devices are joined:
2020-11-22 09:05:10.281 - debug: zigbee.0 (1502) Publish available for 0x00158d000312f7cb = true
2020-11-22 09:05:10.283 - debug: zigbee.0 (1502) DeviceConfigure 0x00158d000366790e undefined not needed
2020-11-22 09:05:10.283 - debug: zigbee.0 (1502) DeviceConfigure 0x00158d000313c7ae undefined not needed
2020-11-22 09:05:10.283 - debug: zigbee.0 (1502) DeviceConfigure 0x00158d00029a900d undefined not needed
2020-11-22 09:05:10.284 - debug: zigbee.0 (1502) DeviceConfigure 0x00158d000322bd4a undefined not needed
2020-11-22 09:05:10.284 - debug: zigbee.0 (1502) DeviceConfigure 0x00158d0004280bff undefined not needed
2020-11-22 09:05:10.285 - debug: zigbee.0 (1502) DeviceConfigure 0x00158d000312f7cb lumi.sensor_magnet.aq2 not needed
2020-11-22 09:05:10.285 - info: zigbee.0 (1502) 0x00158d000366790e (addr 37593): Not supported (model undefined)(Unknown)
2020-11-22 09:05:10.287 - info: zigbee.0 (1502) 0x00158d000313c7ae (addr 42799): Not supported (model undefined)(EndDevice)
2020-11-22 09:05:10.287 - info: zigbee.0 (1502) 0x00158d00029a900d (addr 5818): Not supported (model undefined)(Unknown)
2020-11-22 09:05:10.288 - info: zigbee.0 (1502) 0x00158d000322bd4a (addr 4981): Not supported (model undefined)(Unknown)
2020-11-22 09:05:10.288 - info: zigbee.0 (1502) 0x00158d0004280bff (addr 50996): Not supported (model undefined)(Unknown)
2020-11-22 09:05:10.290 - debug: zigbee.0 (1502) New device event: {"type":"device","device":{"ID":11,"_type":"EndDevice","_ieeeAddr":"0x00158d000312f7cb","_networkAddress":29810,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profileID":260,"deviceID":24321,"inputClusters":[0,3,65535,6],"outputClusters":[0,4,65535],"deviceNetworkAddress":29810,"deviceIeeeAddress":"0x00158d000312f7cb","clusters":{"genOnOff":{"attributes":{"onOff":0}},"genBasic":{"attributes":{"65281":{"1":2955,"3":25,"4":5032,"5":1049,"6":[0,1],"10":0,"100":0},"manufacturerName":"LUMI","powerSource":3,"zclVersion":1,"stackVersion":2,"hwVersion":2,"dateCode":"20161128","swBuildId":"3000-0001"}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet.aq2","_applicationVersion":3,"_stackVersion":2,"_zclVersion":1,"_hardwareVersion":2,"_dateCode":"20161128","_softwareBuildID":"3000-0001","_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1606032074571},"mapped":{"zigbeeModel":["lumi.sensor_magnet.aq2"],"model":"MCCGQ11LM","vendor":"Xiaomi","description":"Aqara door & window contact sensor","supports":"contact","meta":{"battery":{"voltageToPercentage":"3V_2100"}},"fromZigbee":[{"cluster":"genBasic","type":["attributeReport","readResponse"]},{"cluster":"genOnOff","type":["attributeReport","readResponse"]},{"cluster":"genBasic","type":["attributeReport","readResponse"]}],"toZigbee":[],"exposes":[{"type":"numeric","name":"battery","property":"battery","access":"r","unit":"%"},{"type":"binary","name":"contact","property":"contact","access":"r","value_on":false,"value_off":true},{"type":"numeric","name":"linkquality","property":"linkquality","access":"r","unit":"lqi"}]},"name":"0x00158d000312f7cb"}
2020-11-22 09:05:10.291 - info: zigbee.0 (1502) 0x00158d000312f7cb (addr 29810): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2020-11-22 09:05:10.292 - info: zigbee.0 (1502) Zigbee started
2020-11-22 09:05:10.378 - error: zigbee.0 (1502) Device 0x00158d000366790e "undefined" not described in statesMapping.
2020-11-22 09:05:10.384 - error: zigbee.0 (1502) Device 0x00158d000313c7ae "undefined" not described in statesMapping.
2020-11-22 09:05:10.391 - error: zigbee.0 (1502) Device 0x00158d00029a900d "undefined" not described in statesMapping.
2020-11-22 09:05:10.392 - error: zigbee.0 (1502) Device 0x00158d000322bd4a "undefined" not described in statesMapping.
2020-11-22 09:05:10.396 - error: zigbee.0 (1502) Device 0x00158d0004280bff "undefined" not described in statesMapping.
2020-11-22 09:05:11.290 - debug: zigbee.0 (1502) Publish available for 0x00158d000312f7cb = true

Die 5 von 50 Geräten, die mit error angezeigt werden sind im Netzwerk als verbunden gezeigt, sind sie es aber nicht. Habe probeweise einen Kontakt ...f7cb gepairt. Fuktioniert. Der Adapter startet immer wieder neu.

Habe mir das log von gestern angesehen:

2020-11-21 19:16:56.771  - info: javascript.0 (25520) script.js.TV.Onkyo: test onkyo load power: 0
2020-11-21 19:28:02.865  - info: admin.0 (24885) Unsubscribe from all states, except system's, because over 3 seconds the number of events is over 200 (in last second 0)
2020-11-21 19:29:02.880  - info: admin.0 (24885) Subscribe on all states again
2020-11-21 19:30:14.286  - info: host.raspi-3 stopInstance system.adapter.zigbee.0 (force=false, process=true)
2020-11-21 19:30:14.311  - info: host.raspi-3 stopInstance system.adapter.zigbee.0 send kill signal
2020-11-21 19:30:15.341  - info: host.raspi-3 stopInstance system.adapter.zigbee.0 killing pid 26300
2020-11-21 19:30:17.501  - info: host.raspi-3 instance system.adapter.zigbee.0 started with pid 30266
2020-11-21 19:30:23.607  - error: zigbee.0 (30266) zigbee.0 already running
2020-11-21 19:30:23.618  - warn: zigbee.0 (30266) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2020-11-21 19:30:24.276  - error: host.raspi-3 instance system.adapter.zigbee.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-11-21 19:30:24.279  - info: host.raspi-3 Restart adapter system.adapter.zigbee.0 because enabled
2020-11-21 19:30:45.805  - info: host.raspi-3 instance system.adapter.zigbee.0 started with pid 30786
2020-11-21 19:30:49.577  - error: zigbee.0 (30786) zigbee.0 already running
2020-11-21 19:30:49.582  - warn: zigbee.0 (30786) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2020-11-21 19:30:50.153  - error: host.raspi-3 instance system.adapter.zigbee.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-11-21 19:30:50.154  - info: host.raspi-3 Restart adapter system.adapter.zigbee.0 because enabled
2020-11-21 19:31:20.245  - info: host.raspi-3 instance system.adapter.zigbee.0 started with pid 31559
2020-11-21 19:31:25.630  - info: zigbee.0 (31559) starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.19.0, js-controller: 3.1.6
2020-11-21 19:31:25.980  - info: zigbee.0 (31559) Starting Zigbee  npm ...
2020-11-21 19:31:29.715  - error: 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().
2020-11-21 19:31:29.716  - error: zigbee.0 (31559) unhandled promise rejection: Cannot read property 'getEntries' of null
2020-11-21 19:31:29.718  - error: zigbee.0 (31559) TypeError: Cannot read property 'getEntries' of null
    at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55)
    at Function.byIeeeAddr (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:224:16)
    at Controller.getDeviceByIeeeAddr (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:264:31)
    at ZigbeeController.resolveEntity (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:233:52)
    at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:321:48)
    at StatesController.emit (events.js:314:20)
    at StatesController.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:142:14)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
2020-11-21 19:31:29.721  - info: zigbee.0 (31559) cleaned everything up...
2020-11-21 19:31:29.744  - error: 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().
2020-11-21 19:31:29.745  - error: zigbee.0 (31559) unhandled promise rejection: Cannot read property 'mapped' of undefined
2020-11-21 19:31:29.746  - error: zigbee.0 (31559) TypeError: Cannot read property 'mapped' of undefined
    at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:323:36)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
2020-11-21 19:31:29.748  - error: 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().
2020-11-21 19:31:29.749  - error: zigbee.0 (31559) unhandled promise rejection: Cannot read property 'mapped' of undefined
2020-11-21 19:31:29.750  - error: zigbee.0 (31559) TypeError: Cannot read property 'mapped' of undefined
    at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:323:36)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
2020-11-21 19:31:29.754  - error: 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().
2020-11-21 19:31:29.756  - error: zigbee.0 (31559) unhandled promise rejection: Cannot read property 'mapped' of undefined
2020-11-21 19:31:29.757  - error: zigbee.0 (31559) TypeError: Cannot read property 'mapped' of undefined
    at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:323:36)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
2020-11-21 19:31:29.758  - error: 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().
2020-11-21 19:31:29.760  - error: zigbee.0 (31559) unhandled promise rejection: Cannot read property 'mapped' of undefined
2020-11-21 19:31:29.761  - error: zigbee.0 (31559) TypeError: Cannot read property 'mapped' of undefined
    at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:323:36)
    at runMicrotasks (<anonymous>)

Möglicherweise ist das javascript in eine Schleife geraten (siehe erste Zeile). Der Zigbee Adapter ist danach jedenfalls durchgedreht und hat ununterbrochen Fehler ausgeschmissen. Die jetzt laufende backup Version hat sicher keinen loop Fehler.

Frage ist, warum erkennt der controller nach dem backup nicht die Geräte. Muß ich wirklich neu pairen? Wie bekomme ich die 5 Geräte wieder zum Laufen?
Ich benutze den cc2538 (+cc2592), alle Adapter und Programme sind auf dem neuesten Stand.

[Asgothian]

@hukio

Die Meldungen im Log deuten darauf hin das eine der Folgenden Antworten korrekt ist:

• die Version des Zigbee-Herdsman-converters ist veraltet (0x00158d000366790e (addr 37593): Not supported (model undefined)(Unknown))
• es gab Probleme bei der Installation so das eine in sich nicht saubere Version des Zigbee Adapters läuft.
• es gibt Probleme mit der Firmware des cc2538, so das die ID's der Geräte nicht sauber an den Zigbee Adapter gemeldet werden

Daher mach bitte folgendes:

• lass das fixer skript für den iobroker laufen (im Verzeichnis /opt/iobroker nacheinander: iobroker stop, dann iobroker fix, dann iobroker start
• Verifiziere die zigbee-herdsman-converters version (unter /opt/iobroker den Befehl "npm list zigbee-herdsman-converters" absetzen, schauen was er auflistet
• falls es mehrere Versionen gibt, beide entfernen (npm remove zigbee-herdsman-converters, jeweils im Verzeichnis in dem sie installiert sind - sollte /opt/iobroker und/oder /opt/iobroker/node_modules/iobroker.zigbee sein)
• Installiere die aktuelle Version des Adapters noch einmal neu

Wenn der Fehler dann noch erhalten bleibt müsstest Du die Firmware des Sticks neu flashen um zu verifizieren das diese nicht Ursache ist.

Nebenbei noch:

Welche Node-Version läuft bei Dir?
Hast du am Tag bevor die Probleme angefangen haben ein Update von

• Node.js
• admin
• jscontroller

gemacht ?

A.

[arteck]

@Asgothian sagte in Zigbee verbindet keine Geräte mehr:

es gibt Probleme mit der Firmware des cc2538, so das die ID's der Geräte nicht sauber an den Zigbee Adapter gemeldet werden

die ist korrekt.. das garantiere ich

ich vermute du hast irgendeine zwischen Version des adapter erwischt

[hukio]

@Asgothian Meine node version ist 12.19.0. Habe keine updates gemacht vorher. Die converter Antwort ist: zigbee-herdsman-converters@12.0.222 in iobroker.zigbee@1.3.1. Ist das der neueste? Soll ich neu installieren?
Danke für die ausführliche Antwort.
HUK