Excellent! I’m sure you saw that you can tweak how volume control works - the defaults I used work well for me but they’re editable if you want it to be more likely to make larger or smaller adjustments and you can edit the size of the adjustments. Glad it’s working, though!
Not sure what the issue is. I plugged the Sonoff dongle into the Raspberry Pi, went through the configuration process and then added the Philips Dial. Both devices seem properly configured in HA.
Yesterday, updated HAOS with the November release and downloaded the blueprint. In the blueprint, I selected the Philips Dial and the media player for my Lyngdorf streamer (then tried the IPad as an endpoint but both result in the same error).
Hopefully, will have some time over the weekend to look into this.
I moved across a bit more of my previous remote automation this morning, and did a bit more testing.
Play/ pause, next track, previous track and volume all work as expected.
I added a button 2 custom automation and a long press automation, both of these also worked fine.
What didn’t work for me was a button 2 double click automation. I can see what looks like a sensible event is firing, but from the trace the automation doesn’t look to be recognising the event. I can look at the code / do more if that’s helpful. This isn’t urgent for me!
My only other thought is that intuitively from the button position on the device I expected 2/4 to be next and previous track. I need to label the buttons anyway!
Thanks for all your hard work, the volume adjustment is just great to use, much nicer then multiple button clicks.
1 Like
When initially setting up the RDM002, I saw there is an „identity“ button in the device settings. Does anyone know what is supposed to happen when pressing that option in the GUI?
I am starting to wonder if I made a mistake when setting up the hardware.
Interesting. I took a quick look at the blueprint to see if there was an obvious cut and paste error or something like that. I don’t see it. I can’t do more than this now. I’ll have to look when I get home.
When you say “trace” are you looking at Logbook with it enabled from within the blueprint?
This was just a choice on my part. I found that it made the most sense for me, personally, to have the previous and next track buttons be in left/right position versus something else. So I label my buttons like this:
Unfortunately, this labeling approach I use is complicated and error prone. I can’t easily share them. But this will at least clarify why I did it this way. I use the upper right for controlling the lights in the same room as the endpoint.
If you prefer the north/south orientation for transport (or any other changes) the other blueprint might be a better choice. You would just have to create the automations for the buttons and volume adjustments (small, medium, large in each direction) but that’s pretty straightforward. Once you have that set up for one control, you can just duplicate the whole thing for other rooms.
Is it possible the button is “identify” and not “identity”?
Have you installed the Roon integration in Home Assistant as described here:
If you haven’t done that, can you do it? Once you do that, your Roon endpoints will show up in Home Assistant as media players. This will be in addition to them possibly already showing up as media players through other means. You may see them show up multiple times because of this - that’s very normal.
Try choosing the Roon media players from within the automation.
If that’s not it, I can help look at this more when I’m back from vacation. I’m in New Zealand for a couple of weeks and am about to take off on a two-week motorcycle trip which will mean that my time and connectivity is limited 
Success!
I already had the Roon integration installed but something must have gone wrong during the initial setup of the Sonoff dongle and Philips dial. After reinstalling/reconfiguring the hardware it is working now. The basic controls are operational and I was able to add a radio station favorite to button #2. Also played around with the settings for the volume control. Great work!
Thanks again for your help and enjoy your vacation.
1 Like
Wow! That’s great news! I’m so glad you got it working!
Trace is a very cool option in the edit automation screen. It allows you to see what path was taken through an automation (and some of the variables). Very cool if you haven’t seen it.
In my case I can see the double click event arriving - and not triggering any of the code paths. Could be a typo in the event test or something like that.
Try it when you’re back and will do some more digging if it isn’t obvious.
Was really enjoying using your code this afternoon. I think previously I’d just have lived with some volume variation between tracks - but the ease of use of your code / tbe device meant I didn’t!
Just played a little bit with the dial and it is pretty cool and reaction is almost instantaneous .
One thing I just realised is that the dial has an „end point“ where you cannot turn the top wheel any further which e.g. means that at one point you cannot reduce the volume any further. What I have done for now is turn the wheel all the way to the left and then reduced the volume in the Roon app to the lowest level. Was just wondering if there is any other way to „calibrate“ the dial.
I’ve been using these controllers for years and don’t recall ever hitting an end point. It’s possible I somehow just missed it. It’s hard for me to understand how this would be a built-in behavior since the controllers generate step changes, not absolute values. Are you sure this is what’s happening?
My Dial definitively has end points when turning the wheel all the way to the right or left. I currently have set the wheel to be relatively insensitive (i.e. it must be turned quite a lot to make volume changes) which is probably why I realised this. Anyway, not really much of an issue.
Just checked - my RDM002 definitely doesn’t have an endpoint.
I wonder if yours is faulty.
1 Like
I had another look and there was definitively some resistance after a 360 degree turn. After pushing a little harder, the wheel turned past the resistance and now I can turn it all the way without any problem. Maybe there was some dust. Anyway, problem solved and thanks for checking.
1 Like
I’m glad you figured this out. It had me very confused.
Thanks for confirming this, @GregD !
Quick question, probably very simple:
I have helpers/ input buttons defined to control my Lyngdorf streamer. Is it possible to map them to the dial. What I am trying to do is add a mute toggle?
I have tried to add the mute function via the player but that would only work one way(i.e. mute or unmute) and not as a toggle.
You might be able to get it to work with the approach here using a simple script.
1 Like
Thanks for digging this out. In the meantime, I believe I have found out how to map my helper button to the dial.
Back from holiday. I’m not sure how the multi-press issues crept in…probably a copy/paste issue as I rushed them out before I left on vacation. They’re fixed now. You can re-install using the installation button on the blueprint exchange forum and that will overwrite your existing copy.
Sorry for the inconvenience!
Fantastic - now working perfectly!
Thanks again!
1 Like