.

Symptom: After the daily scheduled restart (not controllable by the end user), the Core can no longer join a Beolink multiroom, or be joined by other products. A manual restart clears the issue until the next daily scheduled restart

Hi

I have the same issues at random times.. i have an Eclipse, BS35, 4 cores and it happens that one of the devices is not able to join the multiroom.. it plays on itself but no way to connect it to others in the network. The only way to solve is to reboot it... I already opened a case @customercare... they want me to sent log files as soon as the problem happens. The system can working for days without any problem... but then suddenly the problem occurs... all devices have fixed IP and are hardwired except BS35. For me it looks like the multiroom software part on the faulty device has crashed and does not restart by itself. All decices are reachable via IP without any problem...

I hope this new version can solve these issues

Nico

nico vercammen wrote:

it plays on itself but no way to connect it to others in the network.

Yep, this is exactly the symptom and I’m glad to read you have the issue, while being sorry for you, as B&O claims I’m the only one to have reported it.

I managed to spot the issue in the logs, as well as by running some monitoring tools: At the end of scheduled restart process, the Core sends a remove mDNS message for the beocore service that the Beolink protocol seems to rely on, so it cannot participate correctly to Beolink network.

I managed to go back to 1.6.xxx software which does not have this issue.

What is a daily restart? I have not noticed that on my Core. Also, I have not had any problems with it joining or being joined. What do you mean by a manual restart? I looked through my settings. I have power saving unchecked. Just a thought about what might be a difference as to why I do not experience this problem.

Razlaw wrote:

What is a daily restart? I have not noticed that on my Core. Also, I have not had any problems with it joining or being joined. What do you mean by a manual restart?

Daily restart: Go to the Core configuration pages, check About, Diagnostics, Critical Events (or equivalent, I’m translating from French menu items). You may see regular daily Network State = Down

Manual restart: Go to the Core settings, Product parameters, Troubleshooting, Restart or equivalent

mbolo01 wrote:

Daily restart: Go to the Core configuration pages, check About, Diagnostics, Critical Events (or equivalent, I’m translating from French menu items). You may see regular daily Network State = Down

Manual restart: Go to the Core settings, Product parameters, Troubleshooting, Restart or equivalent

BS Moment, BS Core, BG 4002, BC 4500, BS1, BL18, BL19, BL8000 + RCV1, A6, M5, M3, A1, P6 (tks Botty), H5, TR1

I do see some Network State Down entries, most recently 2 days ago. But they have not caused me any problems. They appear to be around midnight, assuming the times indicated are local.

Under Troubleshoot there is an option to reboot. Have never noticed it and certainly have never had to use it.

Razlaw wrote:

They appear to be around midnight, assuming the times indicated are local.

They are usually appearing at the same time of the day, when the product is not used.

Login to view image

Very similar to what mine shows. However, your appears to show it every day. With my Core it does not occur daily, it is much more sporadic and never needs a manual restart/reboot.

Razlaw wrote:

Very similar to what mine shows. However, your appears to show it every day. With my Core it does not occur daily, it is much more sporadic and never needs a manual restart/reboot.

Interesting, thanks. I wonder why it's different. When looking at my Core logs, at the time the restart occurs, the process schedules the next day one. I'll ask B&O, will see if I get an answer.

mbolo01 wrote:

Interesting, thanks. I wonder why it's different. When looking at my Core logs, at the time the restart occurs, the process schedules the next day one. I'll ask B&O, will see if I get an answer.

BS Moment, BS Core, BG 4002, BC 4500, BS1, BL18, BL19, BL8000 + RCV1, A6, M5, M3, A1, P6 (tks Botty), H5, TR1

mine does only show 2 critical events. One about Spotify and one about Soundwall.

I am glad to have learned of this feature. Now I can play the same music, in sync through a Core in one room, an Essence in another, a Beoplay V1 in a third room, and Apple TV’s connected to a Beovision 10 and a 20 year old Beovision Avant 32 in two other rooms.