Very Easy Custom Philips Hue Dimmer Switch for Z2M(Zigbee2MQTT)

Blueprints Exchange
, , ,
22

You need to use the name you entered (or was entered for you) for the device in Z2M not what you have in HA.

23

I just started messing with this. I suck at yaml but my code does have smooth dimming. I think if you mess with the % and transition it could be pretty customizable. Let me know if this works well.

alias: Livingroom dim
description: Dims livingroom when held
use_blueprint:
  path: patpac9/Hue_Dimmer_Switch_Easy_Custom_Buttons.yaml
  input:
    controller: Hallway hue switch
    down_held:
      - service: light.turn_on
        metadata: {}
        data:
          brightness_step_pct: -20
          transition: 2
        target:
          entity_id: light.livingroom
    up_held:
      - service: light.turn_on
        metadata: {}
        data:
          brightness_step_pct: 20
          transition: 2
        target:
          entity_id: light.livingroom
24

Hi. Thanks for your reply.

Iā€™ve tried your code and itā€™s better, but still not totally smooth. I could start playing with transition and brightness step but I would prefer to use mqtt.publish command, I read somewhere that it should be better than the other solution (brightness_step/brightness_step_pct). Any experience how to get that (mqtt.publish) to operate smoother?
Like I also mentioned in my first comment i use this code for my enOcean PTM 215Z and it operate like a charm, so I donā€™t know why itā€™s a problem when using Hue dimmer switch.

25

I have the same problem i cant not get the blueprint to work. I have tried both the friendly name and the mqqt id that was given at the time. I still dont get a response. if i set up my own automation i can get it to work.

26

Fairly new to HA and Z2M, but just discovered this blueprint and it is just what I needed. Thanks for sharing!

As a related question - I was initially attempting to set up this switch in Z2M using a bind. Has anyone had success with direct binding of this Hue Dimmer Switch to a light or set of lights using the Z2M GUI (Bind under device settings)?

Despite getting messages that the switch is bound to a light successfully i have had no luck getting a response using that methodā€¦ just curious if anyone had similar experience.

27

to remove the warning just replace these lines:

  • conditions: ā€˜{{(ā€™ā€˜holdā€™ā€™ in trigger.payload_json.action) or (ā€˜ā€˜releaseā€™ā€™ in trigger.payload_json.action)
    or ā€˜ā€˜pressā€™ā€™ in trigger.payload_json.action}}ā€™

by this line:

  • conditions: ā€˜{{(trigger.payload_json.action is not none) and ((ā€™ā€˜holdā€™ā€™ in trigger.payload_json.action) or (ā€˜ā€˜releaseā€™ā€™ in trigger.payload_json.action) or (ā€˜ā€˜pressā€™ā€™ in trigger.payload_json.action))}}ā€™

Reason: Hue dimmers are sending status updates regulary. However, these payloads do not have an ā€œactionā€ item. Hence, the whole payload is NULL which leads to this warning.

28

Hi guys.

Are you aware of the removal of the legacy ā€œactionā€ payload in the upcoming Z2M 2.0.0?

See here: Z2M 2.0.0, legacy triggers, _action entity's and hue dimmer blueprints Ā· Koenkk/zigbee2mqtt Ā· Discussion #24997 Ā· GitHub
The blueprint i am using and i assume this one is not working anymore.

This is the one i am using: šŸ’” Awesome HA Blueprints: A curated list of blueprints + easily create controller-based automations (remotes, switches,...) for controlling lights, media players, and more - #106 by pOpY

What do you use now instead?

2 Likes
29

Well today I woke up with non working Philips dimmers:) guess I found the problem:):).

the WAF just went down:) I fly in 6 hours to the other end of the worldā€¦

30

You can enable the legacy action triggers in the z2mqtt options (tab ā€œhomeassasitant integrationā€) Then all should work again (till this is then depracted) but for the time beeing, this is a good way to go.

31

Guys here is an updated blueprint which uses mqtt json payload. Thatā€™s a real solutions until ā€œeventsā€ are coming.

Here it is:

I swear, this would get the WAF high again :sunglasses:

32

Did you manage to add the color cycling to this blueprint?

33

Just a week into HA (first time posting to the community), but fully down the rabbit hole. I have two coordinators going (ZHA HomeConnect and Sonoff 3.0 plus for Zigbee2MQTT). Getting the first Hue remote to pair with the Zigbee2MQTT was easy. Getting the second one took hours and a lot of random button pushing and resetting using the pin hole. I have 8 more to go, but canā€™t seem to figure out the right timing/sequence for pairing. The remotes were previously paired/configured in Apple Home through the Hue app, and Iā€™ve deleted the remotes in the Hue app. Oddly enough, one of the Hue remotes got paired with the ZHA coordinator (which I didnā€™t think was even possible). I removed that, as Iā€™m trying to get all of the Hue remotes paired to Zigbee2MQTT so I can use the blueprints to map the buttons. Iā€™m doing something right because I got two to work, but itā€™s horribly inefficient. I put new batteries in each remote as well. My remotes are V2 (Hue logo for bottom button). Any ideas?

34

First off thank you PatpaC, great blueprint!

If anyone is looking for cycling color temps with the Off/Hue button, here is how I did it, inspired by the solution posted by Daniel (dbrunt).

off_released:
      - action: light.turn_on
        metadata: {}
        data:
          color_temp_kelvin: >
            {% if state_attr("light.sovevaerelse_zigbee","color_temp_kelvin")|
            int(default=0) > 3500 %}3330 {% elif
            state_attr("light.sovevaerelse_zigbee","color_temp_kelvin")|
            int(default=0) > 3320 %}2850 {% elif
            state_attr("light.sovevaerelse_zigbee","color_temp_kelvin")|
            int(default=0) > 2840 %}2440 {% elif
            state_attr("light.sovevaerelse_zigbee","color_temp_kelvin")|
            int(default=0) > 2430 %}1650 {% else %}3700 {% endif %}
          transition: 1
        target:
          entity_id: light.sovevaerelse_zigbee

Best regards