Yet another Philips "Hue Tap dial switch" Blueprint (z2m)

Blueprints Exchange
,
1

Control lights with a Philips Hue Tap Switch. Use the four buttons to control your light(s) with an on, off or toggle, scene activation or custom actions. Supports short release, long release and double press actions. Each beheaviour can configured seperatly.
The dial can be used to dim the most recently used lights or call a custom rotation action for that button.

based on

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.|
Source: blueprints/philips_zigbee_dial_combined_z2m.yaml at main · XXBrain/blueprints · GitHub

Bildschirmfoto_20251111_131002
Bildschirmfoto_20251111_1310021643×1166 98.4 KB

I created a blueprint to combine lights control and custom actions. You could also define one scene per button to be activated. I use this blueprint in my living room to control lights and send remote commands (mute, power toggle, source*, volume) to my old surround system.

  • I originally created this for zha but moved to z2m. Zha Version is still available but be aware that I cant make changes for zha myself anymore because I can’t test them. But you can still use it if you whish. But there are better (supported) ones.
2

Double press support added.

3

Hi Schurki,

thanks for the blueprint.

Tried it, but it does not work for me.

My config:

Config
Config962×1128 77.4 KB

Activity Log:

Activity1
Activity1562×367 25.1 KB

That´s all that happens. The light in my group are not switched on or off.

Any hints? Thx…

4

Thanks for testing and sorry that it’s not working. I can reproduce this. Toggle seems not to be working at all and without the double press helper nothing happens too. I will try to fix it this weekend.

5

Hello Hurst.
Could you reimport the blueprint and ceck again, please? It should work now.

6

Hi Schurki,

thank you - now it works as expected.

But it feels slow.
After pushing a button for about half a second nothing happens and then the light turns on.

The other blueprint I use is from AnderssonPeter. After pushing a button the light turns on immediately.

In your blueprint I like the option to perform an action on button push. On of my three buttons is used to start a script. Thats not possible on the other blueprint.

Maybe you can have a look on the delay.

Thx

7

This is caused by the Double Press check. I will add a feature soon to adjust the time out or disable it completly. Unfortunately it’s required because there is no native double press event in z2m for the dial tap switch.

8

I’m not the author of this BP, but I implemented identical functionality in my instance a year ago. You can’t have an immediate response and double click detection without also having a delay.
Even major smart home manufacturers with full time devs haven’t been able to figure this out - you need a delay to wait for that second click (even if it’s not used).

You need to decide which is of more value to you - instant response with no double click, or slightly delayed response with double click support.

2 Likes
9

Thats a perfect explanation.

@Hurst I updated the blueprint. You can now set the timeout yourself and if no helper is defined it’s 0 by default.

10

Thank you!

I had to set the Double Press Detection Timeout manually to 0, by default there was still the delay.
But with setting to 0 it works really good.

Well done!

11

Broken ‘Prevent on change’ option fixed

12

Hey Schurki,

tried the last version - one error and one warning in Core Logs:

image
image829×263 21.7 KB

image
image549×260 18.6 KB

13

Good Morning Hurst. Sorry to hear that. I did a lot of changes yesterday to simplify the code. Can you try it again.

I changed something that should be the cause. If thats not helping. I will revert it to the older version, that was working for you.

14

Hi,
no reason to apologize - you do a good job here.

With last version one warning appears:

image
image798×240 17.5 KB

this happens when button 3 with a script is used:

image
image1165×630 52.1 KB

And to clarify: Everything is working fine and as expected. It´s just the warning in the logs…
And I didn´t check the logs with the second to last version. So do not know, if the warnings do occur with this version.

15

Well, I added a few checks and currently I can’t see anymore warnings. I will observe it. If you still get warnings, please let me know,

16

Good morning,

there is still this warning when button 3 (with script) is used:

image
image793×240 18 KB

Maybe you can have a look - but I think I can live with this warning :slight_smile:

17

I had to add a case differentiation in the loops with custom actions, but now it should be ok, if no target attribute exists, like in scripts.

18

Perfect - no warnings or errors in the log.
Thank you!

19

Added feature to toggle through scenes.