I have a handful of Zooz ZSE18 motion sensors (not the 4-in-1) that pop up in the logs every 12 hours or so with a warning...
All of them do it (only one is shown). I've tried pulling the battery on them and I've tried changing the driver to the generic zwave motion sensing driver, but nothing seems to do it. Oddly enough the logging for all of the devices is also turned off, so I'm not even sure why the messages are showing up in the logs. The units seem to work just fine, so I guess this is more of an annoyance than anything else, but I would like to resolve the issue.
Odd. Normally, that should only show up if you manually run the configure() command (e.g., by clicking the button on the device page), though it should also run once automatically when the device is first installed. This message is likely also one that will appear regardless of whether debug logging is enabled--debug logging doesn't control all logging, though in most cases you shouldn't see much with debug and info/descriptionText logging both turned off ("special" methods like when the device or preferences are updated/saved and apparently this one are common exceptions).
One explanation for this: do you happen to have a rule that runs configure() on all of these devices every 12 hour or so? Probably not, but worth asking. Did you switch from another driver to this one if it wasn't picked automatically during pairing? If so, consider switching to the plain "Device" driver momentary, running its commands to clear all state and scheduled jobs and whatnot, then switch back.
My best guess for what's really happening: 12 hours is probably this device's wakeup interval. The driver is probably responding to this and running the configure() command in case there are any changes that need to be sent. Ideally this would only happen if there were. You might be able to get it stop by hitting "Save Preferences" and/or "Configure" and waking the device at nearly the same time as that (quick glance at the manual says pressing the Z-Wave button inside the device for 5 seconds should do this, but look it up to be sure); it will often confirm in the logs that all changed were "synced," though this depends on what the driver author did. Or there could be a problem or just an unintentional log entry happening with this driver--none of these last few things are really something we can see since this is a closed-source built-in driver, and these are just guesses based on typical behavior from what we do know about others.
Thanks for the input. These are all just using motion and mode lighting apps, so very straightforward and they definitely should not be getting a pushed configuration change. I tried saving preferences and doing a forced configure but I am not sure I woke the device up manually at the right interval, though I did actually try waking them up by pulling out the battery and putting it back in. That definitely caused them to check in. I thought I had switched one of them to the generic driver but I just went back and checked and it is using the zooz driver. I must not have saved it, so I changed it again and will try. I suspect you are correct though -- I checked the documentation and the default wake-up interval is 12 hours, and there is a corresponding entry in the event log reporting battery level. I'll play with it a bit more and if I can't figure it out I'll just ignore it
Did you switch from another driver to this one if it wasn't picked automatically during pairing? If so, consider switching to the plain "Device" driver momentary, running its commands to clear all state and scheduled jobs and whatnot, then switch back.
