Thermostat Kompatibilität

Stefan341

Jetzt aber


zigbee.0
2025-09-20 23:45:15.879	info	Installed Version: iobroker.zigbee@3.0.5 (Converters 24.8.0 Herdsman 4.4.1)

Asgothian

@stefan341 da siehst du dann auch, warum der Thermostat bei dir nicht geht: die Versionsnummer der converter ist kleiner als die notwendige Versionsnummer.

Du hast jetzt vier Möglichkeiten:

Möglichkeit eins: du Patchst auf deinem System, den Zigbee Adapter, so dass er eine neuere Version der Bibliothek lädt. Das ist einfach und das kann ich dir erklären.
Möglichkeit zwei: du baust einen so genannten externen Converter. der besteht zu 99 % aus dem Code, der im aktuellen Converter vorhanden ist, diesen trägst du auf deinem System zusätzlich ein, dann kannst du den Thermostat mit der jetzigen Version benutzen.
Möglichkeit drei: du wartest ab, bis die Tests an der 3.1 abgeschlossen sind. Die wird den Thermostat auf jeden Fall unterstützen. Wie lange das effektiv dauert, kann ich dir allerdings nicht sagen.
Möglichkeit vier: du installierst die aktuelle 3.1 Testversion, wobei es da durchaus Effekte geben kann, die sich negativ auswirken.

Das einfachste ist Möglichkeit drei. Kein Risiko, aber auch keinen Thermostat.
Etwas komplexer ist Möglichkeit eins: eine Datei ändern, einen Befehl ausführen, fertig.
Das nächst schwerere ist Möglichkeit vier: primär deswegen, weil nicht klar ist, welche Effekte sich bei dem bei dir verwendeten Geräten einstellen. So habe ich zum Beispiel bei den Geräten, die ich verwende keine negativen Effekte. Es gibt aber mehrere Leute, die bei bestimmten Geräten Funktionalität verloren haben.
Das komplizierteste ist der externe Converter, weil du letztendlich JS Skript Code schreiben musst, um den Thermostat zu unterstützen. Es gibt eine gute Vorlage dafür, die ich dir bereitstellen kann. Das Testen und verifizieren, dass es geht, musst du aber machen.

A.

Stefan341

@asgothian
ich tendiere zu 1. Allein durch das laden der neueren Bibliothek können ja keine Fehlfunktionen, wie in der Beta möglich, auftreten oder?

Was passiert wenn eine neue Version des Adapters veröffentlicht wird? Werden dann die Änderungen überschrieben?

Asgothian

@stefan341

nein, da wird nichts schlimmes passieren
ja, beim neu installieren ist die Änderung weg.
die nächste Version Nutz aber sicher eine noch neuere Version.

Zu dem was zu tun ist:

Adapter anhalten
in der Datei Package.json (/opt/iobroker/node_modules/iobroker.zigbee) die Zeile mit ”zigbee-herdsman-converters": finden. Die Zahlen dahinter auf 24.14.0 ändern.
danach auf der Konsole im gleichen Verzeichnis den Befehl npm -i absetzen.
Adapter starten - verifizieren das die 24.14.0 Version der converter geladen wird.

A.

Stefan341

@asgothian

Scheint nicht ganz geklappt zu haben

Der relevante Teil meiner package.json

