NEWS
Best posts made by dimaiv
-
RE: [Verkauft] CC2652P Zigbee Stick
Anleitung
Stick mit einem Ebyte Modul: Aktuele Firmware
Stick mit einem RF-Star Modul: Aktuelle Firmware
Anleitung V1 (SmartRF Flash Programmer 2. Funktioniert nicht mehr für Firmwares ab 11.2022)
Anleitung V2 (ZigStar Multitool)
Zigbee Modul flashen oder NVRAM löschen
Multitool
Für Windows ZigStarGW-MT-x64.exe.zip laden.Firmware flashen
-
Multitool runterladen, entpacken, starten.
-
Aktuele Firmware auswählen (1), drei Hacken setzen (2)
-
Stick vorbereiten.
Es gibt zwei Möglichkeiten.
A. Taste 2 (BSL) gedrückt halten -> Stick einstecken -> Taste los lassen.
B. Stick einstecken -> Taste 1 (RST) drücken und gedrückt halten - Taste 2 (BSL) drücken und gedrückt halten -> Taste 1 los lassen -> nach 1-2 sek Taste 2 los lassen. -
Orangene Button clicken (1) und ungefähr 5 Sekunden warten. Richtige ComPort wählen (2).
-
Start clicken.
-
Wenn es richtig funktioniert, dann sieht es so aus.
-
Wenn erfolgreich gelaufen ist.
Fertig.
P.S.: Falls der Stick im Windows nicht erkannt wird, folgende Treiber installieren:
https://www.makershop.de/ch340-341-usb-installieren/ -
-
RE: Tester für Zigbee Adapter 2.0.x gesucht
@asgothian
Zur Info:
Ich habe mehrere Opple Taster da, die funktionieren mit 3.0.0 und früheren Versionen einwandfrei. -
[Verkaufe] Zigbee LAN/USB/WLAN Gateway CC2652P
Hersteller " Ich " Model "CC2652P + WT32-ETH01, Einsatzbereit" Anzahl 1, Sofort verfügbar *Preis pro Stück 60 €, Anfragen über Chat Nachricht oder Telegramm: https://t.me/Zigbee1 Versand "in DE inkl., mit Verfolgungsnummer" Beschreibung "Leistungsstarke ZigBee Stick / LAN Gateway mit Z-Stack 3.x.0, Update über LAN/USB, mit 3 dBi Antenne und Gehäuse"
Es gibt ab sofort Diskussion-Thread:
FAQ. Zigbee Gateway -
RE: [gelöst] Zigbee/LAN - Adapter wird nicht grün
@segway
Ich erkläre.
Zigbee Adapter (z2m) hat eingebaute Backup Funktion für die Sticks (nvram), was aber nicht richtig funktioniert (noch nie hat es richtig funktioniert).
Deswegen, beim Umstieg auf ein neuer Coordinator (nagel neue, mit leerem nvram) werden in den Stick beim ersten Start, sehr oft unplausible Daten rein geschrieben, was dazu führt, das der Zigbee Adapter nicht mehr startet und spuckt Fehler raus.Geholfen wird damit
- Backup Ordner von Zigbee Adapter wird gelöscht.
und - NVRAM im Coordinator wird gelöscht.
- Backup Ordner von Zigbee Adapter wird gelöscht.
-
RE: Blitzwolf BW-SHP13
@fredf
Einfach die Dose kurz vom Strom nehmen hätte gereicht. -
RE: [Verkaufe] Zigbee Bodenfeuchtesensor
@bjoern77
Die Zeiten sind in die Firmware fest programmiert. Wenn du die Firmware flashen kannst (Cc-debugger), dann kann ich dir die Firmware zur Verfügung stellen mit gewünschten Zeiten. -
RE: DeConz findet nix
@peter-dick
Ehrlich gesagt, was hat es mit dem IoBroker zu tun?
Ich würde mich erstmal an Dresden Elektronik wenden, und dann, wenn Phoscon läuft, weiter schauen.
Latest posts made by dimaiv
-
RE: Tester wanted - Zigbee Adapter 3.1
@asgothian sagte in Tester wanted - Zigbee Adapter 3.1:
@dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:
@asgothian
Mit dieser version geht es
ich hasse das ich das nicht sauber testen kann.
irgendwie hab ich kein passendes Device oder das Zeitverhalten ist so anders das der Fehler bei mir nicht zuschlägt, sprich - das Gerät wird bei dir langsamer in den Herdsman geladen als bei mir, so das bei mir 'mapped' immer vorhanden ist, während bei Dir mapped 'noch' nicht definiert ist wenn er das erste mal durch resolve_entity durch geht.
Das ist Problematisch seit der ZHC die Definitions dynamisch lädt wenn entsprechende Devices auftauchen, und nicht immer alle vorhält.
A.
Kann ich dir irgendwie helfen?
Meine Instanz irgendwie fern freigeben, ich habe da nicht viel Ahnung -
RE: Tester wanted - Zigbee Adapter 3.1
@asgothian
Gerade mit der älteren Version (die von vor 1 Stunde oder so) probiert. Wenn's gleiche Geräte im Netz sind, läuft das Pairing normal durch. -
RE: Tester wanted - Zigbee Adapter 3.1
@asgothian sagte in Tester wanted - Zigbee Adapter 3.1:
@dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:
Jetzt Stürzt der Adapter beim Pairing wieder ab :
Bekanntes oder neues Device ? Bei mir läuft der durch
A.
Neues.
-
RE: Tester wanted - Zigbee Adapter 3.1
@asgothian
Gerade frisch vom Git installiert.
Jetzt Stürzt der Adapter beim Pairing wieder ab :2025-10-01 12:31:08.739 - info: zigbee.0 (15531) Opening zigbee Network for 120 seconds 2025-10-01 12:31:09.208 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined 2025-10-01 12:31:09.213 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model') 2025-10-01 12:31:09.213 - error: zigbee.0 (15531) handleDeviceInterview: Cannot read properties of undefined (reading 'name') 2025-10-01 12:31:12.642 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined 2025-10-01 12:31:12.643 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model') 2025-10-01 12:31:17.239 - info: admin.0 (2458) ==> Connected system.user.admin from ::ffff:192.168.2.100 2025-10-01 12:31:18.540 - info: zigbee.0 (15531) message {"type":"read","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":4,"_endpoints":[{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}}],"_ieeeAddr":"0x84fd27fffed2450f","_interviewState":"IN_PROGRESS","_lastSeen":1759314678537,"_networkAddress":61526,"_type":"Unknown","_linkquality":80,"_skipDefaultResponse":false,"_pendingRequestTimeout":0,"_customClusters":{},"meta":{}},"endpoint":{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}},"data":["localTime"],"linkquality":80,"groupID":0,"cluster":"genTime","meta":{"rawData":{"type":"Buffer","data":[0,79,0,7,0]},"zclTransactionSequenceNumber":79,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}}} received during interview. 2025-10-01 12:31:18.540 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined 2025-10-01 12:31:18.542 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model') 2025-10-01 12:31:18.543 - error: zigbee.0 (15531) 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-10-01 12:31:18.543 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'device') 2025-10-01 12:31:18.543 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'device') at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31) at ZigbeeController.emit (node:events:524:28) at ZigbeeController.emit (node:domain:489:12) at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14) at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14) at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:18.544 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'device') 2025-10-01 12:31:18.545 - error: zigbee.0 (15531) 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-10-01 12:31:18.546 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'options') 2025-10-01 12:31:18.546 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'options') at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39) at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:18.546 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'options') 2025-10-01 12:31:18.553 - info: zigbee.0 (15531) Halting zigbee adapter. Restart delay is at least 30 seconds. 2025-10-01 12:31:18.553 - info: zigbee.0 (15531) cleaning everything up 2025-10-01 12:31:18.553 - info: zigbee.0 (15531) Saved local configuration data 2025-10-01 12:31:18.553 - info: zigbee.0 (15531) cleanup successful 2025-10-01 12:31:18.553 - info: zigbee.0 (15531) terminating 2025-10-01 12:31:18.554 - warn: zigbee.0 (15531) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-10-01 12:31:18.554 - info: zigbee.0 (15531) zigbecontroller stopped successfully - ZH was not running 2025-10-01 12:31:18.554 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined 2025-10-01 12:31:18.554 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model') 2025-10-01 12:31:18.743 - info: zigbee.0 (15531) message {"type":"read","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":4,"_endpoints":[{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}}],"_ieeeAddr":"0x84fd27fffed2450f","_interviewState":"IN_PROGRESS","_lastSeen":1759314678743,"_networkAddress":61526,"_type":"Unknown","_linkquality":80,"_skipDefaultResponse":false,"_pendingRequestTimeout":0,"_customClusters":{},"meta":{}},"endpoint":{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}},"data":["localTime"],"linkquality":80,"groupID":0,"cluster":"genTime","meta":{"rawData":{"type":"Buffer","data":[0,79,0,7,0]},"zclTransactionSequenceNumber":79,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}}} received during interview. 2025-10-01 12:31:18.744 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined 2025-10-01 12:31:18.744 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model') 2025-10-01 12:31:18.744 - error: zigbee.0 (15531) 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-10-01 12:31:18.744 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'device') 2025-10-01 12:31:18.745 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'device') at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31) at ZigbeeController.emit (node:events:524:28) at ZigbeeController.emit (node:domain:489:12) at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14) at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14) at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:18.745 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'device') 2025-10-01 12:31:18.746 - error: zigbee.0 (15531) 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-10-01 12:31:18.746 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'options') 2025-10-01 12:31:18.747 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'options') at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39) at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:18.747 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'options') 2025-10-01 12:31:18.956 - info: zigbee.0 (15531) message {"type":"read","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":4,"_endpoints":[{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}}],"_ieeeAddr":"0x84fd27fffed2450f","_interviewState":"IN_PROGRESS","_lastSeen":1759314678955,"_networkAddress":61526,"_type":"Unknown","_linkquality":80,"_skipDefaultResponse":false,"_pendingRequestTimeout":0,"_customClusters":{},"meta":{}},"endpoint":{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}},"data":["localTime"],"linkquality":80,"groupID":0,"cluster":"genTime","meta":{"rawData":{"type":"Buffer","data":[0,79,0,7,0]},"zclTransactionSequenceNumber":79,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}}} received during interview. 2025-10-01 12:31:18.956 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined 2025-10-01 12:31:18.956 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model') 2025-10-01 12:31:18.956 - error: zigbee.0 (15531) 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-10-01 12:31:18.957 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'device') 2025-10-01 12:31:18.957 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'device') at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31) at ZigbeeController.emit (node:events:524:28) at ZigbeeController.emit (node:domain:489:12) at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14) at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14) at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:18.957 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'device') 2025-10-01 12:31:18.959 - error: zigbee.0 (15531) 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-10-01 12:31:18.959 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'options') 2025-10-01 12:31:18.959 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'options') at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39) at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:18.959 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'options') 2025-10-01 12:31:19.066 - error: host.Test-IoBroker 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-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'device') 2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31) 2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.emit (node:events:524:28) 2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.emit (node:domain:489:12) 2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14) 2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14) 2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker 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-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'options') 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:19.067 - error: host.Test-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-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: TypeError: Cannot read properties of undefined (reading 'device') 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at ZigbeeController.emit (node:events:524:28) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at ZigbeeController.emit (node:domain:489:12) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[4]: 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-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[5]: TypeError: Cannot read properties of undefined (reading 'options') 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[5]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[6]: 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-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: TypeError: Cannot read properties of undefined (reading 'device') 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at ZigbeeController.emit (node:events:524:28) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at ZigbeeController.emit (node:domain:489:12) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14) 2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:19.068 - error: host.Test-IoBroker Caught by controller[8]: 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-10-01 12:31:19.068 - error: host.Test-IoBroker Caught by controller[9]: TypeError: Cannot read properties of undefined (reading 'options') 2025-10-01 12:31:19.068 - error: host.Test-IoBroker Caught by controller[9]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39) 2025-10-01 12:31:19.068 - error: host.Test-IoBroker Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:19.068 - error: host.Test-IoBroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-10-01 12:31:19.068 - info: host.Test-IoBroker Restart adapter system.adapter.zigbee.0 because enabled
Und lässt sich nicht mehr ordentlich starten.
Hier automatischer restart :2025-10-01 12:31:49.284 - info: host.Test-IoBroker instance system.adapter.zigbee.0 in version "3.1.5-alpha.2" (non-npm: ioBroker/ioBroker.zigbee) started with pid 15575 2025-10-01 12:31:49.891 - info: zigbee.0 (15575) starting. Version 3.1.5-alpha.2 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.5, js-controller: 7.0.7 2025-10-01 12:31:49.900 - info: zigbee.0 (15575) Adapter ready - starting subsystems. Adapter is running in info mode. 2025-10-01 12:31:49.900 - info: zigbee.0 (15575) init localConfig 2025-10-01 12:31:49.916 - info: zigbee.0 (15575) --- creating device debug --- 2025-10-01 12:31:49.917 - info: zigbee.0 (15575) Autostart Zigbee subsystem 2025-10-01 12:31:49.917 - info: zigbee.0 (15575) Starting Adapter npm ... 2025-10-01 12:31:49.924 - info: zigbee.0 (15575) Installed Version: ioBroker/ioBroker.zigbee (Converters 25.31.0 Herdsman 6.1.3) 2025-10-01 12:31:49.925 - info: zigbee.0 (15575) configured transmit power : 2025-10-01 12:31:49.925 - info: zigbee.0 (15575) Starting Zigbee-Herdsman 2025-10-01 12:31:51.728 - info: zigbee.0 (15575) Zigbee-Herdsman started successfully with Coordinator firmware version: ZStack3x0 : 20240710 (2-1.2.7.1) 2025-10-01 12:31:51.728 - info: zigbee.0 (15575) Unable to disable LED, unsupported function. 2025-10-01 12:31:51.766 - info: zigbee.0 (15575) 0xe0798dfffe746ae6 (addr 11547): HG06104A - Lidl Livarno Home RGB+CCT LED light strip 2m (Router) 2025-10-01 12:31:51.769 - info: zigbee.0 (15575) 0x00158d0005062c00 (addr 16444): MLI-404011/MLI-404049 - Müller Licht Tint remote control (EndDevice) 2025-10-01 12:31:51.775 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined 2025-10-01 12:31:51.779 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model') 2025-10-01 12:31:51.779 - info: zigbee.0 (15575) 3 devices are part of the network 2025-10-01 12:31:51.779 - info: zigbee.0 (15575) Zigbee started 2025-10-01 12:31:51.781 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined 2025-10-01 12:31:51.782 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model') 2025-10-01 12:31:51.783 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined 2025-10-01 12:31:51.784 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model') 2025-10-01 12:31:51.784 - error: zigbee.0 (15575) 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-10-01 12:31:51.784 - error: zigbee.0 (15575) unhandled promise rejection: Cannot read properties of undefined (reading 'options') 2025-10-01 12:31:51.784 - error: zigbee.0 (15575) TypeError: Cannot read properties of undefined (reading 'options') at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:15:77) at processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.all (index 2) 2025-10-01 12:31:51.784 - error: zigbee.0 (15575) Cannot read properties of undefined (reading 'options') 2025-10-01 12:31:51.808 - info: zigbee.0 (15575) Halting zigbee adapter. Restart delay is at least 30 seconds. 2025-10-01 12:31:51.809 - info: zigbee.0 (15575) cleaning everything up 2025-10-01 12:31:51.809 - info: zigbee.0 (15575) Saved local configuration data 2025-10-01 12:31:51.809 - info: zigbee.0 (15575) cleanup successful 2025-10-01 12:31:51.809 - info: zigbee.0 (15575) terminating 2025-10-01 12:31:51.810 - warn: zigbee.0 (15575) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-10-01 12:31:51.810 - info: zigbee.0 (15575) zigbecontroller stopped successfully - ZH was not running 2025-10-01 12:31:51.810 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined 2025-10-01 12:31:51.811 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model') 2025-10-01 12:31:51.833 - info: zigbee.0 (15575) debug devices set to [] 2025-10-01 12:31:51.909 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined 2025-10-01 12:31:51.910 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model') 2025-10-01 12:31:51.910 - warn: zigbee.0 (15575) resolveEntity returned no entity 2025-10-01 12:31:52.322 - error: host.Test-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-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'options') 2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[1]: at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:15:77) 2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[1]: at async Promise.all (index 2) 2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[2]: allowing role change for colortemp 2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[3]: allowing role change for colortemp_move 2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[4]: allowing role change for hex_color 2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[5]: allowing role change for color 2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[6]: allowing role change for color_xy.x 2025-10-01 12:31:52.326 - error: host.Test-IoBroker Caught by controller[7]: allowing role change for color_xy.y 2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[8]: allowing role change for color_rgb.r 2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[9]: allowing role change for color_rgb.g 2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[10]: allowing role change for color_rgb.b 2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[11]: allowing role change for color_power_on_behavior 2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[12]: allowing role change for color_temperature_move 2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[13]: allowing role change for color_move 2025-10-01 12:31:52.327 - error: host.Test-IoBroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-10-01 12:31:52.327 - info: host.Test-IoBroker Restart adapter system.adapter.zigbee.0 because enabled 2025-10-01 12:32:18.906 - info: host.Test-IoBroker "system.adapter.zigbee.0" disabled 2025-10-01 12:32:23.108 - error: zigbee.0 (15590) adapter disabled 2025-10-01 12:32:23.111 - warn: zigbee.0 (15590) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason 2025-10-01 12:32:23.625 - error: host.Test-IoBroker instance system.adapter.zigbee.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND) 2025-10-01 12:32:23.625 - info: host.Test-IoBroker Do not restart adapter system.adapter.zigbee.0 because disabled or deleted
-
RE: Tester wanted - Zigbee Adapter 3.1
@fabio
Danke.Bei mir läuft das Pairing genau so ab, egal, Strombetrieben oder ein Batteriegerät.
Bei mir gibt's auch Probleme mit "Edit"button, wo man die Name ändern kann. Was ich nicht erklären kann, bei manchen funktioniert, bei anderen nicht (innerhalb von einer Instanz). Also, reagiert gar nicht auf Mausklick.
-
RE: Tester wanted - Zigbee Adapter 3.1
@fabio
Hi. Kannst du mal probieren etwas anzulernen, und nach Fehler im Log schauen? -
RE: Tester wanted - Zigbee Adapter 3.1
@asgothian sagte in Tester wanted - Zigbee Adapter 3.1:
Hallo,
um bei den Events weiter zu kommen brauche ich Informationen dazu welche Gerätetypen für detail-Tests ggf. verfügbar sind. Deswegen melden die 3.1.x-alpha Versionen beim Start
calling onEvent for start on 0x282c02bfffed9110
Ich wäre Dankbar für eine Liste von Gerätetypen (idealerweise mit zigbee2mqtt Link für die entsprechenden Geräte. Dann kann ich mir die Konverter anschauen und ggf. dedizierte Tests anfragen um bei der Umsetzung der Optionen von Z2M vorwärts zu kommen.
Mein Problem ist das ich kaum eigene Geräte habe die diese Funktion nutzen.
A.
Folgende Geräte habe ich mit onEvent (laut Adapter Start):
- Smart thermostat
- TRADFRI LED driver, 10 w
- FYRTUR roller blind, block-out
- 10A UK or 16A EU smart plug
- TRADFRI remote control
- TRADFRI LED driver, 30 w
- SURTE door light panel, white spectrum
- TRADFRI bulb E26/E27, white spectrum
- TRADFRI bulb GU10, white
- TRADFRI bulb E12/E14/E26/E27, color/white spectrum
- TRADFRI bulb E26/E27, white spectrum
- Zigbee smart water valve
- Waterproof (IP65) sensor with screen and probe temperature detection
-
RE: Tester wanted - Zigbee Adapter 3.1
Optionen sind weg:
adapter:3.1.5-alpha.1 installed from:ioBroker/ioBroker.zigbee ZHC / ZH:25.31.0 / 6.1.3
P.S.: Dafür aber Zoom/Skalieren besser geworden.
-
RE: Tester wanted - Zigbee Adapter 3.1
@asgothian sagte in Tester wanted - Zigbee Adapter 3.1:
@dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:
aber wird als idefined angezeigt :
Violett markiert sieht auch nicht so richtig aus, seit 3.1.5
das Undefined kann ein Überbleibsel aus dem unerfolgreichen Versuch es anzumelden sein.
Loesung dafuer:
Den Dialog zum 'Namen anpassen' öffnen, den vorgegebenen Namen löschen, nichts eintragen, abspeichern, Fettich.
Unter 3.1.5 alpha.0 funktioniert es nicht, ich kann keine Namen ändern, ich kann nich die optionen hinzufügen oder löschen, also, da wird nix geschpeichert. Unter 3.1.4 funktioniert es wie beschrieben.
Die Positionierung auf der Kachel kommt immer mal wieder vor - hat etwas mit dem Browser zoom zu tun. Mach den mal etwas kleiner oder etwas grósser, dann sollte das wieder passen.
Es hat mehrere Jahre gut funktioniert unter egal welchem Browser, und erst ab 3.1.5 muss man mit zoom spielen.
Da habe ich bisher keine saubere Lósung für gefunden.
A.