Hi Harry @spockfish,
Thank you very much for this big update.
I have the same issue as @Gavin_Riley, namely that the time on the display is 0:00. This is for both timestamps: the playback-time and the total time of the song.
I have this issue on all three RPIs that have a display. Those are RPI 3A+ or RPI 3B+.
The feedback for the RPI 3B+: e13b5b65f93315d3
Thank you very much for all the efforts!
Kind regards, Frank.
Hmmm… have I totally overlooked that one? Thanks anyways for your feedback. I’ll have a look at my own system, as this sounds like something that’s 100% reproducible.
Still WiFi WPA3 doesn’t work. Can’t login RoPieee to AP
I found a few minor bugs in the GUI regarding the placement of various functions in iOS (iPad) displayed on Chrome or Safari browser. This issue occurs in the following tabs: Audio, Network, Remote, Advanced, Services (UPnP/DLNA, Spotify Connect, Squeezelite), Information.
On Android and PC platforms this issue doesn’t exist.
RPI4 - same issues with time signature reading 0. Also without full power cycle my official Pi touchscreen doesn’t initialize at all. Using Advanced->Reboot comes up with a black display. Multiple tries. Thanks for the updates, looking forward to more features.
Hi all - My pi screen is also blank, I have tried a few reboots etc. The endpoint still works though, I can play music to it, but no clock or album art etc.
One of my displays also went dark after the update process – including during the boot sequence. I ended up re-flashing an older image (which confirmed that the display itself was fine), then re-flashed the current version (which did not work initially), and started the process of writing this up for Harry. Then, the new image just started working – so far so good.
Wifi not working since 2024.04 (on Raspberry Pi 4 Model B Rev 1.1, onboard wifi). Are there problems with WPA3 ? Feedback 561d2325049c947d, but with Wired successful connection (of course), I don’t know if you’ll see a Wireless connection.
By the way, for technical reasons, I have Wifi on a subnetwork (where Roon server is), and Wired on another. So I cannot access Roonserver wired. It could be interesting to be able to force a Roon server address in Ropieee, in another subnetwork (routable of course) to handle these cases
Yes, the are indeed issues. Not something I can fix, we rely on the gods from Raspberry.
That won’t work: Roon uses multicast to find it’s components and you cannot configure an IP address in the Roon ecosystem. That means that you cannot have a Roon ecosystem divided over multiple networks.