Dedicated RHEL 8 VM with RoonServer.
Home WiFi, no VPN.
In this case: Raspberry Pi with roon bridge (ropieee).
I am running Roon on macOS as controller application.
One of my clients is a Raspberry Pi running Ropieee; I use it to occasionally listen to some music to fall asleep to in my bedroom.
This Pi is powered off automatically after the playback stops.
Every time I bring up the macOS Roon application the next day it is hung and can only be quit by using “Force Quit”.
It does not to be related to a specific macOS release/version - I’m running Ventura now, it definitely happened with Monterey the same way.
Steps to reproduce:
- RasPi with Ropieee powered on and ready.
- Roon (up to date version) running on macOS (on a MacBook Pro).
- Ropieee is selected as “audio zone” in Roon.
- Choose some Album; start playback
- optionally: activate the sleep timer to stop playback after a set time
- After playback starts, put the MacBook into sleep mode; the Roon application stays running (the application window may be closed through cmd+w).
- (time passes, playback finishes, the RasPi is powered off by cutting the power supply)
- next day: wake up the MacBook, bring up the Roon application window
- application freezes and can only be quit through “force quit” as it does apparently not get that the Ropieee client has disappeared.
This may happen with other endpoints as well.
I think the issue might be that the Ropieee client is powered off while the controlling application is not active (in the sense of “getting any CPU cycles at all” since the MBP is in sleep mode) but still “running” and it does not undergo some kind of initialization process after the MBP is woken up.
So from the application’s view, the endpoint just suddenly disappears completely during playback (and the wall clock time skips a few hours).