NEWS
ZigBee neue Version 1.5.x
-
nur nebenbei, in der Detailansicht werden die Daten etwas ineinander verschoben, hat jetzt keine Prio, aber wollte es mal gemeldet haben.
Hier mal in Version 1.5.3: -
@arteck Bei mir geht es - mit der aktuellen Version - leider immer noch nicht. Noch eine wahrscheinlich blöde Frage, aber wo finde ich den bei github die alten Versionen z.B. 1.4.3
-
@asgothian Ich bin nicht näher darauf eingegangen, da der gleiche Fehler ja schon in mehreren Posts beschrieben wurde und auch ein issue auf Gihub erstellt wurde (dieser wurde nach meiner Meinung fälschlicherweise geschlossen, da nur ein Upgrade Besserung brachte).
Hier der Log nach einem Adapterneustart:zigbee.0 2021-05-02 14:52:03.256 warn (29011) ELEVATED publishToState: value generated '10' from device 804b50fffe0475a0 for 'Link quality' zigbee.0 2021-05-02 14:52:03.256 warn (29011) ELEVATED publishToState: message received '{"linkquality":10}' from device 804b50fffe0475a0 type 'NAS-AB02B0' zigbee.0 2021-05-02 14:52:03.256 warn (29011) ELEVATED publishToState: value generated 'true' from device 804b50fffe0475a0 for 'Available' zigbee.0 2021-05-02 14:52:03.256 warn (29011) ELEVATED publishToState: message received '{"available":true}' from device 804b50fffe0475a0 type 'NAS-AB02B0' zigbee.0 2021-05-02 14:52:02.426 error (29011) Device 0x00158d0002d40924 "undefined" not described in statesMapping. zigbee.0 2021-05-02 14:52:02.257 info (29011) Zigbee started zigbee.0 2021-05-02 14:52:02.257 info (29011) 0x84182600000e8d75 (addr 17041): AB3257001NJ - OSRAM Smart+ plug (Router) zigbee.0 2021-05-02 14:52:02.256 info (29011) 0x588e81fffed39055 (addr 49501): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router) zigbee.0 2021-05-02 14:52:02.256 info (29011) 0x04cf8cdf3c77d5ba (addr 932): WXCJKG11LM - Xiaomi Aqara Opple switch 1 band (EndDevice) zigbee.0 2021-05-02 14:52:02.256 info (29011) 0x00158d0002e9455f (addr 20024): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.256 info (29011) 0x00158d00036765d3 (addr 59164): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.255 info (29011) 0x00158d0002b43bc8 (addr 2461): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.255 info (29011) 0xccccccfffe9734b3 (addr 2226): E1524/E1810 - IKEA TRADFRI remote control (EndDevice) zigbee.0 2021-05-02 14:52:02.255 info (29011) 0x04cf8cdf3c794714 (addr 20576): WXCJKG13LM - Xiaomi Aqara Opple switch 3 bands (EndDevice) zigbee.0 2021-05-02 14:52:02.255 info (29011) 0xf0d1b800001280d4 (addr 32506): 4058075181472 - LEDVANCE SMART+ panel 60 x 60cm tunable white (Router) zigbee.0 2021-05-02 14:52:02.254 info (29011) 0x00158d000346c229 (addr 52234): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.254 info (29011) 0x00158d0002130983 (addr 22133): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice) zigbee.0 2021-05-02 14:52:02.253 info (29011) 0x588e81fffed981b6 (addr 55626): TS011F_socket_module - TuYa Socket module (Router) zigbee.0 2021-05-02 14:52:02.253 info (29011) 0x00158d000237d2a7 (addr 12343): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.253 info (29011) 0x588e81fffed981fe (addr 20649): TS011F_socket_module - TuYa Socket module (Router) zigbee.0 2021-05-02 14:52:02.253 info (29011) 0xec1bbdfffea217a1 (addr 13489): TS0201 - TuYa Temperature & humidity sensor with display (EndDevice) zigbee.0 2021-05-02 14:52:02.252 info (29011) 0x00158d000316d3c1 (addr 6467): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.252 info (29011) 0x00124b00226763aa (addr 28907): YSR-MINI-01_dimmer - YSRSAI Zigbee LED controller (Dimmer) (Router) zigbee.0 2021-05-02 14:52:02.252 info (29011) 0x00158d0002b49103 (addr 25437): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.252 info (29011) 0x00124b0022e96882 (addr 46137): SNZB-03 - SONOFF Motion sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.251 info (29011) 0x00124b00199448e7 (addr 48893): GL-C-009 - Gledopto Zigbee LED Controller W (Router) zigbee.0 2021-05-02 14:52:02.251 info (29011) 0x00158d0004015f87 (addr 54921): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.251 info (29011) 0x00158d0002e9e6e0 (addr 65069): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.251 info (29011) 0x00158d0002d40924 (addr 47558): Not supported (model undefined)(Unknown) zigbee.0 2021-05-02 14:52:02.251 info (29011) 0x00158d0003e748be (addr 33172): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.250 info (29011) 0x804b50fffe0475a0 (addr 63402): NAS-AB02B0 - Neo Temperature & humidity sensor and alarm (EndDevice) zigbee.0 2021-05-02 14:52:02.250 info (29011) 0x588e81fffe61cbea (addr 15118): E1746 - IKEA TRADFRI signal repeater (Router) zigbee.0 2021-05-02 14:52:02.250 info (29011) 0x841826000010673d (addr 14036): AB3257001NJ - OSRAM Smart+ plug (Router) zigbee.0 2021-05-02 14:52:02.250 info (29011) 0x00158d0002a523d7 (addr 2628): DJT11LM - Xiaomi Aqara vibration sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.249 info (29011) 0x588e81fffed3a1f5 (addr 18328): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router) zigbee.0 2021-05-02 14:52:02.249 info (29011) 0x588e81fffed39fca (addr 4570): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router) zigbee.0 2021-05-02 14:52:02.249 info (29011) 0x5c0272fffec88a9f (addr 22854): TS0043 - TuYa Wireless switch with 3 buttons (EndDevice) zigbee.0 2021-05-02 14:52:02.249 info (29011) 0x00158d0002c8ca73 (addr 2742): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice) zigbee.0 2021-05-02 14:52:02.248 info (29011) 0x00124b001e7328ee (addr 29005): BASICZBR3 - SONOFF Zigbee smart switch (Router) zigbee.0 2021-05-02 14:52:02.248 info (29011) 0x588e81fffed4af03 (addr 56298): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router) zigbee.0 2021-05-02 14:52:02.248 info (29011) 0x04cf8cdf3c75bc86 (addr 48652): WXCJKG12LM - Xiaomi Aqara Opple switch 2 bands (EndDevice) zigbee.0 2021-05-02 14:52:02.248 info (29011) 0x04cf8cdf3c797027 (addr 53350): WXCJKG13LM - Xiaomi Aqara Opple switch 3 bands (EndDevice) zigbee.0 2021-05-02 14:52:02.247 info (29011) 0x04cf8cdf3c75b41d (addr 4216): WXCJKG13LM - Xiaomi Aqara Opple switch 3 bands (EndDevice) zigbee.0 2021-05-02 14:52:02.247 info (29011) 0x04cf8cdf3c75c2c5 (addr 2613): WXCJKG12LM - Xiaomi Aqara Opple switch 2 bands (EndDevice) zigbee.0 2021-05-02 14:52:02.247 info (29011) 0x842e14fffe3a3ede (addr 52955): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router) zigbee.0 2021-05-02 14:52:02.246 info (29011) 0x00158d00028f7b08 (addr 12830): WXKG03LM_rev2 - Xiaomi Aqara single key wireless wall switch (2018 model) (EndDevice) zigbee.0 2021-05-02 14:52:02.246 info (29011) 0x7cb03eaa0a050960 (addr 61861): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router) zigbee.0 2021-05-02 14:52:02.246 info (29011) 0x7cb03eaa0a07cf0e (addr 4872): AB3257001NJ - OSRAM Smart+ plug (Router) zigbee.0 2021-05-02 14:52:02.246 info (29011) 0x14b457fffe077051 (addr 30594): 2AJZ4KPBS - Konke Motion sensor (EndDevice) zigbee.0 2021-05-02 14:52:02.245 info (29011) 0x04cf8cdf3c75b44a (addr 60992): WXCJKG13LM - Xiaomi Aqara Opple switch 3 bands (EndDevice) zigbee.0 2021-05-02 14:52:02.245 info (29011) 0x842e14fffe3a4295 (addr 10137): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router) zigbee.0 2021-05-02 14:52:02.245 info (29011) 0x7cb03eaa0a04cfa1 (addr 46521): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router) zigbee.0 2021-05-02 14:52:02.244 info (29011) 0x00158d000289e4c9 (addr 22483): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice) zigbee.0 2021-05-02 14:52:02.244 warn (29011) ELEVATED publishToState: value generated '10' from device 804b50fffe0475a0 for 'Link quality' zigbee.0 2021-05-02 14:52:02.244 warn (29011) ELEVATED publishToState: message received '{"linkquality":10}' from device 804b50fffe0475a0 type 'NAS-AB02B0' zigbee.0 2021-05-02 14:52:02.244 warn (29011) ELEVATED publishToState: value generated 'true' from device 804b50fffe0475a0 for 'Available' zigbee.0 2021-05-02 14:52:02.243 warn (29011) ELEVATED publishToState: message received '{"available":true}' from device 804b50fffe0475a0 type 'NAS-AB02B0' zigbee.0 2021-05-02 14:52:02.243 info (29011) 0x5c0272fffea16c09 (addr 3637): TS0044 - TuYa Wireless switch with 4 buttons (EndDevice) zigbee.0 2021-05-02 14:52:02.208 info (29011) Currently 48 devices are joined: zigbee.0 2021-05-02 14:52:02.203 info (29011) --> transmitPower : normal zigbee.0 2021-05-02 14:52:02.203 info (29011) Unable to disable LED, unsupported function. zigbee.0 2021-05-02 14:52:02.202 info (29011) Disable LED zigbee.0 2021-05-02 14:52:02.197 info (29011) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}} zigbee.0 2021-05-02 14:52:00.327 info (29011) debug devices set to ["804b50fffe0475a0"] zigbee.0 2021-05-02 14:52:00.324 info (29011) Installed Version: ioBroker/ioBroker.zigbee#0d9f7eb89ed12e8289a323e41d3c5b341d261bfc zigbee.0 2021-05-02 14:52:00.264 info (29011) Starting Zigbee npm ... zigbee.0 2021-05-02 14:52:00.239 info (29011) starting. Version 1.5.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.19.0, js-controller: 3.2.16 host.DESKTOP-24U17KH(SHome) 2021-05-02 14:51:59.551 info instance system.adapter.zigbee.0 started with pid 29011 host.DESKTOP-24U17KH(SHome) 2021-05-02 14:51:57.551 info instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zigbee.0 2021-05-02 14:51:56.989 info (23592) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 2021-05-02 14:51:56.989 info (23592) terminating zigbee.0 2021-05-02 14:51:56.592 warn (23592) ELEVATED publishToState: value generated '0' from device 804b50fffe0475a0 for 'Link quality' zigbee.0 2021-05-02 14:51:56.592 warn (23592) ELEVATED publishToState: message received '{"linkquality":0}' from device 804b50fffe0475a0 type 'NAS-AB02B0' zigbee.0 2021-05-02 14:51:56.592 warn (23592) ELEVATED publishToState: value generated 'false' from device 804b50fffe0475a0 for 'Available' zigbee.0 2021-05-02 14:51:56.592 warn (23592) ELEVATED publishToState: message received '{"available":false}' from device 804b50fffe0475a0 type 'NAS-AB02B0' zigbee.0 2021-05-02 14:51:56.531 info (23592) Zigbee: disabling joining new devices. zigbee.0 2021-05-02 14:51:56.531 info (23592) cleaned everything up... zigbee.0 2021-05-02 14:51:56.530 info (23592) Got terminate signal TERMINATE_YOURSELF host.DESKTOP-24U17KH(SHome) 2021-05-02 14:51:56.530 info stopInstance system.adapter.zigbee.0 send kill signal host.DESKTOP-24U17KH(SHome) 2021-05-02 14:51:56.528 info stopInstance system.adapter.zigbee.0 (force=false, process=true)
Die Warnung kommt von meinem noch nicht gelösten "Sirenen" Problem. Welches Gerät den Fehler verursacht kann ich mangels Ansicht in Geräte nicht sehen.
@arteck Die Version habe ich gerade von Github -
@docgame du musst auf die JavaScript Konsole im Web Browser schauen - da wird es eine Fehlermeldung geben aus der zu erkennen ist warum nichts angezeigt wird.
Diese Fehlermeldung wird gebraucht.
A.
-
@asgothian Bringt dich das weiter ?:
-
Hallo,
ich bin gestern von meinem PI auf einen NUC mit Proxmox und iobroker VM umgezogen. Es hat auch alles geklappt nur der Zigbee liefert mir ein paar Warnungen und stürzt dann irgendwann ab. Kann mir da einer weiterhelfen?
DeviceConfigure failed 0xccccccfffe3a4182 eTRV0100, attempt 3 (Error: ConfigureReporting 0xccccccfffe3a4182/1 hvacThermostat([{"attribute":{"ID":16402,"type":16},"minimumReportInterval":0,"maximumReportInterval":600,"reportableChange":1}], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":4678,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received) at DeconzAdapter.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:607:23) at Generator.throw (<anonymous>) at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:25:65) at runMicrotasks (<anonymous>) at runNextTicks (internal/process/task_queues.js:62:5) at processTimers (internal/timers.js:494:9))
DeviceConfigure failed 0x680ae2fffe16cb14 SYMFONISK Sound Controller, attempt 1 (Error: Bind 0x680ae2fffe16cb14/1 genLevelCtrl from '0x00212effff06973a/1' failed (waiting for response TIMEOUT) at DeconzAdapter.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:711:23) at Generator.throw (<anonymous>) at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:25:65))
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().
unhandled promise rejection: Write 0xccccccfffe7caf45/1 genTime({"timeStatus":3,"time":673271883,"timeZone":7200}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)
Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port' at Driver.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/driver.js:160:28) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/driver.js:8:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/driver.js:4:12) at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/driver.js:158:45) at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14) at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
-
-
@docgame Bitte von meinem Test branch installieren und schauen ob der Fehler weg ist.
(https://github.com/asgothian/ioBroker.zigbee/tarball/GroupsOnDashboard)Wenn der Fehler damit weg ist kann ich schauen ob ich das kurzfristig in den haupt-Zweig gemerged bekomme.
Wichtig: Nach der installation von Github einmal ein Upload des Adapters anstossen.
A.
Bitte besagten Test branch NICHT neu installieren. Ein PR für die Anpassung wegen der fehlenden Device Cards ist gestellt, die Anpassung sollte im Laufe der nächsten Tage in die Aktuelle GitHub Version hinein kommen. Der oben verlinkte Test-Zweig ist aktuell NICHT Stabil. -
@asgothian jetzt wirds merkwürdig:
Nach wegklicken ist in den Einstellungen nichts mehr drin.
-
@docgame Geduld.
- hast du ein Upload gemacht ?
- hast du gewartet bis der Adapter hochgelaufen ist bevor du die Konfiguration geöffnet hast ?
- gibt es warn Meldungen im Log oder in der JS Konsole ?
A.
Nachtrag: Bitte erneut installieren. Gleicher Link.
-
@asgothian Jetzt scheint es wieder zu gehen (Zeigt 1.5.1) Ich bleibe erst mal darauf bis ich was anderes höre....
Vielen Dank und weiterhin gute Besserung.
PS: Hat dir der Log der Sirene, die ich vor einer Woche gepostet habe was gebracht? -
@docgame
Leider nein. Es sind keine Nachrichten von der Sirene aufgetaucht, weswegen der iobroker auch nichts anzeigen kann.Wichtig: Bitte installiere den Test Branch von mir nicht nochmal - der Fix in den Hauptadapter ist auf dem Weg.
-
Sind denn dann die Warnungen im Log, wenn Geräte gepaird werden, auch weg wenn die neue aktuelle Version kommt?
-
@tom-son Nein.
Wenn es aktuell beim Pairen von Geräten Warnmeldungen gibt dann liegt das daran das das Pairen nicht so funktioniert hat wie der Adapter das erwartet. Übliche Gründe sind:
- Die Funkverbindung ist instabil
- Das Gerät antwortet nach dem Pairen nicht mehr
- Die Integration des Gerätes passt nicht zum Gerät.
Keine dieser Ursachen ist durch das Update betroffen. Welche der oben genannten Gründe in Deinem Fall zutreffen kann ich so nicht sagen. Dazu bräuchte ich die Meldungen.
A.
-
@asgothian Ich dachte du kennst das schon da ja schon mal geschrieben wurde...
Wenn ich das Pairen starte (habe mal bewusst nur 30sek eingestellt) dann kommt das parallell ins Log:
zigbee.0 2021-05-02 17:54:16.499 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left" zigbee.0 2021-05-02 17:54:16.498 warn Read-only state "zigbee.0.info.pairingMode" has been written without ack-flag with value "false" zigbee.0 2021-05-02 17:54:16.497 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "0" zigbee.0 2021-05-02 17:54:16.488 info Zigbee: stop joining zigbee.0 2021-05-02 17:54:15.495 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 1" zigbee.0 2021-05-02 17:54:15.491 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "1" zigbee.0 2021-05-02 17:54:14.492 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 2" zigbee.0 2021-05-02 17:54:14.489 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "2" zigbee.0 2021-05-02 17:54:13.487 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 3" zigbee.0 2021-05-02 17:54:13.486 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "3" zigbee.0 2021-05-02 17:54:12.491 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 4" zigbee.0 2021-05-02 17:54:12.487 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "4" zigbee.0 2021-05-02 17:54:11.488 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 5" zigbee.0 2021-05-02 17:54:11.485 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "5" zigbee.0 2021-05-02 17:54:10.489 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 6" zigbee.0 2021-05-02 17:54:10.485 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "6" zigbee.0 2021-05-02 17:54:09.488 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 7" zigbee.0 2021-05-02 17:54:09.485 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "7" zigbee.0 2021-05-02 17:54:08.487 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 8" zigbee.0 2021-05-02 17:54:08.485 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "8" zigbee.0 2021-05-02 17:54:07.488 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 9" zigbee.0 2021-05-02 17:54:07.485 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "9" zigbee.0 2021-05-02 17:54:06.484 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 10" zigbee.0 2021-05-02 17:54:06.482 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "10" zigbee.0 2021-05-02 17:54:05.484 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 11" zigbee.0 2021-05-02 17:54:05.482 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "11" zigbee.0 2021-05-02 17:54:04.484 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 12" zigbee.0 2021-05-02 17:54:04.482 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "12" zigbee.0 2021-05-02 17:54:03.485 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 13" zigbee.0 2021-05-02 17:54:03.482 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "13" zigbee.0 2021-05-02 17:54:02.480 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 14" zigbee.0 2021-05-02 17:54:02.479 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "14" zigbee.0 2021-05-02 17:54:01.483 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 15" zigbee.0 2021-05-02 17:54:01.481 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "15" zigbee.0 2021-05-02 17:54:00.480 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 16" zigbee.0 2021-05-02 17:54:00.478 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "16" zigbee.0 2021-05-02 17:53:59.481 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 17" zigbee.0 2021-05-02 17:53:59.478 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "17" zigbee.0 2021-05-02 17:53:58.485 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 18" zigbee.0 2021-05-02 17:53:58.484 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "18" zigbee.0 2021-05-02 17:53:57.478 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 19" zigbee.0 2021-05-02 17:53:57.477 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "19" zigbee.0 2021-05-02 17:53:56.477 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 20" zigbee.0 2021-05-02 17:53:56.476 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "20" zigbee.0 2021-05-02 17:53:55.479 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 21" zigbee.0 2021-05-02 17:53:55.476 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "21" zigbee.0 2021-05-02 17:53:54.480 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 22" zigbee.0 2021-05-02 17:53:54.477 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "22" zigbee.0 2021-05-02 17:53:53.477 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 23" zigbee.0 2021-05-02 17:53:53.474 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "23" zigbee.0 2021-05-02 17:53:52.477 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 24" zigbee.0 2021-05-02 17:53:52.474 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "24" zigbee.0 2021-05-02 17:53:51.477 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 25" zigbee.0 2021-05-02 17:53:51.473 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "25" zigbee.0 2021-05-02 17:53:50.473 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 26" zigbee.0 2021-05-02 17:53:50.472 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "26" zigbee.0 2021-05-02 17:53:49.473 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 27" zigbee.0 2021-05-02 17:53:49.472 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "27" zigbee.0 2021-05-02 17:53:48.475 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 28" zigbee.0 2021-05-02 17:53:48.472 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "28" zigbee.0 2021-05-02 17:53:47.470 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 29" zigbee.0 2021-05-02 17:53:47.468 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "29" zigbee.0 2021-05-02 17:53:46.472 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 30" zigbee.0 2021-05-02 17:53:46.470 warn Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "30" zigbee.0 2021-05-02 17:53:45.215 warn Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing started "
Bei mir ist das dann noch so dass er die meisten Geräte 2x oder 3x findet, nach einem reload der Seite sind die aber wieder weg...
Adapter Version 1.5.3nodejs -v && npm -v && iobroker -v :
v12.22.1
6.14.12
3.3.5 -
@tom-son sagte in ZigBee neue Version 1.5.x:
3.3.5
Das liegt am js-controller 3.3.x, mit dem 3.2.16 kommt das nicht. Die Meldungen kommen nach dem Upgrade vom js-controller. Das habe ich hier in den letzten Tagen schon bei diversen anderen Adaptern gelesen.
Die Adapter müssen wohl angepasst werden heißt es, -
@tom-son hab ich seit 3.3.5 auch bei diversen Adaptern.
- Mach ein issue für den betroffenen Adapter auf (oder check ob es schon eins gibt)
- Als workaround habe ich bei mir den Loglevel bei betroffenen Adaptern auf "error" gestellt
-
@tom-son die sind meines Wissens bereits Gefixed
A.
-
Hallo in die Runde,
ich möchte gern von meinem Pi mit RaspBee II Steckkarte auf ein Tinkerboard mit LaunchXL-CC1352P-2 und entsprechenden ZigBee Adapter wechseln.
Das Tinkerbord ist als ioBroker Multihost an meinen Master angebunden. Das LaunchXL ist eingebunden und hat auch eine Verbindung zum ioBroker.Ich habe mal die neuste Version des ZigBee Adapter installiert und zwei Geräte angelernt.
Es werden die Daten entsprechend dargestellt. Wenn ich allerdings auf die Kachel klicke dreht diese sich und man kann kurz (ca. halbe Sekunde) den Inhalt sehen und dann ist die Kachel weiß.
Gibt es dazu Informationen?
Nodejs: 12.22.1
npm: 6.14.12
ZigBee: 1.5.4Danke und Gruß
Steffen -
@steffengr sagte in ZigBee neue Version 1.5.x:
Hallo in die Runde,
ich möchte gern von meinem Pi mit RaspBee II Steckkarte auf ein Tinkerboard mit LaunchXL-CC1352P-2 und entsprechenden ZigBee Adapter wechseln.
Das Tinkerbord ist als ioBroker Multihost an meinen Master angebunden. Das LaunchXL ist eingebunden und hat auch eine Verbindung zum ioBroker.Ich habe mal die neuste Version des ZigBee Adapter installiert und zwei Geräte angelernt.
Es werden die Daten entsprechend dargestellt. Wenn ich allerdings auf die Kachel klicke dreht diese sich und man kann kurz (ca. halbe Sekunde) den Inhalt sehen und dann ist die Kachel weiß.
Gibt es dazu Informationen?
Nodejs: 12.22.1
npm: 6.14.12
ZigBee: 1.5.4Danke und Gruß
SteffenEs liegt an Safari.
Wann werden die Zustände für die Batterien aktualisiert?Danke und Gruß
Steffen