Test Adapter zigbee2mqtt
-
@idlebit Ich weiß ich nerve
Bei dem Roborock-Adapter, der scheinbar auch via MQTT kommuniziert, hatte ein user auch diese seltsamen Fehlermeldungen, da wurde scheinbar was am Adapter angepasst. Da ich nun leider absolut keinen Dunst davon habe, was da eigentlich schief läuft, kann ich auch nicht deuten ob das jetzt 100% das gleiche Problem ist.https://github.com/copystring/ioBroker.roborock/issues/27
closed 0.0.5 Adapter startet ständig neu #27
-
@toralt Mein Adapter abreitet über Websocket, MQTT ist nur Experimentell und nicht voll getestet!
Also wenn Du MQTT nutzten solltest stell das erstmal um. -
@idlebit nope, bin auf websocket, ganz nach Empfehlung.
-
@idlebit
Guten Morgen,
ich will auf zigbee2mqtt umsteigen habe Folgendes Problem mit dem Aqara presence detector FP1 RTCZCGQ11LM in Verbindung mit dem zigbee2mqtt Adapter.
Bei Z2M bekomme ich folgende Warnung nach/während dem Koppeln.warning 2023-02-18 10:22:24zigbee-herdsman-converters:xiaomi:aqara_fp1: Unknown key 0x010c = 3Iobroker Protokoll:
host.AndCom 2023-02-18 10:23:39.276 info "system.adapter.zigbee2mqtt.0" disabled host.AndCom 2023-02-18 10:23:30.137 warn Do not restart adapter system.adapter.zigbee2mqtt.0 because restart loop detected host.AndCom 2023-02-18 10:23:30.137 info Restart adapter system.adapter.zigbee2mqtt.0 because enabled host.AndCom 2023-02-18 10:23:30.136 error instance system.adapter.zigbee2mqtt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) zigbee2mqtt.0 2023-02-18 10:23:29.580 warn Terminated (UNCAUGHT_EXCEPTION): Without reason zigbee2mqtt.0 2023-02-18 10:23:29.579 info terminating zigbee2mqtt.0 2023-02-18 10:23:29.568 warn Start try again in 1 seconds... zigbee2mqtt.0 2023-02-18 10:23:29.546 error Cannot set properties of undefined (setting 'prop') zigbee2mqtt.0 2023-02-18 10:23:29.546 error TypeError: Cannot set properties of undefined (setting 'prop') at createDeviceFromExposes (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/lib/exposes.js:970:29) at DeviceController.createDeviceDefinitions (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/lib/deviceController.js:30:39) at Zigbee2mqtt.messageParse (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/main.js:154:40) at WebSocket.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/main.js:125:18) at WebSocket.emit (node:events:525:35) at Receiver.receiverOnMessage (/opt/iobroker/node_modules/ws/lib/websocket.js:1180:20) at Receiver.emit (node:events:513:28) at Receiver.dataMessage (/opt/iobroker/node_modules/ws/lib/receiver.js:541:14) at Receiver.getData (/opt/iobroker/node_modules/ws/lib/receiver.js:459:17) at Receiver.startLoop (/opt/iobroker/node_modules/ws/lib/receiver.js:158:22) zigbee2mqtt.0 2023-02-18 10:23:29.544 error unhandled promise rejection: Cannot set properties of undefined (setting 'prop') zigbee2mqtt.0 2023-02-18 10:23:29.544 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().Der Z2M Adapter wird Rot, wenn ich den FP1 lösche, dann wird die Instanz wieder Grün.
Fehler tritt mit Conbee2 und Zonoff Stick auf.
Bitte um Hilfe, sonst lohnt sich der umstieg für mich nicht, habe mehrere FP1 im einsatz. -
Ich bin grad unterwegs, daher nur kurz und knapp.
warning 2023-02-18 10:22:24zigbee-herdsman-converters:xiaomi:aqara_fp1: Unknown key 0x010c = 3Hier kann ich so grundsätzlich nicht viel machen und muss auf zigbee2mqtt verweisen.
Aber das der Adapter dann abstürzt ist nicht ok und das werde ich mir natürlich ansehen.
@andre hattest du nicht auch den FP1 im Einsatz?
-
@idlebit Vielen Dank für die schnelle Antwort und deine Mühe
-
@aragon sagte in Test Adapter zigbee2mqtt:
aqara_fp1
der hat noch ein paar probleme .. hab ich gerade festgestellt.. musst du abwarten
-
@idlebit sagte in Test Adapter zigbee2mqtt:
@andre hattest du nicht auch den FP1 im Einsatz?
Ich hab den auch im Einsatz. Pairing war problemlos. Meldungen im Log habe ich nicht. Coordinator ist ein Sonoff ZBDongle-E.
Derzeit verwende ich nur den Datenpunkt "presence" über verschiedene scripte. Das tut zuverlässig, sonst hätte ich schon Probleme mit der Frau...
[EDIT] Mal bei zigbee2mqtt geschaut? Da scheint es Einschränkungen zu geben was Zigbee Channel und Firmware angeht...
https://www.zigbee2mqtt.io/devices/RTCZCGQ11LM.htmlMfG,
André -
@andre ne du der macht allgemein noch probleme...
da werden nicht alle exposes gezogen... hab mal ein Fix auf Github gestellt -
@arteck Hast mal nen Link für mich?
-
@aragon Kannst du mal aus dem Git installieren?
Jetzt sollte maximal "nur" noch ein Warning auftauchen, und wenn du auf Debug stellst sollte es noch mehr Infos über das Problem kommen...Könntest Du mir die mal zu Verfügung stellen?
@toralt das könnte auch mit deinen Problem zusammenhängen also nen Versuch wert
-
-
@idlebit
Ich hoffe ich habe alles richtig gemacht.
Hier die aktuelle Ausgabe im Protokoll. Die Instanz wird Rot.host.AndCom 2023-02-18 14:27:49.105 info "system.adapter.zigbee2mqtt.0" disabled host.AndCom 2023-02-18 14:27:42.918 info Restart adapter system.adapter.zigbee2mqtt.0 because enabled host.AndCom 2023-02-18 14:27:42.917 error instance system.adapter.zigbee2mqtt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) mqtt.0 2023-02-18 14:27:42.457 info Server: Changed type of "mqtt.0.zigbee2mqtt.0x54ef4410006492a3" from "number" to "string" zigbee2mqtt.0 2023-02-18 14:27:42.360 warn Terminated (UNCAUGHT_EXCEPTION): Without reason zigbee2mqtt.0 2023-02-18 14:27:42.358 info terminating zigbee2mqtt.0 2023-02-18 14:27:42.350 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } zigbee2mqtt.0 2023-02-18 14:27:42.318 warn Start try again in 1 seconds... zigbee2mqtt.0 2023-02-18 14:27:42.304 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } zigbee2mqtt.0 2023-02-18 14:27:42.291 error Cannot set properties of undefined (setting 'prop') zigbee2mqtt.0 2023-02-18 14:27:42.290 error TypeError: Cannot set properties of undefined (setting 'prop') at createDeviceFromExposes (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/lib/exposes.js:970:29) at DeviceController.createDeviceDefinitions (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/lib/deviceController.js:30:39) at Zigbee2mqtt.messageParse (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/main.js:154:40) at WebSocket.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/main.js:125:18) at WebSocket.emit (node:events:525:35) at Receiver.receiverOnMessage (/opt/iobroker/node_modules/ws/lib/websocket.js:1180:20) at Receiver.emit (node:events:513:28) at Receiver.dataMessage (/opt/iobroker/node_modules/ws/lib/receiver.js:541:14) at Receiver.getData (/opt/iobroker/node_modules/ws/lib/receiver.js:459:17) at Receiver.startLoop (/opt/iobroker/node_modules/ws/lib/receiver.js:158:22) zigbee2mqtt.0 2023-02-18 14:27:42.289 error unhandled promise rejection: Cannot set properties of undefined (setting 'prop') zigbee2mqtt.0 2023-02-18 14:27:42.288 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(). zigbee2mqtt.0 2023-02-18 14:27:42.287 info MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x54ef4410006492a3","ieee_address":"0x54ef4410006492a3","status":"started"},"type":"device_interview"}' zigbee2mqtt.0 2023-02-18 14:27:42.272 info Starting interview of '0x54ef4410006492a3' zigbee2mqtt.0 2023-02-18 14:27:42.270 info MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x54ef4410006492a3","ieee_address":"0x54ef4410006492a3"},"type":"device_joined"}' zigbee2mqtt.0 2023-02-18 14:27:42.264 error Cannot set properties of undefined (setting 'prop') zigbee2mqtt.0 2023-02-18 14:27:42.264 error TypeError: Cannot set properties of undefined (setting 'prop') at createDeviceFromExposes (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/lib/exposes.js:970:29) at DeviceController.createDeviceDefinitions (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/lib/deviceController.js:30:39) at Zigbee2mqtt.messageParse (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/main.js:154:40) at WebSocket.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/main.js:125:18) at WebSocket.emit (node:events:525:35) at Receiver.receiverOnMessage (/opt/iobroker/node_modules/ws/lib/websocket.js:1180:20) at Receiver.emit (node:events:513:28) at Receiver.dataMessage (/opt/iobroker/node_modules/ws/lib/receiver.js:541:14) at Receiver.getData (/opt/iobroker/node_modules/ws/lib/receiver.js:459:17) at Receiver.startLoop (/opt/iobroker/node_modules/ws/lib/receiver.js:158:22) zigbee2mqtt.0 2023-02-18 14:27:42.261 error unhandled promise rejection: Cannot set properties of undefined (setting 'prop') zigbee2mqtt.0 2023-02-18 14:27:42.260 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(). zigbee2mqtt.0 2023-02-18 14:27:42.234 info Device '0x54ef4410006492a3' joined zigbee2mqtt.0 2023-02-18 14:27:29.384 info MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{"time":254,"value":true},"status":"ok","transaction":"1t5n7-4"}' -
Das scheint aber nicht die aktuelle Version vom git zu sein.
Wie bist du vorgegangen?
-
@idlebit
Instanz entfernt
Expertenmodus eingeschaltet
auf die Katze geklickt
dann von Github geklickt
Adapter aus Liste ausgesucht und installiert
Anschließend Adapter installiert -
@aragon Entfernen musst du nichts, aber der Rest passt .. komisch ich prüfe ..
-
@idlebit
Mein Fehler hatte in den Einstellungen unter Repositories auf Beta stehen, umgestellt auf Stable.
Jetzt siehts anders aus, Instanz bleibt GRÜN.zigbee2mqtt.0 2023-02-18 14:53:17.474 debug {"date_code":"20210121","definition":{"description":"Aqara presence detector FP1","exposes":[{"access":5,"description":"Indicates whether the device detected presence","name":"presence","property":"presence","type":"binary","value_off":false,"value_on":true},{"access":1,"description":"Temperature of the device","name":"device_temperature","property":"device_temperature","type":"numeric","unit":"°C"},{"access":1,"description":"Number of power outages (since last pairing)","name":"power_outage_count","property":"power_outage_count","type":"numeric"},{"access":1,"description":"Presence events: \"enter\", \"leave\", \"left_enter\", \"right_leave\", \"right_enter\", \"left_leave\", \"approach\", \"away\"","name":"presence_event","property":"presence_event","type":"enum","values":["enter","leave","left_enter","right_leave","right_enter","left_leave","approach","away"]},{"access":7,"description":"Monitoring mode with or without considering right and left sides","name":"monitoring_mode","property":"monitoring_mode","type":"enum","values":["undirected","left_right"]},{"access":7,"description":"The distance at which the sensor detects approaching","name":"approach_distance","property":"approach_distance","type":"enum","values":["far","medium","near"]},{"access":7,"description":"Different sensitivities means different static human body recognition rate and response speed of occupied","name":"motion_sensitivity","property":"motion_sensitivity","type":"enum","values":["low","medium","high"]},{"access":2,"description":"Reset the status of no presence","name":"reset_nopresence_status","property":"reset_nopresence_status","type":"enum","values":[""]},{"access":1,"description":"Most recent region event. Event template is \"region_<REGION_ID>_<EVENT_TYPE>\", where <REGION_ID> is region number (1-10), <EVENT_TYPE> is one of \"enter\", \"leave\", \"occupied\", \"unoccupied\". \"enter\" / \"leave\" events are usually triggered first, followed by \"occupied\" / \"unoccupied\" after a couple of seconds.","name":"action","property":"action","type":"enum","values":["region_*_enter","region_*_leave","region_*_occupied","region_*_unoccupied"]},{"access":2,"description":"Definition of a new region to be added (or replace existing one). Creating or modifying a region requires you to define which zones of a 7x4 detection grid should be active for that zone. Regions can overlap, meaning that a zone can be defined in more than one region (eg. \"zone x = 1 & y = 1\" can be added to region 1 & 2). \"Zone x = 1 & y = 1\" is the nearest zone on the right (from sensor's perspective, along the detection path).","features":[{"access":2,"name":"region_id","property":"region_id","type":"numeric","value_max":10,"value_min":1},{"access":2,"item_type":{"features":[{"access":2,"name":"x","property":"x","type":"numeric","value_max":4,"value_min":1},{"access":2,"name":"y","property":"y","type":"numeric","value_max":7,"value_min":1}],"name":"zone_position","type":"composite"},"name":"zones","property":"zones","type":"list"}],"name":"region_upsert","property":"region_upsert","type":"composite"},{"access":2,"description":"Region definition to be deleted from the device.","features":[{"access":2,"name":"region_id","property":"region_id","type":"numeric","value_max":10,"value_min":1}],"name":"region_delete","property":"region_delete","type":"composite"},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"RTCZCGQ11LM","options":[{"access":2,"description":"Calibrates the device_temperature value (absolute offset), takes into effect on next report of device.","name":"device_temperature_calibration","property":"device_temperature_calibration","type":"numeric"}],"supports_ota":true,"vendor":"Xiaomi"},"disabled":false,"endpoints":{"1":{"bindings":[],"clusters":{"input":["genBasic","genIdentify","aqaraOpple"],"output":["genIdentify","genOta"]},"configured_reportings":[],"scenes":[]}},"friendly_name":"0x54ef4410006492a3","ieee_address":"0x54ef4410006492a3","interview_completed":false,"interviewing":false,"manufacturer":"aqara","model_id":"lumi.motion.ac01","network_address":58871,"power_source":"DC Source","software_build_id":"","supported":true,"type":"EndDevice"} zigbee2mqtt.0 2023-02-18 14:53:17.473 warn Cannot 0x54ef4410006492a3 create Device from Exposes! zigbee2mqtt.0 2023-02-18 14:53:17.464 debug Device: 0x54ef4410006492a3 not found, queue state in incStatsQueue! zigbee2mqtt.0 2023-02-18 14:53:17.463 debug Device: 0x54ef4410006492a3 not found, queue state in incStatsQueue! zigbee2mqtt.0 2023-02-18 14:53:17.463 debug Device: 0x54ef4410006492a3 not found, queue state in incStatsQueue! zigbee2mqtt.0 2023-02-18 14:53:17.462 debug Device: 0x54ef4410006492a3 not found, queue state in incStatsQueue! zigbee2mqtt.0 2023-02-18 14:53:17.462 debug Device: 0x54ef4410006492a3 not found, queue state in incStatsQueue! zigbee2mqtt.0 2023-02-18 14:53:17.461 debug Device: 0x54ef4410006492a3 not found, queue state in incStatsQueue! zigbee2mqtt.0 2023-02-18 14:53:17.461 debug Device: 0x54ef4410006492a3 not found, queue state in incStatsQueue! zigbee2mqtt.0 2023-02-18 14:53:17.460 debug Device: 0x54ef4410006492a3 not found, queue state in incStatsQueue! zigbee2mqtt.0 2023-02-18 14:53:17.460 debug Device: 0x54ef4410006492a3 not found, queue state in incStatsQueue! zigbee2mqtt.0 2023-02-18 14:53:17.459 debug Device: 0x54ef4410006492a3 not found, queue state in incStatsQueue! zigbee2mqtt.0 2023-02-18 14:53:17.445 info Starting interview of '0x54ef4410006492a3' zigbee2mqtt.0 2023-02-18 14:53:17.433 info MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x54ef4410006492a3","ieee_address":"0x54ef4410006492a3"},"type":"device_joined"}' zigbee2mqtt.0 2023-02-18 14:53:17.428 debug TypeError: Cannot set properties of undefined (setting 'prop') -
@idlebit ich habs jetzt nicht ganz kapiert, habe aber auch 4 x FP1 im Einsatz. Ich habe nun auch mit der Katze via Github nochmal den Treiber installiert.
Habe eben den 1.30.1 Container gestartet -> Läuft!
Besten Dank! -
@aragon Konnte den Fehler eingrenzen...
Dieser neuen State mach mir Probleme weil er eine Objekt in einen Objekt ist und das gab es meines Wissens vorher nicht. da muss ich nun mal grübeln wie ich das umsetzte.
{ "access": 2, "description": "Definition of a new region to be added (or replace existing one). Creating or modifying a region requires you to define which zones of a 7x4 detection grid should be active for that zone. Regions can overlap, meaning that a zone can be defined in more than one region (eg. \"zone x = 1 & y = 1\" can be added to region 1 & 2). \"Zone x = 1 & y = 1\" is the nearest zone on the right (from sensor's perspective, along the detection path).", "features": [ { "access": 2, "name": "region_id", "property": "region_id", "type": "numeric", "value_max": 10, "value_min": 1 }, { "access": 2, "item_type": { "features": [ { "access": 2, "name": "x", "property": "x", "type": "numeric", "value_max": 4, "value_min": 1 }, { "access": 2, "name": "y", "property": "y", "type": "numeric", "value_max": 7, "value_min": 1 } ], "name": "zone_position", "type": "composite" }, "name": "zones", "property": "zones", "type": "list" } ], "name": "region_upsert", "property": "region_upsert", "type": "composite" }, -
@idlebit Okay vielen Dank für die Info und deine Mühe
