BETA Release 20260613

[spockfish (Harry ten Berge)]

Another beta release for this weekend.

Nothing too exciting: the realtime audio information that is available for USB devices is now also available for the HAT (if present). Furthermore a kernel update and some improved logging.

Enjoy!

[Frank_M (Frank Minne)]

Five RoPieees are updated.
All working as it should.
Thank you again for the nice work.

[Moshe_Zolotov]

Installation went well on RPI5+Display2

Thanks

[Sheemie_Ruiz]

Update works on Holo Red.

Thank you

[spockfish (Harry ten Berge)]

@Sheemie_Ruiz

Update works on Holo Red.

Out of curiosity: how does the RED ‘shows itself’ on RoPieee? As a single USB device or do you have 2 devices visible on the audio tab?

[Sheemie_Ruiz]

Two devices.

If I use USB, it shows both devices, and shows locked by the program I use.

Then I2S is used, it shows only one device.

UAC2.0 Gen2 = I2S

UAC2.0 Gen2.1 = USB

[James_Fitzell]

Hey Harry, I’ve been updating all of my devices to the latest beta and no new issues but I’m still seeing the extensions all disappearing from Roon at some stage (previously mentioned on the May beta). It’s not a major issue, but it’s odd that it happens to all of them at much the same time/uptime. Music continues fine, it’s just the extension that loses connection.

BETA Release 20260525

Hey Harry, not sure if this is the best place to mention it but yesterday after 10 days update every one of my Ropieee’s (all running RoPieee 2026.05 (3705) [BETA] (or the Pi3 equivalent)) dropped their extensions. I rebooted Roon server with no success. When I rebooted each endpoint it came back up. Could be a one-off, but it’s odd that it impacted all of them at once (and I’d upgraded them all at the same time so it was ~10 days uptime for all of them)

** EDIT: Whatever is causing it, it’s fixed by an endpoint restart but it’s not fixed by a touchui restart.

Jun 19 14:52:29 Study ropieee-touchui[164446]: WARN [navigationcontroller.cpp(90)] NavigationController::communcationFailure() problem detected! (remote connected: true; core detected: false)
Jun 19 14:52:29 Study ropieee-touchui[164446]: WARN [navigationcontroller.cpp(90)] NavigationController::communcationFailure() problem detected! (remote connected: true; core detected: false)
Jun 19 14:52:29 Study ropieee-touchui[164446]: WARN [navigationcontroller.cpp(90)] NavigationController::communcationFailure() problem detected! (remote connected: true; core detected: false)
Jun 19 14:52:34 Study ropieee-touchui[164446]: WARN [navigationcontroller.cpp(90)] NavigationController::communcationFailure() problem detected! (remote connected: true; core detected: false)
Jun 19 14:52:34 Study ropieee-touchui[164446]: INFO [screencontroller.cpp(161)] ScreenController::setDefaultBrightness()
Jun 19 14:52:34 Study ropieee-touchui[164446]: INFO [screencontroller.cpp(107)] ScreenController::exec_brightness() 26
Jun 19 14:52:34 Study ropieee-touchui[164446]: INFO [navigationcontroller.cpp(128)] NavigationController::processState() screen: 13
Jun 19 14:52:34 Study ropieee-touchui[164446]: WARN [navigationcontroller.cpp(90)] NavigationController::communcationFailure() problem detected! (remote connected: true; core detected: false)
Jun 19 14:52:34 Study ropieee-touchui[164446]: INFO [roon.cpp(37)] Roon::ipAddress() found interface: “end0”
Jun 19 14:52:34 Study ropieee-touchui[164446]: INFO [roon.cpp(48)] Roon::ipAddress() “192.168.11.252”

[spockfish (Harry ten Berge)]

Can you send me feedback?

[Moshe_Zolotov]

Today I had two (few minutes apart) consecutive Ropieee black screens, which required power off and on. Attached is the log 69183112984cb67e

Please advice

Thanks

Edit: so, it just happened twice, since then, everything working fine.

[spockfish (Harry ten Berge)]

@Moshe_Zolotov

Today I had two (few minutes apart) consecutive Ropieee black screens, which required power off and on.

but was it dead? did you checked if you could reach the webpage?
when you restart the pi, the actual running log is gone, so there’s nothing to see.

[James_Fitzell]

Sure thing. Here’s one of them still not showing the extension (and I haven’t rebooted it).

64e0e13ed9edb407

[Moshe_Zolotov]

Ropieee turned off three times today while playing. Screen blank. WebUi not accessible at all (not even ping). Requires power restart.

Log ce41b2e77c382887

Thanks

[spockfish (Harry ten Berge)]

What I see is that your Roon server quite often immediately disconnects after the pairing. And I even saw time outs on the extension level (so this is handled by SDK from Roon). So this might be network related… I assume you already tried restarting your ROCK?

[Moshe_Zolotov]

Currently experiencing lots of periodic music cut offs. Reset server (roon, Hqplayer) mesh network, main router, to no avail. Issues are repaired for a little while after each Ropieee reboot, then issue return.

Edit_1:

Reinstalled Hqplayer server (newer version 5.17.2). Moved to less CPU demanding filters Number of music cut-offs slightly reduced, but they still occure frequently.

Currently I am on the last Beta version.

Sending new log 57e6198bcfd5a2b9

Thank you very much for the support.

Edit_2:

Ropieee installed (or reinstalled) OTA version ‘RoPieee 2026.05 (3755) [BETA]’, on my device.

Currently not experiencing any music cut-off for the last hour.

Thanks again

[spockfish (Harry ten Berge)]

you have undervoltage messages, i suggest you check your power supply.

[Moshe_Zolotov]

Thanks

I did change my 5V 2A ps to 5V 3A one.

Thanks again

[James_Fitzell]

Hi Harry,

Yes I’ve tried rebooting Roon (with no change, the extensions that are broken don’t fix and the ones that are working don’t break).

The only thing that fixes it so far is rebooting each endpoint (I have tried restarting the touchui service but it doesn’t help, not sure if there are others I should try).

Thanks

[spockfish (Harry ten Berge)]

No, the touchui is not involved. There’s only the ropieee-remote, which is the extension.

[James_Fitzell]

Ok. Apologies, I’ve been restarting the wrong thing. I’ll try restarting the remote next time it occurs. (Presumably on the latest beta rather than this one )