[HAWK]

Rolf2 wrote:

For my Essence MK II an update was in the app this evening and it is now on 2.1.50867. I do not know what the update has changed. Although I have the „automatic update“ function enabled, I had to trigger it manually. I will keep an eye on it. Beosound 2 updated as described in previous post to 2.1.50871. Emerge is still on 1.8.10017.

 

My Essence MKII also upgraded to 2.1.50867, so good news.
What puzzles me, however, is that the Google Cast firmware still is on 1.44.xxx. And the problem is that the Essence in this way can NOT be used as part of a Google Home Speaker group.

For this to work, at least Google Cast 1.52.xxx is needed, did found this out because my Harman Kardon speakers had the same problem, but after upgrading the Google cast version, not anymore, see https://www.googlenestcommunity.com/t5/Speakers-and-Displays/Group-speakers-casting-not-working-with-Harman-Kardon-Citation-One/m-p/227131#M42984 .

The strange thing is that for the Beosound Core, this Google cast update to 1.52.xxx was already done early 2022, together with fw 2.0.4793 (see https://support.bang-olufsen.com/hc/en-us/articles/4419765148689-Software-release-notes)., but for the Essence MKII, this 2.0.4793 with the right 1.52.xxx Google cast version, was never released (see https://support.bang-olufsen.com/hc/en-us/articles/4419756669585 , btw: Oct 2021 seems wrong, must be Oct 2022?).

Let’s hope the Google Cast update for our Essence MKII will follow soon too!

• This reply was modified 3 weeks, 2 days ago by HAWK.
• This reply was modified 3 weeks, 2 days ago by HAWK.

[HAWK]

PS1: don’t know if this is the right thread, but I was following this thread very actively on the “old” forum (under the same username) and can not find any continuation for this): https://archivedforum2.beoworld.org/forums/p/45567/338558.aspx#338558

PS2: why a new forum with 2 archives and different credentials, etc? Ok, that question is certainly in the wrong thread here 😎

• This reply was modified 3 weeks, 2 days ago by HAWK.

[Rolf2]

@HAWK

I am not using chromecast, though it shows as „enabled“. My sw version is 1.28.102057, so, far behind what seems to be the latest version. I cannot help here, sorry.

Kind regards,

Rolf

[HAWK]

Rolf2 wrote:

@HAWK

I am not using chromecast, though it shows as „enabled“. My sw version is 1.28.102057, so, far behind what seems to be the latest version. I cannot help here, sorry.

Kind regards,

Rolf

Thx, my mistake: my HK speaker had cast version 1.44.xxxx, the Beosound Essence MKII has cast version 1.28.102057 for me too. There is an B&O update to 1.52.xxx apparantly (e.g. for the Core), but apparantly not (yet) for the Essence MKII…..

[ebnrob]

HAWK wrote:

but apparantly not (yet) for the Essence MKII

B&O have told me they can’t update Chromecast in the M5 and Essence Mk2. This is what they said to me:

“Our technical department would like to inform you that the hardware of Beoplay M5 does not support the requirements from Google and this is not a Bang & Olufsen’s decision, but part of new requirements from Google.”

Their suggestion was to buy a Chromecast audio dongle and connect it to line in. I’ve just bought a Wiim Pro streamer which has a built in Alexa receiver as well as chromecast which I’ve connected to my M5’s line-in. Works well.

• This reply was modified 6 days, 6 hours ago by ebnrob.

[ebnrob]

Tignum wrote:

After some friendly e-mail exchange I received this answer: “We are pleased to inform you that yes it will be fixed in a future software update regarding the issue; the issue has been reported to the Product Development team, and they will provide a software update as soon as possible.”

B&O have pushed an update to my Cores and M5 that addresses this issue with number key presses not being relayed to joined speakers or masterlink. The software version is 2.1.51691. No update to the a9 Mk4 yet.

[Millemissen]

@ebnrob
‘number key presses not being relayed to joined speakers or masterlink’

Could you please explain what that means – an example would be helpfull.

MM

[ebnrob]

Millemissen wrote:

@ebnrob ‘number key presses not being relayed to joined speakers or masterlink’ Could you please explain what that means – an example would be helpfull. MM

Hi MM, this was the problem I had which is now fixed in the newest firmware v2.1.51691:

I’ve discovered that I cannot use the number pad in a link room after joining. For example, if  TuneIn is playing on my M5 and I join my A9 mk4 to it, I can’t select presets using the number pad on the BR1 (BT) in the link room. This also means I can’t select the CD playing, or directly change FM radio station on my BS9000 via the NL/ML converter. I’m not sure if it’s an issue with the BR1 that’s also received a Firmware update, or the speakers.

[HAWK]

ebnrob wrote:

HAWK wrote:

but apparantly not (yet) for the Essence MKII

B&O have told me they can’t update Chromecast in the M5 and Essence Mk2. This is what they said to me: “Our technical department would like to inform you that the hardware of Beoplay M5 does not support the requirements from Google and this is not a Bang & Olufsen’s decision, but part of new requirements from Google.” Their suggestion was to buy a Chromecast audio dongle and connect it to line in. I’ve just bought a Wiim Pro streamer which has a built in Alexa receiver as well as chromecast which I’ve connected to my M5’s line-in. Works well.

Thx for the heads up. You mention the M5 AND the Essence MK2, so also the Essence Mk2 does not support the requirements from Google?

Let’s see if I can connect a Chromecast to the line-in of the Essence Mk2 then (no idea if this is even possible).

[Millemissen]

Just tried casting to one of my Essence MK2’s.

This did not work and kind of locked the Essence – it became unresponsive and showed as offline.
Before I managed to get to the power cable, it rebootet itself.

Chromecast version is 1.28.102057/sw of device is 2.1.50867.
It seems it does not support CC anymore.

Luckily I hardly ever use CC for audio, so not a big deal.
However, I have a CC Audio dongle somewhere, which I could connect to the line-in.

MM

[ebnrob]

HAWK wrote:

so also the Essence Mk2 does not support the requirements from Google?

Hi Hawk,

Yes the reply from B&O was in relation to my M5, however they both share the same hardware platform.

The line-in on the essence should auto detect the signal from whatever’s connected, switch the speakers on and change the source to line-in, in the same way the M5 does.

[Millemissen]

ebnrob wrote:

Millemissen wrote:

@ebnrob ‘number key presses not being relayed to joined speakers or masterlink’ Could you please explain what that means – an example would be helpfull. MM

Hi MM, this was the problem I had which is now fixed in the newest firmware v2.1.51691:

I’ve discovered that I cannot use the number pad in a link room after joining. For example, if TuneIn is playing on my M5 and I join my A9 mk4 to it, I can’t select presets using the number pad on the BR1 (BT) in the link room. This also means I can’t select the CD playing, or directly change FM radio station on my BS9000 via the NL/ML converter. I’m not sure if it’s an issue with the BR1 that’s also received a Firmware update, or the speakers.

Thanks for explaining.
I haven’t noticed anything of that kind with my Essence – maybe this is because my user behaviour is different?

I have – as of today – an M5, which I haven’t set up yet……wonder which version that will have.
Usually both devices have the same SW, or?

The firmware of all my Essences is lower than what you mention for the M5.
I wonder if the Essence will be updated too – but maybe only the M5 was affected (which is unlikely).

MM

[Author]

Posts