BETA Release 2026.02

Hi,

I’ve just pushed the first beta build for 2026.02!

Besides the usual kernel update this has (for now) one feature: adding Snapcast to RoPieee’s supported services.

Recently I’ve been playing with Music Assistant: a streaming server solution from the Home Assistant team. It looks promising: I already like it more than Plex music :wink: And important: it’s open source.

Music Assistant has it’s own native protocol (and client), but that’s still under heavy development. It does however also support Squeezelite (LMS) and Snapcast.

I wanted to release this early, so we can have a relatively long test period.

Enjoy!

7 Likes

Installed on 5 RPIs (3 * RPI3B and 2*RPI4B).
All seems to work perfectly.
@spockfish Thank you for your endless improvements.
Kind regards, Frank.

1 Like

Installed on RPi 5 16gb with display 2. Connected to Roon, Hqplayer. My RPi 5 feeds two USB outputs concurrently.

Installation was smooth. Boot at 1st trial :smiley:

Thanks

1 Like

Good evening Harry

Both screens ara up and running. No issues at all
Display 1 on Raspberry Pi 4 Model B Rev 1.4
Display 2 on Raspberry Pi 4 Model B Rev 1.5

Tnx again

1 Like

Hello Harry,

Ropieee no longer recognizes the DAC since the update.
Stack Audio Link II (CM3)

Atoll DAC300

1ad3c13fb19ee0e9

Best Regards

Hello @spockfish,

Based on your comments, I installed Music Assistant Server (running in a Docker container).

I can stream from MA to my Sonos speakers, but RoPieee does not show up as a Snapcast player.

I assume there is some issue with my home network that I need to fix, but was curious if the Snapcast integration worked out-of-the box for you, with no custom settings in MA.

Thanks for the time and effort you devote to RoPieee!

Yes, except that you need to enable ‘Snapcast’ as a ‘Provider’ in MA, but I assume you did that.

A few things: for discovery it relies on M-DNS. That can cause issues with Docker containers, so be aware.

And on the client side: not sure if you use an USB DAC or HAT, but Snapcast wants to lock the audio device. And it does that when starting up. That means that if you’re listening to Roon for example, and want to switch to Snapcast, you probably need to restart RoPieee.

Long shot, but …

Is there anyone who can provide me a feedback with 2 the same USB DAC’s? So 2 identical USB DAC’s connected to RoPieee and powered on?

Hey Harry,

i dont use the betas right now, and i dont have the exakt same USB DACs, but a SMSL DAC (SU-1) and a DDC (PO100 Pro) that identify themselves both as the same device in the webinterface, an i believe its the same USB-implementation (XU316). Maybe worth a shot?

Yeah, this question is really not related to the beta builds, so I should have just created a new topic :wink:

YEah, let’s try.

Thanks!

Thanks for those suggestions @spockfish

As you mentioned, the issue was related to networking/discovery in the Docker environment (running via OrbStack on macOS).

When I spun up the Docker container on my Synology NAS instead, the USB DAC was recognized by Snapcast right away.

1 Like

Feedback ID: 616b3a1a548fbc8e

Hey Harry, I can’t do it right now but I can later today or tomorrow. I have several usb DACs of the same make/model. For what it’s worth, previously I actually tried to have both on the same Ropieee and it never worked, it never saw the second one

Hey Harry, I’ve generated two pieces of feedback.

cb16f8055c9fe06e
Just after a fresh reboot with only the one USB DAC attached (so shouldn’t be worth looking at unless you need to compare to a known good). I’ve only got the one DAC plugged in (as shown below) but for some reason this SPDIF DAC always shows up as two devices in Roon (the second named #1 but not enabled)

9edb407af953cfe1
After plugging in the second USB DAC (per below images, looks like both are correctly detected now)

Cheers,
James

1 Like

Is it possible to roll back by switching back to the stable channel ?

Regards

@Jpaul
According to me, if you switch now to the stable channel, RoPieee will do an upgrade when the Stable build-number is higher then your actual Beta build-number. In other words, returning to stable channel will take until a new stable version is published. You can also just reflash your SD-card and leave it on the stable channel.
Kind regards, Frank.

That is not correct. Switching back to stable results in the latest stable being downloaded again. Keep in mind that this will take a few hours though.

1 Like

I waited quite a long time (over 7 hours) without any rollback

Stack Audio Link2 (CM3) - f512967eaa6f223f

RPI4 - a3ce950e9c4a25d0

Regards

Hmmmm…. I see an issue. @Frank_M was not entirely correct in his anwer, but neither was I ;-

Anyways: if you want to go back to stable right now you need to reflash.

As you’re running the last beta, which has only added Snapcast: is there a specific reason you want to back to stable right now?

Hi Harry,

Ropieee beta 2026.02 no longer recognizes my DAC (Atoll DAC300)

Stack Audio Link II (CM3)

1ad3c13fb19ee0e9

However, with an RPI4, the DAC is recognized correctly.

Regards