Still dead nodes in this version?

[marcel 1]

I still have dead nodes. a few beta versions ago it was solved, but they are all over the place again... Problem for the scenes as they do not complete and especially a problem for the more special tasks like floor heating control.... Anyone a suggestion?

[robmac 173]

Don't say something that is not true. I know a number of users that have no Danfoss at all and still have dead nodes.

Why do You think it is not true? Danfoss Valves makes the bigger impact in Z-wave engine if they are not able to connect with controller. I am not going to say that everytime You habe dead nodes it is Danfoss fault. But they "help" to make other modules dead (making big traffic in z-wave engine) and that is true!

I think all thermostats and sleeping devices have a significant impact but not convinced either way they are the cause. Some people with only a few and small networks have no issues.

[richo 4]

wasil,

It's a simple solution to it. After you get all Danfoss communicating with HC2 just remove the pooling time from each of them - delete any number you have.

Then the number of communication with Danfoss decrease dramatically and as a bonus batteries last much, much longer.

During the summer I have removed batteries from all Danfosses but it didnt help a lot.

[hvb83 1]

Richo, does that also mean I have to remove a zero if that is what my current polling interval for the Danfosses is set at? My wake-up interval is set at 600s. With that config my trv's go through a set of batteries in 2 months.

I can live with that, since my zipabox had an error and went through the batteries within 2 days. But if the battery-life can be increased even further, that would be nice.

[richo 4]

Richo, does that also mean I have to remove a zero if that is what my current polling interval for the Danfosses is set at?

Yes, then it means "no pooling"

[robmac 173]

Update on the issues I was having with my HC2.

My supplier replaced my HC2 in early January. I finally got it all configured last weekend.

Two big differences.

• 
  I replaced all of my everspring switch modules with fibaro.
  A new HC2. started with a more recent firmware than my original and has extra usb so new hardware.
  

All code and scenes same other than the id's of the devices.

Now the good news for me.

• No pauses
  No dead nodes on a regular basis though only one week in

so was it just the faulty HC2 or was it a combination of everspring modules and faulty HC2,

I hope those that still have issues get fixes soon.

[Krikroff 199]

Please login or register to see this image.

/emoticons/default_icon_mrgreen.gif" alt=":mrgreen:" /> i have two plug eversprings that have stopped functioning last 15 days, they died 1 month after the end of warranty

Please login or register to see this image.

/emoticons/default_icon_mad.gif" alt=":-x" /> ! Good news: replaced by wallplug

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />

[robmac 173]

I have a load of the everspring and they have been very reliable. Used them with homeseer with no issues.

I don't really suspect them of causing the issue. It was more that the Fibaro plugs are so nice. Even if I do have to use an adaptor in the UK

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />

e-bay time

[sergiobaiao 5]

I'm having this very same issue for a long time with one of our customers. We installed a Fibaro system on an apartment, with 12 lighting modules (between dimmers and relays) along side with 6 roller blind modules. The module which is most distant from the HC2 is about 9~10m, all of them are installed on the living room of the apartment. Almost everyday, no matter what i change in the configuration of the HC2 (have tried pooling time, not marking modules dead, etc, etc etc) i get modules marked as dead. Sometimes they show as awake but all commands sent to the modules don't work.

Sometimes i get error messages on the web interface like:

[01] ID 24: Sending error

[01] ID 24: Sending error

My client is asking me to remove all hardware from his apartment, and i really don't know what to do. I've tried to solve this problem with Fibaro Support from my distributor here in Brazil (Munddo Distribuidora) but no matter what they try nothing is getting solved.

I really want some word from someone from Fibaro to see what i can do to solve this with my client. This client is a very influent person, which not only knows a lot of people, but also owns a magazine in my city, and if he decides to talk about this with people he knows, this may ruin my company.

There should be something that can be done to solve this, as well as to prevent it from happening again. Modules that are always powered on (not on battery) should never get disconnected. Fibaro must do something about this.

My company sell and install automation systems for 3 years. We work with other brands than Fibaro, and Fibaro is the only one giving us trouble. Automation is something that is supposed to ALWAYS work, seamlessly, flawlessly, so the client doesn't even know it's there. It's very hard to sell a product that gives problems almost every week.

[ivan.ruban 3]

I also have problems with dead nodes. Fibaro HC2 version is 3.590, Polling interval is 300 seconds, pollig dead devices = yes.

In my case it is the same 3 devices all the time - Fibaro RGBW, Fibaro Dimmer and Fibaro 3kW switch. They become dead approximately every week, sometimes less often. No problems at all with other devices which are Fibaro, Everspring and mix of others.

The devices are fully functional in reality and I can control them again as soon as I wake up them. So I guess that either selecting "do not mark as dead", using the script from this thread or setting polling to 0, will help to fix my problem.

And I actually tried the script from this thread - it works as a charm. But it is a workaround. I would really like to understand why Fibaro thinks that these 3 devices are dead. HCL users however cannot use such magic scripts, so the only chance for them is to play with configuration of dead nodes.

And I fully agree with robmac:

As the script works, it indicates that the nodes are not dead. It really proves that there is an issue as they recover with no reconfiguration or change in routing.

At some point in time, communication to and from a procedure in the software is not working via the rest of the software stack, the z-wave controller, the network and the device in a timely fashion. When the script runs, communication must be back to normal or it would not work.

so frustrating ... an intermittent issue. As so many have this issue it can not all be environmental.

I tried to rebuild the network route for problem devices ( fibaro:call(id,'requestNodeNeighborUpdate',1) ) - did not help much. I saw also the reciepe from robmac, but have not tried that yet:

Please login or register to see this link.

[robmac 173]

When you discover that the z-wave engine is only single threaded from the release notes of the new alpha I think we know where there could be a potential issue.

With this pattern it is so easy to get a priority inversion either side of the single thread. The network is multi-threaded by definition so no first in first out and the rest of the software is multi-threaded.

At some point it is almost inevitable that returns can not get out to the software and new can not get into the z-wave driver as it is full. Like a traffic jam where there is a single lane road with passing places. Too much traffic in both directions and everything grinds to a halt. If no one gets out and directs traffic you could sit there all day. The delay probably ends when a message timeout occurs that frees everything up. That might be why some messages go missing and don't appear after the pause.

v4.x stable is a big hope to fix.

[ivan.ruban 3]

HC2 3.901 Alpha release notes has "multithreading" in a list of features. But it does not say if it is a completely new feature or an improved functionality. If the whole application is single-threaded it is quite dangerous. There are a lot of things that requires multiple threading:

• - scenes
  - event-driven changes
  - z-wave communication with devices
  - ...

I am very qurious to take a look at application architecture.

Anyway the presence of both "multithreading" and "new improved Z-Wave engine" sounds very promising. And I hope Fibaro team took into considerations "dead nodes" problem that so many has, and which a top-class product must not have!

[alex88 71]

I have started running a ventilation script to open and close windows every day.

Since running it I keep detecting dead nodes with my dead node script that runs every hour.

The nodes (Fibaro Blind Modules) seem to go dead when the windows close. All I am doing in my ventilation script is running this to close the windows:

Example for Fibaro Blind Module with ID = 87:

Please login or register to see this code.

Has anyone had a similar experience?

[deanrparry 19]

i got pissed off with dead nodes aswell! changed my antenna on the hc2 a put the aerial in the loft/attic on a 10m extension and it has been PERFECT since! 10 days + without a glitch!

[alex88 71]

i got pissed off with dead nodes aswell! changed my antenna on the hc2 a put the aerial in the loft/attic on a 10m extension and it has been PERFECT since! 10 days + without a glitch!

What did you do to change the antenna? Sounds like I need to do the same.

[deanrparry 19]

Please login or register to see this link.

and you will need to order the adapter... fme to sma i think it was! good luck

Please login or register to see this image.

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

[alex88 71]

Please login or register to see this link.

and you will need to order the adapter... fme to sma i think it was! good luck

Please login or register to see this image.

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

nice one. i'll add it to the never ending list of things to do to get this home automation system up and running.

[wasil 0]

i got pissed off with dead nodes aswell! changed my antenna on the hc2 a put the aerial in the loft/attic on a 10m extension and it has been PERFECT since! 10 days + without a glitch!

Are You still satisfied with Your new antenna? Did You have any dead nodes since You have bought it?

[deanrparry 19]

Antenna has changed system I would not go back to normal antenna now!

[wasil 0]

Antenna has changed system I would not go back to normal antenna now!

To sum up, no more problem with signal and dead nodes?

[Def461 0]

4 Fibaro's installation since January - ALL FOUR have problems with dead nodes.

Even in 20 sq. m of SINGLE room - I have one or both rollers DEAD and unfuntional scripts for rollets!

What spell do I need to use to make it work proper?