Exceeded inactivity period and failed poll

[mlevin77]

My brand new Aeon repeaters, which imported to the system fine and are able to Test Connectivity just fine, are showing up as
Exceded inactivity period and failed poll
Last Change Time Never - Period = 738079 days 21 hours 30 mins

anything I can do to get them off the list - I only want to be warned if they go down and become unreachable.

Also, a few of my water sensor alarms (Everspring) are also showing this - does it mean there's really a problem with them?

3rd floor Crawlspace attic Everspring Water Sensor Alarm - Parent with 4 children Last Change Time 10/14/2021 at 10:28 PM - Period = 2 days 23 hours 2 mins

Exceeded inactivity period, failed poll AND Invalid State

[SteveMSJ]

My brand new Aeon repeaters, which imported to the system fine and are able to Test Connectivity just fine, are showing up as
Exceded inactivity period and failed poll
Last Change Time Never - Period = 738079 days 21 hours 30 mins

anything I can do to get them off the list - I only want to be warned if they go down and become unreachable.

I don't have any repeaters, so don't have direct knowledge. As far as I am aware they report as supporting status but probably can't actually be polled. You could test this by trying a manual poll, i.e. in Device View filter to show only a repeater and click on the poll icon. As far as I am aware HS doesn't provide anyway of programmatically testing these so I would just exclude them by selecting from the list 'Select devices to Exclude from checking'.

Also, a few of my water sensor alarms (Everspring) are also showing this - does it mean there's really a problem with them?

3rd floor Crawlspace attic Everspring Water Sensor Alarm - Parent with 4 children Last Change Time 10/14/2021 at 10:28 PM - Period = 2 days 23 hours 2 mins

Exceeded inactivity period, failed poll AND Invalid State

I have an Everspring leak sensor which is very old but works great and the batteries last for years and years. Interestingly mine only has 3 child devices but perhaps your's is a newer model or was included with a different version of the Z-Wave pi. As this is a battery device I presume you are monitoring this in the Battery Devices section of SDJ-Health which will alert you if it doesn't wake-up on schedule. I would exclude any battery devices from the General Devices monitoring as noted above for the repeaters. However, you might want to also investigate why one of its child devices is in an Invalid State. It might just have got set that way when it was originally included by the Z-Wave pi and won't have been reset because HS doesn't try to control it. If you are happy that all is well you can use the Reset feature in SDJ-Health to reset all the Invalid Device flags.

I hope this helps,
Steve

[mlevin77]

> You could test this by trying a manual poll, i.e. in Device View filter to show only a repeater and click on the poll icon.

sorry, where is that? I'm in the Z-wave tab of that device and I don't see a poll icon. (I do see polling interval options though).

[mlevin77]

> I presume you are monitoring this in the Battery Devices section of SDJ-Health which will alert you if it doesn't wake-up on schedule. I would exclude any battery devices from the General Devices monitoring as noted above for the repeaters.

ok I excluded battery devices from the General Devices page. But how do I see them on the Battery Device section, to know which ones haven't reported in?

[SteveMSJ]

> You could test this by trying a manual poll, i.e. in Device View filter to show only a repeater and click on the poll icon.

sorry, where is that? I'm in the Z-wave tab of that device and I don't see a poll icon. (I do see polling interval options though).

From the normal HS4 Devices Page (i.e. click on 'Devices' menu item), filter the displayed devices so that you only have a Repeater showing. Then click the right hand icon on the tool bar, looks a bit like 'A'. The tool tip if you hover over it is 'Poll Devices'.



Steve

[SteveMSJ]

> I presume you are monitoring this in the Battery Devices section of SDJ-Health which will alert you if it doesn't wake-up on schedule. I would exclude any battery devices from the General Devices monitoring as noted above for the repeaters.

ok I excluded battery devices from the General Devices page. But how do I see them on the Battery Device section, to know which ones haven't reported in?

Normally you would have set up all the Battery Device monitoring first as that is the primary purpose of the plug-in. When you first install SDJ-Health only the Battery Devices configuration is readily available and you have to click past the warnings about 'These functions are disabled by default as they are intended for experienced HS users' before accessing General Device and Log Monitoring

If you have left everything in their default settings then non-listening Z-Wave battery devices, such as the leak sensor should have been picked up and be monitored automatically. Other types of devices need some manual intervention and everything is highly configurable so can get complicated. Have a look at the guide where it is explained in more detail than I can go into here. Let me know how you get on.

