As my holiday is approaching I’m thinking of doing another ‘smallish’ release.
For now it’s a .2, but maybe this will become 2025.07.
Anyhow, the reason why I want this out is that it improves (somewhat) the wireless reliability. “Somewhat”, because issues with Realtek devices remains an issue, unfortunately. However, as this is now upstreamed in the Linux kernel, I would expect things to change for the better rather quickly.
Anyways, here’s the changelog (for now):
IMPROVEMENT: make (onboard) WiFi more reliable
IMPROVEMENT: add frequency band to wireless information
2025.06.2 (2567) working well so far on pi4 model b rev1.4
8GB memory, 16GB disk, on-board wifi, no remote or display
allo digione spdif HAT
roon, airplay2, plexamp
Hi @spockfish
All RoPieee are updated without problems.
Thank you for adding the frequency band in the WiFi-info. Very handy. Now I know that all my displays are running on the 5GHz-band. Great.
Enjoy your well-deserved holiday.
Kind regards, Frank.
Since the last couple of updates, I cannot have Spotify AND Plexamp services both configured. If I do, then I cannot select Spotify as the output device. Disabling Plexamp returns Spotify to working operation, but then I’m without Plexamp.
issue is known, still needs to be fixed in plexamp … if you get stuck in this state, just start playback to plexamp on ropieee and then pause or stop … wait 10 seconds, then the audio device is released as normal for other apps to use
@spockfish
Hi Harry,
I have the impression that a certain instability has entered the last Beta-update (2025.06.2).
This is the third time that I cannot connect via a browser to a RoPieee. It is on 2 RPIs (type 3A plus). They both have a display, and I see that on the display Option Buttons re-appeared, although it was disabled in the config. Also the LEDs of the RPI are active again, but they were disabled in the advanced menu. The connected “Generic USB HID”-remote is not functional. But for the rest, all seems to work: I can push the play-button on the screen, and than the streamer (not RoPieee) starts to work.
So I believe that the config-file is not loaded correctly when booting up, and the GUI is not starting up.
Both RPIs are connected via WiFi, but when I connect a wired Ethernet, The problem persist: I cannot connect to the GUI (but I can check the new IP-address on the RoPieee-screen).
Since the GUI is not working, I cannot send you a Feedback to analyze what is going wrong.
The only solution is to re-flash the SD-card.
The first time, I took a brand-new SD-card, to be sure that that is not an issue, but since the RPI with new SD-card has again the same issue, I am quite sure that this is not a problem of the SD-card.
Have you, or someone else running this Beta-version, have encountered the same problem.
I know that you are probably enjoying a well deserved holiday, so I don’t suppose you will be able to dive immediately into this problem. But I want to warn you that perhaps there is an issue with the stability of Beta 2025.06.2.
Kind regards, Frank.
… exporting config db …
… waiting for ‘config’ to appear …
… waiting for ‘config’ to appear …
… waiting for ‘config’ to appear …
… waiting for ‘config’ to appear …
… waiting for ‘config’ to appear …
… config export: we’re taking the slow path …
Absolutely. It was running perfectly.
But this morning, when I booted it up, I saw again the Option Buttons, and I knew that I wouldn’t be able to logon to the GUI to check anything (as previous time).
Once it enters this error-state, yes. I can reboot it, and each time the GUI i snot working.
But it is not that I can force it to get into the error-state after a fresh install.
Since this is the third time that I experience this issue, I think it will do it a forth time. But that can take several days.
Yes, indeed. I just remove the 230V of the adapters.
I have just done another test. I tried to connect via SSH, and that one is working. I cannot logon, as I do not have the credentials, but perhaps this is a way to give you a kind of feedback.
