Edit

Edit

Hi,

the rollout are started in the nordic countrys first , then after that rest of the world

will beosound edge get Spotify connect as well?

Beouser66 wrote:

Hi,

the rollout are started in the nordic countrys first , then after that rest of the world

That seems to be the reason.

However, one may wonder why the support was not able to provide me with that information (there were three guys involved in my request).

And also - it would be nice, if we could have a scedule for the roll-out.

By the way - if you go to the german part of the B&O website, you will find exactly the same information on use and opdating of the M3 in order to have Spotify Connect there as on the danish part of the site……despite the fact that the update is not rolled out in Germany (yet).

MM

A6, M3's, Harmony just updated.

the Netherlands

11 of my speakers/TVs including Harmony, A9, BS1 and BS2 updated this morning here in the US.

Carolpa wrote:

A6, M3's, Harmony just updated.

the Netherlands

Thanks - I had a look at mine (in the app) - lo and behold....also available now - and downloading.....and success!

I am on a german ip here.

Thank you B&O 🙂

MM

BeoSound 1 2nd.gen (non-GVA, North America) updated from: 1.11.45905   to: 1.12.47108

Spotify Connect is working.  Note: You might have to exit the Spotify application and restart it to force it to scan for devices.  Should be automatic, but it didn't discover my BS1/2gen/non-GVA/1.12 until I quit.  

As expected & reported, my 1.7 BS1 (as an example) cannot be joined to my 1.12 BS1 while the latter is playing via Spotify Connect -- doesn't even show up in the B&O App's list -- but it can be joined while playing from the DLNA server.  Whether this is the B&O App being "smart" to prevent it, or some underlying "feature" of Spotify Connect protocol interaction is unknowable for mere mortals, but I confirm the rule stated that the speaker joining must also have Spotify Connect support is true, or "enforced", or whatever.

---> The bug where DLNA playback does not update the counter from 0:00 is still (¡STILL!) not fixed.  (Since 1.7.  That's at least 3 versions now...)

Minor app bug: Product Settings/About still reports the old 1.11 software version #, even though Product Settings/Software shows the new 1.12 version #.  App must be storing it somewhere, because the device's webserver reports the correct new # too.