Hi,
Spotify changed (again) something on their API, which resulted in silence ([Bug]: Spotify doesn't play anymore · Issue #26 · RoPieee/RoPieee · GitHub)
This beta release fixes that issue. If everything is ok, we release asap.
Thanks
5 Likes
Hi Harry,
Thanks for all the work!
Unfortunately the Spotify fix doesn’t work for me.
I tried this beta release, 2025.10.2 on my allo usbridge sig.
UPNP works.
Regards,
Annejan
This beta wasn’t released for the Usbridge.
Hi Harry,
I would like to thank you once again for your incredible work, and speedy response and proaction.
This beta 2025.10.2 has fixed Spotify connect it seems to be working perfectly again on my Raspberry Pi 3B 
Kind Regards
Darryn Melck
1 Like
Ah, that’s why it still said 2025.10.1… 
Don’t worry, stable builds are incoming 
1 Like
@spockfish
Hi Harry,
One of my RoPieee’s is sometimes restarting without any reason.
This morning, it did it again. When I tried to connect to the GUI, it was very slow. I tried to make a “Feedback”, but after 8 hours, still no unique identifier.
So I started the feedback again, and now it was at normal speed:
fb1301e65841b008
Can yo see what went wrong around 8:00 this morning so that the RoPieee restarted of its own?
It is connected to WiFi, but the WiFi-antenna is less then 1 meter away.
Another RoPieee is 10 cm away from this “problematic” RoPieee, and I have never seen that one restart of its own. The only difference is that the one with the problem is powered on 24/7.
Kind regards, Frank.
Did you check the advanced tab to see if “reboot schedule” is setup?
Also, not sure if would help harry but what timezone are you in? “8:00 this morning” could be anytime.
Thank you for your message.
In the settings, no reboot is sheduled.
And I am in the same timezone as Harry, so it is 8:00 AM for both of us. That is the reason I didn’t think of stipulating my timezone.
Thank you for the remarks, Frank.
1 Like
Hi Frank,
Thanks for your feedback.
The logs show an error (leakage) which in the end results in the system a) slowing down b) ultimately rebooting.
Question: is this reproducible on this unit? Because then we can test with an early beta build if my fix solves the issue.
And of course the big mystery: why is this being triggered? What’s happening here?
Hi Harry,
The problem is that this is not reproducible. Sometimes I see that that RPI is suddenly rebooting. Up till now it is the only one of my RoPieee’s that I have seen rebooting unexpectadly, but it is not the first time that that one reboots. I really cannot tell since which kernel this “extra feature” was introduced.
For me it is not a big drama, as that RPI is mainly used as clock on my desk. I use another RoPieee as display for my ROON-endpoint, and an additional one as ROON-endpoint. And those two latest are never restarting (but are also only powered on when I am working at my desk at home, so max. 14 hours continuously after which they are again turned off).
Could it be that there is a problem with the SD-card, due to which a “corrupted” file triggers this issue? If you want, I can reflash the SD-card, so to exclude it. But again, I cannot tell how long I have to test before I can be sure that this issue disappeared. That is always the problem with isues that are not reproducible.
Kind regards, Frank.
No, not related. One of RoPieee’s apps got stuck, which in the end resulted in running out of memory. I fixed that issue (your logs were very beneficial), just trying to reason on the ‘why’ and ‘why not more often’.
Hi @spockfish
I have had again very slow reaction on the GUI. I wanted to create again a feedback, but after hours still no result. I have tried several times to create a feedback.
Finally, I was able to create it (never restarted RoPieee).
95c0bddb31c10103
Perhaps this can help you in finding the origin of the problem.
Kind regards, Frank.