Very nice! As a request: is it possible to get the artist, album and song information too? So I can get it displayed on my dashboard, The way displays are implemented in Roon itself are very limited.
I already added this info as tags. But I will look at the dashboard since I currently not use it, maybe I overlook something.
I just released a new beta, with a long requested feature: the ability to start internet radio and the artist radio. It currently only works on outputs. I plan to enable it for zones as well once it’s stable.
Deleted my post because I was asking if I could start playlists or radio stations in the future and somehow missed the bit that it was in beta already. Thanks for making the app Merijn!
Really nice to see so many ppl are currently enjoying the app. I am gonna release 1.1.1, first in beta, containing the latest nodejs driver. The current driver is a bit outdated, but it’s great to see it just received some love from Roon Labs.
Yes, this is possible, good one. I just added the action cards for shuffling a genre, and starting a playlist. Release 1.1.2 is in beta now, once stable let’s put this one live for all users.
Thank you for the bug reports! I need to do more work to stabilize this release because of updates to Roon Labs’ internal driver. Also the app doesn’t detect yet when the Roon Core goes offline or online yet, which is important for enabling or disabling devices, flows, and input forms to avoid errors. We currently have around 15 test users, please continue testing. It helps! Hope to give an update soon!
Wrong player starts when i start playlist. In my case flow should start “Baard Ole” output, but “Bad nede” is started 4ea06d5e-daf3-4311-939b-5fb6ea244afc
Hello everyone,
I would like to control my Roon server via Homey. The server is in a different VLAN, so Homey isn’t displayed in the extensions. Is there a workaround?
The Roon app acts as a network device using broadcast, not Homey-specific. Its driver communicates like other Roon devices. For VLAN issues, enable multicast routing or use a network repeater.
I’m releasing version 1.1.3 containing some code refactorings, to beta. Current beta version 1.1.2 seems pretty stable. But let’s have this done first so I can gather all outstanding requests and get ready to implement them.
Unfortunately, I’m still having the problem that the Homey extension isn’t showing up under Roon. My Roon server is in a different VLAN than Homey, but multicast is enabled. I can access other devices across VLANs. Roon is installed as ROCK on my system. Does anyone have any ideas about this? Edit: My network is based on UniFi.
Hi! This is a known limitation with VLAN setups. The issue is that Roon Core can’t discover the Homey extension across VLANs, not the other way around.
For UniFi networks, try these steps:
Enable mDNS in your UniFi Controller:
- Go to Settings → Networks → [Your Homey VLAN] → Advanced
- Enable “Multicast DNS”
Allow Roon discovery traffic between VLANs:
- Ensure UDP ports 9003-9004 can reach from Roon VLAN to Homey VLAN
- Check that multicast/broadcast forwarding is enabled between VLANs
Quick workaround: Temporarily move Homey to the same VLAN as ROCK. Once Roon discovers and pairs with the Homey extension, you can move Homey back to its original VLAN - the connection should persist using the established IP.
Unfortunately, this is a Roon Core discovery limitation that the Homey app can’t work around - it depends entirely on your network configuration allowing Roon to “see” Homey across VLANs.
Since you mentioned multicast is already enabled, double-check that mDNS is specifically enabled for cross-VLAN communication in UniFi. Some users have also had success with creating specific firewall rules allowing all traffic between Roon and Homey VLANs temporarily during pairing.
Please let me know if the temporary VLAN move works - that would confirm it’s purely a discovery issue!
