Philips Hue Tap Dial Switch - Zigbee2MQTT

Blueprints Exchange
, , , ,
35

As far as I can see there’s quite a bit of overlap between the ‘new’ types and the existing actions.

  • action_direction is already a part of the main action.
  • Action type indicates whether a rotation is small (step) or fast (rotation). So that also overlaps.
  • The action_time property seems to be a bit more fine-grained as to how fast the rotation was. Since I don’t really have a need for this I will not incorporate it into the blueprint myself, but if anyone has a proposal how to, they could create one.
36

Is there a way to set brightness and color when pressing a button?
My kitchen for example has a morning automation for the wife and the lights are set low. When I go into the kitchen and use the hue tap I would like the lights to come on at a set brightness and color.
I am currently using a blueprint for the Ikea switch for the kitchen which has this implemented. My plan is to replace this switch with the hue Tap.

Thank for the hard work!

37

Yes there is, use this in your action.

38

There is another problem I am seeing in the two rooms I setup. Both have 1 light that will not toggle on with the rest of the lights. They will however toggle on on the second press when the rest of the light turn off. These rooms are setup on differs t buttons on the switch.
Very strange behaviour that I can not understand why.
Any ideas?

Edit:
So I can get button 2 to toggle a scene, single press. I can not get button 1 to toggle (single press) . Button one turns the lights on to the button 2 scene (weird). I have removed and redone button 1 many times with the same outcome!
On a side note, is there a way to use a group of lights?

Thanks

39

Ok so I have found 2 issues.
First one is a problem with the hue Tap. I will warranty it next week.

The second is as far as I can tell, the blueprint or how I am trying to use it. Let me explain. If I set up button 1 with a scene or device/entities (press) it works fine. If i now add a scene to the same button as press/release it stumbles. The light won’t turn off on a single press but will flash, then turn on the scene set to press/release. If i press and hold, the lights will toggle off. Press and hold is not setup at all. So where did it get a press/hold command from? I have tried this on 3 tap switches with the same result no matter what button I choose/setup.
The devices/entities and the scenes are selected from call service if that helps.

Edit:
It would appear that the blueprint is activating the different presses as one. I added a fan toggle to my bedroom on press/hold. I already have a single press to toggle the lights on the same button (same room). When I press/hold it will turn the lights on and maybe toggle the fan. The fan sometimes comes on then as I release the button turns off.

Am I Doing something wrong?
How to fix this?

Thanks

40

I recently migrated from ZHA to Z2M and used that ZHA Blueprint. Since I am not that good in coding I was wandering what needs to be done to change the blueprint in order to get that funcionality. It was pretty slick to have the possibility to adjust the brightness of the recent light

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.

2 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.

1 Like
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.

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