Home Center 3 fail to update and end up in recovery mode.

[JohanJD 2]

While trying to update from the Fibaro Home Center 3 interface the system crashes and runs into recovery mode. This was already in previous beta from which i waited to upgrade. With the zigbee addition i really want to update. 

 

I am currently on 5.100.22 and want to update to 5.102.23 (beta). I select cloud backup and do the update as i did many times already. Anybody else having issues with this? 

 

Thanks in advance. 

[Tomislav Barbarić 1]

+1

 

Please login or register to see this image.

/monthly_2022_04/image.png.6d4bee8723dc8b32d2fe87fa8a043354.png" />

[Poom 7]

Anyone who has master slave setup update this firmware version?  Did the update get through or error?  Please let me know.

 

[Tony270570 107]

@Poom i do have master/slave and the update went well. For some reasons (initial issues... )  i use to update machine per machine I don't use the update all at once option.

@JohanJD I add the at the first update but after a repair/re update it went well. You can try if you wish to. Don't forget to backup first.

[JohanJD 2]

@Tony270570 i have done the second update now. It is starting services for 10 minutes already. I don't think it will go well. I only have one device, no master/slave setup. 

[Tony270570 107]

It tooks me a few minutes on starting services as well, if it doesn't work the better thing to do will be to contact the support, they will be able to help understanding the issue and fix it.

 

[m.roszak 763]

We would like to arrange some debugging, we can do this here (just PM me for details) or you can go with support.

[Manech 0]

hello i need your help, since the previous beta, impossible to restart the box after the updates, rebooting, then starting services in a loop.
  After 30 minutes, 1 hour the safe mode (in red) appears and offers me a repair in the previous non-beta version.
I tried at least 15 times, restarted the box manually, but nothing worked.

[m.roszak 763]

We are preparing a small fix for that.
It will be resolved soon.

[JohanJD 2]

On 4/8/2022 at 6:48 PM, m.roszak said:

We would like to arrange some debugging, we can do this here (just PM me for details) or you can go with support.

Thank you for the help. Unfortunately i am on holiday now and will return next monday. I will reach out to you than, is that okay? I have exactly the same situation as Manech, so if a fix is available before my return i will try that first of course. 

Edited April 13, 2022 by JohanJD

[Poom 7]

On 4/11/2022 at 7:51 PM, m.roszak said:

We are preparing a small fix for that.
It will be resolved soon.

@m.roszak  Should I wait until this small fix is released?  Or should I go ahead and update my system using the current firmware release?

[m.roszak 763]

We are still working on it, with the help of Manech. We can't reproduce this on our side, the best way is to wait a bit.

 

I will let you know after diagnose if this is something specific to Manech system or this can occur elsewere.

[Poom 7]

@m.roszak I see Fibaro just release the new firmware 5.110.15.  Is it safe for me to start update the system or should I wait a bit more.

[m.roszak 763]

It should be safe as we did fixed the issue mentioned here.

 

Regards,

Michał

[Manech 0]

Hi Michal, were you able to spot the problem on my configuration and create the patches for other customers? do I need to extend remote access. if yes no problem if it can help you.
could you send this information Device  to the zigbee/fibaro developer service to see if it is possible to integrate it because it is a very useful zigbee device that allows you to connect to the electricity meter. Please and thanks. Manech 

 

Please login or register to see this image.

[m.roszak 763]

We found the issue and fixed it

[Manech 0]

Thanks ????

[Poom 7]

@m.roszak The new update went smoothly.  Thank you.

[Maths 1]

Hello,

 

@m.roszak How to update version without interface access ?

Edited April 15, 2022 by Maths

[m.roszak 763]

From the user point od view access to web interface locally is neccessary for safety reasons to perform the update.