I’v just pushed out another beta with the following updates:
support for hardware mixers on USB Devices. Up until now, you could only configure a hardware mixer if you are using a HAT (that supports that). However, there also USB devices out there that have a hardware mixer as well. That has now been implemented. Keep in mind: this is for UPnP/DLNA, Squeezelite, Spotify, Airplay. With Snapcast this is not possible.
bump the kernel, with a fix for properly disabling EEE. This is causing an issue for some users (at least for @James_Fitzell ).
Hi Harry,
Updated 5 RoPieees (3 x RPI3B with Display I and 2 x RPI4B with USB-DAC). All went well.
Thank you again for all the efforts.
Kind regards, Frank.
RoPieee 2026.05 (3679) [BETA]
Hardware: Raspberry Pi 4 Model B Rev 1.4; 4GB RAM, 16GB disk
Network: wired ethernet
Audio: USB DAC (TEAC) — Roon RAAT, AirPlay2, Spotify Connect, Squeezelite
Display: no
Remote: Flirc — Roon RAAT only
confirmed that Audio now reports: LOCKED by Airplay, as expected.
One thing I notice — and this is not new in this beta — is that if I want to use Squeezelite, after listening to other services, I have to either reboot the Pi, or stop/restart the Ropieee Squeezelite service, before it appears as a device in Lyrion. Once there, it’s fine.
Yes. This is a known issue and related to how certain services handle access to the audio device. Basically there are 2 types of services:
those that intelligently access the audio device when actually needed (as in: playing audio). Examples are Roon and HQP.
services that require a static audio device configuration, and try to lock the service when being started, whether you’re actually playing audio or not.
So this is a known issue. The good news is that, now we have realtime information by which application is locking the audio device, we can implement logic like this:
detect a non-playing window (let’s see 5 seconds of being unlocked)
see which service is configured but stopped because of not being able to access the audio service
restart that service
That willl take some time to implement, but it is high on the list because this is the reason why I built the realtime monitoring in the first place.
