I’ve been using several Schlage zwave locks for years now, with the last couple of years using the @philh30 driver for Schlage 468/469 locks with the @h0ckeysk8er modifications. Today I noticed a lag between when I touch the circle on the ST tile to open or close the lock, and when the lock actually opens or closes. Sometimes it doesn’t even complete the task at all. Sometimes it does it, but the circle spins for another 5 seconds before the tile status updates.
Yet, if I press the tile from my Sharptools dashboard, the lock opens or closes almost as soon as I receive the green “Command Sent” confirmation.
If Sharptools is just sending codes to the SmartThings engine, how is it executing things more reliably than ST itself. Is there some change happening for the locks? I saw the notice of changes coming for the SLGA Service, but that’s scheduled to be complete in December. Will the SLGA changes cause a failure in using this version of the lock driver such that I will have to switch back to a gerneric ST driver? That would be unfortunate, because Phil’s/Bruce’s driver provides far more information that I am using in Sharptools.
Anyone else experiencing strange results with Zwave locks?
Thanks. I do have one installed on my phone, but it’s not active. Also, I have several Zwave light switches, and they respond almost immediately.
I rebooted the hub last night from the web app, and the locks seem to be responding better from their own tile. But the reaction to the “Lock All” button in the SLGA tile in the Life section is still very slow.
I also have Schlage z-wave locks. I am using the standard z-wave lock driver. I don’t notice any delay. On the flip side, I have had problems with delayed actions with some zigbee lights. Sometimes up to 5 seconds between button press and action.
Since it’s working almost immediately from Sharptools and not from the mobile app, I’m guessing it’s something between the app and the ST cloud. The driver isn’t invoked until the command is received at the hub from the API.
Also, I believe Sharptools is likely hitting the public API vs the app which uses a private/Client API. That could make a difference.
The manual lock/unlock functions should still work. And changing settings would still work. What would change is a few things
when SLGA goes away, there will be no way to maintain lock/pin codes for locks using existing 3rd party drivers (without modifications)
the current Z-Wave Lock PH driver provides the name of the user who unlocks the lock via the lockCodes capability. Since they are deprecating SLGA, I expect lockCodes will be deprecated as well so that function will no longer work
existing 3rd party drivers would have to be updated to support the new lockUsers and lockCredentials capabilities that replace lockCodes and the presentation would have to be updated to support adding lock users and pin codes on the device card directly vs a centralized app. @rboy has indicated they have made the necessary changes and will time an updated release of their driver to the production release of the stock driver
What you would likely loose by using the stock driver is the ability to modify the Schlage settings of the lock in a convenient fashion. You could always switch back and forth between the 3rd party driver and the stock driver, but that typically results in loss of pin codes, but perhaps not in the new stock driver implementation. You could also use a 3rd party Z-Wave configuration driver like those that both Phil and Mariano developed, but again, not nearly as convenient.
I might take a stab at updating Phil’s driver to support the new capabilities and presentation, but it might be easier to take the Schlage settings customizations and re-add those to the stock driver to create an altogether new driver.
I’ve been knee-deep in my day job and stage managing a show and haven’t spent much time lurking around here but might have some free time in the upcoming weeks to tinker around. Will let know if I come up with something.