Phillips Hue Lightstripe reagiert langsam

skunked · 1. Dezember 2024 um 08:40

Hallo zusammen,

ich bediene mein Lightstripe im Wohnzimmer mit dem HUE Tab Dial.
Das Problem ist, wenn ich das Licht dimme, oder per Tastedruck auf eine Helligkeit einstellen möchte, dann reagiert er erst paar Sekunden später… ( 20 Sekunden ca… )

Ich betreibe es mit dem MQTT Stick von Sonoff… ich bekomme folgende Meldung im LOG:

z2m: Publish ‘set’ ‘state’ to ‘Lighstripe Wohnzimmer’ failed: ‘Error: ZCL command 0x00178801049b573a/11 genLevelCtrl.moveToLevelWithOnOff({“level”:0,“transtime”:10}, {“timeout”:10000,“disableResponse”:false,“disableRecovery”:false,“disableDefaultResponse”:false,“direction”:0,“reservedBits”:0,“writeUndiv”:false}) failed (Timeout - 51995 - 11 - 152 - 8 - 11 after 10000ms)’

der LQI des Tap Dials liegt bei 93 genau so auch der Lightstripe…

Hat jemand eine Idee an was das liegen kann ?

dp20eic · 1. Dezember 2024 um 09:14

Moin,

zu wenige Informationen

Welche Versionen und Firmwares, wie und wo installiert?
Ich habe ein Issue gefunden, das diesen Fehler beschreibt, ob es da auch eine Lösung gibt, kann ich nicht sagen, habe es mir nicht durchgelesen.

github.com/Koenkk/zigbee2mqtt

Error: ZCL command genOnOff.on

opened 10:45PM - 11 Apr 24 UTC

closed 11:39PM - 11 May 24 UTC

rw-django-fan-2020

problem

### What happened? My Home Assistant System crashed. Dont know why. Had to move… to another Device (ThinClient). Restored my Home Assistant Backup. But zigbee dont work anymore. Help. ### What did you expect to happen? I expected it to work. ### How to reproduce it (minimal and precise) _No response_ ### Zigbee2MQTT version 1.36.1-1 ### Adapter firmware version 0x26780700 ### Adapter ConBee2/RaspBee2 ### Setup Add-on on Home Assistant OS on Proxmox VM ### Debug log error 2024-04-12 00:24:18Publish 'set' 'state' to 'Blitzwolf Steckdose 2' failed: 'Error: ZCL command 0x3425b4fffe4984d2/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (76))' debug 2024-04-12 00:24:18Error: ZCL command 0x3425b4fffe4984d2/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (76)) at DeconzAdapter.sendZclFrameToEndpoint (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:666:23) at Request.send (/app/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20) at Endpoint.zclCommand (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:760:28) at Endpoint.command (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:591:24) at Object.convertSet (/app/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:46:17) at Publish.onMQTTMessage (/app/lib/extension/publish.ts:259:36) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17)

github.com/Koenkk/zigbee2mqtt

Error: ZCL command genOnOff.on (continuation of #22189)

opened 10:47AM - 17 Oct 24 UTC

majkers

problem

### What happened? This is a continuation of IMHO mistakenly closed issue #2218…9. From time to time. It is hard to tell exactly when but one of my coordinators ie. [Xiaomi ZNCZ02LM](https://www.zigbee2mqtt.io/devices/ZNCZ02LM.html#xiaomi-zncz02lm) fails with an error: `[2024-10-17 12:10:31] error: z2m: Publish 'set' 'state' to 'gniazdko_xiaomi' failed: 'Error: ZCL command 0x00158d0002347282/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 18793 - 1 - 88 - 6 - 11 after 10000ms)'` And since it is a coordinator, all of my devices connected to it fall out off the mesh network. As it is continuation of https://github.com/Koenkk/zigbee2mqtt/issues/22189 you can see that it is a problem of many coordinators with many hardwares. I tested it with Conbee II then moved to Sonoff ZBDongle-P with firmware version 20240710 and then moved back to 20230507 but it doesn't help. I've also noticed that trying to set state via frontend to my socket sometimes do change it as I hear the click sound but there is no confirmation in z2m state and then I see an error mentioned above. ### What did you expect to happen? I expect those errors not to happen ### How to reproduce it (minimal and precise) There is no real reporducer. Maybe setting on/off state quickly. ### Zigbee2MQTT version 1.40.2 ### Adapter firmware version tested with 20230507 and 20240710 ### Adapter Conbee II and Sonoff ZBDongle-P ### Setup Add on on Home Assistant OS ### Debug log _No response_

VG
Bernd

skunked · 1. Dezember 2024 um 09:28

Ich habe Home Assistant auf einem Respi 5 installiert und alles an Hardware ist alles auf dem neusten Stand… ich schau mir mal die Post durch…