The system recovered from an unexpected error 😤

[Sjekke 85]

I regularly get this error and I always have to get my HC3 off the electricity to restart.
 

• How can I see what this error causes?
• Can the device not restart itself?
• What if I'm on vacation?

 

Until today, my HC2 turned out to be much more reliable than my HC3.

Every help is appreciated.

Please login or register to see this attachment.

[petergebruers 1,261]

On 2/1/2023 at 8:01 PM, m.roszak said:

We are now investing new promising lead, as soon we will have an ultimate fix I will let you know.

 

They have fixed an issue with their OS a while ago and my HC3, now running 5.132.9, no longer reboots with that error. Unfortunately we have to conclude, based on reports like yours, there is another, possibly separate issue with the OS. Fibaro is investigating this second issue but has not reported back yet.

 

1 hour ago, Sjekke said:

Can the device not restart itself?

AFAIK all users reported that they did not notice the reboots because the reboots are infrequent (meaning: once every X days) and if it happens when you sleep, you won't notice. This makes me think that all other users have seen an "automatic reboot" - which IMHO is built into the HC3 firmware, there is nothing to configure.

 

A recovery from such an event can take very long, 20 to 60 minutes. Did you wait that long?

[Sjekke 85]

15 minutes ago, petergebruers said:

 

They have fixed an issue with their OS a while ago and my HC3, now running 5.132.9, no longer reboots with that error. Unfortunately we have to conclude, based on reports like yours, there is another, possibly separate issue with the OS. Fibaro is investigating this second issue but has not reported back yet.

 

 

This occurred on 5.131.57 (but I had it even before that). In the meanwhile I moved to 5.132.9

 

41 minutes ago, petergebruers said:

AFAIK all users reported that they did not notice the reboots because the reboots are infrequent (meaning: once every X days) and if it happens when you sleep, you won't notice. This makes me think that all other users have seen an "automatic reboot" - which IMHO is built into the HC3 firmware, there is nothing to configure

 

The previous times I had this error (older firmware) the HC3 restarted automatically.

 

43 minutes ago, petergebruers said:

A recovery from such an event can take very long, 20 to 60 minutes. Did you wait that long?

 

I did.

 

I hope the new 5.132.9 resolves this problem.

[m.roszak 478]

@Sjekke

It should restart itself as Peter wrote.

I will contact you tomorrow on PM.

[Lode 18]

@m.roszak I have the same problem.

Please login or register to see this attachment.

[Kage 36]

i also have this. Mostly between 00:00 and 03:00. it recovered itself but my scenes that are automatically doesn't start the are infect enabled. In the api scene there is also nothing to see if it is still running only when it "started".

 

The isRunning and enabled are the same thing. woud be nicer if isRunning means if the scene is running in a setTimeOut. So you know is the scene is "enabled" and if the scene isRunning tru timer or active in eq. "while true" or while run=1 etc....

[Kage 36]

i notice when there is a error in the scene the isRunning is false then.

[A.Socha 112]

Please install 5.132.9 and tell us if problem is still there

[GeeMoney 3]

Just got the same error message and running on 5.132.9 . 

[Joep 181]

I have 2 HC3's on firmware 5.130.64. One has the problem and one not. I update to 5.132.9 and see if it fixes the problem on the error giving HC3.

[Gabor1 3]

I have the same problem since 5.110 2 hc3 in master-slave. sometimes the master not rebooting, just feeze, sometime the slave. very frustrating, thinking to leave fibaro with all of my systems...