Interaction between Spotify App and Bluos App on Andriod please explain
AnsweredI have multiple Bluesound speakers. To simplify there are an upstairs stereo pair and a downstairs stereo pair.
I opened the Bluos App on Andriod, made sure the upstairs stereo pair was working. Opened Spotify and selected the Upstairs stereo as source then started music on the upstairs stereo. I noticed the Bluos App had music playing from Spotify. Everything OK.
I went downstairs and turned on the downstairs stereo pair, went to Spotify and selected the downstairs stereo pair and music was playing from them. I noticed that music was also still playing on the upstairs stereo even though in Spotify I unselected it in favour of downstairs. I changed the song for the downstairs pair, then found that the downstairs pair was playing a different song than the upstairs pair. I turned off the downstairs pair and I closed down Spotify and found that the Bluos App was still playing on the upstairs pair.
This means that the Bluos App is cacheing or downloading the Spotify playlist ?
Can you please explain the relationship between Spotify and Bluos ?
In particular how Bluos calls / interacts with Spotify. Which has control etc. This will assist in me understanding what is happening when I change sources.
Also, is the interaction the same on Windows ?
-
Official comment
When using Spotify, all interactions are controlled using the Spotify App as all BluOS Players are independent Spotify Connect end-points. Once started, the stream is not re-directed via your phone, it is actually reassociated from your phone to the BluOS Player.
For more details, see Spotify's own KB on how Spotify Connect works; https://support.spotify.com/ca-en/article/spotify-connect/
-
Tony, thank you for pointing me to the Spotify Connect page from which I now understand the server based Spotify connectivity syncing the phone and windows etc, allowing each in time to control.
The Bluos App then acts as switch between sources, Spotify, TuneIn, etc etc, displaying at the bottom of the screen what is currently playing. It also acts as a Queuing system from multiple sources. Bluos is also server based since PC and Phone can both be running at the same time.
Synchronization between Spotify clients (Phone and PC) and Bluos (Phone and PC) clients can take some time so it could be the case that downstairs and upstairs were running different songs was due to synchronisation.
Could you please expand on this statement "all BluOS Players are independent Spotify Connect end-points"
It seems from my configuration that the Bluos devices (nodes/cards and speakers) store it's own device configuration i.e. Name, IP, Power etc internally, which can be viewed and modified by the http page.
The bluos app then stores stereo pairs and what else in relation to the expected names/ip address of node/speakers ?
I now have 8 speakers, set into 4 stereo pairs, these speakers will switch between two networks, each of which has one node/card interfacing a traditional passive speaker system so it would be helpful to know what the speakers/nodes and the bluos app each know and what order the information is used, for example, does the speaker promote itself to the network/Bluos app, or does the Bluos app search the network for expected devices. This will help in deciding whether a reboot of the speaker, clearing the cache/data of the android app or resetting the speaker is the correct action to take when speakers/nodes are not found.
0
Please sign in to leave a comment.
Comments
2 comments