Polling... How does it really work? Proper settings?

[Ltek]

All of my sensors seem to work properly but I'm hit-miss on getting Battery to report. Some sensors seem fine while others never report even when woke manually.

I've searched this forum for over an hour, reading everything I can find.. not help

I manually set all my Battery child devices to 10 hrs to see if that helps.

Ultimately is there any REAL understanding of what the proper polling intervals need to set and on what devices?

For example... I'm looking at thee below and you can see many polling intervals were set to very short time frames (I set battery from 12 down to 10 hrs)

Should those intervals be so low? Wont that create a lot of extra, unnecessary, load on HS3 (or Zwave) processing - even if the polling is 'cleaned up' after so many are queued?

Child Device: Home Security CC: Notification Ver: 5 Polling: Polling Interval: 21m, 2s
Child Device: Application Status CC: Application Status Polling: Polling Disabled
Child Device: Battery CC: Battery Polling: Polling Interval: 10h, 0m, 0s
Child Device: General Purpose Alarm CC: Sensor Alarm Polling: Polling Interval: 20m, 46s
Child Device: Motion CC: Sensor Binary Polling: Polling Interval: 20m, 48s
Child Device: Temperature CC: Sensor Multilevel Ver: 8 Polling: Polling Interval: 20m, 50s
Child Device: Luminance CC: Sensor Multilevel Ver: 8 Polling: Polling Interval: 20m, 52s
Child Device: Seismic Intensity CC: Sensor Multilevel Ver: 8 Polling: Polling Interval: 20m, 54s
Child Device: Acceleration X-Axis CC: Sensor Multilevel Ver: 8 Polling: Polling Interval: 20m, 56s
Child Device: Acceleration Y-Axis CC: Sensor Multilevel Ver: 8 Polling: Polling Interval: 20m, 58s
Child Device: Acceleration Z-Axis CC: Sensor Multilevel Ver: 8 Polling: Polling Interval: 21m, 0s

[rmasonjr]

I have some devices that report battery % fine and others that I have completely given-up on No amount of dark magic can make them report.

Eventually, I will be moving the majority of my motions to hard-wired.

[Ltek]

I have some devices that report battery % fine and others that I have completely given-up on No amount of dark magic can make them report.

Eventually, I will be moving the majority of my motions to hard-wired.

Sounds like HS has not fixed this bug ... putting in wired motions sensors is not a fix. And something many of us cannot do.

[integlikewhoa]

Sounds like HS has not fixed this bug ... putting in wired motions sensors is not a fix. And something many of us cannot do.

The fix is to have a sensor that actually reports its battery to HS on its own when it changes a certain amount or drops below a certain point. Polling is not the new answer to anything. Polling is a very crude and old way of getting data by poking the sensor even if nothing has changed. How about if I kept poking you every 20 min to asked how you felt while you were sleeping. Its much more efficient for me to not bother you while your asleep and if you don't feel good just tell me when your awake and ready to tell me.
The other problem is not all sensors get battery% very accurately. Most don't change in 1% increments or at a normal usage curve. ie might say 91% for months then rapidly drop to 50% in one shot.

Ofcourse the best solution is not to use batteries at all. "rmasonjr" really has the best idea. Changing and monitoring batteries reduces the effectiveness of home automation as battery devices are slower to respond and require maintenance that can't be automated (unless you got a robot that goes around the house changing batteries ever few months).

[ewkearns]

How about if I kept poking you every 20 min to asked how you felt while you were sleeping.

I'd call you "the night nurse."

[integlikewhoa]

All of my sensors seem to work properly but I'm hit-miss on getting Battery to report. Some sensors seem fine while others never report even when woke manually.

Also not sure if this is related to your problem.

https://forums.homeseer.com/showthread.php?t=189705

But in the above thread the OP was watching the "last changed time" and assuming his battery device was not updating since that time was not updating.

This problem was found to be a device setting that wont update that time if the sensor reported the same battery% as was already displayed.

I'm not sure what your battery is currently reading and how you know it's not updating but if your looking at that last changed time you might want to look into that setting or enable z-wave debug to see whats going on behind the HS3 UI.

[pohoda]

Same issue here. 2 Kwikset locks and a door/window sensor and none of them report the correct battery level nor ever update. The door lock battery status worked in HS2.