This blueprint enables comprehensive control of the Philips Hue Tap Dial Switch (RDM002) through Zigbee2MQTT or ZHA integration, supporting custom actions, light automation, and media player control.
Key Features:
Dual Integration Support: Works with Zigbee2MQTT (Z2M) and/or ZHA
4 Buttons: Short press, long press, and multi-press (Z2M: double, ZHA: double/triple/quad/quint)
Rotary Dial: Context-aware based on last button pressed
Custom Mode: Execute personalized home automation routines
Light Mode: Control brightness, color temperature, and transitions with schedule support
Media Mode: Volume, playback control, and speaker grouping
Adaptive Lighting Support: Integrates with schedule helpers and sensors for dynamic adjustments
Auto-Adjust: Automatically update lights when your schedule changes
Reset to Defaults: Quick reset to default light settings
Configurable Dimming Speed: Adjust how fast lights dim with the dial
Requirements:
Home Assistant: Version 2024.10.0 or later
Zigbee Integration: Zigbee2MQTT (Z2M) and/or Zigbee Home Automation (ZHA)
Compatible Model: Philips Hue Tap Dial Switch (RDM002)
First big update. You can now use the Lights mode without setting up a schedule.
So only the Text Helper for the button presses is still needed to use this Blueprint. I am trying to figure out a way to be able to do this without the Text Helper so it is easier to use for new users.
With the newer version of the blueprint the Schedule is not necessary anymore, you can now set the default start brightness, color_temp and transition directly in the blueprint, these will be used if the schedule is not set. If you don’t see those options reimport the blueprint.
I tried the short button press with Toggle first, but if you want to change between lights and the light is already on it will then turn the light off that is already on if you press that button. The way it is implemented currently, it will reset the light to the ‘default’ state set by the schedule or what you set manually.
I am planning to change the Blueprint to have ‘preset actions’ or ‘custom action’ per button press type instead of a full Custom/Light/Media mode, so it is more flexible to use. But this is quite a complete overhaul of the logic behind it, so will take some time.
That sounds fantastic, I look forward to the update! This is already by far the nicest integration for this device I’ve used and the only one I’ve been able to make fit my use case.
Figured that may be the case on short press = toggle having just scanned through the logic.
Well it took some days of work. But I have released basically a v2 of my Blueprint. You can reimport it over the old version but you will need to setup certain parts again.
The code has been optimised and more is now fully customisable.
Due to some changes it will not be fully compatible with the previous versions. Some entities have changed names to prevent the old stored settings causing issues. They will be ignored in the new blueprint.
There is no more Custom/Light/Media mode per button, but you can select different presets for the Light and Media mode per button. The presets are ignored if you don’t select a Light for the Light options or Media for the Media options. The Custom Actions are always run together with the other options you select. But can be empty if you don’t need Custom Actions.
Hi! I just installed one of a few Hue Tap Dials I purchased for my home renovation and found your blueprint after trying a few others which I found to be a little too simple.
First off, my text helper window had some fields missing compared to your screenshot, however it SEEMS to work anyway:
Second, I have only used Ikea’s switches before with buttons to dim. With the wheel on the Dial Switch I found it very easy, by mistake, to dim to low, so the lights turn off. Would it be possible to add a feature to the blueprint with an option to toggle the wheel not turn off the lights when dimming?
You can only set those filters during creation of the Text Helper.
The extra options are mainly aimed at limiting which values can be stored in the input_text value. As the Blueprint handles the writes and reads to the value, the filtering is optional so it should work fine without those filters in it.
The dimming response is how ZHA handles dimming of a light. I am using the ‘Step’ command to provide a smooth dimming command. So when you dim it below 1% it will turn the light off. That’s just how ZHA handles the dimming when using the Step command.
Hi, I have just started using your Blueprint and was wondering if there is anywhay to capture which lights are used in a button press?
I have four lights in my hallway and I have programmed different button presses for Button 1 to bring on a different number of the lights but under the dimming setting there is only an option to “hard select” certain lights.
As an example, Button 1, Double Press turns on Lights 2 and 3, it would then be great to be able to use the dimmer on those two lights. Button 1, Triple Press turns on Lights 2, 3 and 4. Any ideas on how to set up the dimming function?
This is currently not supported by the Blueprint itself. It only stores and checks which button was last pressed, independent of what type of press was used.
Extending it with this functionality would need extra helpers and rewrite of the whole logic.
So you can only set one dial setting per button press. Which is still more than the original 1 dial setting for the whole device. You could set lights abc to button 1 and lights abcd to button 3 for example. And use the multiple presses for other actions.
I am using the multiple presses for other actions on the same lights or to control other devices. So don’t have this problem for my usecase.
I’ll look at using more of the buttons. My plan was to use a single Tap Dial Switch for multiple rooms but I might need another or to simplify the level of control.
The dimming response is how ZHA handles dimming of a light. I am using the ‘Step’ command to provide a smooth dimming command. So when you dim it below 1% it will turn the light off. That’s just how ZHA handles the dimming when using the Step command.
Not sure if I could make some logic to fix this, as the step command takes care of the fluid dimming, by adding logic you’d need to check the state of the light which will not be updated as fast.
As mentioned before, the state of the light is not tracked by the blueprint. As that would not be viable for how ZHA handles the Dimming and the Light control.
This looks very cool! Any chance to make this work for Z2M (Zigbee2mqtt)? I’m a noob when it comes to creating blueprints, would love a Z2M version just like this.
There is no quick way to convert between the two systems.
Not all actions that are implemented in ZHA are present in Z2M. The multiple presses for instance are not there, so you’d need logic for that inside the blueprint.
Not sure when I would have time to convert the Blueprint and it won’t have the same features at first.
As I am using the buttons in ZHA myself, I cannot test it properly to see if it responds correctly with each update of Z2M.
Key Features:
Requirements:
