ZHA - Philips Hue Dimmer Switch (RWL020, RWL021)

Blueprints Exchange
,
63

I am also experiencing the same issues. I think looking into it, it is not receiving the same parameters any longer.

1 Like
64

It looks like it is something to do with some of the args on the blueprint. The args before for a step down was

- '{{ args == [1, 56, 9] }}'

after the update it looks to be

- '{{ args == [<StepMode.Down: 1>, 56, 9] }}'

I tried updating the file but it is an error, my guess it that it is unable to parse the value. I am not sure how to get a value that will work.

I managed to make my off button work by removing the args from the off with effect path, obviously this will have some ramifications, but it will get the basics working for now.

- conditions:
    - '{{ command == ''off_with_effect'' }}'
    - '{{ cluster_id == 6 }}'
    - '{{ endpoint_id == 1 }}'
    sequence:
    - service: light.turn_off
      target: !input 'light'
      data:
        transition: 1

Help appreciated.

65

Hi, same problem for me on two remotes, for off the on button gets triggered, here event data:

event_type: zha_event
    data:
      endpoint_id: 2
      cluster_id: 64512
      command: off_press
      args:
        button: 'off'
        press_type: press
        command_id: 0
        args:
          - 4
          - 0
          - 33
          - 0
          - 0
      params: {}

might be related to this: ZHA ikea tradfri button up/down buttons service calls are not recognized anymore Ā· Issue #69375 Ā· home-assistant/core Ā· GitHub

66

Same here. Iā€™ve switched over to the V2 version which seems to be working ok

1 Like
67

Thank you. V2 works fine and has even more possibiltles.

68

@vanstinator have you seen this?

69

Bump, still on 2022.3.8 until I get a path forward. :slight_smile:

70

Why not just using V2? Works perfectly.

72

I fixed the issue by changing the args parameter to seperate lookups in the params dict.

See my version here:

No functional changes have been made, so this can be used as a drop in replacement.

1 Like
73

Seems there was a change in 2022.6.0 and brightness value is no longer returned as 0 when the light is off (Iā€™m assuming) so V2 throws an error when turning on.

To get it working again I changed the line

cur_brightness : '{{ state_attr(light, ''brightness'') | int }}'

to

cur_brightness : '{{ state_attr(light, ''brightness'') | default(0) }}'
6 Likes
74

Thanks for your sharing. I had the same problem since the update your solution solved the problem.

75

Thanks for sharing the fix!

76

Hi together,

I tried all version of this script, and i have always the same issue. I am able to dim and turn off the lamp but turning on does not work. Does anyone know what the issue or how to debug?

77

solution got already posted by bamzero

79

I have the same problem

80

Fix my issue thanks!

81

The blueprint, as it installs using automated install, is broken, It will definitely turn on the light, but dim and off no longer working.
I use the blueprint so I donā€™t have to mess with code too much. If there is a fix, it should really be put in the blueprint so others downloading do not have to mess with the code to fix a bugā€¦

There are alternative blueprints for the RWL020 / RWL021 (Version 1) Dimmer Switches, and there is a nice V2 dimmer switch blueprint if you have the new one with the Hue button on the bottom.
This one works well for the Version 1 (RWL020/RWL021) dimmers, a lot of options in it though and maybe not quite as simple, but the main thing is it works.

1 Like
82

This blueprint does not seem to be working anymore with my RWL020. The on button will work to turn the light on, but the dim and off buttons do not do anything.

Can we get a fix please? This is my favorite blueprint for this device and would love to keep using it.

1 Like
83

Can confirm. Currently, both the v1 and v2 versions seem to be broken. v2 doesnā€™t even seem to pick up any actions. v1 does register my off/on presses, but doesnā€™t do anything to the lights.

84

hey guys, i fixed it.
i dont understand why, but the declaration of the variable ā€˜argsā€™ doesnt work anymore.

quickā€™nā€™dirty fix:
replace all ā€˜{{ args == [ā€¦] }}ā€™
with ā€˜{{ trigger.event.data.args == [ā€¦] }}ā€™

that sould fix it.

6 Likes