HS Battery Child Device NOT Updating "time" at Wakeup

[BobSpen]

Steve,
I have an AeoTec Motion/Temp Sensor(Battery Child) that had a wakeup interval set in the device at 12 hrs and I believe HS set a 12hr Polling Interval on the Root device at install. The "Last Change Time" on the Battery Child reported correctly(remember this for later). In this condition I occasionally would get a "too soon" Z-wave warning in the Log so I removed the Polling in the Root device. Now the "Last Change Time" does not update but I see the wakeup-reporting in the log and your PI seems satisfied. Any clue as to why would the "Last Change Time" not update w/o polling?

[SteveMSJ]

Steve,
I have an AeoTec Motion/Temp Sensor(Battery Child) that had a wakeup interval set in the device at 12 hrs and I believe HS set a 12hr Polling Interval on the Root device at install. The "Last Change Time" on the Battery Child reported correctly(remember this for later). In this condition I occasionally would get a "too soon" Z-wave warning in the Log so I removed the Polling in the Root device. Now the "Last Change Time" does not update but I see the wakeup-reporting in the log and your PI seems satisfied. Any clue as to why would the "Last Change Time" not update w/o polling?

Hi Bob,

The Last Change Time on the Battery child should only change when the level changes, not at every update. Is that what you are saying?

Whether the battery child needs polling to update its value depends on the actual device details. I don't know what model yours is, but the modern AeoTec (Aeon) devices push their battery level when it changes and don't need the Z-Wave pi to poll them. You certainly wouldn't want the Z-Wave pi polling the root device as that polls all the child devices. You might need a polling interval of 12 hours for the battery child of it is an old model. I've never seen HS set polling on a root device, it normally sets polling on battery children to 12 hours by default.

The above is all referring to the Z-Wave pi, SDJ-Health is monitoring whether the device is alive by the wake-ups, Not polling. The battery level however requires the Z-Wave pi to report correctly as that owns the device.

So, are you saying you don't think the battery level is being updated? Do you have LogToDatabase turned on in SDJ-Health so you can see the History of battery levels for the device? The history would give an indication that it has stopped reporting.

Steve

[BobSpen]

Steve,
I have the "Do not update device last change time if device value does not change:" UNCHECKED on all my battery devices, so the 'Last Change Time" indicates the last wakeup and battery report. This is what stopped changing even though I see the wakeups in the LOG. It is an Fibaro FGMS-001(NOT Aeon as I indicated earlier) Motion/temp monitor that seems to be a "modern" z-wave Plus device. This is the first time I have used this device so I don't have much history with it but had expected it to operate like my other "modern devices.

[SteveMSJ]

Steve,
I have the "Do not update device last change time if device value does not change:" UNCHECKED on all my battery devices, so the 'Last Change Time" indicates the last wakeup and battery report. This is what stopped changing even though I see the wakeups in the LOG. It is an Fibaro FGMS-001(NOT Aeon as I indicated earlier) Motion/temp monitor that seems to be a "modern" z-wave Plus device. This is the first time I have used this device so I don't have much history with it but had expected it to operate like my other "modern devices.

My Fibaro devices push battery levels when they change without requiring polling. Having said that there is no harm in setting a polling interval, on the battery child, with a value similar to the wake-up period. This is actually good practice in case HS happens to be down for maintenance when the device sent its new battery level and was therefore missed. If you have the 'Do not update...' UNCHECKED and a polling interval set on the battery child then you should see the time update at each wake-up presuming the poll is successful. You would need to look at the messages immediately following a wake-up to see if that is working. If not you will have to lodge a query with HS as I don't know why that would not work. This is all to do with the Z-Wave pi not SDJ-Health.

Are you sure you have both the unchecked option and the polling interval set in the z-Wave pi for the battery child of the device? Without polling the Fibaro devices only send a battery level when the value changes so the Last Change won't update until the value changes even if the option is unchecked.

Let me know how you get on.

Steve

[BobSpen]

Steve,
Thanks for your insights. Before I installed your program I got used to scanning down my battery devices and looking at the Last Change Time, so I got alarmed when I noticed the Fibaro devices did not update the Last Change Time every day(twice). I will set 12 hr polling on the battery child for my 'comfort" and see how that goes.
Again, Thank you.