-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Philips Huhe dimmer switch RWL021 fail to bind on/off after upgrade to 1.36.1-1 #22073
Comments
I am having the same issue with the RWL021, but dimming is not working either. And as it is used in the kitchen the WAF is really low now! |
My guess the nested group naming issue has something to do with this issue: It was causing issues in dev already, but might be the whole issue is there when you don't have any nesting. |
@grafalex82, would you mind to look at this issue? |
Just to add I'm experiencing the same issue since the same update, however it (so far) it seems to be only affecting 3 out of 6 of my switches. |
What is the difference between the working and not working ones? |
I'm trying to work this out. I will update here if I find anything. |
I also have one that still works, but the rest of them has stopped to work. I can not find any difference.. The firmware are the same, all configuration are the same, and the naming standard are the same. I have deleted the non working and tried to add them again, but I still get the same problem. |
What are you trying to control with the not working and working ones? Hue bulbs? Ikea bulbs? Any other? |
Hue bulbs on all of them. I have eaven tried to bind the non working remote to the bulb group that the working one are binding to. |
I have the exact same problem with the Hue wall switch module since 1.36.1-1. :( |
I have a group with only Linkind ZL00030014 (https://www.zigbee2mqtt.io/devices/ZL00030014.html#linkind-zl00030014) bulbs showing the same symptoms. All of the other groups showing the same issues are all wholly hue based. |
I use the dimmer switch with IKEA bulbs. No control over the bulbs. White tunable bulbs. Any chance that the working ones are color bulbs? |
All white hue - Working I have another 2 groups I've not tested that are all colour but.. I don't think white/colour is a thing here. |
The second button of the Hue Wall Switch has also stopped working due to this change. |
I have noticed that all my Hue wall switches (model: RDM001) are behaving strangely. The events are all sent twice. After a reset, it seems to work again. My RWL022 dimmer switch had no problems. |
I also did, the it worked, but just for a short time. |
I tried a factory reset, but that made the diming also to stop working. |
I had the same experience. It didn't last very long. I'm really glad that I'm not alone with this problem. I couldn't find any messages for days. |
I've tried rolling back to 1.36.0 however this issue persists :( |
Same here |
Same here, it's a nightmare to don't have light switches anymore... Hope someone find a fix for this very soon... |
I do not have any Philips or HUE devices. Can someone post me a log from a working Z2M version so that I could compare? Also, what device is generating these actions? |
I don't have a working Z2M version any more, as it don't help to downgrade. However one of the remote devices is still working, so maybe it will help with logfiles from that and one of the non working devices? What logfile do you want me to grab? |
Remote Gjesterom is still working
|
I can see in the log file that the remote that works get groupID 1, and the remotes that don't work get groupID null
|
This is what I get when I try to bind or unbind:
|
This is what I see too. |
Glad we are all having the same issue. My wife is already very angry, because the bathroom light wall switch isn‘t working anymore. 😬 |
Guys, I am really willing to help, but from the logs above it does not look like my changes could lead to these effects. My changes were related to parsing an MQTT message, while logs above do not mention this at all. What is worrying me in these logs is "Received Zigbee message ... with groupID null" statement. For me this looks like incorrect processing of incoming Zigbee message. |
I also think it is really strange and scary that it didn't help to downgrade Zigbee2mqtt to solve the problem. |
Here is also a log from after I have factory reset the Hue Remote and joining it to Z2M again: (Edit: I have also downgraded to 1.36.0 here..)
|
I'm not using ConbeeII. https://smartlight.me/smart-home-devices/zigbee-devices/zigbee-coordinator-v4-cc2652p is what I'm using here with the same symptoms. |
I went out and bought a new IKEA STYRBAR remote today to get a lightswitch, but I have the same problem with that one. It looks like it's either Zigbee2mqtt or me that have to move out of the house if we don't get any fix for this.
|
@Koenkk Are you able to take a look at this issue? |
I'm not sure if this is the same issue however when I press any button I am getting action as null
|
What if you press unbind and then press a button on the switch straight after @aervig ? |
Thanks, that worked, and I can confirm that I can control the light with it again now. |
So, happy wives all round then? :) It looks like there's possibly a problem with multiple bindings against a single source endpoint here. |
@mUbsta, no, not really. I have remotes which should operate the bulb and meanwhile communicate with Z2M and HA to control other things, but I have a guess where things went side way. Looking at the recent changes, the new modern extent changes messed things up as seems to. So tagging @mrskycriper. I tried the trick mentioned above, and removed the coordinator from the binding, then the remote worked with the group. But once I added back the coordinator, then the group binding was not working anymore. |
I think this issue can be fixed by force removing the device from z2m, restarting z2m and re-pairing the device. Probably this happened due to an auto reconfigure which I've already disabled for the new release |
I've tried this and still having the same issue with multiple bindings I'm afraid. Has anyone else had any luck? |
I have unbinded |
I can confirm this worked also for me. Let‘s see for how long… |
What exactly did you do to get it to work again? I successfully (at least according to the popups in Z2M) unbound the dimmer switch from the light group and then afterwards tried binding it again but this failed and I can't control the lights with the switch. Edit: I didn't unbind the switch from the coordinator, now it seems to be working as well. |
Still no permanent solution for this? |
I find it very strange that this issue still exists after 2 weeks. Makes me wonder about zigbee2mqtt ..... Anyway, I am holding off upgrading to this version and I can recommend to not update zigbee2mqtt in the beginning of the month, but wait to the last day instead. |
Hello, I had remove source endpoint 1 with coordinator and clusters : levelCtrl , OnOff. The hue dimmer switch control directly the light but no information remote to z2m. |
Add binding to |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days |
What happened?
Philips Huhe dimmer switch RWL021 fail to bind on/off after upgrade to 1.36.1-1.
After upgrading is it not logner possible to turn lights on and off with the remote, so it seems like something with the binding has gone wrong.
It still works to dim the light up and down.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.36.1-1
Adapter firmware version
0x26580700
Adapter
ConBee2/RaspBee2
Setup
Home Assistant OS
Debug log
Info 2024-04-04 10:34:53MQTT publish: topic 'zigbee2mqtt/Remote Soverom/action', payload 'off_press'
Info 2024-04-04 10:34:53MQTT publish: topic 'zigbee2mqtt/Remote Soverom', payload '{"action":"off_press_release","action_duration":null,"battery":100,"brightness":255,"counter":1,"linkquality":255,"update":{"installed_version":-1,"latest_version":-1,"state":null},"update_available":null}'
Info 2024-04-04 10:34:53MQTT publish: topic 'zigbee2mqtt/Remote Soverom', payload '{"action":"","action_duration":null,"battery":100,"brightness":255,"counter":1,"linkquality":255,"update":{"installed_version":-1,"latest_version":-1,"state":null},"update_available":null}'
Info 2024-04-04 10:34:53MQTT publish: topic 'zigbee2mqtt/Remote Soverom/action', payload 'off_press_release'
The text was updated successfully, but these errors were encountered: