-
-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IKEA LED2003G10 with IKEA E2001/E2002 Styrbar remote / Zigbee2MQTT #581
Comments
I have the same issue. Hopefully any help comes soon :) |
Yeah, i'm having the same issue |
Hello, I had the same issue and was looking at what could go wrong. I found that one condition to check the previous value of the button pressed does not work as expected. Unfortunately, I don't know why this is happening, but deleting the condition fixes the issue, or at least I did not encounter any side behavior. Basically detection of last last pressed button for triggering the correct "release" action is now disabled. Feel free to try my fix and propose a better solution #584. |
I have the same issue. Tested you're solution and it work's. |
Had the same issue. Solution provided by @jiridostal worked for me, too. |
The proposed solution works for me too, thanks! |
Same issue here - and the fix indeed works ❤️ Thank you! |
Worked for me too, thanks! |
@jiridostal |
Blueprint name
Hook - Light
Home Assistant Core Version
2023.11.2
Home Assistant Installation Type
Home Assistant Supervised
Description
Hello,
my Ikea bulbs misbehave for a while now and since it's getting darker outside this issue starts to annoy me again.
When dimming or brightening the lights they just keep on going instead of stopping when the remote button is released.
I don't know if this connected with an update of Zigbee2MQTT and if the behavour of Z2M changed.
Any help is appreciated.
Thanks in advance
Florian
Automation YAML config
To Reproduce
Expected behavior
stop dimming/brightening when remote button is released
Actual Behaviour
dimming/brightening doesn't stop
Additional Details
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: