FIBARO DEAD MODULES

[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.

[sergiobaiao 5]

there is one very important thing i forgot to mention about this one client. He lives on an apartment, only him and his wife, and they are almost everytime out of the apartment...they live very early in the morning, only go there for lunch and after that only at night, to sleep. I don't think there is too much traffic in the Z-Wave network mainly because there are so few modules (i've seen setups with more than 70 modules) and there are no associated modules at all. I'm using the recomended pooling as of HC2 saying :

Number of devices: 18.

Recommended devices polling time interval: 125s.

And so far, what i've seen is a complete lack of interest on Fibaro's side to support not only me but everyone having this problem. I bet there are a lot ot clients and integrators over the world with this kind of problem, many don't even know about this forum, and they're are lost in the open with this problems.

The latest recomendation of Brazil's Fibaro support (actually Munddo Distributor Support) was to use an UPS on the HC2 to prevent bad power to keep restarting the HC2, but i can't see how this is going to help because the modules will still have power outages and power cycles because of that.

[Lauri 6]

Have fibaro support made a teamview session with you to check the HC2 working issues?

I would suggest you to do the most difficult thing - replace this HC2 with new one and add all the modules again.

If you tell HC2 to not mark devices as dead but it does this anyway, this shows that there is something wrong with this...

Have you tried reconfiguring z-wave network? Scene:

--[[

%% properties

%% globals

--]]

if (fibaro:countScenes() > 1) then fibaro:abort() end;

local id_device = 1

fibaro:call(id_device,'requestNodeNeighborUpdate')

fibaro:debug('Rediscover all nodes')

fibaro:sleep(10000)

We have installed Fibaro systems to 400m2 house and no issues with dead nodes at all.

Another thing you could do yourself -

Please login or register to see this link.

Use this Toolkit that Kirkoff has made, you can check with this - is there any devices which should be reconfigured etc..

I hope you get this issue solved asap.

Lauri

[sergiobaiao 5]

Lauri,

I already replaced the HC2, didn't solve the problem. I really want Fibaro support team to directly intervent on this, because nothing we tried so far is working.

[Lauri 6]

I think you should make a phone call directly to Fibaro then. Sometimes e-mails are not very fast indeed

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" />

[Guest Kuuno]

what material are the walls in apartment?

are the same modules getting dead?

what happens of you disable the "mark as dead" function, is the signal transmitted all the time?

[robmac 173]

sergiobaiao,

I had a very similar problem but in the end it was a bad HC2 and you have tried that.

From your list you have tried most things so you probably have tried but just incase.

you don't say if you have removed modules in turn to see if it is a bad module

you don't say if you have checked for electromagnetic interference? Try any cheap chinese power supplies for starters.

[Tcheri 15]

I had similar problems. After a remote access to my HC2, Fibaro support advices :

In the z-wave network configuration:

- pulling dead device to off

- put 0 as "Devices polling time interval" global parameter

As I have Danfoss valves, put a minimum wake-up time to 600-900 and a different value to each, for example 600-620-640... (I've 13 of them).

I've also changed the refresh Home Energy Meter DSB09104, to reduce the update

values (parameters 111 to 113).

With all those changes, my z-wave network is much more stable.

What I see, is that more the device is far from the HC2, the more you have to reduce the z-wave traffic. If not, devices on the path are overloaded.

[sergiobaiao 5]

what material are the walls in apartment?

are the same modules getting dead?

what happens of you disable the "mark as dead" function, is the signal transmitted all the time?

Kuuno,

There is only one area that has a wall between the HC2 and the modules, and this area never had any problems. The majority of the modules (9 lighting and 5 roler shades) are in the same room (a living room), without any walls and very near to the HC2 (at most 10m). The modules getting dead are totally random. After a module get disconnected, the only thing i can do to make it work again is to remove and add the module again, which makes it being assigned a different id, thus making me change all the scenes which have the module.

[robmac 173]

After a module get disconnected, the only thing i can do to make it work again is to remove and add the module again

How do you remove the module if it has no communication?

[sergiobaiao 5]

After a module get disconnected, the only thing i can do to make it work again is to remove and add the module again

How do you remove the module if it has no communication?

by removing it from the wall box and pressing the button on it, and using the removal procedure on the HC2.

the module is working fine as far as i know, but HC2 keeps loosing it.

[robmac 173]

So the device does not wake but radio coms is working.

Long shot but has someone else got a z-wave network with same home id in the next apartment?

[sergiobaiao 5]

So the device does not wake but radio coms is working.

Long shot but has someone else got a z-wave network with same home id in the next apartment?

It's a 24 store building, with 1 apartment/floor, and the only apartment which has automation is this one so far.

[robmac 173]

and I thought I had issues before christmas.

Any LUA code/scenes or virtual devices?

[sergiobaiao 5]

and I thought I had issues before christmas.

Any LUA code/scenes or virtual devices?

none at all. only block scenes

[Guest Kuuno]

i did not get what happens if you disable marking nodes as dead?

if you click the module that shows "sending error" does the state change on HC2 side?

[sergiobaiao 5]

i did not get what happens if you disable marking nodes as dead?

if you click the module that shows "sending error" does the state change on HC2 side?

When i disable that option, the module looses connection the same way and starts giving the "sending error"

After this happens, the only way to get it back working is to remove and re-add to the system

[A.Socha 133]

sergiobaiao, sending error mean you got problem with connection with that device. Try have a lower traffic in network, lower pooling, bigger wakeups

[sergiobaiao 5]

sergiobaiao, sending error mean you got problem with connection with that device. Try have a lower traffic in network, lower pooling, bigger wakeups

If you read all my previous posts you'll understand what my problem really is... there is nothing that would cause a big traffic, i only have 18 modules, being 12 lighting and 6 roller blinds, all fibaro modules. I've set them to never be marked dead, i don't have any battery modules, but every week i have different modules being marked as dead/offline, and no matter what i do, the only way to have them working again is remove and add them to the HC2, thus making me having to edit all the scenes to update the module. As i already stated, I've already changed the HC2, there is no walls between most of the modules (there is only one wall between the HC2 and 3 modules, the rest of them is in a large living room without anything between the HC2 and them), there is no other apartment on the same building with a Z-Wave network.

The only downside here is that we live in a VERY HOT city, that sometimes can reach over 40º Celsius, and because of that we have a lot of power outages.

I have tried everything that Munddo support crew told me to, have spent a lot of ours on this, and the client is asking me to remove all equipment off his apartment because they don't work.

[robmac 173]

Dirty power make the modules lock up?

[sergiobaiao 5]

Dirty power make the modules lock up?

I wish I could give you this answer....this is what Fibaro's distributor support staff in Brazil are saying, but nothing has been confirmed