Spotify web player in moOde local display

[Ale2.0]

@Ale2.0

From your question in the "Upcoming moOde 8.2.3 release" thread, I inferred you are trying to run the Spotify web player (https://open.spotify.com) in the moOde local display (which uses chromium-browser). If my inference is wrong, then this message is just a typing test.

Out of curiosity, I tried reaching the Spotify web player using Raspberry Pi OS on my Pi400. It works fine and can stream to the Spotify renderer on any of my moOde players. This is with chromium-browser 104.0.5112.105, same as the version installed in moOde.

Then, on a moOde player with a LCD display, I hacked /home/pi/.xinitrc to start chromium-browser at https://open.spotify.com. The expected first page showed up and I proceeded to log into my premium account [1]. Oops, instead of the Spotify home screen, I get a "Playback of protected content is not allowed" screen. I did a little digging on the InterWeb™ and figured out that the desktop version of RaspiOS installs library libwidevinecdm.so but the lite version does not.

I just needed to run the following on my moOde player

Code:

sudo apt-get install libwidevinecdm0

and restart the local UI.

Now I can log into my Spotify account, select a playlist, direct the stream to the Spotify renderer running on the same or other player, and listen.

At this point, however, the wheels came off the wagon: the interface became unusable (IMHO) as I tried to look for other selections. I won't go into details; you can explore for yourself. 

To add insult to injury, the app even forgets my login credentials despite me choosing "remember me". Admittedly, I didn't explore why this difference with the desktop version of RaspiOS.

At this point I'm done since I'm not interested in this use case personally. Perhaps with some more poking you can make it work for you.

Regards,
Kent

[1] I plugged in a USB keyboard to use in logging in.

Ciao Kent

Thank you very much for sharing your experiences!

I did the same but never came over the warning...
It is not quite logical to me but may the cause be that I am using an RPI3?

I yet don't want to belive it but it seems the most logical answer to me.

Thank you very much.