HAWK wrote:

Ok, yesterday it did work all day, but today at 18:04 (CET) it stopped working again (despite the new DNS servers in my router). At 19:30 it worked for a few minutes, but now (19:42) it stopped working again. 

Totally unpredictable behaviour.........I give up and enjoy my Harman Kardon (Citation Towers, great speakers by the way!).

So for me in Germany all devices from different manufacturers work without problems.
For my BS2 mk1, the Chromecast version is still the same as yours and it works here at any time of day completely without issues ...?
@HAWK
Just one last idea if you still feel like trying (since you have other good speakers :))
1.
I also had DHCP disabled in the B&O app and gave my BS2 a static IP (outside my routers DHCP range!), see screenshot below, and changed the DNS server.
Whether that also makes an improvement in this case, I do not know.
2.
If this is not too cumbersome and annoying in your case, you could try a daily reboot of your router.
Or better just a reconnect.
If your router, like my Fritzbox, offers this possibility. With a reconnect you get a new IP address in seconds and this solves various kinds of problems. I can well imagine that it also would help in this case.
But if not, then I'm out of ideas and can't think of anything else to try :)

I can confirm my A5 and M5 are also not working with CG. Both speakers states in critical events: "Authentication server unreachable, stopping Google Cast".

I still have version 1.24.41.628 on my M5. It states that this is the newest version. Strange that one user could upgrade to 1.25. I have tried restaring the M5 several times to force it to look for an update. No success.

I wrote with B&O support yesterday. I was told a software fix was being worked on but they could not provide an expected release.

@Ulrike: I know how to give my products a static IP. But you wrote something about giving an IP outside the routers DHCP range. How is this done? How do I know my routers DHCP range? Can you help clarify?

Best regards

Ulrike wrote:

HAWK wrote:

Ok, yesterday it did work all day, but today at 18:04 (CET) it stopped working again (despite the new DNS servers in my router). At 19:30 it worked for a few minutes, but now (19:42) it stopped working again. 

Totally unpredictable behaviour.........I give up and enjoy my Harman Kardon (Citation Towers, great speakers by the way!).

For my BS2 mk1, the Chromecast version is still the same as yours and it works here at any time of day completely without issues ...?
@HAWK
Just one last idea if you still feel like trying (since you have other good speakers :))
1.
I also had DHCP disabled in the B&O app and gave my BS2 a static IP (outside my routers DHCP range!), see screenshot below, and changed the DNS server.
Whether that also makes an improvement in this case, I do not know.
2.
If this is not too cumbersome and annoying in your case, you could try a daily reboot of your router.
Or better just a reconnect.
If your router, like my Fritzbox, offers this possibility. With a reconnect you get a new IP address in seconds and this solves various kinds of problems. I can well imagine that it also would help in this case.
But if not, then I'm out of ideas and can't think of anything else to try :)

Thx again @Ulrike. I have a Fritz!Box too, and it is not so complicated to try this, I will do later today. 

@Tiktak: normally your router provides internal IP numbers, for example in the range 192.168.1.10 until 192.168.1.200, you can then decide to give your B&O device a fixed address outside this range, e.g. 192.168.1.201 (max range is between 1 and 255, but normally these lower and higher numbers are already reserved for other/network devices, gateways, etc). If you don't know how to do this, better be careful and ask some one who knows about this. 

tiktak wrote:

@Ulrike: I know how to give my products a static IP. But you wrote something about giving an IP outside the routers DHCP range. How is this done? How do I know my routers DHCP range? Can you help clarify?

Best regards

Usually under Network Settings/ Home Network/ IPv4 Settings. In my case the DHCP range is from 20 to 200, this is usually the default setting.

And here is how to reconnect instead of rebooting:

Ok, I followed Ulrike his suggestions, so I gave the B&O device a fixed IP address (out of the DHCP range) AND also reconnect my router. Since my provider gives customers a (semi) fixed external IP address, my external IP address did not change, but ok, just to be sure. 

The GC started to work correctly, as before, but since 17:55 (CET) it gave the same error again. 

Did a reboot (again) and now it works again....but for how long?

Ok, it seems more than (only) an IP/addressing issue, and let's wait for the upcoming new (GC) firmware, as tiktak wrote that B&O support is been working on.

Short update: less than half an hour, at 18:29 (CET), it stopped working again, same error. 

Since I mainly stream to multiple speakers, using Google Home (Groups) it is very annoying, but ok. I stop testing now, and will use the B&O app in the mean time, and GC for the other speakers. 

Update from B&O support:

I just received an email stating that they are "constantly working om a solution to ensure Chromecast is working again. B&O is working with Google to fix the issue.The problem is due to a server error."

No information regarding a timeframe for update.

stampfki wrote:

Hi, particularly my M5 keeps bothering me. it’s Running on the latest Firmware 1.24 and out of the blue it suddenly makes trouble. 

link

 

any idea why it’s not showing its serial ID and the system tells about failed software update?

Additionally it has been also disappeared from the Google app as chrome cast device.

 

Really frustrated here...

Br from Germany :)

Did reset the M5 and keep trying to pair it to the IOS B&O app. But it simply does not appear there. As Bluetooth device I can see and pair it, but it’s showed with serial no 00000 as part of the default Bluetooth name. Usually it shows up as BeoplayM5-serial no. Any ideas? It’s on firmware 1.24 and I haven’t initiated any update, which hasn’t been offered anyway.