· Ropieee d9212ee5d5b7db1b Since moving Roon from NUC/ROCK to windows PC I cannot find the Ropieee extension. It does not show up under extensions. Is there something else I need to do to activate it? Ropieee runs on a Pi4 with two connected endpoints a Chord Hugo and an RME DAC. Both endpoints are detected by Roon and play music. I just cannot get the Ropiee display to work. The display says that I need to enable the Ropiee extension, but that is not visible in Roon. This worked OK with working display when using ROCK as server.
Tell us about your home network
· Virgin Hub modem (not used as router) Orbi Mesh wireless network with two wired satellites. All endpoints are wired. There are a couple of ethernet switches in the network.
Thanks for writing in and for sharing your report!
Since your endpoints are playing music, your basic network routing is fine, but Roon extensions rely on a different discovery mechanism that Windows often treats with more suspicion than ROCK did.
Windows Firewall is significantly more restrictive than the ROCK operating system. Even if Roon is working, the “handshake” required for extensions might be blocked.
On your Windows PC, go to Control Panel > System and Security > Windows Defender Firewall.
Select Allow an app or feature through Windows Defender Firewall.
Ensure both Roon.exe and RoonAppliance.exe are checked for both "Private" and "Public" networks.
Ensure your network profile is set to Private. If it is set to Public, Windows will hide your PC from other devices on the network, which prevents extensions from connecting.
Sometimes a third-party antivirus (like Norton or McAfee) manages the firewall. If you have one, you’ll need to ensure the Roon processes are whitelisted there as well.
RoPieee might still be trying to “talk” to the unique ID of your old ROCK installation.
Access the RoPieee web interface by typing http://ropieee.local (or the Pi’s IP address) into a browser.
Navigate to the Roon tab.
Even if everything looks correct, click "Save Changes" (even if you didn't change anything) and let the unit reboot. This forces the RoPieee Roon Bridge and the extension service to broadcast a fresh announcement to the network, which your new Windows Core should pick up.
I use Norton 360 so windows firewall options are greyed out. Within windows the network is set to private.
In Norton 360 there are four Roon related apps that are signalled as “allow” for all options. These apps are “Roon Appliance” “Roon” “RAAT Server” and “RAAT Server”. (ie RAAT Server twice.)
My Ropieee interface does not have a Roon tab. The available tabs are: System, Audio, Network, Display, Remote, Advanced, Services, Information and Devices. I cannot see a “save changes” option on any of the Ropieee tabs. I did try reinstalling Roon Bridge, but no joy.
So far no joy with any of the above, or multiple reboots, reinstallations etc.
Thanks for confirming those Norton and Windows network settings. Since the firewall and network profile are properly configured and the audio zones are working perfectly, this points to a specific quirk with how the RoPieee extension registers itself with a brand-new Roon Server core.
The RoPieee web interface has evolved over time, which is why you aren’t seeing the old “Roon” tab or a direct save button on those pages.
To force the extension to re-announce itself to your new Windows PC, please follow the exact sequence outlined by another user who solved this specific migration issue here: How to re-add Ropieee extension to Roon
Since RoPieee is a third-party implementation (independently developed and maintained by Harry, rather than official Roon Labs software), our visibility into its internal extension services is a bit limited.
If the steps in that post don’t get the display working, your best course of action is to open a new topic in our dedicated Audio Gear Talk > RoPieee category. The developer and a very knowledgeable community of RoPieee power users monitor that section closely and will know exactly how to trigger the display extension on the newest RoPieee builds.
The extension is showing an error during connection to the Roon server.
Can you remove the paired extension? Go in to Roon → Settings → Extensions → Authorizations and then ‘View’. Remove all RoPieee extensions and restart your Pi.
Thanks for your reply. That link doesn’t really show detailed steps, it shows a solution for a fairly specific set of circumstances that don’t match mine. I’ll proceed further with spockfish.
Tried removing the paired extension as suggested. However, there are no extensions listed under authorisations. I rebooted Ropieee and then rebooted Roon as well. Still no current or previously authorised extensions. I’ve also sent you updated feedback 992069d9f8955755.
For further information, I don’t know if this is a related problem or another problem to solve. Since the migration from ROCK to Windows my Airplay devices and Chromecast devices do not work. The devices show as endpoints in Roon and Roon sends music to the devices. I briefly get a signal path but no music plays and within a few seconds the indicator switches from playing to pause/stop depending on source.
Just to confirm, my Ropieee endpoints play, it is just a problem with the extension/display. Also a NAD T778 which uses RAAT also plays correctly in another room.
Tried the above, still seem to get the same problem. On an Airplay device (Yamaha AVR) the endpoint shows up in Roon as an Airplay device, I can play a track, but no sound. I get a signal path in the Roon GUI but the track timer does not move. After a period the GUI switches back to pause (from play) and the signal path disappears. Switching in and out of compatibility mode does not appear to make a difference.
Trying the same thing on a Naim Mu-so 2 (Google cast device) gives a similar result. As does trying 2 Nvidia shields (get a picture showing track playing on a connected tv, but track timer does not move and no sound) and a Sky Q box.
My iphone will play music (Wifi connection) but my Ipad (again Wifi) gets stuck on enabling.
Tried turning off firewall, no joy. Tried a variety of other things that kept me occupied for most of the day.
Then from deep in my mind came the memory that when I previously tried to set up Roon Arc with Tailscale I lost my Linn Roon Endpoint. Since moving back to Windows I was using Arc with Tailscale again.
Turned Tailscale off and all appears to be good. Ropieee now has a display up and running. All my endpoints appear to be singing again.