Thanks - in the meantime I’d modified the local version, but can confirm that your update also fixes it.
Did the latest Home Assistant update break this blueprint? Now I only get the dial to work, and none of the buttons are responding.
Hi.
I’m the author of the blueprint. I haven’t see any issues with 2025.8 or 2025.8.1.
If you’re still having issues, can you enable logbook logging in your instantiation of the blueprint and then check the logbook to see if button presses are showing up? You can also navigate directly into the ZHA integration and then navigate into your specific dial and see Logbook events there. That won’t include the additional logging the blueprint does, but you’ll be able to see if the button presses are making their way into ZHA. If they aren’t getting to ZHA, they’re not going to get to the blueprint.
Let us know.
It seems like I had a hardware issue…
1 Like
I have the same issue. Did you get the toggle working?
For now I reported it as an issue: ZHA - Hue Tap Dial Switch RDM002 - toggle not working · Issue #161377 · home-assistant/core · GitHub
I hope this was the right place to do that.
Hi, @ikzelf.
I’m the author of the blueprint. You created an issue against Home Assistant “Core”. That’s Home Assistant itself - it’s very unlikely that this is a core issue. It’s likely to be an issue in your configuration. Possibly, but less likely, and issue in the blueprint. Least likely, an issue in core 
Can you provide some additional info to help figure out what’s going on?
The post you replied to included mention of seeing tap activity showing up in the log. Are you at the same point? In other words, have you made sure logging is enabled in the blueprint by setting “Enable logging to Logbook” to true?
Does your knob correctly control media playback? (in other words, is it just your custom automation for your lights that doesn’t work)
Looking more closely at the comment you replied to, I’m actually confused by what the post says. The author is saying that button 4 presses aren’t working for a light automation. In this particular blueprint, a tap on button 4 is is always a “Next Track”. The blueprint allows the configuration of other button 4 events such as long presses and multi taps, but not a single tap.
You can fully customize a single tap on button 2, but that’s the only button that can have a custom tap event. (all buttons can custom long press and custom multi tap).
If you really want button 4 to do something custom, I’ve made another blueprint that allows for full customization of all events. There’s a link to it in the first post on this thread.
So let me know where you’re at with this and we can go from there. I do use a tap on button 2 to toggle lights and it works fine and I’m fairly confident that the blueprint works.
thanks for your reply. The button press is delivered (short press). I tried to use it as a toggle for lights on/off. The switch ON works, the switch OFF works but the toggle does not. I can imagine something like a state is missing.
I am a fresh HA user so please don’t assume I know how to do even the basic things. I found this in traces:
Option 16
Executed: 21 January 2026 at 15:24:16
Result:result: false
conditions/0
[Error in describing condition: undefined is not an object (evaluating ‘e.includes’)]
Executed: 21 January 2026 at 15:24:16
Result:result: false entities:
does that help?
It doesn’t help but I don’t think it’s a problem with this blueprint. Assuming you have a light system that supports basic automation, toggle should be straightforward.
My suggestion is that you disentangle this issue from the blueprint. Get your automation working as a standalone automation and then, once it’s working, do the same thing within the automation.
You can do this by going to Settings > Automations and scenes, clicking “Create Automation”. Then work on getting a light toggle to work. Once you have that, do the same thing for the button you want to automate in the blueprint.
In the end, it should probably look very similar to what I posted in the screenshot. Hoep this helps.
thanks, I will try to find what I can for that. An other thing I noticed, the toggle from a double tap does work. Just not from the single tap. BTW: the lamp is a Hue so that should not be a problem.
Also, when I use ‘Run action’ the toggle also works as expected.
That’s the UI for the other blueprint, not this one.
Button 3 Short Press shows “Light Toggle” and then a second item turning a light off. That’s not right. Fix it so it looks the same as Button 1 Double Press, which you know is working.
I hope this gets you pointed in the right direction.
You should close the issue you raised on “Core”. I don’t think there’s a core bug.
I also don’t think there’s a bug in the blueprint, and I’d like to reserve discussion in this thread for blueprint issues.
For anyone following this thread…
I posted an update to this blueprint. You should be able to install it by clicking the “Install Blueprint” button on the first post and then allowing Home Assistant to overwrite the existing version.
This update has one feature only - it splits media player into two targets instead of one. The first is the “Volume” player, the second is the “Transport” player.
This change allows you to specify one device whose volume should be controlled and another device which will receive the play/pause, previous track, and next track events. This is useful for people who have separate streamers, transports, DACs, pre-amps, etc.
This is small breaking change. Your automations will require attention after you’ve installed this. You simply open each, one at at time, and specify the correct volume and transport media players.
Hope you find this useful!
1 Like