tiktak wrote:

Sorry for the late reply. I wanted to test it thoroughly before giving a positive feedback.

 

I am happy to say that I can now connect to my A6 and M5 via Chromecast. I can play for long time and is not disconnected.

My units have been without restart for several weeks now. I do not experience the connection to the server is lost.

 

All is fine on my end. At long last. 🙂

It seems to work more stable then before, but still same firmware for Beosound as well as for Google CC version. 

It still has hickups, but less then before. 

Likewise, after the latest SW update my A6 stays connected and available in the Google Home app. The only remaining hiccup is that scheduled events (aka. "routines" in Google speak), such as streaming the news at 6am from TuneIn via Chromecast to a speaker group which includes the A6 don't always reliably happen. I think this is a Google Home problem, though, and not something B&O is to blame for.

I'm starting to think this is never going to get fully resolved... I'm also getting more & more convinced this is not a b&o but an Google issue.

Google seems be doing an extremely sh*t job with it's chromecast, even my nvidia shield is starting to have issue with chromecast now (until I reverted it back to the factory version of CC)... hell, since this year even my google chromecast audio devices, so 100% pure google devices, are having issue connecting (and I had many of them for my multiroom)

Luckily there is one extremely fine working solution, get an Ipad and stream using airplay 2, no hickups, never a failure to stop/start, perfect volume control, select what speakers should be playing your music if you have multiple airplay 2 speakers, all nicely in sync. For me personally this was a bit of a pain as I was quite anti-apple and all my devices are android but after 1 month now with the ipad I'm starting tho think I might actually replace my android phone too with an iphone.

Long story short, don't blame B&O for the failures of Google.

My A9 is also working fine again for the past couple of weeks using Chromecast and speaker groups set up in Google Home (Chromecase version 1.28.102057). For me AirPlay 2 produces a lag between the speakers sometimes after a while, which is frustrating. There is also a lag in playback, play/pause etc (due to buffering I suppose)

My Essence MK2 is also working "rather stable" now, no new firmware from B&O or GC, but it is workable now. When you change a lot during Google Home Group playback, it will stop playing in the end, but it is better then before. 

Let's hope they still will roll-out new (and more stable) firmware, since they mentioned to do that months ago! 

Although not using CC that much, CC has worked well on my Essence MK2 - when I needed it - for quite some time now.

MM

My A6 is now running stable grouped together with a Google Home speaker since the latest B&O SW update a few weeks ago. The A6 is currently running 1.25.43619.92550662 with CC version 1.28.102057. I noticed that when B&O pushed this update (from 1.25.43618), google speaker groups stopped working until I did a reset. After that reset it's been 100% stable.

I have to say it still boggles the mind that B&O seems to be unable to get their SW under control without impacting their customers in a major way. CC and Airplay are *KEY* features in their product line, touted in every add I see from them. Yet, it took 6 months from the time I bought the A6 several years ago for B&O to even enable the CC feature. And then they screwed it up again as we've witnessed over the past few months, almost crippling the products at times. Certainly not what you'd expect from a premium brand (with premium pricing to go with it).

Interesting to hear. 

My Essence MK2 updated on April 15th, from 1.25.42740.xxxx to 1.25.43618.xxxx and since then no more Google Authorization Errors in the log anymore, so that explains at least the better stability. 

Google Cast version still the same (1.28.102057)