Spotify Connect Gremlins for a Couple of Weeks?

[Er00]

Plan

Premium

Country

United Kingdom

Device

Controlling devices: Windows 10, Android

Receiving devices: Facebook Portal, Arylic receiver

My Question or Issue

I switched back to Spotify a year or so ago after being forcibly migrated from Google Play Music to YouTube Music and giving it a fair shot, and for the last 6+ months I've been using Spotify Connect fairly successfully to play music on my Facebook Portal (on an almost daily basis). 

However, for the last few weeks (perhaps since the big outage?) there have been oddities:

• Sometimes when controlling from my Android device it gets desynced and the controlling device and receiving device think they're playing different conten. Often when the above happens, I then start to be unable to connect using Spotify Connect
• Reconnecting to the playing device when it is possible does bring the controlling device back in line with what the receiving device thinks is playing
• I can no longer play specific songs using Spotify Connect controlled from my Windows PC (just get the "Spotify can't play this right now." warning), instead I can only play a playlist
• Often the receiving device just starts playing a seemingly random assortment of songs (ie a "radio" type auto playlist, not the thing I've selected to play, nor one of my other common playlists or anything)

Is this something others have been experiencing? Is there any way to to mitigate these issues or at least work around them? It's making me greatly reconsider my "Spotify Connect is really great, we should totally use that instead of <insert other tech here> for setting up our new house", I have genuinely gone from loving this feature to being frustrated by it on a daily basis and I'd like to go back!

[dinomight]

Hey there @Er00,

Thanks for reporting your issues with Spotify Connect on this device. While I'm not certain at the moment of the extent of any possible issues with Connect, there is an ongoing thread on this page related specifically to Samsung speakers, and I'm wondering if this might be becoming a more widespread issue. Unfortunately, I don't have a workaround at the moment, but I'm hoping this will be resolved before long. We'll be keeping an eye on the community for further issues, and I will pass these threads to the right people who can look into what might be occurring.