search

dresden-elektronik / deconz-rest-plugin

deCONZ REST-API plugin to control ZigBee devices
BSD 3-Clause "New" or "Revised" License
1.9k stars 502 forks source link

Hue Dimmer Switches RWL021 not always working on first key press #2965

Closed networkpotato closed 4 years ago

networkpotato commented 4 years ago

Describe the bug

Once in a while, when pressing (any) button, nothing happens and the Dimmer's LED lights up solid red. Then, upon the next key press, it works again. It's like the Dimmer is asleep and needs to be waken up.

This happens on all my 5 Hue Dimmer Switches. All running on the latest firmware 6.1.1.28573 (same problem on the previous firmware also).

Steps to reproduce the behavior

Expected behavior

Screenshots

Environment

deCONZ Logs

Additional context

I have experienced this issue since I started using deCONZ around 2 years ago. So it was like this on previous firmwares and deCONZ verisons.

Never happened when my switches used to be connected to the Hue Bridge

Mimiix commented 4 years ago

I've had this too, but recently they stopped doing that. I can confirm this happens, but i don't know how to fix it.

MadMonkey87 commented 4 years ago

I think i had the same issue back in the time the switches were paired with the original bridge

ebaauw commented 4 years ago

Once in a while, when pressing (any) button, nothing happens and the Dimmer's LED lights up solid red. Then, upon the next key press, it works again. It's like the Dimmer is asleep and needs to be waken up.

Typically that means one of two things:

  1. The dimmer's battery is at critical level. Note that reading the level of button cell batteries is inherently flawed, so it might report critical one moment and 20% the next;
  2. The dimmer doesn't receive an ACK from the coordinator on the attribute report. Most likely because its parent router has been rebooted or switched off, but could also be due to routing issues on the Zigbee network. I don't know how the dimmer is supposed to react, but if it's any similar to the Hue motion sensor, it will find a new parent, possibly sending the report as a broadcast in the mean time.

For one the solution is simple: try a fresh battery. For 2 you'd have to sniff the Zigbee traffic to see what's happening. I have the impression that the recent versions of deCONZ somehow deteriorated the routing issues (at least for Hue devices): I see my Hue motion sensors blink red more often.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

networkpotato commented 4 years ago

Well this is still an issue for me. Happens every once in a while. The batteries are fine (>60%)

Mimiix commented 4 years ago

@ludipq Can you show me a screenshot of your network?

Maybe some logging on when it occurs?

ebaauw commented 4 years ago

Again, we need a sniffer log of the Zigbee traffic when this happens. I don’t think this is a bug in deCONZ. @ludipq are you sure your Zigbee routers (lights) are powered all the time?

networkpotato commented 4 years ago

@ludipq Can you show me a screenshot of your network?

Maybe some logging on when it occurs?

Again, we need a sniffer log of the Zigbee traffic when this happens. I don’t think this is a bug in deCONZ. @ludipq are you sure your Zigbee routers (lights) are powered all the time?

Yes, they are powered 24/7.

Next time it happens I will take note of the date and time and post the logs :)

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Mimiix commented 4 years ago

@ludipq Did anything happen yet?

stale[bot] commented 4 years ago

As there hasn't been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

stale[bot] commented 4 years ago

As there hasn't been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it isn't solved, request to get this opened again.