“Unusual” is a subjective term; certainly in Community homes, we have plenty of indication of sub-optimal Z-Wave and ZigBee networks. Whether this is a problem of the base hub radio, interference, or “un-repaired” networks, is open for investigation … but network issues are a challenge that must face all of the products based on these networking technologies.
The situation of not throwing a deadbolt on an open door is a critical case. Unfortunately, most smart locks do not have any way to verify that the bolt was thrown into the latch, and not outside of it (unless it gets a jam error ). Frankly, it should be inherent to the DTH for all Deadbolt Locks that a closure sensor be mandatory.
Regardless, I don’t see the case of a lost message in this example. The door was commanded to Lock at 11:43pm and it did. Where’s the lost message?
I just see that SHM failed to notice the door unlocking. Is that due to a lost message or SHM failure?
These are important to walk through, but the details are critical; glad @slagle has access to internal logs to help trace the situation.
And… redundancy never hurts. In the case the Z-Wave Lock is “unlocked” message gets lost (either from a network issue or SmartThings), home security is significantly enhanced with the addition of a single inexpensive closure Contact Sensor on the door. It won’t help if the root cause of no alert is a broken SHM, but at least the state of the door is verified without a video camera.