Release 2025.10.1

Hi,

A quick patch release for the UPnP regression is out there…

Release Notes
Changelog

Enjoy the weekend!

7 Likes

Works fine on my side…. Many thx Harry

Question: would it be possible to have Lossless for Spotify in the next release, as I could see on LibreSpot’s GitHub that aac_24 is now supported apparently?

AAC is a lossy file type …

Nope. Or to be more precisely: the fact that en external project has a new release and/or implemented a new feature, does not automatically mean that it will be in the next RoPieee release. It could be that additional configuration work is required, for example.

And in this case specifically: lossless is not done, and it is going to take some more time. The fact that Librespot is now technically capable of doing AAC24 does not mean it’s capable of doing Spotify AAC24 (it’s not).

It’s done when it’s done :wink:

3 Likes

No worries, as there is no hurry … many thx in any case for this already great piece of software which is RoPieee

2 Likes

Hi Harry,

It is me again :), I have been using 2025.10.1 from beta for a few days and I am using mConnect Lite to access Qobuz thru UPnP to play music. From time to time I received a notification from mConnect saying “Device sent an error response.” This notification is very random.

I have submitted a feedback #22fde8f1390afb4f. Could you take a look when you have a minute to see whether that is my problem or not. You have a nice weekend. Many thanks!

Alfred

I see a lot of low-level error(s) during communication with your HAT (Audiophonics).
That causes the device errors.

Thanks

Hi,
Spotify stopped working on stable version, same as a while back will show sort of progress bar but won’t play anything. I switched to beta version and have 2844 running now, still not working.
I send a feedback file 8ffe83c1fd516b49
Hope the feedback file can shed some light on it.

Regards!

Same here Spotify connect has broken on this stable build 2025.10.1 feedback sent 4d3930fab55aa159 Spotify is just skipping through tracks.

Regards

1 Like

Looks like it’s been reported on over at Librespots github page "Looks like Spotify changed something again on their servers and is causing librespot to stop playing tracks. I can successfully connect but tracks do not play. On initial connect there is a log that indicates setup of state failed: invalid state and a 400 bad request with the message that the client specified an invalid argument. Skipping to the next track causes librespot to fail with continuous Track should be available, but no alternatives found

Appears that Spotify’s servers made some breaking changes to their API."

1 Like

Yeah, unfortunately Spotify broke their API’s again :-1:

I’ll monitor this closely: [Bug]: Spotify doesn't play anymore · Issue #26 · RoPieee/RoPieee · GitHub

1 Like