Schlage locks going offline/online

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

Nothing to do with the driver. SmartThings has tweaked the firmware for managing device offline detection. The FE599 is very susceptible to packet loss/delayed and if a single packet is lost (or delayed) it can lead to the hub thinking the device is offline. You should report it to SmartThings support to investigate it. They had recently reverted these changes to make the offline detection less aggressive but it’s possible they have re introduced those changes. @nayelyz @alissa.dornbos

Meanwhile your best defence is a strong mesh with minimal delays and packet loss. What that means is remove any dead devices and do a mesh repair and also add a few high quality buffering devices in your mesh

FAQ: why would I need another beaming repeater if my zwave lock is already close to my hub?

Absolutely right JD. This question is the number 1 question we get from users in many different forms. I’ll outline the most common symptoms folks experience when using locks: My lock is 5ft from my hub I can see the lock/unlock events in the history but I don’t see the user code/name I can lock/unlock using my mobile app but my codes aren’t being programmed Some of my codes are being programmed while others aren’t My codes are being programmed but I’m not getting notifications/actions aren’t being executed when the codes are used It works in the mornings but not in the evenings It was working till recently and now it’s having trouble I moved my lock closer/next to my hub but I’m still having issues One of my locks is working perfectly, the other one (closer to the hub) is having tr…