ZigBee neue Version 1.7.x
-
@arteck sagte in ZigBee neue Version 1.7.x:
@zarello na wenn die lampe nicht in den pairing modus geht dann kannst du restren was du willst..
Öhm, sie geht in den pairing modus. Zumindest fängt sie an zu flackern.
Was meintest Du denn mit Reset? -
@zarello sagte in ZigBee neue Version 1.7.x:
Öhm, sie geht in den pairing modus. Zumindest fängt sie an zu flackern.
ahh das hast du nicht geschrieben.. dann schau weiter
-
@arteck So, das Backup ist zurückgespielt, alle Adapter sind wieder installiert und gestartet.
Die Lampe ist leider weiterhin nicht im System. Als Datenpunkt ist sie jetzt vorhanden, die Verbindung funktioniert jedoch leider nicht. Es gibt jetzt einen weiteren Datenpunkt im Zigbee-Adapter, der den gleichen Namen mit einem "0x" vorangestellt hat. Da ist der Name, den ich eingegeben hatte hinterlegt:
Ich werde jetzt folgendes versuchen:
- Lampe aus dem Zigbee-Adapter zu entfernen
- Edit: Das normale Löschen hatte nicht funktioniert, Löschen erzwingen verwendet.
- Lampe ausschalten
- Zigbee-Adapter beenden
- evtl. im Objektbaum übrig gebliebene Datenpunkte der Lampe entfernen
- Zigbee-Adapter wieder starten
- Kopplung im Zigbee-Adapter anwerfen
- Lampe wieder in den Kopplungsmodus bringen
Mal sehen, ob sie sich dann wieder verbindet. Ansonsten weiß ich leider nicht mehr weiter.
Edit: Die Kopplung der Lampe klappt weiterhin nicht mehr. Die Lampe geht in den Kopplungsmodus (zumindest interpretiere ich das so, da sie nach dem sechs mal Aus- und Einschalten in ein sanftes, leicht unregelmäßiges Blinken verfällt), sie wird jedoch vom Zigbee-Adapter nicht registriert.
Ich probiere es nun einmal damit den Rechner runterzufahren und neu zu starten. Vielleicht benötigt der Zigbee-USB-Stick eine kleine Pause oder ein Reset.
- Lampe aus dem Zigbee-Adapter zu entfernen
-
@zarello zieh mal den coordinator ab.. und steck den wiedser rein.. gehts jetzt
-
@arteck sagte in ZigBee neue Version 1.7.x:
@zarello zieh mal den coordinator ab.. und steck den wiedser rein.. gehts jetzt
Hurra, reboot des RasPi (incl. Coordinator) hat geholfen. Jetzt konnte ich die Lampe wieder koppeln und sie ist auch richtig konfiguriert. Es waren also wohl tatsächlich Überbleibsel aus einer älteren Version, dass der Typ und der Name am Anfang fehlten.
Vielen Dank
-
@arteck Update auf 1.7.4 von 1.6.18
folgende Warnmeldung bekomme ich im Log.
DeviceConfigure:DeviceConfigure failed 0x54ef44100025c54b lumi.magnet.acn001, attempt 1 (Error: Read 0x54ef44100025c54b/1 genPowerCfg(["batteryVoltage"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received) at DeconzAdapter.sendZclFrameToEndpoint (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:655:23) at Endpoint.sendRequest (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:299:20) at Endpoint.read (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:472:28) at Object.configure (/opt/iobroker/node_modules/zigbee-herdsman-converters/devices/xiaomi.js:54:13) at DeviceConfigure.doConfigure (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceConfigure.js:145:9) at DeviceConfigure.configure (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceConfigure.js:124:17) at DeviceConfigure.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceConfigure.js:60:21) at async Promise.all (index 1))Das hatte ich im 1.6.18 nicht. Es läuft aber eigentlich alles bis auf die Batteriegeschichte, das sind die ganzen fenster und türsensoren mit der falschen batteriespannung also 2950V anstatt 2,95V, genau diese Obejekte erzeugen den Fehler die anderen nicht. Hast du dafür eine Lösung? Danke für das Update schaut gut aus mit der Farbe in dem Objekt Baum.
-
@arteck
Anbei wie gewünscht das Logfile.
Wie gesagt, nach dem Update geht der Adapter in einen BootLoop.
Der Rechner wurde schon neu gestartet und der Sonoff V3+ hat Gestern auch die neueste Firmware erhalten.
Der Fehler tritt aber auch mit dem "alten" CC2531 auf und zwar direkt nach dem Update.
Ich habe auch mal den Adapter gelöscht und neu installiert, leider hat das auch nicht geholfen.2022-05-31 18:41:26.015 - error: zigbee.0 (2622) DB closed 2022-05-31 18:41:26.050 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.070 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.071 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.073 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.097 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.108 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.117 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.127 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.128 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.129 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.175 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.177 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.178 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.179 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.180 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.450 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.452 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.453 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.484 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.485 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.508 - info: zigbee.0 (2622) terminating with timeout 2022-05-31 18:41:26.630 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.643 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.644 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.674 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.681 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.686 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.693 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.704 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.706 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.708 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.718 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.719 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.720 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.728 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.734 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.741 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.742 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.750 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.756 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.762 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.763 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.769 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.866 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.870 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.874 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.875 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.877 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.881 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.882 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.886 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.890 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.894 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.899 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.900 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.907 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.908 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.916 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.918 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.919 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.920 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.922 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.923 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.932 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:26.935 - warn: zigbee.0 (2622) get state error: Connection is closed. 2022-05-31 18:41:27.335 - info: iot.0 (2763) Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com 2022-05-31 18:41:27.522 - info: vis.0 (2868) vis license is OK. 2022-05-31 18:41:27.684 - error: host.smarthome 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: 2022-05-31 18:41:27.686 - error: host.smarthome Caught by controller[0]: TypeError: Cannot read property 'replace' of undefined 2022-05-31 18:41:27.687 - error: host.smarthome Caught by controller[0]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:495:35) 2022-05-31 18:41:27.696 - error: host.smarthome Caught by controller[0]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35) 2022-05-31 18:41:27.696 - error: host.smarthome 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: 2022-05-31 18:41:27.696 - error: host.smarthome Caught by controller[1]: Error: DB closed 2022-05-31 18:41:27.697 - error: host.smarthome Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) 2022-05-31 18:41:27.697 - error: host.smarthome Caught by controller[1]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) 2022-05-31 18:41:27.697 - error: host.smarthome Caught by controller[1]: at Object.onceWrapper (events.js:422:26) 2022-05-31 18:41:27.698 - error: host.smarthome Caught by controller[1]: at Socket.emit (events.js:315:20) 2022-05-31 18:41:27.698 - error: host.smarthome Caught by controller[1]: at Socket.EventEmitter.emit (domain.js:467:12) 2022-05-31 18:41:27.698 - error: host.smarthome Caught by controller[1]: at TCP. (net.js:673:12) 2022-05-31 18:41:27.699 - error: host.smarthome instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-05-31 18:41:27.700 - info: host.smarthome Restart adapter system.adapter.zigbee.0 because enabled 2022-05-31 18:41:28.123 - info: iqontrol.0 (2779) systemLanguage = de 2022-05-31 18:41:28.127 - info: iqontrol.0 (2779) Creating Popup States... 2022-05-31 18:41:30.123 - info: vis.0 (2868) Terminated (NO_ERROR): Without reason 2022-05-31 18:41:30.190 - info: iot.0 (2763) Connection changed: connect 2022-05-31 18:41:31.795 - info: host.smarthome instance system.adapter.vis.0 terminated while should be started once 2022-05-31 18:41:32.659 - info: iqontrol.0 (2779) Creating Widget States... 2022-05-31 18:41:32.661 - info: iqontrol.0 (2779) Lists deactivated. 2022-05-31 18:41:32.662 - info: iqontrol.0 (2779) Deleting unused Objects... 2022-05-31 18:41:32.668 - info: iqontrol.0 (2779) Subscribing to states... 2022-05-31 18:41:32.671 - info: iqontrol.0 (2779) iQontrol ready. 2022-05-31 18:41:33.047 - info: web.0 (2911) starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.web, node: v14.16.1, js-controller: 4.0.23 2022-05-31 18:41:33.909 - info: web.0 (2911) socket.io server listening on port 8082 2022-05-31 18:41:33.924 - info: web.0 (2911) http server listening on port 8082 2022-05-31 18:41:34.573 - info: info.0 (2735) starting. Version 1.9.19 in /opt/iobroker/node_modules/iobroker.info, node: v14.16.1, js-controller: 4.0.23 2022-05-31 18:41:34.897 - info: info.0 (2735) Reading/updating systemdata. 2022-05-31 18:41:36.221 - info: alexa2.0 (2010) Subscribing to states... 2022-05-31 18:41:36.577 - info: info.0 (2735) State value to set for "info.0.sysinfo.cpu.info.speed" has to be type "string" but received type "number" 2022-05-31 18:41:36.776 - info: info.0 (2735) State value to set for "info.0.sysinfo.cpu.info.cache-l3" has to be type "number" but received type "string" 2022-05-31 18:41:37.254 - info: info.0 (2735) cpu Temp res = {"main":49,"cores":[49,49,49,48],"max":49,"socket":[0],"chipset":null} 2022-05-31 18:41:57.883 - info: host.smarthome instance system.adapter.zigbee.0 started with pid 3725 2022-05-31 18:42:03.152 - info: zigbee.0 (3725) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.16.1, js-controller: 4.0.23 2022-05-31 18:42:03.319 - info: zigbee.0 (3725) delete old Backup files. keep only last 10 2022-05-31 18:42:03.322 - info: zigbee.0 (3725) Starting Zigbee npm ... 2022-05-31 18:42:03.939 - info: zigbee.0 (3725) Installed Version: iobroker.zigbee@1.7.4 2022-05-31 18:42:04.809 - info: zigbee.0 (3725) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}} 2022-05-31 18:42:04.820 - info: zigbee.0 (3725) Unable to disable LED, unsupported function. 2022-05-31 18:42:04.841 - info: zigbee.0 (3725) --> transmitPower : normal 2022-05-31 18:42:04.863 - info: zigbee.0 (3725) Currently 12 devices are joined: 2022-05-31 18:42:04.970 - info: zigbee.0 (3725) 0x00158d00044da480 (addr 64924): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:04.983 - info: zigbee.0 (3725) 0x7cb03eaa0a004e60 (addr 62482): AB3257001NJ - OSRAM Smart+ plug (Router) 2022-05-31 18:42:04.986 - info: zigbee.0 (3725) 0x00158d000446f6f1 (addr 3112): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:04.989 - info: zigbee.0 (3725) 0x00158d000446f71a (addr 7985): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:04.993 - info: zigbee.0 (3725) 0x00158d00040171b8 (addr 9070): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:04.994 - info: zigbee.0 (3725) 0x00158d0004234d79 (addr 16889): Not supported (model undefined)(Unknown) 2022-05-31 18:42:04.997 - info: zigbee.0 (3725) 0x00158d0004016171 (addr 16237): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:04.999 - info: zigbee.0 (3725) 0x00158d00040d3ef8 (addr 50029): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:05.001 - info: zigbee.0 (3725) 0x00158d00042302fd (addr 38978): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:05.003 - info: zigbee.0 (3725) 0x00158d0004042239 (addr 52695): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:05.006 - info: zigbee.0 (3725) 0x00158d00047b5630 (addr 58436): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 2022-05-31 18:42:05.009 - info: zigbee.0 (3725) 0x00158d00045c0abb (addr 63218): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 2022-05-31 18:42:05.012 - info: zigbee.0 (3725) Zigbee started 2022-05-31 18:42:05.033 - error: zigbee.0 (3725) 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(). 2022-05-31 18:42:05.034 - error: zigbee.0 (3725) unhandled promise rejection: Cannot read property 'replace' of undefined 2022-05-31 18:42:05.046 - error: zigbee.0 (3725) TypeError: Cannot read property 'replace' of undefined at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:495:35) at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35) 2022-05-31 18:42:05.047 - error: zigbee.0 (3725) Cannot read property 'replace' of undefined 2022-05-31 18:42:05.080 - info: zigbee.0 (3725) cleaned everything up... 2022-05-31 18:42:05.146 - info: zigbee.0 (3725) Zigbee: disabling joining new devices. 2022-05-31 18:42:05.584 - info: zigbee.0 (3725) terminating 2022-05-31 18:42:05.590 - warn: zigbee.0 (3725) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-05-31 18:42:06.128 - warn: zigbee.0 (3725) get state error: Connection is closed. 2022-05-31 18:42:06.129 - warn: zigbee.0 (3725) get state error: Connection is closed. 2022-05-31 18:42:06.327 - error: host.smarthome 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: 2022-05-31 18:42:06.328 - error: host.smarthome Caught by controller[0]: TypeError: Cannot read property 'replace' of undefined 2022-05-31 18:42:06.328 - error: host.smarthome Caught by controller[0]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:495:35) 2022-05-31 18:42:06.329 - error: host.smarthome Caught by controller[0]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35) 2022-05-31 18:42:06.329 - error: host.smarthome instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-05-31 18:42:06.330 - info: host.smarthome Restart adapter system.adapter.zigbee.0 because enabled 2022-05-31 18:42:36.540 - info: host.smarthome instance system.adapter.zigbee.0 started with pid 3788 2022-05-31 18:42:41.573 - info: zigbee.0 (3788) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.16.1, js-controller: 4.0.23 2022-05-31 18:42:41.761 - info: zigbee.0 (3788) delete old Backup files. keep only last 10 2022-05-31 18:42:41.765 - info: zigbee.0 (3788) Starting Zigbee npm ... 2022-05-31 18:42:42.405 - info: zigbee.0 (3788) Installed Version: iobroker.zigbee@1.7.4 2022-05-31 18:42:43.238 - info: zigbee.0 (3788) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}} 2022-05-31 18:42:43.250 - info: zigbee.0 (3788) Unable to disable LED, unsupported function. 2022-05-31 18:42:43.271 - info: zigbee.0 (3788) --> transmitPower : normal 2022-05-31 18:42:43.288 - info: zigbee.0 (3788) Currently 12 devices are joined: 2022-05-31 18:42:43.377 - info: zigbee.0 (3788) 0x00158d00044da480 (addr 64924): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:43.386 - info: zigbee.0 (3788) 0x7cb03eaa0a004e60 (addr 62482): AB3257001NJ - OSRAM Smart+ plug (Router) 2022-05-31 18:42:43.388 - info: zigbee.0 (3788) 0x00158d000446f6f1 (addr 3112): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:43.390 - info: zigbee.0 (3788) 0x00158d000446f71a (addr 7985): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:43.392 - info: zigbee.0 (3788) 0x00158d00040171b8 (addr 9070): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:43.393 - info: zigbee.0 (3788) 0x00158d0004234d79 (addr 16889): Not supported (model undefined)(Unknown) 2022-05-31 18:42:43.395 - info: zigbee.0 (3788) 0x00158d0004016171 (addr 16237): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:43.396 - info: zigbee.0 (3788) 0x00158d00040d3ef8 (addr 50029): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:43.398 - info: zigbee.0 (3788) 0x00158d00042302fd (addr 38978): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:43.400 - info: zigbee.0 (3788) 0x00158d0004042239 (addr 52695): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2022-05-31 18:42:43.402 - info: zigbee.0 (3788) 0x00158d00047b5630 (addr 58436): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 2022-05-31 18:42:43.404 - info: zigbee.0 (3788) 0x00158d00045c0abb (addr 63218): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 2022-05-31 18:42:43.406 - info: zigbee.0 (3788) Zigbee started 2022-05-31 18:42:43.425 - error: zigbee.0 (3788) 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(). 2022-05-31 18:42:43.426 - error: zigbee.0 (3788) unhandled promise rejection: Cannot read property 'replace' of undefined 2022-05-31 18:42:43.427 - error: zigbee.0 (3788) TypeError: Cannot read property 'replace' of undefined at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:495:35) at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35) 2022-05-31 18:42:43.428 - error: zigbee.0 (3788) Cannot read property 'replace' of undefined 2022-05-31 18:42:43.472 - info: zigbee.0 (3788) cleaned everything up... 2022-05-31 18:42:43.537 - info: zigbee.0 (3788) Zigbee: disabling joining new devices. 2022-05-31 18:42:43.977 - info: zigbee.0 (3788) terminating 2022-05-31 18:42:43.983 - warn: zigbee.0 (3788) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-05-31 18:42:45.011 - warn: zigbee.0 (3788) get state error: Connection is closed. 2022-05-31 18:42:45.012 - warn: zigbee.0 (3788) get state error: DB closed 2022-05-31 18:42:45.013 - warn: zigbee.0 (3788) get state error: DB closed 2022-05-31 18:42:45.014 - warn: zigbee.0 (3788) get state error: DB closed 2022-05-31 18:42:45.014 - warn: zigbee.0 (3788) get state error: DB closed 2022-05-31 18:42:45.014 - warn: zigbee.0 (3788) get state error: DB closed 2022-05-31 18:42:45.015 - warn: zigbee.0 (3788) get state error: DB closed 2022-05-31 18:42:45.015 - warn: zigbee.0 (3788) get state error: DB closed 2022-05-31 18:42:45.016 - warn: zigbee.0 (3788) get state error: DB closed 2022-05-31 18:42:45.016 - warn: zigbee.0 (3788) get state error: DB closed 2022-05-31 18:42:45.017 - warn: zigbee.0 (3788) get state error: DB closed 2022-05-31 18:42:45.018 - warn: zigbee.0 (3788) get state error: DB closed 2022-05-31 18:42:45.019 - info: zigbee.0 (3788) terminating with timeout 2022-05-31 18:42:45.027 - warn: zigbee.0 (3788) get state error: Connection is closed. 2022-05-31 18:42:45.028 - warn: zigbee.0 (3788) get state error: Connection is closed. 2022-05-31 18:42:45.029 - warn: zigbee.0 (3788) get state error: Connection is closed. 2022-05-31 18:42:45.030 - warn: zigbee.0 (3788) get state error: Connection is closed. 2022-05-31 18:42:45.031 - warn: zigbee.0 (3788) get state error: Connection is closed. 2022-05-31 18:42:45.210 - error: host.smarthome 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: 2022-05-31 18:42:45.211 - error: host.smarthome Caught by controller[1]: TypeError: Cannot read property 'replace' of undefined 2022-05-31 18:42:45.211 - error: host.smarthome Caught by controller[1]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:495:35) 2022-05-31 18:42:45.211 - error: host.smarthome Caught by controller[1]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35) 2022-05-31 18:42:45.212 - error: host.smarthome instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-05-31 18:42:45.212 - info: host.smarthome Restart adapter system.adapter.zigbee.0 because enabled 2022-05-31 18:42:45.212 - warn: host.smarthome Do not restart adapter system.adapter.zigbee.0 because restart loop detected -
@gountled sagte in ZigBee neue Version 1.7.x:
Cannot read property 'replace' of undefined
installier von GIT und schau nochmal.. da ist ein kaputtes Device in deiner liste
und für die Zukunft LOGs in Code tag bitte..damit man es besser lesen kann
-
@babl sagte in ZigBee neue Version 1.7.x:
DeviceConfigure failed 0x54ef44100025c54b
der hat seine konfog nicht bekommen.. dreh die Kachel von dem Gerät da ist ein icon für nochmaliges senden der konfig.
du musst aber einmal auf den knopf drücken vopn dem Teil zum aufwecken..als beispiel
-
@arteck ok danke dir
-
@arteck Danke!
Post geändert und später installiere ich mal neu aus dem GIT
Das defekte Device bekomme ich nicht gelöscht. -
@arteck Läuft wieder mit 1.7.5.
-
@arteck sagte in ZigBee neue Version 1.7.x:
der Object Baum wird laut dem available status eingefärbt. man kann direkt erkennen welche Geräte offline sind
Wie lange muss ein Sensor nicht online sein damit er als offline gekennzeichnet wird? Da muss ja dann eine Art Verbindung geprüft werden.
Ich prüfe alle 3 Stunden den Zeitstempel um herauszufinden welcher Sensor offline ist. Wäre es besser den available Status zu prüfen? -
@brainbug sensor wird nicht geprüft wie den auch.. der legt sich schlafen wenn der nix sendet..
der available status wird nur zur anfang gesetzt bei start des adapter.. mit dem Zeitstempel ist schon ok -
@arteck Moin, bei mir wird die Version 1.7.5 als neue erkannt. Installiere ich sie sieht zunächst alle gut aus. Einen Moment später steht dann wieder die 1.7.4 als aktuell und in kann die 1.7.5 wieder installieren. Nach 5 Versuchen scheint jetzt die 1.7.5 zu laufen. Es werden allerdings diverse Objekte als nicht angemeldet angezeigt. Nach dem dem Neustart des Adapters werden alle als verbunden angezeigt, aber eben nur für einen Moment? Nutze die aktuelle iobroker Version und einen Conbee II. Hatt jemand eine Idee, wie ich das Verhalten korrigieren kann?
-
Hi,
ich habe hier eine Paulmann LED Leuchte, diese wurde mit vorhingen Versionen zwar falsch erkannt, ich konnte sie aber schalten. Nun funktioniert sie nicht mehr.
New device joined '0x00158d0001dd6d22' model CCT light Interview successful: [object Object] Interview started: 0x00158d0001dd6d22
Edit:
Habe sie wieder zum leuchten bekommen.
Wichtig ist das Leerzeichen bei "CCT light "Könntest du sie hinzufügen?
{ zigbeeModel: ['CCT light '], model: '50083', vendor: 'Paulmann', description: 'LED Panel Cesena', extend: extend.light_onoff_brightness_colortemp(), }, -
Habe jetzt die neue Version 1.7 installiert.
In der Übersicht unter der Zigbee.x.-Instanz sind die Symbole nun zu sehen aber unter Objekte nicht:
-
@segway machmal adapter upload
-
@arteck sagte in ZigBee neue Version 1.7.x:
@segway machmal adapter upload
Yep, hat geklappt !
ABER leider mit weissem Hintergrund und nicht transparent wie die anderen
-
@segway ja einen tod müssen wir sterben.. die werden von zigbee2mqtt genutzt..da sind die leider mit hintergrund
