HC2 Zwave Engine Freeze

[fgallnii 0]

Hello,

 

I have a HomeCenter 2 box since two years.

Since the version 4.0.6, sometimes the Zwave Engine freezes...

 

I explain : I have one scene which turns on 5 devices (fibaro). This is made with a lua loop (instruction "for" and not "while").

 

After the end of the scene sometimes the zwave action on devices are ok many seconds after (it can varied between 30 seconds and 2 minutes to have my actions effectly sent to the zwave modules). I have 31 registered devices with a polling time to 300ms.

 

During this "freeze" time :

• the interface respond well
• the cpu and memory are ok
• any manual action on a device doesn't work (or are queued to the previous freezed actions)

So concretely, sometimes I have a "queue of zwave action" which run with a delay (between 30s and 2minutes).

Any idea about this problem?

 

Thanks in advance.

 

 

[fgallnii 0]

Hi again,

 

It seems that the engine freezes come on evening every days. I don't see any freeze on morning.

Do you have the same behavior? or do you have these freezes all the day?

 

One more question: do you know if the HC2 box makes a mesh reconfiguration every night?

[Maxim 0]

In my case freezing does not depend on time of the day. 

 

I have no idea about mesh reconfiguration every night.

[fi-bar-oh 47]

Is fibaro actually reading this? A.Socha? anyone or are you hiding behind your keyboards and bank accounts again?

 

Help these guys it is totally unfair... do NOT blame beta!!! I have a (stable) 4.080 hcl that freezes here! and a (beta) hc2 on 4.081 that does aswell... i've not complained because look what happened last time you annoyed me, i swore at you as you blamed users constantly (foul language) and you banned me (easy solution)!

 

This time me and my wife accept i poisoned our entire home with your junk but we lived with it for 3 years+ i think now... it is like having a dog you cannot toilet train... constantly cleaning up everyday behind it!

 

Man up! Fix these issues or AT LEAST answer support tickets... day 4 and counting!

 

I wish to GOD i never accepted 4.080 everything was FAIRLY stable until i did!

Please login or register to see this image.

/emoticons/default_sad.png" alt=":(" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[alex88 71]

Is fibaro actually reading this? A.Socha? anyone or are you hiding behind your keyboards and bank accounts again?

 

Help these guys it is totally unfair... do NOT blame beta!!! I have a (stable) 4.080 hcl that freezes here! and a (beta) hc2 on 4.081 that does aswell... i've not complained because look what happened last time you annoyed me, i swore at you as you blamed users constantly (foul language) and you banned me (easy solution)!

 

This time me and my wife accept i poisoned our entire home with your junk but we lived with it for 3 years+ i think now... it is like having a dog you cannot toilet train... constantly cleaning up everyday behind it!

 

Man up! Fix these issues or AT LEAST answer support tickets... day 4 and counting!

 

I wish to GOD i never accepted 4.080 everything was FAIRLY stable until i did!

Please login or register to see this image.

/emoticons/default_sad.png" alt=":(" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

 

 

4 days... i have tickets that I opened in January 2016 that have not been closed. All I get is that they have been assigned and someone (Roman etc) is working on them. I don't know why support is being so unresponsive, other than maybe all the problems that people have been recently reporting.

 

My experience is that you should not upgrade unless you absolutely have to. I do not think that the software is designed well enough for multiple upgrades. If you keep upgrading you are likely to find faults that others do not experience when they have only upgraded a few times or if they have started on that build.

 

I suppose the only logical conclusion is that they are swamped and they are working on fixes as quickly as they can. All we can do is wait and see. Eventually the big companies will come along and consume the market with devices that just work ....

 

 

PS: All that said, I think they may have fixed one of my tickets (where my zwave engine freezes up), but I am not sure as

1)they have communicated nothing

2) every now and then I get delays - nothing as bad as the 30+ second delays when I first upgraded to 4.070

 

Who knows anymore. The only thing I can probably say for sure is they need more developers and more people on tech support.

[barend121 13]

I got this once with a Greenwave powernode 6, once...

Hc2 works fine for me, sometimes 4 sec delay with motion sensor and light on, for the rest super System!

[fi-bar-oh 47]

Still no response here... Annoying thing is I'm doing them the favour of leaving my system broken so they can spot the issue!

Bet if if I used foul language right now I'd get a response on the forum in less than 60 minutes!

[gucio1234 79]

Update from my end as my HC2 was "lazy" - I posted my contribution to this topic earlier .

 

I was in touch with Fibaro support, they advised to reconfigure z-wave network. I could not do it as the network was not responsive. They advised to reconfigure each z-wave device separately - it did not help.

 

Then they asked me to open for them the port to SSH to my box for investigation.

They checked and said that the slow responsiveness of my box was caused by too frequent reports of the devices reporting temperature and power consumption.

I corrected this for my UBSes and AEON Multisensors and now HC2 is responding fast as earlier.

 

I asked Fibaro if there is any way from the user level to investigate the z-wave network and they said NO, and it has to be done by the support. 

[fi-bar-oh 47]

Update from my end as my HC2 was "lazy" - I posted my contribution to this topic earlier .

I was in touch with Fibaro support, they advised to reconfigure z-wave network. I could not do it as the network was not responsive. They advised to reconfigure each z-wave device separately - it did not help.

Then they asked me to open for them the port to SSH to my box for investigation.

They checked and said that the slow responsiveness of my box was caused by too frequent reports of the devices reporting temperature and power consumption.

I corrected this for my UBSes and AEON Multisensors and now HC2 is responding fast as earlier.

I asked Fibaro if there is any way from the user level to investigate the z-wave network and they said NO, and it has to be done by the support.

And you changed frequency of updates for temperatures to? How many devices?

[gucio1234 79]

I set that UBSes is not to be polled automatically by HC2. It reports the change of temperature when it is greater than 0,5 C  (default).

 

AEON LABS Multisensors DSB-05 are polled by the system at default interval.

 

For AEON LABS Multisensor DSB-05 I set the paramter 111 to 60 s    (it was earlier 3 s)

 

 

I have 6 UBSes with total of 22 Dallas temp sensors and 3 DSB-05.

[JEAU 2]

Hi gucio1234,

 

My HC2 was stop working every 24 hours and I used to manually restart through power button, I reported this to Fibaro support and they connected and they said the same thing as yours, after they have connected to my HC2 now all the the devices are dead no z-wave devices work any more, I restored several times from different backup but non of them works any more,

even I have tried with new fresh restored still does not work, Fibaro support does not respond any more !!! I am not sure what to do any idea? my HC2 Software Version is :4.540

Thanks 

Please login or register to see this attachment.