Dea node not dead

[HomeSystem.sk 69]

I have a problem with one network.

Almost ever switch after I trigger it says 2x transfer failed and then it says transfer ok. Sometimes, the transfer OK comes too late and the device goes to dead node, even though it really gets on. Many times it just does not get on but immediatelly after wake up and clickink again the transfer goes ON.

This happens with devices located few meters from HC2, so this should not be range problem.

The entirele network is too slow, the transfer just takes too long.

 

Does any of you have similar behavior?

[Tony270570 107]

Hi, did you tried to reconfigure the mesh network for that device? 

[Sankotronic 2,370]

@HomeSystem.sk,

 

This more sounds like congestion in z-wave network. Check settings for pooling devices, turn off pooling dead devices if turned on at least to see if it will improve speed. Check if there are some dead devices or devices that have no obvious problem but actually battery is depleted. Also check any code that is triggered by devices that are sending value reports like smart plugs and if there is no looping code that is sending commands without checking status or something like that. 

 

Sorry if I bubbling but sometimes it helps to remember the right thing.

[HomeSystem.sk 69]

@Tony270570 Yes I tried, the strange thing is that it worked and now it folling apart and Z-Wave reconfigurations does not help anymore.

 

@Sankotronic polling dead nodes is off, I will try to activate it just to see. I am going to remove all the scenes and see if it helps. The system has just 4 scenes, for turning on the heater and for turning on the water boiler...

Ok so without active scenes, pooling dead nodes and anything, situation still remain the same.

[Tony270570 107]

@HomeSystem.sk maybe a badly inclusion a device flowing the zwave network. Did you tried excluding / including your device or at least reconfigure it?

[HomeSystem.sk 69]

But which one  Currently 10 out of 14 relay switches are marked as dead, only 4 are still kind of alive.

 

Straingly none of battery powered devices (there are only motion sensors from Fibaro) are dead. I see that they do not work perfect and reports does not come as they should (mostly temperature) but they are not dead at all.

[Tony270570 107]

I See  but it's a new informationI it's basic questions but did you had a look to your CPU/RAM usage? did you remember to have tried something special like reconfiguring your zwave network?  I read some issues in another thread after a full mesh reconfiguration.

last question do you have a fresh backup?

Edited March 19, 2017 by Tony270570

[HomeSystem.sk 69]

Yes of corse.

The CPU/RAM are alright, just like in every other HC2. CPU around 1-3% and RAM around 30%.

I did z-wave reconfiguration, but that helped for a time only. The longer the system is on the more dead nodes are there. 

The backup is there, only I dont have access to the HC2 if you want to sugest that  It is in customers house and I already spend there a lot of time with no luck, I am waiting for Fibaro support answer for two weeks already so I am trying to find inspiration here whet else to try

[Tony270570 107]

well have look here : 

Please login or register to see this link.

it will not fix anything but can explain the problem. without access to the machine yes it will be hard to restore a backup  don't have anymore ideas to suggest @HomeSystem.sk really sorry and hope the support will help quickly !!

[Sankotronic 2,370]

Well, there is always question if there is something in vicinity of HC that can interfere with z-wave signal? Maybe moving it to another place. I had problems with z-wave network and some devices were reporting dead until I move it from internet router, HUE bridge and TV. Some of this dead devices were near to HC just to mention so with direct communication. Most persistent was Fibaro door/window sensor that I had to re-include two times before it stop reporting transfer fail and falling dead.

[HomeSystem.sk 69]

Well, this HC2 is in the technician office, they have some network devices there around. Can this be the case for this behavior? As it really does not work now at all.

[Sankotronic 2,370]

3 hours ago, HomeSystem.sk said:

Well, this HC2 is in the technician office, they have some network devices there around. Can this be the case for this behavior? As it really does not work now at all.

 

To find out, there is only one way, relocate HC2 or switch off those devices (if possible) for few hours at least to test. Usually with interference even small relocation can solve the problem.

[HomeSystem.sk 69]

On 19/03/2017 at 8:04 PM, Sankotronic said:

Well, there is always question if there is something in vicinity of HC that can interfere with z-wave signal? Maybe moving it to another place. I had problems with z-wave network and some devices were reporting dead until I move it from internet router, HUE bridge and TV. Some of this dead devices were near to HC just to mention so with direct communication. Most persistent was Fibaro door/window sensor that I had to re-include two times before it stop reporting transfer fail and falling dead.

Ok I asked customer to move it, he moved it to another floor and everything seems to go to normal. No more transfer filed, communication seems ok. Actually we got 3 dead nodes on motion sensors but at least I know that system is giving the right information. Thanks Sankotronic for help.

Actually it is mindblowing that location can change so much.

[Sankotronic 2,370]

Just now, HomeSystem.sk said:

Ok I asked customer to move it, he moved it to another floor and everything seems to go to normal. No more transfer filed, communication seems ok. Actually we got 3 dead nodes on motion sensors but at least I know that system is giving the right information. Thanks Sankotronic for help.

Actually it is mindblowing that location can change so much.

 

Hi @HomeSystem.sk,

 

I'm glad that it helped. For those dead nodes now should be sufficient to refresh mesh network but not at once for all network, but only for neighbor devices first and then those dead ones with waking up. If some of them still persist to die, then exclusion/inclusion should help. It is good practice to use mains powered modules strategically positioned within the network.

[HomeSystem.sk 69]

Yes, that is not a problem anymore, if the network behave normal and shows the real status then I know what to do  I have wall plugs there to repeat the signal where needed, so thats ok. I will wait a day before I will wake them up manually, maybe they get back to live  One sensor is now in the room with HC2 and it says it is dead, so probably it just need to figure new way to it. But definitelly, I can deal with this now.

 

The strainge thing was as well that before basically all main powered devices got dead eventually but the sensors never got marked as dead even though I knew they do not report. So basically if there is signal interference you have NO IDEA what is really going on in the network in reality.