Nick Steel
Nick Steel
Fair enough. Just to confirm and for anyone else that finds themselves here * @dbischof90 had * Cross-compiled for armv7 using gcc-arm-linux-gnueabihf (v10.2.1 from Bullseye) * Running natively on Bullseye...
> That factor should go away if I use a Bookworm base image on Docker, right I have no idea!
I'm not sure I totally understand what has happened to you here (what is moped??) but there is an issue right now which essentially means username and password login is...
No response and we already have issues tracking the auth changes.
I've had this a couple of times but when I try and track it down, it magically resolves itself after a while. So my current theory is that it's some...
Actually, in this case, I'm not sure why the error doesn't propagate through to Mopidy logging given it's coming through as a gstreamer Error, which we are setup to catch....
There's currently a device and user specific librespot issue. Every implementation is suffering from it. It appears Spotify are rolling out a change to their protocol
See https://github.com/librespot-org/librespot/issues/1308
Providing the username in your mopidy.conf matches the username in the credentials.json then the credentials.json takes priority over any supplied password. Some types of Spotify account get unexpected usernames in...
`GST_DEBUG=3,*spotify:6*` should do it EDIT: or maybe `,*spotify:7*` ?