Dead devices

[Tcheri 15]

Since dead devices are back with the latest 4.04x version, I try to understand how Fibaro manage that.

 

So I have ofter dead devices, always the same, usually devices that are far from the HC2. But I can have 2-3 devices in a small areas (some are exactly at the same place) with one dead and the other never dead. Of course, I've trie multiple times to mesh the network, without any changes.

 

But what is strange for me is that :

 

- when they are dead, I click one time on them and they works immediatly

- from LUA, if I use the command wakeUpDeadDevice, but this has no effect. Why ?

Please login or register to see this code.

[KristianO 15]

I don't think they are "live" just because you click on them, its just "live" waiting for new polling and then if it fails it becomes dead again.

[sonnyboy 11]

@Tcheri what kind of devices is dead? My BeNext dimmers liked to die before. Then i exluded them from polling, sens then i doesent have any problems with them and they work as they should.

[boerremk 84]

fibaro:call(1, "wakeUpDeadDevice", idPompe);

should be:

fibaro:call(1, 'wakeUpAllDevices', idPompe);

[petergebruers 1,268]

Or to wake up all dead devices (V4 firmware):

Please login or register to see this code.

How many mains powered devices do you have?

[Tcheri 15]

Thanks for your reply.

 

I should have 40+ powered devices. What is strange for me, is that when I call wakeUpAllDevices or wakeUpDeadDevice, the device stay dead in the UI. Normal ?

[petergebruers 1,268]

Thanks for your reply.

 

I should have 40+ powered devices. What is strange for me, is that when I call wakeUpAllDevices or wakeUpDeadDevice, the device stay dead in the UI. Normal ?

Thanks! I'm away, I'll check "wakeUpDeadDevice" tonight. You have about the same amount of devices as me and I think you can benefit from reducing polling to an absolute minimum. I wrote a script to make that easier. There's also some explanation of polling & wake up:

Please login or register to see this link.

You also have many LC12... these devices are very sensitive to communication errors. I don't know the details but the blinking antenna and bell symbol is indicative of this. The LC13 is less sensitive to... "something". It has to do with timing & communication. But that doesn't help you. But here's an odd thing I got from Fibaro support, when I was still running 3.6: set each valve at 10 s different wake up interval. So what I have is 600, 610, 620, ... It may seem odd, but I do think the valves get synchronized to a clock and if you set them at the same interval, they wake up at the same time. I could confirm this theory, if had time and opportunity to move my valves from my production to my test environment (the garden shed

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />). Maybe some day.

[Tcheri 15]

Thanks! I'm away, I'll check "wakeUpDeadDevice" tonight. You have about the same amount of devices as me and I think you can benefit from reducing polling to an absolute minimum. I wrote a script to make that easier. There's also some explanation of polling & wake up:

Please login or register to see this link.

You also have many LC12... these devices are very sensitive to communication errors. I don't know the details but the blinking antenna and bell symbol is indicative of this. The LC13 is less sensitive to... "something". It has to do with timing & communication. But that doesn't help you. But here's an odd thing I got from Fibaro support, when I was still running 3.6: set each valve at 10 s different wake up interval. So what I have is 600, 610, 620, ... It may seem odd, but I do think the valves get synchronized to a clock and if you set them at the same interval, they wake up at the same time. I could confirm this theory, if had time and opportunity to move my valves from my production to my test environment (the garden shed

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />). Maybe some day.

 

Indeed, I've implemented your great script and found some inconsistencies. I still have 2 everspring smoke detectors with a NIL, but they are lacking template and the UI dos not contains wake-up field.

 

When you say 'reducing polling', you mean reduce the poll, so increase the poll delay ? (currently set at 600)

Most of the battery devices have a wake-up of 900 or more.

 

I've retested the wakeupalldevices, and indeed it seems to work.

[petergebruers 1,268]

I 'll check the documentation if you can give me the model numbers.

I meant to say: try not to poll. And if you have to poll, because the device needs it, then choose the highest possible time, that will still give sufficiently good user experience. The idea is to reduce traffic.

Please let me know how it goes...

[Tcheri 15]

and I guess on the top of the poll and wakeup, there are all the devices parameters. Ex on Aeon Labs devices where parameter 111,112,113 defines update intervals. As Aons labs does not have templates anymore in V4 (Grrrrrrrrrrrr), impossible to know which values are set for each devices...

[petergebruers 1,268]

Absolutely. Good point. I am away, but later I can check the docs for those MultiSensor parameters.

Also, the controller ("1") is probably in too many association groups. I'll give an example later.

[Tcheri 15]

for Aeon Labs, I know them well : all switches , multi sensor, energy meters uses the 111,112,113 parameter to define the time gap to report to group 1, 2 and 3

[petergebruers 1,268]

Oh, sorry, I misunderstood. The Aeon parameters were meant as an example of relevant parameters. And you know them well, but are annoyed that there's no template. OK.

[petergebruers 1,268]

@Tcheri May I ask how things are going now? Hopefully in the right direction?