Maybe you could tell that to BangOlufsen on their twitter feed too.

I am trying e.g. on https://twitter.com/stephane_barbey/status/1368186427255701510?s=20https://twitter.com/stephane_barbey/status/1368186427255701510?s=20https://twitter.com/stephane_barbey/status/1368186427255701510?s=20https://twitter.com/stephane_barbey/status/1368186427255701510?s=20https://twitter.com/stephane_barbey/status/1368186427255701510?s=20hhthttps://twitter.com/stephane_barbey/status/1368186427255701510?s=20tps://twitter.com/stephane_barbey/status/1368186427255701510?s=20ttps https://twitter.com/stephane_barbey/status/1368186427255701510?s=20//twitter.com/stephane_barbey/status/1368186427255701510?s=20

Stan wrote:

Interesting. I don't have an M5, but my Essences have been more stable since the most recent update. My M3 has always been stable.

If you go to B&W good luck, and I hope it works out. Personally, I think chromecast is just unstable in general. Up until my B&O devices started flaking out over the last few months, my Google chromecast audio was, by far, my least reliable chromecast device (so unreliable that my wife has given up even trying to use it). Granted, it only cost $40, but if Google can't even get their own devices to work reliably, what chance do 3rd parties have?

I can also confirm that on M5 and A6 the new software update (1.25.74x) does not fix the Chromecast issue. After restart the speaker can connect to Chromecast for some hours before the server connection error reappears.

I would like to encourage everybody who are experiencing this problem to write a short description of the problem to B&O Support. If nothing else to force them to acknowledge that we are a flock of frustrated customers

Keeping my fingers crossed for a fix between Google servers and B&O but my hopes are running low.

I've received somewhat hopeful news from support concerning this issue, a solution might be near:

Louis (Bang & Olufsen)

Mar 7, 2021, 16:46 GMT+1

duplicate

Thx, that's hopeful. 

With the latest fw upgrade it is little more stable, but still no really doable, so let's wait for the GC upgrade. 

Not sure if it is because I didn't notice it before, I doubt, but since product updates I find that the volume level starts from 0 to the current value progressively when changing from one source to another ,where before the newly selected source was straight at the current volume level. Same when starting a source when product is previously in standby.

mbolo01 wrote:

Not sure if it is because I didn't notice it before, I doubt, but since product updates I find that the volume level starts from 0 to the current value progressively when changing from one source to another ,where before the newly selected source was straight at the current volume level. Same when starting a source when product is previously in standby.

Hmmm.... have not noticed that...