Per Device Period of Inactivity for General Monitoring?

[mterry63]

Hello Steve,

Have you considered adding per device period of inactivity in addition to "Per Interface" for general monitoring? For example, for my Z-wave device I have some that would easily be considered failed if not changed in 24 hours, but also some that wouldn't chanage for a week. For now I'm just excluding the infrequently used items, but it would be great to have "per device" values.

Perhaps this is a great pain to code, but just my 2 cents on what I think would be a valuable feature.

[SteveMSJ]

Hello Steve,

Have you considered adding per device period of inactivity in addition to "Per Interface" for general monitoring? For example, for my Z-wave device I have some that would easily be considered failed if not changed in 24 hours, but also some that wouldn't chanage for a week. For now I'm just excluding the infrequently used items, but it would be great to have "per device" values.

Perhaps this is a great pain to code, but just my 2 cents on what I think would be a valuable feature.

I have considered it in the past but didn’t consider the increased complexity worthwhile for general devices. For battery devices I incorporated the ability to override most of the global settings for individual devices as I felt it was an essential feature.
For Z-Wave general devices you can set the plug-in to poll the device if the inactivity period has been exceeded. This means that if, as your case, you set the period to 24 hours then devices that haven’t shown activity for this long will be checked by a poll. I find this works well in practice and don’t feel the need to fine tune for individual devices.

It is something I might revisit in the future though.

Steve

[mterry63]

That's probably a good solution for the Z-wave devices, I imagine my non-pollable devices will report in less than 24 hours. I'll give it a shot, thanks.