Question: I have a simple zwave plus switch(Leviton). Responds to the device page (on, off). However, it seems to have stopped recording events. Why?
Device page:
I'm guessing "Current States" doesn't update, either? If that doesn't happen, there's no hope of the "Events" page doing so, either.
The first thing I'd do is check your model number and verify that you are using the recommended driver from this list: List of Compatible Devices - Hubitat Documentation (yours could be it, but there are multiple models from Leviton and that driver isn't for all of them).
If you turn on debug logging, does anything show after a digital or physical event? If so, there's hope--perhaps the driver just isn't parsing it correctly. (In the logs, you'd probably see something like a BasicReport or SwitchBinaryReport.) If not, I'm guessing this is an older switch. Did you happen to have anything set up before that may have helped with at least physics events, like polling? Still wouldn't explain digital...
Wonder if it is a driver issue, a firmware update, or some other bug?
What happens if you use a different driver? There are a few other Generic Z-wave _____ Switch drivers. They might not work quite right, but maybe enough for testing.
If the current states are updating, but events are not, and you have verified it is not a browser issue by opening in an incognito window or cleared all your cache...
Then I would guess database corruption and do a soft reset. But that's just me.
I had a GE z-wave plus dimmer that suddenly stopped updating events around a month ago. I removed it and rejoined and it worked briefly, then it started spamming the hub so fast it maxed out the cpu and was difficult to get to the device page to remove it. It is now a Zooz 77.
I changed the driver to "Generic Z Wave Plus Switch", without any change.
I did happen to notice that there are only 50 entries in the history. Could it be that when it reached 50 entries there is some sort of bug, and the device history doesn't "roll off" - I had specified 50 as the default (see my first screen shot). Could this be a bug?
I changed the value, but it still hasn't "rolled off".
I just went and looked a a whole bunch of devices, and many of them have absolutely no history. They are Zigbee, Iris Zigbee, and Zwave.
I am not sure if this is a @gopher.ny thing, but at least he can do some digging or refer it to the team member who needs to look at it. This is my C7 Victor, in case you need to look at it.
Yes, there's a bug with overly aggressive event cleanup, deleting events that are a week old or more. Similar bug exists for device states, although a referential integrity contraint prevents deleting current device states even if they're older. It is fixed in upcoming 2.2.8, and logic properly honors the value set with /hub/advanced/maxEventAgeDays/value endpoint.
That's just weird. Which hub is it happening on? Hub name will work.
Based on events and last activity date, it looks like things are going out to the device but nothing comes back in. The max events were probably set to 50 at some point, and that's how many events are left. Other devices appear to work normally, based on the data, and there are no obvious errors in the back end logs. Something's up about that switch...
Should I just exclude and then include, i.e. start over?
It's a weird situation, this bug.
In this case, it's not a big thing. However, there may be situations where this "stopping of events" becomes a serious issue.
That was the driver that I switched to. After switching I hit configure.
No difference. No history.
Still responsive to on/off, but not reflection of that on the device screen.
IF the ZWave action is there and a "Zniffer" shows the device is sending out messages when the device is pressed, then it would have to be the driver or the hub.
Does this driver support HAIL messages?
This Leviton device is old enough where the button press locally on the device will send out a HAIL message. There was originally a patent issue with sending out "Report" messages with respect to Basic, Binary, Multilevel Reports after a local change on the device.
The newer drivers must be able to handle that.
There are plenty of people on this forum that have DS15S or other Leviton DZ devices that are using a driver that works with HAIL from the device. The driver should poll the status of the device that sent the HAIL and then update the Hub.