Steve

[mlevin77]

From the normal HS4 Devices Page (i.e. click on 'Devices' menu item), filter the displayed devices so that you only have a Repeater showing. Then click the right hand icon on the tool bar, looks a bit like 'A'. The tool tip if you hover over it is 'Poll Devices'. Steve

I have HS3. I put checkmarks next to the repeater devices I wanted to poll, found the poll icon above, clicked it, and it's now polling everything :-) I see

46 @ Polling: 1st floor hallway Aeon Labs Repeater Slave (Status is: (Result not set by Plugin))
60 @ Polling: 3rd floor 3rd floor bedroom door landing Aeon Labs Repeater Slave v6 (node 65) (Status is: 0)
30 @ Polling: 2nd floor Upstairs living room Aeon Labs Repeater Slave Node 4 (Status is: (Plugin Reports Timeout Before Result)

and the water sensors etc. are not showing there at all (even though it seems to be polling a bunch of stuff I didn't checkmark).

[mlevin77]

Normally you would have set up all the Battery Device monitoring first as that is the primary purpose of the plug-in. When you first install SDJ-Health only the Battery Devices configuration is readily available and you have to click past the warnings about 'These functions are disabled by default as they are intended for experienced HS users' before accessing General Device and Log Monitoring
If you have left everything in their default settings then non-listening Z-Wave battery devices, such as the leak sensor should have been picked up and be monitored automatically. Other types of devices need some manual intervention and everything is highly configurable so can get complicated. Have a look at the guide where it is explained in more detail than I can go into here. Let me know how you get on.
Steve

thank you Steve. I did read the manual carefully when I first set it up, a couple of years back now, and it all worked. But now I've moved to a new computer and a new Zwave device (ZNET) and am struggling to remember everything I did and get back to a working situation... The problem is that it's listing so many things as in error that I won't know when something is really off (or maybe all of them are really out of connection now!). When I poll them manually as you suggested, the battery ones should wake up, or they need to be manually woken somehow?

[SteveMSJ]

I have HS3. I put checkmarks next to the repeater devices I wanted to poll, found the poll icon above, clicked it, and it's now polling everything :-) I see

46 @ Polling: 1st floor hallway Aeon Labs Repeater Slave (Status is: (Result not set by Plugin))
60 @ Polling: 3rd floor 3rd floor bedroom door landing Aeon Labs Repeater Slave v6 (node 65) (Status is: 0)
30 @ Polling: 2nd floor Upstairs living room Aeon Labs Repeater Slave Node 4 (Status is: (Plugin Reports Timeout Before Result)

and the water sensors etc. are not showing there at all (even though it seems to be polling a bunch of stuff I didn't checkmark).

I don't know what you mean by check marks? Are you referring to the bulk editing check boxes? They don't have anything to do with the polling. When you use the manual poll button in HS3/4 it polls everything you have showing in your current view. What I said was filter your view (use the location and location2 filters) so that only a repeater is showing them manually poll it.

I think we are going down a rabbit hole here so let's back up. The suggestion about a manual poll was just to experiment with how a repeater responded to a poll. The best thing is just to exclude your repeaters from the General Device Checking as I suggested in message #2.

Steve

[SteveMSJ]

thank you Steve. I did read the manual carefully when I first set it up, a couple of years back now, and it all worked. But now I've moved to a new computer and a new Zwave device (ZNET) and am struggling to remember everything I did and get back to a working situation... The problem is that it's listing so many things as in error that I won't know when something is really off (or maybe all of them are really out of connection now!). When I poll them manually as you suggested, the battery ones should wake up, or they need to be manually woken somehow?

Non-listening battery devices won't poll manually unless manually woken up. You can poll them using Z-Wave actions, or with regular polling, in which case the polls are queued until the device wakes-up. Anyway don't start polling non-listening battery devices it will only cause problems. You can poll listening battery devices ( e.g. Locks ) sparingly, but it is generally best to avoid automatic recurring polling wherever possible. The first troubleshooting tip with Z-Wave communication problems is to turn off all polling globally and see what affect it has.

From reading some of your other posts on the forum I can see that your Z-Wave network is in a bit of a mess with lots of communication errors so it's not surprising that you are getting warnings left right and centre. Hopefully the plug-in will help you focus on which devices are having problems and enable you to focus your attention on those parts of the network.

Steve