I have this simple rule that turns on the powder room light when the door is closed. After it is reopen and a slight delay it either turns the light off or dims it to a level matching other lights in the area.
I have noticed that sometimes the close of the door doesn't trigger the light on. Its always the first closure after a period of no activity. If I open door and close it again then the light on action performs.
I thought this was maybe a ZWave issue where the sensor wasn't getting through to the hub. But when I look at 8:21:27.716 there is no triggering of app 415 (as seen with the second closure a minute later), but the log would seem to confirm the contact closure was indeed received by the hub. If the contact closure was coherent enough a ZWave message to make it to the log why wasn't the rule trigger triggered? Something seems off here....
Try this: go to the device details page, events tab, check if there is a corresponding event (matching timestamp) for the log that did not trigger the rule. If there is, check that the 'state change' is set to true.
Some drivers sometimes log state updates even when they are not state changes (and thus don't generate an event).
OK weird. Contacts events tab doesn't show anything at 8:21:27. So its in the log but didn't trigger an event?
Also 8:22:24 and 10:09:30 double triggers both door contact apps yet only one is coded for a door closing, the other is door open (see off rule below). Could this be a case of switch bounce where the contact sensor is sending back to back open/close messages? I would have thought the zwave device would debounce the switch.
Closed at 8:21:27
Opened at 8:22:20
Closed at 8:22:24
Opened at 8:22:30
Again, some drivers occasionally log state (e.g. after a refresh call) even when there was no state changes.
The other possibility is that event has rolled off the list. I believe the default event history size is 11. You can change it to something larger while debugging, say 30, in the device details page somewhere.
When you click on an event in the events log, a popup appears with all the details about the event.
This is looking like a driver problem. I switched from the internal Hubitat Zooz driver to the advanced driver from JTP10181 and the problem seems to have gone away. For some reason a contact close was randomly not triggering an event with the built in driver. In fairness this was an intermittent so a couple more days to confirm for sure but I suspect a bug in the stock ZSE41 driver.
I also updated the ZSE41 firmware to 2.3 from 2.0. There were some hurdles there due to added complexity of battery devices for OTA but eventually I got it sorted. Powered devices are trivial but there are some steps to make battery OTA work due to the two step firmware process (needs to interrogate the device for current driver rev b4 you can setup target driver, which means waking up a couple times). Might warrant a note on a help page somewhere about extra steps for battery powered device OTA.
