ZHA - Philips Hue v2 Smart Dimmer Switch and Remote - RWL022

hey, do you guys have any trouble connecting the dimmer to HA ? I can’t make it work, everytime I pair it I can run the blueprint once or twice and then the dimmer disconnects and blinks orange or red. Battery is full, and I just switched from a dimmer v1 that worked perfectly, any advice ?

Seems to be working fine with SkyConnect and ZHA. Thanks for the blueprint.
May I ask is there a easy way to change percentage of brightness increase/decrease?
image

Did this blueprint stop working for anybody else lately? seems like something was changed in zha yet again?

Have tried repairing a couple of times, but it’s not working anymore… (the pairing works, but the blueprint actions don’t)

Ok, so for some reason since the update to 2023.12.03 makes the automation based on this blueprint trigger 3 times per button press.

Since the automation is set to mode: single, according to trace, it just stops running because only one instance is allowed to run, making it break completely. I don’t really understand the reason for this, but setting the mode in the blueprint to parallel seems to mostly fix it.

EDIT: Stopped working again.

I’m not using this device anymore so I can’t do any testing. If anyone else wants to contribute some changes I am happy to update my template.

1 Like

how can i pait it with ZHA? there is no device showing up although i reseted the device… any hints?

Thank you so much!!

I have a (n00b, sorry) question though. When connected to a Hue bridge I always used the “Hue” button to scroll through different scenes. So if you pressed once you get scene 1, press again scene 2 etc.

Also, I used the up and down buttons to dim the light. I’m sure I have to edit the Up Hold and Down hold for that but I’m not exactly sure how.

How do I set this up in HA and this blueprint?

HI,
How did you add brightness feature ?

Hi,
is it possible to specify the trigger more? Like in lines 111-118 in this gist ZHA - Hue Dimmer Fully Configurable.yaml · GitHub?

Because now it triggers on every ZHA event and would be a bit easier on the HomeAssistant when you have a lot of ZigBee devices.

Hi,
I love this blueprint @dustins , but unfortunately I use Zigbee2MQTT. Would there be any possibility of adapting this magnificent bueprint to Zigbee2MQTT please? Thank you!

Thank you for this integration @dustins !
Works like a charm.
Added as Automation (as by default)

Tested:
HomeAssistant Yellow 1.3
Core 2024.9.2
Supervisor 2024.09.1
Operating System 13.1

Tested by controlling group of 2 Phillips Hue Play Bars (on/off and ±10/20/30 percents brightness) plus single/double click on “Hue” button as switch for few Phillips Hue Smart plugs.

Summary
alias: Philips Hue v2 Smart Dimmer Switch and Remote
description: ""
use_blueprint:
  path: dustins/zha-philips-hue-v2-smart-dimmer-switch-and-remote-rwl022.yaml
  input:
    zha_device: 28b68a7d48de3e71401e77dd7c6431d3
    Power_Press:
      - action: light.toggle
        metadata: {}
        data: {}
        target:
          entity_id: light.nochniki
    Power_Press2x:
      - action: light.toggle
        metadata: {}
        data: {}
        target:
          entity_id: light.nochniki
    Power_Press3x:
      - action: light.toggle
        metadata: {}
        data: {}
        target:
          entity_id: light.nochniki
    Power_Press4x:
      - action: light.toggle
        metadata: {}
        data: {}
        target:
          entity_id: light.nochniki
    Power_Press5x:
      - action: light.toggle
        metadata: {}
        data: {}
        target:
          entity_id: light.nochniki
    Up_Press:
      - action: light.turn_on
        metadata: {}
        data:
          brightness_step_pct: 10
          transition: 1
        target:
          entity_id: light.nochniki
    Up_Press2x:
      - action: light.turn_on
        metadata: {}
        data:
          transition: 1
          brightness_step_pct: 20
        target:
          entity_id: light.nochniki
    Up_Press3x:
      - action: light.turn_on
        metadata: {}
        data:
          transition: 1
          brightness_step_pct: 30
        target:
          entity_id: light.nochniki
    Down_Press:
      - action: light.turn_on
        metadata: {}
        data:
          transition: 1
          brightness_step_pct: -10
        target:
          entity_id: light.nochniki
    Down_Press2x:
      - action: light.turn_on
        metadata: {}
        data:
          transition: 1
          brightness_step_pct: -20
        target:
          entity_id: light.nochniki
    Down_Press3x:
      - action: light.turn_on
        metadata: {}
        data:
          transition: 1
          brightness_step_pct: -30
        target:
          entity_id: light.nochniki
    Hue_Press:
      - action: switch.toggle
        metadata: {}
        data: {}
        target:
          entity_id: switch.signify_netherlands_b_v_lom007_switch
    Hue_Press2x:
      - action: switch.toggle
        metadata: {}
        data: {}
        target:
          device_id: 68ff9b933ff8e81a4cadeb3c66a9cc31

UPD:
Unfortunately “Hue” button “Hold”(aka long press) isnt wprking exactly as i expected.
It triggers “Single press” effect, followed with “Hold” effect.
Therefore, triggering those two separately becomes not possible.

For now using single and double press, but older relatives simply not always can click fast enough :smiley:

Is there a way to either extend timeout between presses, or prevent single press from triggering, when button is held for Hold/long press action?

@Tolerant How I fixed it for me was assign the action to the single press release, this event doesn’t get send in case of a hold event.
Then you can have both working perfectly.

1 Like

Thank you, i will it this way :grinning: :ok_hand: