Looking for a DEAD DEVICES code

[AutoFrank 372]

HI,

I am looking to detect and report on any device that is dead on a daily basis

I could probably write one using the api but was wondering of if anybody have canned code to detect the dead devices before I create one myself

 

Thanks

 

 

[petergebruers 1,268]

Please login or register to see this code.

 

[AutoFrank 372]

Thanks @petergebruers

[cag014 731]

Please login or register to see this code.

The function above tries to wake up dead devices.... if not send email.

 

[AutoFrank 372]

Thanks @cag014

[petergebruers 1,268]

the "wake up code" only changes a status flag on your HC, it does not test the device. This is why I use this piece of code in a scene that turns of all devices. It will do 1 attempt at turning off a dead device. If it is still dead after  5 seconds, I print out the status. So this gives me a list of all "really dead" devices. If you do not want to turn of the device, you could first get its "value" then send that same value to the device again.

 

Please login or register to see this code.

 

Edited September 3, 2017 by petergebruers

[AutoFrank 372]

Thanks @petergebruers

Perhaps a combined approached might work well for me 

[cag014 731]

 @petergebruers

 

You're absolutely correct, but (at least in my case) usually the dead devices are sensors and there is no way to send any command w/o wake up.

I'll be glad if you can share any idea how to wake them properly.

Thanks 

[petergebruers 1,268]

@cag014 as far as I know, the HC marks a battery operated device as "dead" if it did not wake up in a certain time. That is my own observation, and Fibaro posted something along those lines. If you want the details, I will try to find the post. So either the device does not wake up or the wake up got lost. I do not have it very often, but I know what you are talking about. Maybe it has to do with battery level, or quality of the batteries. If I remember well, it happened to an old Aeon MultiSensor, and when I replace the batteries it wakes up and is functional again

 

Some of my scripts (for presence detection) use "lastModifiedTime". For instance, if a certain motion sensor was breached 4 hours ago, and still has not reported "safe", I assume it is dead, even if it is not technically dead. The room has two sensors, so automation still works. When you use NiMH cells in the old MultiSensor,  the sensor might go from battery ok to empty, and stay stuck "breached". I do not recomrend NiMH in that sensor, because of this issue and also because the sensor will destroy your cells... But I like to experiment so I do use rechargeable cells.

 

 

[cag014 731]

In my case I have an issue with Fibaro door sensor and sensors connected to UBS.

 

[petergebruers 1,268]

The ubs is an old device and might have mesh and range issues. I would update the mesh on mains powered devices near the UBS and the UBS itself.

 

Are the door sensors FGK-101 (the ones that do not have a built-in temperature sensor)? In that case, same story as UBS.  It would surprise me that the newer version has this problem.

[qnstie 4]

@cag014 I do not know if you have a similar problem, but I had a long-lasting issue with my wireless Popp Rain Meter, which becomes dead usually within 30 minutes from last manual wake. In the UI it manifests itself as a grey cross and a standard "communication problem" message. When I click it in the UI, it wakes up without any problems. But when I  tried to wake it up periodically from the code using fibaro:wakeUpDeadDevice(ID) command, it never works.

Perhaps you have a similar issue.

 

I solved my problem replacing the above command with:

  api.post("/devices/"..v.."/action/wakeUpDeadDevice", {});

which works great (because it is exactly what the UI does, apparently the implementation of this service does something more than just calling the fibaro:wakeUpDeadDevice(ID)).

 

Maybe it will be of some help.

My full scene code is attached below (as you can see I have a predefined list of the devices that potentially need waking up, I do not query all of the devices).

Please login or register to see this code.

 

[cag014 731]

 @

Please login or register to see this link.

 

Your absolutely correct , that's the reason that I use following call

Please login or register to see this code.

It works every time, but please pay attention to @petergebruers remark -only changes a status flag on your HC, it does not test the device.

[petergebruers 1,268]

I cannot remember exactly when, but probably more than a year ago the function "fibaro:wakeUpDeadDevice(ID)" was deprecated and changed to:

Please login or register to see this code.

Notice the subtle change. But that is not the whole story. A little bird tells me that the "old" function is still there and it is a wrapper around that newer function, so they should perform exactly the same! I changed all my code to use the fibaro:call syntax long time ago so I have never tried the older syntax again.