Update to 4.9 fails and FGT is unresponsive

[Fyase 5]

I was contacted by the Fibaro Service Desk.

 

They are aware of these issues.

 

So I invite the guys that had issue with the update to write an email to the support team to track the case.

 

Raffaele

Edited November 26, 2021 by Fyase

[Flash 100]

Same here,

2 pinhole devices bricked.

4 devices seems to have no issue's ( still on 4.7 with failed update)

1 button device updated to 4.9, also seems to be oke.

[BOT 1]

The topic has been moved from "

Please login or register to see this link.

" to "

Please login or register to see this link.

".

 

Temat został przeniesiony z "

Please login or register to see this link.

" do "

Please login or register to see this link.

".

[Emperyan 1]

I also have one heat controller that is not responding anymore. It seems to be completely dead - not even any lights.
Is there any way to bring it back to life?

[petergebruers 1,261]

Just now, Emperyan said:

Is there any way to bring it back to life?

Not that I know of, but please do send an email to [email protected], they *may* offer you (some) remote support to diagnose and try to fix the issue. In my case, they offered remote assistance, but I am not at home and the TRVs have been disconnected, so that won't happen this weekend. Maybe next week.

[Flash 100]

Mail send to support,

Let's see what they have to say.

 

Already response.

They working on it, and try to clarify the problem. No requests for access to my HC

Edited November 26, 2021 by Flash

[Amoscaceca75 0]

Hello

Also I same problem 7 eath controller, two update 4.9 all OK one failed but works at 4.7, 4 show no signs of life
I await solutions

Edited November 26, 2021 by Amoscaceca75

[akatar 207]

You have to wait  a while, i guess

 

you can remove and add the device again (i could) but the device is unconfigured (not usable)

22 hours ago, m.roszak said:

It is blinking cyan?

It is almost impossible to cripple the device with OTA (there are redundancies implemented).

Devices won't start the update if battery is low, other than that - there are no other requirements.
Event if update was interrupted it should normally start again after second try. 
 

You have to do better then this, it is a real problem

[m.roszak 476]

We are doing better, problem is being analized and OTA was suspended.

 

I am not working on every project in Fibaro, there are a lot of them and I just cannot participate in everything

 

As for removing device when it is still in OTA procedure (blinking cyan) - yep, that may cripple the device. Please don't do this as mentioned in pinned topic on this forum.

 

We will add this to changelog and warnings before releasing the firmware again.

 

Every one affected by the issue with not responsive devices after OTA procedure please contact support ASAP.

 

[akatar 207]

11 minutes ago, m.roszak said:

 

 

I am not working on every project in Fibaro, there are a lot of them and I just cannot participate in everything

 

 

 

not? you - as most important person? are there actually things going on without youre approval??

[m.roszak 476]

Please don't be sarcastic, that is not neccesary.

[Emperyan 1]

Mine is not blinking anymore. No sign of life at all.

[Flash 100]

Hello @m.roszak

2 hours ago, m.roszak said:

Every one affected by the issue with not responsive devices after OTA procedure please contact support ASAP.

 

Did send a mail to support.  Got the feedback that they working on it. Is this enough or do the people that have a device that failed during update, and not responding anymore do something else??

Edited November 26, 2021 by Flash

[m.roszak 476]

Device is still included but blinking cyan or completly off? Do not need to respond here, support needs to know that.

[tinman 1,025]

3 hours ago, m.roszak said:

As for removing device when it is still in OTA procedure (blinking cyan) - yep, that may cripple the device. Please don't do this as mentioned in pinned topic on this forum.

 

actually with zwave engine 3 i can always exclude (S2 enabled, with wrong DSK to force no security, add, wait, wakeup again), re-include and restart firmware update (over API call), so seems to be only dangerous with zwave engine 2 to exclude/include

Edited November 26, 2021 by tinman

[akatar 207]

3 hours ago, m.roszak said:

Please don't be sarcastic, that is not neccesary.

I'm sorry sir, my deepest apologies

[m.roszak 476]

Won't comment that.

[jvdw26 0]

I updated 3 FGT with HC3, first one was successful. the other two are bricked now and not responding anymore.

I stopped updating the others. I had one bricked when I was updating to 4.7 the last time.

I going to stop with this controllers and step over to another brand. I am not happy to buy new controllers by every update.

 

I have the same advise .... DON'T UPDATE TO THIS VERSION AT THIS MOMENT

[Flash 100]

10 hours ago, m.roszak said:

Device is still included but blinking cyan or completly off?

Devices still included. No Cyan blinking or any light at all.

After soft config device, gives an succes in the message tab.

 

11 hours ago, m.roszak said:

Do not need to respond here, support needs to know that.

 Oke thank you

[Emperyan 1]

Support did not come back to me before the weekend on my dead heat controller - and I assume they won´t until Monday at least.

They told me to not do anything until they reply - but it´s getting a little warm in the house with the valve completely open all the time.....