ZHA - Philips Hue Tap Switch Mini - Custom Controls (RDM002)

[stephane1 (cherie)]

Hi,

I am trying to use the custom controls blueprint, however no philips devices are found.

An idea ?

Thanks

[gTunes]

Hi, @stephane1. Can you post your last post on the other blueprint thread, please? Thanks.

[stephane1 (cherie)]

Sorry I did a mistake, my problem is with the custom controls blueprint !

[gTunes]

Got it.

I’m surprised to hear this. You definitely have a Philips RDM002 as pictured in the first post and its connected via Zigbee Home Automation (and not Zigbee 2 MQTT or something else)?

Can you share a picture of what you see when you look at the device? I see this for mine.

[stephane1 (cherie)]

My devices are connected via Zigbee 2 MQTT !

[gTunes]

This blueprint, and the other one I referenced, is specific to Zigbee Home Automation (ZHA) and doesn’t support Zigbee 2 MQTT.

Unless you decide to switch to ZHA, I’m afraid you won’t be able to use it. I’m glad we at least figured out what the issue was!

I did make a blueprint for controlling this dial using Z2M back in 2023, but I’m not sure if that blueprint still works and I’m not currently supporting it because I’ve moved to ZHA. If you’re interested in looking at it, it’s here, but if you find issues I don’t think I’ll be able to help.

Z2M - Philips Hue Tap Dial - Media Controls

Hi. This blueprint supports controlling a media device and additional custom automations with a Philips Hue Tap Dial control. It is specific to Z2M. [image] Features of this blueprint: Simple selection of a single media device to be controlled User-specifiable volume steps - if your physical device uses a volume range other than 1-100, you can specify that range and this automation will scale incremental steps appropriately The controller generates three rotation speed events : s…

[stephane1 (cherie)]

Ok, thanks you for all your explanations.

[Montolio (Bernhard)]

Thank your for your blueprint, it helps a lot.

But unfortunate it does not work when activating scenes.
I noticed the blueprint is called three times when I press a button.

• the first which triggers nothing
• the second which triggers “button_1_press”
• the third which triggers “button_1_short_release”

The the third one is my problem. Because this one cancels my action which is configured for button 1 short presses.
Any idea what is going on here?

[gTunes]

@Montolio

The the third one is my problem. Because this one cancels my action which is configured for button 1 short presses.

Hi. Thanks for posting this.

I have a theory but before I explain that - based on your explanation, it seems that moving your automation to the button_1_short_release event would fix the problem. If it does, that’s probably the simplest thing to do.

I suspect that the issue you’re encountering is caused by the “automation mode” specified within the blueprint. The automation mode is currently set to “restart” which means that if an event is being processed and another event arrives, the in-progress event is stopped.

You can read about automation modes here: Automation modes - Home Assistant

I’m guessing that whatever your automation is doing is in progress at the time of the button release. So the in-progress “press” event is pre-empted so the release event can be handled.

I’m not sure the other modes are better for this automation. If you want to experiment with a different mode, you can edit your local blueprint and change the line that is currently

mode: restart

to use single, queued, or parallel. Honestly, though, I think the most straightforward approach is to just move to using release events.

Please let me know what you try and how it goes! Thanks!