Z-Wave engine partly stopped working

[ArjanM 1]

Hi all,

 

I'm using my Home Center 3 for a couple of years now and am using ~100 different Z-Wave units, of which 90% are Fibaro modules.

I am not using the Z-Wave 3.0 engine, and I'm running version 5.130.64 for 2 weeks now.

 

My configuration has always been working without any issue, but yesterday the Z-Wave engine has partly crashed.

The HC3 did still receive all incoming data, like temperature values or on/off states. But I wasn't able to turn on/off any light.

 

First I tried a normal restart, but after 15 minutes it still said "starting services". Which normally is done much quicker.

Then I unplugged the HC3 from power. It then restarted quickly and the issue was resolved.

 

Questions:

1- Can I do anything to debug this issue? Are there any logs I can check?

2- Does anyone have any idea why this happened? Has it to do with this version? (5.130.64)

3- Can I add another HC3 to my setup as slave/secondary to avoid down time in the future? Could I then reboot the master HC3 while continuing network control using the slave HC3?

 

Thank you for your thoughts.

Edited December 13, 2022 by ArjanM

[A.Socha 112]

you can dowload logs and report problem to [email protected]

[marbe 20]

I'm working with support on a similar bug where the api functionality in QA gets partially limited. Instead of the correct response to api.get, only an empty value is returned. Restarting the controller does not help, only disconnecting from power. I've sent a number of logs to support over the last year, with each new version I look forward to fixing it, but so far it's repeated with the latest 5.130

Edited December 14, 2022 by marbe

[ArjanM 1]

On 12/13/2022 at 4:34 PM, A.Socha said:

you can dowload logs and report problem to [email protected]

Thank you for the suggestion. After your post I managed to download the logs and send an email to Fibaro, this was their reply:

 

Quote

"Unfortunately, with such a number of devices, there may be some communication problems, the cause of which is difficult to determine clearly without increased levels of logs. In case of recurrence, please download a log dump once again, and enable support access on the gateway."

 

I still don't know why this crash happened and I am surprised that Fibaro states that 87 Z-Wave devices on a Home Center 3 might be demanding. I asked them again whether they checked my attached log files, but no more answer came back. Unfortunately, since the log files are encrypted, I have no option to research this myself.

[ArjanM 1]

Update: Fibaro raised the log level on my Fibaro Home Center 3. In case it happens again, they told me to immediately download the log files and ask them to check for the cause.

[Neo Andersson 141]

There is an issue with these system crashes, that is lingering in the air quite a bit..I think developers are all aware of this, but the problem behind the scenes must be more complex..thats my guess...it is a huge problem..all these "Unexpected error happend" or all random crashes (i had several of them too} are having the highest priority among other issues i can tell you this without having this confirmed from developers...

This is a basic, fundamental issue of the system, and i bet that developers are focusing on these problems with majority of their resources..

 

[fuser99 7]

H

On 1/17/2023 at 11:40 PM, Neo Andersson said:

There is an issue with these system crashes, that is lingering in the air quite a bit..I think developers are all aware of this, but the problem behind the scenes must be more complex..thats my guess...it is a huge problem..all these "Unexpected error happend" or all random crashes (i had several of them too} are having the highest priority among other issues i can tell you this without having this confirmed from developers...

This is a basic, fundamental issue of the system, and i bet that developers are focusing on these problems with majority of their resources..

 

 

Hope so. HC3 has become very unstable to me in the last year. I consider moving to something else but I still hope Fibaro team will fix those issues we all have.