I’m having a weird issue with this blueprint where sometimes it sets the brightness to the minimum apparently just before turning a light off, I have the force brightness toggle off.
Tested with two different Hue bulbs, both of them always go back to their previous brightness level if toggled on/off via the HA interface or in the Hue app. If I just turn off the bulb with the switch using the blueprint though, when the bulb is turned back on through any method it’s set at minimum brightness.
It’s almost as if the “turn off” process which fades the brightness to off sets the actual brightness at the minimum in the last step.
You create an automation based on that blueprint.
Select a remote that you use and select some lights that need to switch.
Save the automation and test if it works.
The (big) downside of my version is that you can only target a single light entity. So you can’t target area’s or devices anymore. sorry!
But these cool features make up for that:
I used the new ‘select’ selector introduced in version 2021.3.
The “on” button behavior is adjustable. By default it behaves like this:
- Press it while the light is off, and the light will turn on to the last set brightness.
- Press it again while the light is on, the light will turn to the fixed brightness setting.
Limit the minimum brightness of the light(s) when dimming down. Set this to zero to disable this feature.
Add actions for double / triple presses!
Does this blueprint not work for you? Did you add your Hue dimmer to ZHA before July 2020? It might help to press the ‘Reconfigure device’ button on the ZHA Device info page. This enables some new ZHA quirks functionality.
I just received a new Hue Dimmer and hooked it up to ZHA. So far so good. I noticed it is recognized as RWL022. The blueprint cannot find the dimmer. Is there any chance you can update the blueprint to support RWL022 as well?
I would be very grateful!
Hi,
My RWL022 works with this blueprint, once I removed the “manufacturer” selector.
This switch is no more from “Philips”, but “Signify Netherlands B.V.” (like my Hue bulbs)
Main difference is that the top button is used for on/off (I think the bottom button “hue” is designed to trigger other actions)
I am a new user, and used the built-in Hue Integration to add my hub. The bulbs all work just fine. I have 4 dimmer switches (model: 324131092621) that look like they were added as devices, but the only thing that is showing up is the battery level Entity. Your blueprint is just what I was looking for to add events to the dimmers. However, when I try to pick one of my dimmers, the Device pulldown in the blueprint says, “No matching devices found”. The dimmer in the Devices configuration is checked, “Enable Device”. Is there something else needed to configure Home Assistant to recognize these dimmer devices? Thanks.
Not sure if it is exactly what you’re looking for, but I have a blueprint for this remote which can control up to 5 different sets of lights depending on number of clicks.
After resetting my remote, it seems I am now in the same boat as others and need to update my firmware, though I seem to be missing something on how to do this. I put this in Developer Tools > Service but it says failed to call service zha.issue_zigbee_cluster_command Unknown error when I try to run it.
Can @term or anyeone else here who has updated their firmware tell me what I am doing wrong as I’d sure like to be able to use this again.
Edit 1
As a quick follow up, here is the log info for the “unknown” error:
2021-05-31 14:29:44 ERROR (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Error executing script. Unexpected error for call_service at pos 1: 11
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 366, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 566, in _async_call_service_step
await service_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1481, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1516, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 728, in admin_handler
await result
File "/usr/src/homeassistant/homeassistant/components/zha/api.py", line 1057, in issue_zigbee_cluster_command
response = await zha_device.issue_cluster_command(
File "/usr/src/homeassistant/homeassistant/components/zha/core/device.py", line 604, in issue_cluster_command
cluster = self.async_get_cluster(endpoint_id, cluster_id, cluster_type)
File "/usr/src/homeassistant/homeassistant/components/zha/core/device.py", line 530, in async_get_cluster
return clusters[endpoint_id][cluster_type][cluster_id]
KeyError: 11
Edit 2
According to Upgrading Hue dimmer with ZHA OTA - #32 by TheJulianJES, this is resolved by changing the endpoint to 2. I have tried that and the update service fires but I don’t see anything in the logs about the OTA and the remote is currently still the same as when I started today.
I did press buttons but it didn’t seem to change anything. Can you elaborate on which thing I should turn on debug for? Zigbee Home Automation - Home Assistant lists a ton of things but I’d like to be a little more targeted if possible because of the volume of logs. Thanks!
Hi,
It works great but is there maybe a possibility to add a custom action when i double press or long press on the power on or off buttons or something? I know i could do it with just an automation but that will and switch the light and run my automation. On a double press i only need to trigger my thing and not the blueprint automation.
Just got this one connected (RWL022), and discovered it to not be working with this bp.
Did you get a solution for this remote?
I will admit to not going through all the bp’s for hue remotes, but I’m using this bp for the old remotes, and love the setup, and the one I found does’nt have the same functions.
Was it possible to get the RWL022 added to this bp, without having to edit it?
I have 1 RWL021 and 2 RWL022, and finally used automations to configure them (easier for me to tweak the behaviour, directly from the UI).
Automation works quite well.
I configured each button to control both sides of the room (4 spots each):
top button for room side 1 (simple press to switch on/off, with previous intensity preserved. Double press to turn on to 100%)
bottom button for room side 2 (same behaviour)
middle buttons to increase/decrease intensity (simple click for side 1, double click for side 2)
