If anything was resolved, there is no note in the release notes that anything changed in the driver. If you worked with someone, it wasn’t me. I just submit tickets, am told that it’s been referred to engineering, and the ticket is closed. The only time I heard further was on the final Recessed Door Sensor 7 ticket, when I was told on Oct. 5 that, hopefully, everything would be fixed in the next (2.2.4) release.
3 Recessed Door Sensor 7 devices, 1 Door/Window 7 device.
I’m just asking whether anything changed. If it was, then I will spend the hours regression testing and make up a new bug list and submit new tickets.
Right now, the devices are paired without security just to get things working as they are. I don’t care about security on the 3 Recessed Door sensors I have now because they just turn lights on/off in closets. It might be nice to have the Door/Window sensor paired securely because it senses opening/closing of the garage door. I’d like to put Recessed Door sensors on the front & back door for security, but those should be paired securely.
With only installation of 2.2.4 and no exclusion/reset/inclusion of any devices, I notice that one of the Recessed Door Sensors no longer reports that it has a tamper switch reporting clear. The other two never reported a tamper switch. As you know, the Recessed Door Sensor does not have a tamper switch.
Two of the Recessed Door Sensors still report a serial number of all zeros as long as your arm; the third does not report a serial number.
All of the Recessed Door Sensors work, more or less, yet one of them, before the update, would go into a mode where it reported “Not Responding” and would lag response by several seconds; after the door was opened, it would resume responsiveness and report OK. Another one would report “Not Responding” and then “Failed”, yet always worked. The third has never reported “Not Responding” or “Failed”.
I’m not one to obsess over “Not Responding” or “Failed” messages as long as the devices work, and I don’t look at the Z-Wave Details page unless something is not working. I’m not one to obsess over Z-Wave repairs; since there is only the one non-Plus Z-Wave device, I just let the mesh self-route as it wants.
The 2.2.4 update hasn’t been installed long enough to know whether this behavior has been fixed.
Ever since the Door/Window sensor has been paired without security, it has worked reliably.
Screen shots attached for the Recessed Door Sensors. There seems to be no correlation between the ones that show the long zero serial numbers and the other issues (reporting failure or non-response, prior reporting of a non-existent tamper switch).
I really don’t believe this is a mesh issue. Hub is centrally located, and there are Ring Extender 2 devices about every 30 feet from the hub. Only one non-Plus Z-Wave device (Somfy ZRTSI), Lights are Hue (on hub Pro) and Lutron Caseta. It’s really a very vanilla install, and the house is fairly small, about 2000 square ft on two floors. Only about a dozen Z-Wave devices, and 4 of those are the Ring Extenders.
Coat closet sensor has never had an issue. Bedroom closet is the one that occasionally lags, Library closet is the other one that occasionally doesn’t respond. All work mostly.
