Dead Nodes - they are back again

[Mib 15]

I had my problems with dead nodes before (

Please login or register to see this link.

= dead  nodes)  and could solve it mostly by not using FIBARO Motion Sensor anymore.

Until yesterday.

In the morning the system worked fine - at noon I realized the first dead nodes - in the evening nothing worked anymore.

The system was up for 19 days since I updated to 4.080. So I rebooted for several times. No help. I have not changed anything in the last few weeks. So what causes the disaster? I have no clue.

Please login or register to see this image.

/emoticons/default_icon_curve.gif" alt=":-/" />

 

MIB

[candrea77 26]

As far as I understand , v4.080 is unstable if some zwave device not respond to the network frame.

Today I've got another system freeze after 11 days : I realized that a zwave switch was unplugged from the plug.

 

So it seems that 4.080 freeze if some device that are in the DB not talk with the system ......

 

I ask all users to report here their experience and if they have the same behaviour.

[alex88 71]

I am v4070 and it is also unstable. zwave network issues. takes up to and longer than 30 seconds on occasions for zwave commands to get through, so devices don't respond at all (intermittent).

[Guest fat]

I am on v4.070 and have found that if some devices are down that it can slow down the whole network. I have a 24v power supply for an RGBW module in my roof. Here in Australia it's gets hot in summer and I don't want the power supply operating in those temps so I switch it off. When I do this it can sometimes slow down the z wave network

[Mib 15]

Thank you for your answers. It seems you are all right. I found the reason for my complete network breakdown.  

I use Netatmo weather station since 5.3.2016. It works fine.  I also have a additional indoor module for the basement which uses batteries. Though those batteries are supposed to last a year mine were  dead after a couple of weeks. The Netatmo app did not warn me at all. By coincidence I realized it when I was checking the not working meshed network. So there must be a context.

When you (c

Please login or register to see this link.

) write the stable version v4.080 is unstable and has problems with not responding modules it seems to fit perfect to my breakdown.

What I do not understand is that I removed the whole Netatmo stuff at 10:00 in the morning but it took till 16:00 that the network did recover. At 17:00 it worked again.

So why took it so long?

 

MIB

[Sankotronic 2,370]

My HCL2 is on 4.070 software version. Sometimes one of the smart wall plugs stays unplugged but I never noticed any problems with z-wave network. In two occasions this same plug was shown in iPhone app as dead even was plugged on power, but after tapping on X it show immediately as ok and can be controlled. There is one smoke detector, dimmer 2 and three door/windows sensors that are located on some distance from HC2 but they were never reported as dead. Maybe my z-wave network is stable because I carefully planned my network setup and placed wall plugs and dimmers in such way that all battery powered sensors can reach HCL2 if not directly then through one of them? 

 

At the moment my system has over 40 Fibaro modules (sensors) included with 27 Philips HUE lamps and about 22 scenes running for about 1 month and except some minor trouble with HUE I can say that it is working very stable and doing exactly as I expected and programmed.

 

So my question is, should I upgrade to 4.080 at this point when everything is working just fine?