RBoy
September 22, 2024, 10:22pm
7
This issue is a classic symptom of packet loss in the network. Locks are FliRS devices and need special buffering devices to reliable communications. See this post for details
This question comes up a lot. Suppose you have a Z wave lock, but the status doesn’t seem to update or commands don’t always seem to work. Typically someone in the community will recommend that you add another beaming repeater within 10 feet or so of the lock. So the question is why would you need that if the lock is already pretty close to the hub?
The short answer is that the hub is busy, and it takes some load off of it if you have a separate beaming repeater near your lock.
The long answer is in the following thread (this is a clickable link)
Also, since I get asked all the time what’s an inexpensive Zwave plus beaming repeater, for the US hub the Minoston miniplug is often on sale for right around $20. It should not require any custom code, it’s just a very simple one socket on/…
Drivers by themselves cannot fix a packet loss issue, there are other features which can be enabled through drivers, see this post for a list of available features for this lock over zwave
Universal Enhanced Z-Wave Lock driver
This driver is enhanced to fix bugs in the stock ST ZWave Lock driver, include patches for bugs in lock firmwares and bring out additional features for Schalge, Yale, Kwikset, IDLock, Popp, Samsung, Delaney, August Pro, Danalock, KeyWe, Philia, Vivint, Locstar etc zwave locks (see below for a full list of models and features). This works with all ZWave locks and newer ZWave Plus locks (see below for a list of locks tested).
It discovers/learns the lock features and automatically configures them. If a feature is not supported by the lock it will not show up or say Unsupported.
You need SmartThings Smart Lock Guest Access (SLGA), Advanced Web UI or a SmartApp like Lock User Management (LUM) , Rental Lock Automater (RLA) to program user …
2 Likes