Very strange.........my Essence MK2 (GC v1.28) was working around 17:00 (CET), did not notice any problem, but now it seems to have stopped working around 19:00 (CET). Did a reboot again now (around midnight CET), and all is working again now. No connection errors anymore.

Did check the critical log file, and strangely the last few days, every time around 18:00/19:00 CET the GC Authentication error is there, not on other times.

Does the GC server has a dinner break or so around that time? 😕

Let's see if the same thing happens tomorrow, and there is a pattern........given the above messages of other people, it seems time related. Please check the log if it indeed happens around the same time every day.

stampfki wrote:

BTW: are the products with GVA working? Have those been updated to Chromecast >1.28?

My Beosound 1 GVA has Chromecast-version 1.44.219548

HAWK wrote:

Very strange.........my Essence MK2 (GC v1.28) was working around 17:00 (CET), did not notice any problem, but now it seems to have stopped working around 19:00 (CET). Did a reboot again now (around midnight CET), and all is working again now. No connection errors anymore.

Did check the critical log file, and strangely the last few days, every time around 18:00/19:00 CET the GC Authentication error is there, not on other times.

Does the GC server has a dinner break or so around that time? 😕

Let's see if the same thing happens tomorrow, and there is a pattern........given the above messages of other people, it seems time related. Please check the log if it indeed happens around the same time every day.

It works just now and every time I tested today. With limitations. Because strangely the BS2 played with the Qobuz app via Chromecast only stuttering, I have no idea why.
Switched to Roon, network the same, it worked fine and without stuttering, see last screenshot ....?

My 3 devices tend to check around 3, 9 and 13, but it's not "clockwork" (varies +/- 30 minutes,  and not every day).  These times are CST (Chicago)

Also, one of my devices hasn't checked for 2 days (and is unreachable by CC, but works fine with NL), and another failed 30-ish minutes ago, but recently showed again in Google Home.

HAWK wrote:

Very strange.........my Essence MK2 (GC v1.28) was working around 17:00 (CET), did not notice any problem, but now it seems to have stopped working around 19:00 (CET). Did a reboot again now (around midnight CET), and all is working again now. No connection errors anymore.

Did check the critical log file, and strangely the last few days, every time around 18:00/19:00 CET the GC Authentication error is there, not on other times.

Does the GC server has a dinner break or so around that time? 😕

Let's see if the same thing happens tomorrow, and there is a pattern........given the above messages of other people, it seems time related. Please check the log if it indeed happens around the same time every day.

Did some more testing today, and GC worked flawlessly and continously from morning until afternoon ...........but at 17:37 (CET, that is 10:37am CST in Chicago) it stopped working. Again GC Authentication failure. Now, 2 hours later, still no luck (also not aftter reboot). Will check it again in a few hours. 

The B&O app keeps working, so it is really a Chromecast issue, that appears to happen daily. 

And indeed, around midnight CET it worked again. Rebooting without the GC error and streaming as it should be. 

So the GC error only in appeared here from 17:37 until max midnight... Maybe a Google server goes down and is rebooted after a few hours when noticed?

HAWK wrote:

And indeed, around midnight CET it worked again. Rebooting without the GC error and streaming as it should be. 

So the GC error only in appeared here from 17:37 until max midnight... Maybe a Google server goes down and is rebooted after a few hours when noticed?

This hypothesis should be easy to verify - I remember that you have other Chromecast built-in speakers from another brand. If it's true, GC shouldn't work with them at this time either?

Ulrike wrote:

This hypothesis should be easy to verify - I remember that you have other Chromecast built-in speakers from another brand. If it's true, GC shouldn't work with them at this time either?

Good point! My other brand Chromecast devises keep working (day and night :)) , but they all run GC v1.44 or newer, so it might be that the reroute "older" GC v1.28 devices to a different server?

Have you ever tried to contact Google support? They should be able to answer that. I called them on January 24 and was told that the firmware on the affected devices had apparently expired, that the manufacturer would have to update it, and that all the problems were related to firmware that was no longer up to date. In any case, the number I was called back from is this: 0016504179099

However, it is possible that this is no longer valid and that you have to create a new Google support ticket.

Just an idea to rule out other possible causes:
You could try to change the DNS servers in your router settings. Usually found under Network Settings =》DHCP
If you use the DNS servers of your internet service provider, it is possible that their DNS servers are overloaded at times, especially in the evenings during peak hours. Doesn't happen that rarely.
You could try
8.8.8.8 (Google DNS)
And as a second, substitute in case of overload
1.1.1.1 (Cloudflare DNS)
Maybe it helps?