Oh! that one I missed! So USB device plugged in, you not touching it, but doing volume control on the display breaks stuff?
Removing the USB device fixes it then?
Oh! that one I missed! So USB device plugged in, you not touching it, but doing volume control on the display breaks stuff?
Removing the USB device fixes it then?
Yup, that was the most recent testing.
While the device is plugged in, any form of volume control breaks playback… even if I don’t touch the usb buttons/knob.
While the device is unplugged, the endpoint works perfectly.
Ok thanks.
I really think this is not related to this device specifically: tonight I’ll try to reproduce this on my test environment.
Rather interesting case… ![]()
Not sure if it makes a difference but I’m using a USB DAC too. I only have one hat DAC and unfortunately it’s in a case that blocks access to the USB so I can’t easily test the issue there… can test on other rpi’s though.
Ok, I’ve tested with a Pi equipped with a display. It works as expected. No weird stuff like you’re seeing…
I’m gonna test a bit more with a DAC connected as well, because that’s a difference.
Hi Harry,
I’m leaning towards it being a dodgy device. I’ve tried it on another pi and although it’s being detected it’s not playing/pausing at all (on stable or beta). Unfortunately I can’t test volume knob since I’ve realised most of my usb outputs have fixed volume.
Hi,
I’ve pushed out another beta. This is really, really… really the last build before my holidays the next coming 2 weeks ![]()
Anyways, nothing too exciting: some web interface changes wrt new documentation and a fix for the ‘Spotify is broken’ issue.
So ok, maybe that is exciting ![]()
Enjoy!
Two units updated RPi4 with no screen one RPi3b with Display 1 both are working fine.
RPi4s are on RoPieee 2025.06.2 (2678) [BETA]. Kernel version: 6.12.41-SPCKFSH-v8+
RPi3B is on RoPieee 2025.06.2 (2681) [BETA]. Kernel version: 6.12.41-SPCKFSH-v7+
Unit 2 below has not updated yet as it was off line for a few days. I just got it back online today so it may take a bit for it to pick up the updates. I hope? We’ll see how long it takes. It is still on 2611 beta.
Unit 1
Unit 2 - not updated yet
Unit 3
Hey @spockfish, this one was user error… I’d forgotten to enable the extension.
I dunno what’s going on, it’s consistently breaking on the Bedroom Pi where I’ve tested it numerous times, but it’s now working fine on the other Pi. I can use it in its current location and it works well so I’ve given up and am moving on ![]()
Unit 1
Unit 2
Unit 3
Unit 4
Did you add changes to Network Tab for save last used input LAN/WiFi ?
Please don’t do that.
I report here stuff that’s been done.
This is not the place to ask for features and whether they are implemented or not.
Thanks
Hi, I’m sorry, but you wrote earlier that you added some new functions to the Network tab. Hence my question about details. Regards
@spockfish Harry I have one RPi4b that seems to refuse installing the update… it says its done it but then I get a subsequent update available message. ive done it a few times now and here is a feedback from the last effort
dda1fdfe20f86074
Hmmm maybe it did 2 updates but now correct … 2661 to 2861 maybe my eyes playing tricks but pretty sure I had it have to do 2 updates
Are you sure that’s not “2681” for the last update?
Hi Harry, Unit 2 in the above list has dropped the screen extension. Still playing music perfectly, just Roon doesn’t see the extension anymore and the display shows it’s lost connection to Roon.
Might be a one-off, but generated feedback for reference: 4a6975432bacddc0
Hi Harry, Unit 4 dropped the extension sometime in the last 6 days. Same behaviour as unit 2 (only with the remote rather than the display).
I feel like this beta has some minor instability in the extension, but the roon bridge side is working perfectly for all of mine so far.
Feedback 2da721c4fc3345cb before I rebooted it. (And yes I know you’re away, no rush)
Hmmm… the only thing I see is an ‘unpair’ coming froming the ROCK.
Weird. Neither has disappeared again (yet) and Unit 1 has worked fine through the whole period (uptime currently 15 days). Unit 4 (and a 5th that’s not on the beta) don’t have display/remotes to make the extension relevant but are also showing up. I updated Roon Server/Core a few days ago (after the two issues) so fingers crossed it just never reoccurs.
Hi all,
Just got back from a roadtrip to the south of Sweden, so fresh and ready for some RoPieee work!
I’ve just pushed out another beta round. This build contains the ‘proper fix’ for the Spotify connection issues that just popped up before my holidays.
If everything seems ok, we’re going to release this week.
The only thing that is a pain is the issue from @Frank_M , which seems to be more and more a specific combination of kernel and type of SD card. I’ve bought the exact same setup as his, and mine works absolutely perfectly over the last weeks.
The choice is this: either stick to an older version of the kernel for PI 3 (during our extensive testing we found a version that also works for @Frank_M ), which has it’s negative effects as well, or upgrade the Pi 3 as usual, but make a remark in the documentation about the SD card brand.
Both are far from ideal of course, so let me thinker on this for a while. But I really, really want to release this week because of the Spotify issue.
Let me know how it goes, and as usual a big thanks!