"dependencies": {
    "@iobroker/adapter-core": "^3.2.3",
    "@iobroker/dm-utils": "^1.0.10",
    "humanize-duration": "^3.33.0",
    "tar": "^7.4.3",
    "ajv": "^8.17.1",
    "uri-js": "^4.4.1",
    "typescript": "^5.8.3",
    "zigbee-herdsman": "4.4.1",
    "zigbee-herdsman-converters": "24.14.0"

Log nach dem Neustart

zigbee.0
2025-09-21 00:40:37.652	info	Installed Version: iobroker.zigbee@3.0.5 (Converters 24.8.0 Herdsman 4.4.1)

Kann es sein, dass er npm -i nicht genommen hat? Die Ausgabe war wie folgt:

npm <command>

Usage:

npm install        install all the dependencies in your project
npm install <foo>  add the <foo> dependency to your project
npm test           run this project's tests
npm run <foo>      run the script named <foo>
npm <command> -h   quick help on <command>
npm -l             display usage info for all commands
npm help <term>    search for help on <term>
npm help npm       more involved overview

All commands:

    access, adduser, audit, bugs, cache, ci, completion,
    config, dedupe, deprecate, diff, dist-tag, docs, doctor,
    edit, exec, explain, explore, find-dupes, fund, get, help,
    help-search, hook, init, install, install-ci-test,
    install-test, link, ll, login, logout, ls, org, outdated,
    owner, pack, ping, pkg, prefix, profile, prune, publish,
    query, rebuild, repo, restart, root, run-script, sbom,
    search, set, shrinkwrap, star, stars, start, stop, team,
    test, token, uninstall, unpublish, unstar, update, version,
    view, whoami

Specify configs in the ini-formatted file:
    /home/iobroker/.npmrc
or on the command line via: npm <command> --key=value

More configuration info: npm help config
Configuration fields: npm help 7 config

npm@10.9.3 /usr/lib/node_modules/npm

Asgothian

@stefan341 stimmt, mein Fehler, der Befehl hätte npm i heißen müssen.

A.

Stefan341

@asgothian
Das hat soweit geklappt. Jetzt wird der Thermostat richtig erkannt.

Danke für deine Hilfe.

Stefan341

@asgothian
Kurz was zu meinen Beobachtungen. Wenn ich neue Geräte zum Adapter hinzufüge, bricht das Pairing beim ersten mal bei etwa 17 Sekunden Restzeit ab. Ich denke, der Adapter startet dann neu (das konnte ich nicht genau beobachten, da ich nicht drauf gefasst war). Beim zweiten Versuch klappt das Pairing. Dann werden allerdings die Thermostate nicht mehr erkannt. Ich muss dann npm i neu ausführen.

Asgothian

@stefan341 sagte in Thermostat Kompatibilität:

@asgothian
Kurz was zu meinen Beobachtungen. Wenn ich neue Geräte zum Adapter hinzufüge, bricht das Pairing beim ersten mal bei etwa 17 Sekunden Restzeit ab. Ich denke, der Adapter startet dann neu (das konnte ich nicht genau beobachten, da ich nicht drauf gefasst war). Beim zweiten Versuch klappt das Pairing. Dann werden allerdings die Thermostate nicht mehr erkannt. Ich muss dann npm i neu ausführen.

Ob der Adapter abstürzt siehst du im Log - da wäre ich dann gezielt dran interessiert. Das kannst du durch 'log herunterladen' immer noch als Textdatei bekommen - du musst nur den ungefähren Zeitpunkt kennen.

Dann interessieren mich die Meldungen. Eigentlich sollte dadurch nichts neu installiert werden

A.

Stefan341

@asgothian

Das müsste der relevante Teil des Logs sein

2025-09-22 18:09:35.880 - info: zigbee.0 (110710) List of port: [{"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"1a043fc8e5a5ed11bc85f1a32981d5c7","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_1a043fc8e5a5ed11bc85f1a32981d5c7-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyAMA0"}]
2025-09-22 18:09:39.245 - info: zigbee.0 (110710) Opening zigbee Network for 60 seconds
2025-09-22 18:09:48.251 - info: zigbee.0 (110710) Starting interview of '0x44e2f8fffe0f3d69'
2025-09-22 18:09:48.408 - info: zigbee.0 (110710) Device '0x44e2f8fffe0f3d69' announced itself
2025-09-22 18:09:58.388 - warn: zigbee.0 (110710) Device 0x44e2f8fffe0f3d69 "undefined" not found.
2025-09-22 18:10:17.587 - info: zigbee.0 (110710) Device '0x44e2f8fffe0f3d69' announced itself
2025-09-22 18:10:23.648 - error: zigbee.0 (110710) 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-09-22 18:10:23.649 - error: zigbee.0 (110710) unhandled promise rejection: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
2025-09-22 18:10:23.649 - error: zigbee.0 (110710) Error: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:541:23)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:439:20
at Queue.execute (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
at ZStackAdapter.sendZclFrameToEndpoint (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:437:16)
at Request.send (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:86:20)
at Endpoint.sendRequest (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:338:20)
2025-09-22 18:10:23.650 - error: zigbee.0 (110710) Exception-Code: 205: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
2025-09-22 18:10:23.705 - info: zigbee.0 (110710) Halting zigbee adapter. Restart delay is at least 30 seconds.
2025-09-22 18:10:23.706 - info: zigbee.0 (110710) cleaning everything up...
2025-09-22 18:10:23.709 - info: zigbee.0 (110710) Saved local configuration data
2025-09-22 18:10:24.127 - info: zigbee.0 (110710) Closing Zigbee network, 16 seconds remaining
2025-09-22 18:10:24.708 - warn: zigbee.0 (110710) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-09-22 18:10:25.376 - error: host.ioB-Slave Caught by controller[1]: 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-09-22 18:10:25.377 - error: host.ioB-Slave Caught by controller[2]: Error: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
2025-09-22 18:10:25.377 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:541:23)
2025-09-22 18:10:25.377 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:10:25.377 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:439:20
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at Queue.execute (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpoint (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:437:16)
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at Request.send (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:86:20)
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at Endpoint.sendRequest (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:338:20)
2025-09-22 18:10:25.378 - error: host.ioB-Slave instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2025-09-22 18:10:25.379 - info: host.ioB-Slave Restart adapter system.adapter.zigbee.0 because enabled
2025-09-22 18:10:56.276 - info: host.ioB-Slave instance system.adapter.zigbee.0 in version "3.0.5" started with pid 113951
2025-09-22 18:10:59.609 - info: zigbee.0 (113951) starting. Version 3.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.19.0, js-controller: 7.0.7
2025-09-22 18:10:59.657 - info: zigbee.0 (113951) Adapter ready - starting subsystems. Adapter is running in info mode.
2025-09-22 18:10:59.659 - info: zigbee.0 (113951) init localConfig
2025-09-22 18:10:59.747 - info: zigbee.0 (113951) delete old Backup files. keep only last 10
2025-09-22 18:10:59.751 - info: zigbee.0 (113951) --- creating device debug ---
2025-09-22 18:10:59.752 - info: zigbee.0 (113951) Autostart Zigbee subsystem
2025-09-22 18:10:59.753 - info: zigbee.0 (113951) Starting Adapter npm ...
2025-09-22 18:10:59.775 - info: zigbee.0 (113951) Installed Version: iobroker.zigbee@3.0.5 (Converters 24.8.0 Herdsman 4.4.1)
2025-09-22 18:10:59.778 - info: zigbee.0 (113951) configured transmit power : normal
2025-09-22 18:10:59.780 - info: zigbee.0 (113951) Starting Zigbee-Herdsman
2025-09-22 18:11:00.326 - info: zigbee.0 (113951) Zigbee-Herdsman started successfully with Coordinator firmware version: ZStack3x0 : 20210708 (2-1.2.7.1)
2025-09-22 18:11:00.327 - info: zigbee.0 (113951) Unable to disable LED, unsupported function.
2025-09-22 18:11:00.388 - info: zigbee.0 (113951) 0x0ceff6fffe3c8598 (addr 46294): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.397 - info: zigbee.0 (113951) 0x0ceff6fffe755a7f (addr 49277): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.401 - info: zigbee.0 (113951) 0x0ceff6fffe7501c8 (addr 7664): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.404 - info: zigbee.0 (113951) 0x842712fffe7dfb91 (addr 35623): SNZB-03P - SONOFF Zigbee PIR sensor (EndDevice)
2025-09-22 18:11:00.409 - info: zigbee.0 (113951) 0x842712fffe774abf (addr 57506): SNZB-03P - SONOFF Zigbee PIR sensor (EndDevice)
2025-09-22 18:11:00.412 - info: zigbee.0 (113951) 0x842712fffe7ce735 (addr 1191): SNZB-03P - SONOFF Zigbee PIR sensor (EndDevice)
2025-09-22 18:11:00.596 - info: zigbee.0 (113951) 0x842e14fffe15cc5b (addr 12785): HG06106C - Lidl Livarno Lux E27 bulb RGB (Router)
2025-09-22 18:11:00.602 - info: zigbee.0 (113951) 0x588e81fffeb97054 (addr 27716): HG06106C - Lidl Livarno Lux E27 bulb RGB (Router)
2025-09-22 18:11:00.605 - info: zigbee.0 (113951) 0x08ddebfffef31e0f (addr 44003): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.608 - info: zigbee.0 (113951) 0x0ceff6fffef0fab0 (addr 8324): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.611 - info: zigbee.0 (113951) 0x08ddebfffef34e8b (addr 10209): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.614 - info: zigbee.0 (113951) 0x0ceff6fffe796d31 (addr 36130): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.617 - info: zigbee.0 (113951) 0x08ddebfffef31b25 (addr 64216): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.620 - info: zigbee.0 (113951) 0x0ceff6fffeab2ccf (addr 13515): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.622 - info: zigbee.0 (113951) 0x0ceff6fffeab4874 (addr 20809): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.624 - info: zigbee.0 (113951) 0x0ceff6fffef0e279 (addr 10908): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.627 - info: zigbee.0 (113951) 0x0ceff6fffe7a9bd0 (addr 47572): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.629 - info: zigbee.0 (113951) 0x0ceff6fffe7a8e5d (addr 31454): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.632 - info: zigbee.0 (113951) 0xd44867fffe4c596c (addr 39389): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.634 - info: zigbee.0 (113951) 0xd44867fffe4c2e92 (addr 19118): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.637 - info: zigbee.0 (113951) 0xd44867fffe4c599b (addr 65102): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.639 - info: zigbee.0 (113951) 0xd44867fffe4c5abe (addr 41666): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.641 - info: zigbee.0 (113951) 0x0ceff6fffe782803 (addr 57086): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.643 - info: zigbee.0 (113951) 0xd44867fffe4c5cbb (addr 8990): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.644 - info: zigbee.0 (113951) 0x0ceff6fffeab7583 (addr 41118): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.647 - info: zigbee.0 (113951) 0x0ceff6fffe5d918f (addr 15791): SNZB-01P - SONOFF Wireless button (EndDevice)
2025-09-22 18:11:00.649 - info: zigbee.0 (113951) 0x8c65a3fffed4f850 (addr 63166): SNZB-06P - SONOFF Zigbee occupancy sensor (Router)
2025-09-22 18:11:00.698 - info: zigbee.0 (113951) 0xa4c1383b3d92b80b (addr 54748): A1Z - Nous Smart plug (with power monitoring) (Router)
2025-09-22 18:11:00.702 - info: zigbee.0 (113951) 0xa4c1387e12b8dd59 (addr 62068): A1Z - Nous Smart plug (with power monitoring) (Router)
2025-09-22 18:11:00.806 - info: zigbee.0 (113951) 0xa4c13864ccc9a98c (addr 45241): Unsupported (model TS0601)(Router)
2025-09-22 18:11:00.809 - info: zigbee.0 (113951) 0xa4c138ff1cae6d53 (addr 29372): A1Z - Nous Smart plug (with power monitoring) (Router)
2025-09-22 18:11:00.817 - info: zigbee.0 (113951) 0xa4c138a331371316 (addr 17723): B1Z - Nous 1 gang switch (Router)
2025-09-22 18:11:00.819 - info: zigbee.0 (113951) 0xa49e69fffe71c86c (addr 47788): SNZB-01P - SONOFF Wireless button (EndDevice)
2025-09-22 18:11:00.822 - info: zigbee.0 (113951) 0xc4d8c8fffe03db9f (addr 1809): SNZB-03P - SONOFF Zigbee PIR sensor (EndDevice)
2025-09-22 18:11:00.842 - info: zigbee.0 (113951) 0xa4c13849367c6744 (addr 55396): Unsupported (model TS0601)(Router)
2025-09-22 18:11:00.862 - info: zigbee.0 (113951) 0x44e2f8fffe0f3d69 (addr 20298): Unsupported (model undefined)(Unknown)
2025-09-22 18:11:00.863 - info: zigbee.0 (113951) Currently 36 devices are joined:
2025-09-22 18:11:00.865 - info: zigbee.0 (113951) Zigbee started
2025-09-22 18:11:02.117 - info: zigbee.0 (113951) debug devices set to ["a4c138f98b74ad84"]
2025-09-22 18:11:03.456 - warn: zigbee.0 (113951) download icon undefined for undefined Device not available. Check your devices.
2025-09-22 18:11:03.624 - warn: zigbee.0 (113951) Device 0xa4c13864ccc9a98c "TS0601" not found.
2025-09-22 18:11:03.627 - warn: zigbee.0 (113951) Device 0xa4c13849367c6744 "TS0601" not found.
2025-09-22 18:11:07.545 - warn: zigbee.0 (113951) Device 0x44e2f8fffe0f3d69 "undefined" not found.
2025-09-22 18:11:34.166 - info: zigbee.0 (113951) Opening zigbee Network for 60 seconds
2025-09-22 18:11:43.235 - info: zigbee.0 (113951) Starting interview of '0x44e2f8fffe0f3d69'
2025-09-22 18:11:43.391 - info: zigbee.0 (113951) Device '0x44e2f8fffe0f3d69' announced itself
2025-09-22 18:12:06.961 - info: zigbee.0 (113951) Device '0x44e2f8fffe0f3d69' announced itself
2025-09-22 18:12:18.739 - error: zigbee.0 (113951) 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-09-22 18:12:18.740 - error: zigbee.0 (113951) unhandled promise rejection: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
2025-09-22 18:12:18.740 - error: zigbee.0 (113951) Error: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:541:23)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:439:20
at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
at ZStackAdapter.sendZclFrameToEndpoint (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:437:16)
at Request.send (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:86:20)
at Endpoint.sendRequest (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:338:20)
2025-09-22 18:12:18.740 - error: zigbee.0 (113951) Exception-Code: 205: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
2025-09-22 18:12:18.772 - info: zigbee.0 (113951) Halting zigbee adapter. Restart delay is at least 30 seconds.
2025-09-22 18:12:18.772 - info: zigbee.0 (113951) cleaning everything up...
2025-09-22 18:12:18.774 - info: zigbee.0 (113951) Saved local configuration data
2025-09-22 18:12:19.039 - info: zigbee.0 (113951) Closing Zigbee network, 16 seconds remaining
2025-09-22 18:12:19.775 - warn: zigbee.0 (113951) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-09-22 18:12:20.451 - error: host.ioB-Slave Caught by controller[1]: 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-09-22 18:12:20.451 - error: host.ioB-Slave Caught by controller[2]: Error: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
2025-09-22 18:12:20.452 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:541:23)
2025-09-22 18:12:20.452 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:12:20.452 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:12:20.452 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:12:20.452 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:12:20.452 - error: host.ioB-Slave Caught by controller[2]: at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:439:20
2025-09-22 18:12:20.453 - error: host.ioB-Slave Caught by controller[2]: at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
2025-09-22 18:12:20.453 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpoint (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:437:16)
2025-09-22 18:12:20.453 - error: host.ioB-Slave Caught by controller[2]: at Request.send (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:86:20)
2025-09-22 18:12:20.453 - error: host.ioB-Slave Caught by controller[2]: at Endpoint.sendRequest (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:338:20)
2025-09-22 18:12:20.453 - error: host.ioB-Slave instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2025-09-22 18:12:20.453 - info: host.ioB-Slave Restart adapter system.adapter.zigbee.0 because enabled
2025-09-22 18:12:51.452 - info: host.ioB-Slave instance system.adapter.zigbee.0 in version "3.0.5" started with pid 113971
2025-09-22 18:12:54.784 - info: zigbee.0 (113971) starting. Version 3.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.19.0, js-controller: 7.0.7
2025-09-22 18:12:54.827 - info: zigbee.0 (113971) Adapter ready - starting subsystems. Adapter is running in info mode.
2025-09-22 18:12:54.830 - info: zigbee.0 (113971) init localConfig
2025-09-22 18:12:54.922 - info: zigbee.0 (113971) delete old Backup files. keep only last 10
2025-09-22 18:12:54.926 - info: zigbee.0 (113971) --- creating device debug ---
2025-09-22 18:12:54.926 - info: zigbee.0 (113971) Autostart Zigbee subsystem
2025-09-22 18:12:54.927 - info: zigbee.0 (113971) Starting Adapter npm ...
2025-09-22 18:12:54.951 - info: zigbee.0 (113971) Installed Version: iobroker.zigbee@3.0.5 (Converters 24.8.0 Herdsman 4.4.1)
2025-09-22 18:12:54.955 - info: zigbee.0 (113971) configured transmit power : normal
2025-09-22 18:12:54.956 - info: zigbee.0 (113971) Starting Zigbee-Herdsman
2025-09-22 18:12:55.520 - info: zigbee.0 (113971) Zigbee-Herdsman started successfully with Coordinator firmware version: ZStack3x0 : 20210708 (2-1.2.7.1)
2025-09-22 18:12:55.522 - info: zigbee.0 (113971) Unable to disable LED, unsupported function.

Was ich interessant finde, dass ziemlich weit unten steht, er hätte die Version 24.8.0 installiert.

In der Package.json war aber die ganze Zeit immernoch 24.14.0 eingetragen. Das musste ich nicht nochmal ändern, nur wie gesagt, npm i neu ausführen.
Also muss er die Information, dass er die 24.8.0 nehmen soll, vom woanders bekommen haben.

Das Ganze ist passiert als ich einen Sonoff Wasserlecksensor (https://sonoff.tech/de-de/products/sonoff-zigbee-water-leak-sensor-snzb-05p?srsltid=AfmBOoq7u9MMsclweMGV9GAVErWKMuuqfzP8_fFHTw3iYfjvag5peNWf) neu hinzugefügt habe.

Danach habe ich testweise noch einen NOUS Stecker (https://www.berrybase.de/nous-a1z-smarte-steckdose-zigbee?srsltid=AfmBOopai3I40lRkPd8k3wEIaWRCqAsdo9DLR5SMw1_F3qQLTzP_keHn) hinzugefügt. Das hat ohne Zwischenfälle geklappt.

Ich hoffe, ich konnte dir mit den Informationen weiterhelfen

Asgothian

@stefan341 sagte in Thermostat Kompatibilität:

@asgothian

Das müsste der relevante Teil des Logs sein

2025-09-22 18:09:35.880 - info: zigbee.0 (110710) List of port: [{"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"1a043fc8e5a5ed11bc85f1a32981d5c7","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_1a043fc8e5a5ed11bc85f1a32981d5c7-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyAMA0"}]
2025-09-22 18:09:39.245 - info: zigbee.0 (110710) Opening zigbee Network for 60 seconds
2025-09-22 18:09:48.251 - info: zigbee.0 (110710) Starting interview of '0x44e2f8fffe0f3d69'
2025-09-22 18:09:48.408 - info: zigbee.0 (110710) Device '0x44e2f8fffe0f3d69' announced itself
2025-09-22 18:09:58.388 - warn: zigbee.0 (110710) Device 0x44e2f8fffe0f3d69 "undefined" not found.
2025-09-22 18:10:17.587 - info: zigbee.0 (110710) Device '0x44e2f8fffe0f3d69' announced itself
2025-09-22 18:10:23.648 - error: zigbee.0 (110710) 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-09-22 18:10:23.649 - error: zigbee.0 (110710) unhandled promise rejection: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
2025-09-22 18:10:23.649 - error: zigbee.0 (110710) Error: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:541:23)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:439:20
at Queue.execute (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
at ZStackAdapter.sendZclFrameToEndpoint (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:437:16)
at Request.send (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:86:20)
at Endpoint.sendRequest (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:338:20)
2025-09-22 18:10:23.650 - error: zigbee.0 (110710) Exception-Code: 205: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
2025-09-22 18:10:23.705 - info: zigbee.0 (110710) Halting zigbee adapter. Restart delay is at least 30 seconds.
2025-09-22 18:10:23.706 - info: zigbee.0 (110710) cleaning everything up...
2025-09-22 18:10:23.709 - info: zigbee.0 (110710) Saved local configuration data
2025-09-22 18:10:24.127 - info: zigbee.0 (110710) Closing Zigbee network, 16 seconds remaining
2025-09-22 18:10:24.708 - warn: zigbee.0 (110710) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-09-22 18:10:25.376 - error: host.ioB-Slave Caught by controller[1]: 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-09-22 18:10:25.377 - error: host.ioB-Slave Caught by controller[2]: Error: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
2025-09-22 18:10:25.377 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:541:23)
2025-09-22 18:10:25.377 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:10:25.377 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:439:20
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at Queue.execute (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpoint (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:437:16)
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at Request.send (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:86:20)
2025-09-22 18:10:25.378 - error: host.ioB-Slave Caught by controller[2]: at Endpoint.sendRequest (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:338:20)
2025-09-22 18:10:25.378 - error: host.ioB-Slave instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2025-09-22 18:10:25.379 - info: host.ioB-Slave Restart adapter system.adapter.zigbee.0 because enabled
2025-09-22 18:10:56.276 - info: host.ioB-Slave instance system.adapter.zigbee.0 in version "3.0.5" started with pid 113951
2025-09-22 18:10:59.609 - info: zigbee.0 (113951) starting. Version 3.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.19.0, js-controller: 7.0.7
2025-09-22 18:10:59.657 - info: zigbee.0 (113951) Adapter ready - starting subsystems. Adapter is running in info mode.
2025-09-22 18:10:59.659 - info: zigbee.0 (113951) init localConfig
2025-09-22 18:10:59.747 - info: zigbee.0 (113951) delete old Backup files. keep only last 10
2025-09-22 18:10:59.751 - info: zigbee.0 (113951) --- creating device debug ---
2025-09-22 18:10:59.752 - info: zigbee.0 (113951) Autostart Zigbee subsystem
2025-09-22 18:10:59.753 - info: zigbee.0 (113951) Starting Adapter npm ...
2025-09-22 18:10:59.775 - info: zigbee.0 (113951) Installed Version: iobroker.zigbee@3.0.5 (Converters 24.8.0 Herdsman 4.4.1)
2025-09-22 18:10:59.778 - info: zigbee.0 (113951) configured transmit power : normal
2025-09-22 18:10:59.780 - info: zigbee.0 (113951) Starting Zigbee-Herdsman
2025-09-22 18:11:00.326 - info: zigbee.0 (113951) Zigbee-Herdsman started successfully with Coordinator firmware version: ZStack3x0 : 20210708 (2-1.2.7.1)
2025-09-22 18:11:00.327 - info: zigbee.0 (113951) Unable to disable LED, unsupported function.
2025-09-22 18:11:00.388 - info: zigbee.0 (113951) 0x0ceff6fffe3c8598 (addr 46294): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.397 - info: zigbee.0 (113951) 0x0ceff6fffe755a7f (addr 49277): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.401 - info: zigbee.0 (113951) 0x0ceff6fffe7501c8 (addr 7664): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.404 - info: zigbee.0 (113951) 0x842712fffe7dfb91 (addr 35623): SNZB-03P - SONOFF Zigbee PIR sensor (EndDevice)
2025-09-22 18:11:00.409 - info: zigbee.0 (113951) 0x842712fffe774abf (addr 57506): SNZB-03P - SONOFF Zigbee PIR sensor (EndDevice)
2025-09-22 18:11:00.412 - info: zigbee.0 (113951) 0x842712fffe7ce735 (addr 1191): SNZB-03P - SONOFF Zigbee PIR sensor (EndDevice)
2025-09-22 18:11:00.596 - info: zigbee.0 (113951) 0x842e14fffe15cc5b (addr 12785): HG06106C - Lidl Livarno Lux E27 bulb RGB (Router)
2025-09-22 18:11:00.602 - info: zigbee.0 (113951) 0x588e81fffeb97054 (addr 27716): HG06106C - Lidl Livarno Lux E27 bulb RGB (Router)
2025-09-22 18:11:00.605 - info: zigbee.0 (113951) 0x08ddebfffef31e0f (addr 44003): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.608 - info: zigbee.0 (113951) 0x0ceff6fffef0fab0 (addr 8324): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.611 - info: zigbee.0 (113951) 0x08ddebfffef34e8b (addr 10209): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.614 - info: zigbee.0 (113951) 0x0ceff6fffe796d31 (addr 36130): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.617 - info: zigbee.0 (113951) 0x08ddebfffef31b25 (addr 64216): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.620 - info: zigbee.0 (113951) 0x0ceff6fffeab2ccf (addr 13515): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.622 - info: zigbee.0 (113951) 0x0ceff6fffeab4874 (addr 20809): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.624 - info: zigbee.0 (113951) 0x0ceff6fffef0e279 (addr 10908): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.627 - info: zigbee.0 (113951) 0x0ceff6fffe7a9bd0 (addr 47572): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.629 - info: zigbee.0 (113951) 0x0ceff6fffe7a8e5d (addr 31454): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.632 - info: zigbee.0 (113951) 0xd44867fffe4c596c (addr 39389): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.634 - info: zigbee.0 (113951) 0xd44867fffe4c2e92 (addr 19118): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.637 - info: zigbee.0 (113951) 0xd44867fffe4c599b (addr 65102): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.639 - info: zigbee.0 (113951) 0xd44867fffe4c5abe (addr 41666): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.641 - info: zigbee.0 (113951) 0x0ceff6fffe782803 (addr 57086): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.643 - info: zigbee.0 (113951) 0xd44867fffe4c5cbb (addr 8990): SNZB-02P - SONOFF Temperature and humidity sensor (EndDevice)
2025-09-22 18:11:00.644 - info: zigbee.0 (113951) 0x0ceff6fffeab7583 (addr 41118): SNZB-04P - SONOFF Contact sensor (EndDevice)
2025-09-22 18:11:00.647 - info: zigbee.0 (113951) 0x0ceff6fffe5d918f (addr 15791): SNZB-01P - SONOFF Wireless button (EndDevice)
2025-09-22 18:11:00.649 - info: zigbee.0 (113951) 0x8c65a3fffed4f850 (addr 63166): SNZB-06P - SONOFF Zigbee occupancy sensor (Router)
2025-09-22 18:11:00.698 - info: zigbee.0 (113951) 0xa4c1383b3d92b80b (addr 54748): A1Z - Nous Smart plug (with power monitoring) (Router)
2025-09-22 18:11:00.702 - info: zigbee.0 (113951) 0xa4c1387e12b8dd59 (addr 62068): A1Z - Nous Smart plug (with power monitoring) (Router)
2025-09-22 18:11:00.806 - info: zigbee.0 (113951) 0xa4c13864ccc9a98c (addr 45241): Unsupported (model TS0601)(Router)
2025-09-22 18:11:00.809 - info: zigbee.0 (113951) 0xa4c138ff1cae6d53 (addr 29372): A1Z - Nous Smart plug (with power monitoring) (Router)
2025-09-22 18:11:00.817 - info: zigbee.0 (113951) 0xa4c138a331371316 (addr 17723): B1Z - Nous 1 gang switch (Router)
2025-09-22 18:11:00.819 - info: zigbee.0 (113951) 0xa49e69fffe71c86c (addr 47788): SNZB-01P - SONOFF Wireless button (EndDevice)
2025-09-22 18:11:00.822 - info: zigbee.0 (113951) 0xc4d8c8fffe03db9f (addr 1809): SNZB-03P - SONOFF Zigbee PIR sensor (EndDevice)
2025-09-22 18:11:00.842 - info: zigbee.0 (113951) 0xa4c13849367c6744 (addr 55396): Unsupported (model TS0601)(Router)
2025-09-22 18:11:00.862 - info: zigbee.0 (113951) 0x44e2f8fffe0f3d69 (addr 20298): Unsupported (model undefined)(Unknown)
2025-09-22 18:11:00.863 - info: zigbee.0 (113951) Currently 36 devices are joined:
2025-09-22 18:11:00.865 - info: zigbee.0 (113951) Zigbee started
2025-09-22 18:11:02.117 - info: zigbee.0 (113951) debug devices set to ["a4c138f98b74ad84"]
2025-09-22 18:11:03.456 - warn: zigbee.0 (113951) download icon undefined for undefined Device not available. Check your devices.
2025-09-22 18:11:03.624 - warn: zigbee.0 (113951) Device 0xa4c13864ccc9a98c "TS0601" not found.
2025-09-22 18:11:03.627 - warn: zigbee.0 (113951) Device 0xa4c13849367c6744 "TS0601" not found.
2025-09-22 18:11:07.545 - warn: zigbee.0 (113951) Device 0x44e2f8fffe0f3d69 "undefined" not found.
2025-09-22 18:11:34.166 - info: zigbee.0 (113951) Opening zigbee Network for 60 seconds
2025-09-22 18:11:43.235 - info: zigbee.0 (113951) Starting interview of '0x44e2f8fffe0f3d69'
2025-09-22 18:11:43.391 - info: zigbee.0 (113951) Device '0x44e2f8fffe0f3d69' announced itself
2025-09-22 18:12:06.961 - info: zigbee.0 (113951) Device '0x44e2f8fffe0f3d69' announced itself
2025-09-22 18:12:18.739 - error: zigbee.0 (113951) 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-09-22 18:12:18.740 - error: zigbee.0 (113951) unhandled promise rejection: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
2025-09-22 18:12:18.740 - error: zigbee.0 (113951) Error: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:541:23)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:439:20
at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
at ZStackAdapter.sendZclFrameToEndpoint (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:437:16)
at Request.send (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:86:20)
at Endpoint.sendRequest (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:338:20)
2025-09-22 18:12:18.740 - error: zigbee.0 (113951) Exception-Code: 205: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
2025-09-22 18:12:18.772 - info: zigbee.0 (113951) Halting zigbee adapter. Restart delay is at least 30 seconds.
2025-09-22 18:12:18.772 - info: zigbee.0 (113951) cleaning everything up...
2025-09-22 18:12:18.774 - info: zigbee.0 (113951) Saved local configuration data
2025-09-22 18:12:19.039 - info: zigbee.0 (113951) Closing Zigbee network, 16 seconds remaining
2025-09-22 18:12:19.775 - warn: zigbee.0 (113951) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-09-22 18:12:20.451 - error: host.ioB-Slave Caught by controller[1]: 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-09-22 18:12:20.451 - error: host.ioB-Slave Caught by controller[2]: Error: ZCL command 0x44e2f8fffe0f3d69/1 ssIasZone.enrollRsp({"enrollrspcode":0,"zoneid":23}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
2025-09-22 18:12:20.452 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:541:23)
2025-09-22 18:12:20.452 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:12:20.452 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:12:20.452 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:12:20.452 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:639:20)
2025-09-22 18:12:20.452 - error: host.ioB-Slave Caught by controller[2]: at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:439:20
2025-09-22 18:12:20.453 - error: host.ioB-Slave Caught by controller[2]: at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
2025-09-22 18:12:20.453 - error: host.ioB-Slave Caught by controller[2]: at ZStackAdapter.sendZclFrameToEndpoint (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:437:16)
2025-09-22 18:12:20.453 - error: host.ioB-Slave Caught by controller[2]: at Request.send (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:86:20)
2025-09-22 18:12:20.453 - error: host.ioB-Slave Caught by controller[2]: at Endpoint.sendRequest (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:338:20)
2025-09-22 18:12:20.453 - error: host.ioB-Slave instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2025-09-22 18:12:20.453 - info: host.ioB-Slave Restart adapter system.adapter.zigbee.0 because enabled
2025-09-22 18:12:51.452 - info: host.ioB-Slave instance system.adapter.zigbee.0 in version "3.0.5" started with pid 113971
2025-09-22 18:12:54.784 - info: zigbee.0 (113971) starting. Version 3.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.19.0, js-controller: 7.0.7
2025-09-22 18:12:54.827 - info: zigbee.0 (113971) Adapter ready - starting subsystems. Adapter is running in info mode.
2025-09-22 18:12:54.830 - info: zigbee.0 (113971) init localConfig
2025-09-22 18:12:54.922 - info: zigbee.0 (113971) delete old Backup files. keep only last 10
2025-09-22 18:12:54.926 - info: zigbee.0 (113971) --- creating device debug ---
2025-09-22 18:12:54.926 - info: zigbee.0 (113971) Autostart Zigbee subsystem
2025-09-22 18:12:54.927 - info: zigbee.0 (113971) Starting Adapter npm ...
2025-09-22 18:12:54.951 - info: zigbee.0 (113971) Installed Version: iobroker.zigbee@3.0.5 (Converters 24.8.0 Herdsman 4.4.1)
2025-09-22 18:12:54.955 - info: zigbee.0 (113971) configured transmit power : normal
2025-09-22 18:12:54.956 - info: zigbee.0 (113971) Starting Zigbee-Herdsman
2025-09-22 18:12:55.520 - info: zigbee.0 (113971) Zigbee-Herdsman started successfully with Coordinator firmware version: ZStack3x0 : 20210708 (2-1.2.7.1)
2025-09-22 18:12:55.522 - info: zigbee.0 (113971) Unable to disable LED, unsupported function.

Was ich interessant finde, dass ziemlich weit unten steht, er hätte die Version 24.8.0 installiert.

In der Package.json war aber die ganze Zeit immernoch 24.14.0 eingetragen. Das musste ich nicht nochmal ändern, nur wie gesagt, npm i neu ausführen.
Also muss er die Information, dass er die 24.8.0 nehmen soll, vom woanders bekommen haben.

Das Ganze ist passiert als ich einen Sonoff Wasserlecksensor (https://sonoff.tech/de-de/products/sonoff-zigbee-water-leak-sensor-snzb-05p?srsltid=AfmBOoq7u9MMsclweMGV9GAVErWKMuuqfzP8_fFHTw3iYfjvag5peNWf) neu hinzugefügt habe.

Danach habe ich testweise noch einen NOUS Stecker (https://www.berrybase.de/nous-a1z-smarte-steckdose-zigbee?srsltid=AfmBOopai3I40lRkPd8k3wEIaWRCqAsdo9DLR5SMw1_F3qQLTzP_keHn) hinzugefügt. Das hat ohne Zwischenfälle geklappt.

Ich hoffe, ich konnte dir mit den Informationen weiterhelfen

Ich fürchte da musst du noch eine Zeile in der package.json ändern. Da steht zigbee-herdsman: 4.x.x Die musst du auf zigbee-herdsman: 5.0.4 anpassen, dann sollten die Abstürze weg sein. (natürlich wieder ein npm i dazwischen

A.

Stefan341

@asgothian

removed 3 packages, changed 1 package, and audited 959 packages in 10s

127 packages are looking for funding
  run `npm fund` for details

26 vulnerabilities (1 low, 13 moderate, 9 high, 3 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

ist es sinnvoll npm audit fix --force auszuführen?

Asgothian

@stefan341 nein

Stefan341

@asgothian
Ok, ich werde berichten falls mir noch was auffällt

Danke nochmal

NEWS

Thermostat Kompatibilität

Support us

457
Online

32.1k
Users

80.7k
Topics

1.3m
Posts

NEWS

Thermostat Kompatibilität

Support us

457Online

32.1kUsers

80.7kTopics

1.3mPosts

457
Online

32.1k
Users

80.7k
Topics

1.3m
Posts