Almost all nodes dead, cause and resolution.

[anu 0]

I would like to share my experience that cost me two weeks.

 

I hit the mesh network reconfiguration for entire network on my HC2 then nodes are starting to die, in a day almost all nodes are dead.

All AC powered nodes are dead only AEONLab Muti-sensor continue to work but show some incorrect data, such as show high temp (70c+) and trigger potential fire.

 

I try to add/remove nodes but no success, but some devices will able to add/remove by put extremely close to the box (few centimeters).

 

I reach Fibaro Support by email and they think it's antenna problem, and suggest I tried HCL, I tried on HCL and experience the same issue.

 

Then I root the device and found that something is flooding /tmp/Zwave.log and then I realized what's the problem.

 

 

 

So I would like to share cause and symptoms on this case:

- Almost all nodes are dead

- Some devices will continue to work but got some strange data (AEON Multisensor shown temp as 70'c +)

- Unable to remove/add device properly

- Z-wave led blink rapidly

 

Cause:

- Some z-wave device flooding signal

 

Resolution:

- Unplug all powered devices and restart again.

 

 

In this case z-wave debug message is very helpful, maybe your team should consider put in on the web ui so it can review without root access.

 

Thank you. 

[Guest 22]

Both my Zwave.log and hcserver.log in /tmp do grow fast with warnings and error's

 

I've not have time to look at them closely, but will do now and report back.

[Guest bozman]

How do I reach to /tmp isn't ssh and root blocked I have tried other accounts but that isn't working?

[Guest 22]

no comments

[Guest bozman]

Ok thanks for sharing!

[anu 0]

Fibaro Support said they will show Z-wave debug log in later firmware, please wait.

 

 

How do I reach to /tmp isn't ssh and root blocked I have tried other accounts but that isn't working?