Philips Hue Tap Dial Switch - Zigbee2MQTT

Blueprints Exchange
, , , ,
41

Hello,

I’ve upgraded my zigbee2mqtt server (1.42) and since then this blueprint doesn’t work anymore (I have no _action entities to choose now)

42

Everyone, I have updated the blueprint to fix compatibility with Z2M 2.0. Please read the opening post for instructions on how to get it working again.

3 Likes
43

I haven’t upgraded Z2M to V2.0 yet, but the change over to trigger actions from the MQTT topic was rather painless - thanks for addressing this so quickly!

1 Like
44

I’ve just updated HA and Z2M and this was exactly what I needed. Thank you for such a quick update.

1 Like
45

Thanks for the update!
Unfortunately it does not work for me, I’m getting the following error:
“Message malformed: required key not provided @ data[‘trigger’][0][‘platform’]”

here is my yaml:
description: “”
use_blueprint:
path: freakshock88/philips_hue_tap_dial_switch_zigbee2mqtt_actions_blueprint.yaml
input:
mqtt_topic: “zigbee2mqtt/Button Hue”
remote_button_1_single_press:
- type: toggle
device_id: d00177b9781f33e976d66a2c11e516c4
entity_id: 7b17bf7a6015b526802f1b42ff394b9e
domain: light
alias: Leds Lights

Thanks!

46

Are you using a recent version of Home Assistant?

47

Can you please format your yaml code properly.

48

Ho, sorry, I’ve haven’t noticed that the formatting was gone.
I’m using 2024.6.4, I will try to upgrade to latest but having some unrelated issues for the moment.

description: ""
use_blueprint:
  path: freakshock88/philips_hue_tap_dial_switch_zigbee2mqtt_actions_blueprint.yaml
  input:
    mqtt_topic: zigbee2mqtt/Button Hue
    remote_button_1_single_press:
      - type: toggle
        device_id: d00177b9781f33e976d66a2c11e516c4
        entity_id: 7b17bf7a6015b526802f1b42ff394b9e
        domain: light
alias: HueTap
49

I see, the HA update will fix this issue. The syntax for automations changed recently and I’m using the modern trigger instead of the old platform syntax.

2 Likes
50

thanks for the confirmation!

51

I’m running into the same issue with the update breaking the action of the automation.

however when i follow the updated YAML, I get the error “missing input button_sensor”, what am I missing?

When I check the device entities I cannot see an button action anymore, so I don’t know what I would reference here?

thanks you in advance

52

Check the opening post again, it explains how you should edit your automation to work again.

1 Like
53

Worked now! thanks a lot. I thought I tried it before the exact same way. Sometime its good to try again.

appreciate your work :slight_smile:

54

Idk if this has been mentioned before but it would be really useful if the dial control could be split into buttons instead of single dial rotate function

and also double press support?

• ⁠dial_rotate_left_btn_1
• ⁠dial_rotate_right_btn_1
• ⁠dial_rotate_left_btn_2
• ⁠dial_rotate_right_btn_2

etc…

Use Case Example:

User has multiple speakers in different rooms

interact with button 1 and rotate dial to control living room speaker
interact with ⁠button 2 to make the dial control the bedroom speaker instead

basically the dial rotate will control the last interacted button.
in my case I just double press since i dont have any use case for doubleclicking

55

That’s not implemented in Z2M itself. But can be achieved with this Blueprint:

I made my own for ZHA which can control each button with multiple press types and dial options per button:

56

Thank you so much, this saved me a lot of headache after updating Z2M today!