Not seeing any issues here, just remember that the name is case sensitive (for now) or use the a slot id
I’ve tried multiple routine conditions and only “lock state” will trigger a routine. For troubleshooting purposes, I have setup single condition:
- user name: fails
- user slot id: fails
- action type: fails (manually/keypad/remotely all fail)
- lock state: successful
Adding another condition besides lock state fails: Manually + locked or Manually + Unlocked.
I have also tried creating new routines after switching to beta driver to rule out any oddness with the routine itself.
Then the lock either isn’t reporting that information or the packet containing that information is getting lost in the mesh. There are two separate events sent by the lock. One is generic and other contains everything else that the driver uses for routines.
Just going to say that my experience is exactly the same as @Perigord. Only lock state seems to be causing routines to activate. Any other option results in the routine not activating.
If it helps, I’m using the Beta/legacy driver with Kwiset 910 locks. I have 5 locks at three different locations, all with the same results so I doubt all my meshes are to blame.
I’d suggest doing driver logging using the ST CLI using the command “smartthings edge:drivers:logcat”. You will be prompted for the IP address of your hub and then select the lock driver. You should then do a series of lock/unlock events and see what the lock is returning to the driver and what the driver is doing with that information.
The beta version of the Universal Enhanced Z-Wave lock driver doesn’t have support for using code slot or code slot name in Routines. Only the paid version of the production release of the driver has that support.
Adding that I never had a problem with the old rboy device handler and that another edge driver has similar functionality does work as advertised. Only change to my network is movement to edge. I am happy to work through any troubleshooting steps, but am not sure what they are. I doubt (but not ruling out) multiple locks that previously functioned properly are suddenly having network/mesh issues, especially since other sources indicate proper functionality.
It’s not clear to me which driver you are actually using at this point. Are you using the stock ST lock driver, the Rboy beta driver, or the Rboy paid production driver, or something else? If you are using the Rboy beta version of the Universal Enhanced Z-Wave lock driver, it doesn’t have support for using code slot or code slot name in Routines. Only the paid version of the production release of the driver has that support.
If you are using the paid production version and it’s still not recognizing code slot or code slot names in Routines, then I’d suggest doing driver logging using the ST CLI using the command “smartthings edge:drivers:logcat”. You will be prompted for the IP address of your hub and then select the lock driver. You should then do a series of lock/unlock events and see what the lock is returning to the driver and what the driver is doing with that information.
I am using SharpTools for this. Rule deletes codes at 5 pm and adds them back in the morning, and only on weekdays.
1 Like
Hi. I’m currently using a Yale YRD210 lock with a Z Wave lock edge driver. It currently only allows control and state detection of Lock and unlock. It does not recognize if it’s unlocked via pin code using the keypad. Can I clarify if the pin codes work and what other functionalities are added when I use your drivers?
My initial post in this thread called that I’m using the beta driver, v2023-06-02. It would have been great for @rboy to specify that the beta version of the driver I am using is working as designed and does not do much, if anything, with name/codes. Guidance in the thread is ambiguous as best. A comment in May said beta driver reports name or slot # but routines can’t use them). It seems as though the beta driver does not have “feature parity with DTH,” although I’m sure there is some hair splitting between what the legacy device handler did vs. the smart app.
Net is I need to pay to play.
Newer/Paid driver performs the functions I expected from the beta driver. @RBoy - Please be clearer on what the community can expect from each. I was clear in my initial post I was using the beta driver and told that my lock was not sending all data (and possible mesh issues). The response was lazy at best, as all I really need to be told was to purchase the newer driver, which has its own frustrating nuances. +1 for delivering the functionality I currently require and -5 for the goose chase.
4 Likes
Hi, @RBoy - I installed the legacy LUM migration drivers through your website, and I am confused on how to get the old LUM functionality that I previously purchased with these new migration / beta drivers.
When we go on our vacations (it’s nice to finally be retired!), we activate temporary time-expiring door codes for our pet sitters. I would receive notifications from Smart Things when the pet sitters entered and when they left our house. We have had to fire some pet sitters in the past who did not provide the services that they claimed they were providing.
We also have our neighbors stop in during our vacations to check on plants and other home stuff while we are vacationing.
Are there any instructions on how to enter temporary time-expiring door codes and get some form of Smart Things / SMS notifications of guest (or neighbor) entry/exit with the new beta/migration drivers?
Thanks!
LUM is a legacy Groovy app and all Groovy apps stopped being supported in January 2023. You can no longer use LUM.
There is no native ST capability for time based user lock codes and Rboy has not released a replacement for LUM in the new architecture.
Some people are using other third party solutions that support time based codes like Seam or lockmanager.io. Others are using Sharptools to add and delete codes at specific times to emulate the behavior formerly in LUM.
As far as notifications go, you should be receiving ST app messages if you have Smart Lock Guest Access (SLGA) installed. For SMS notifications, you can use ST Routines to create customized texts for specific users, if you have the paid driver that exposes the lock/unlock code slot name. You can use a 3rd party rules engine like Sharptools and still send customized messages if you have their premium level that allows access to event data via variables.
And some of us use Lock Code Manager (LCM) in Hubitat. 
1 Like
Thanks, @bthrock - I will check Hubitat out on Monday, when their offices are open.
Your best source for information is going to be the Hubitat Community Forums.
To be clear, in order to use LCM, I run SmartThings and Hubitat in parallel. The majority of my devices are paired to my SmartThings hub using Edge drivers, then replicated in Hubitat via HubiThings Replica, which allows me to take advantage of the strengths of both systems, one of which is—for now, at least—LCM.
My wife strongly prefers the SmartThings UI and sorely misses RBoy’s LUM, but Hubitat’s LCM provides the functionality we need until that is once again available. I’m grateful to the developer of HubiThings Replica, who did a lot of work to get the two systems to work together.
While I know people have different opinions on RBoy’s new subscription model, I plan on supporting it so that he has an incentive to continued developing the driver and LUM and, hopefully, get them at least close to what they once were. For me, personally, I never thought my modestly priced lifetime license would or should apply to an entirely new ecosystem that forced the developer to start all over again. Others see it differently, and I respect that. I’ve just made my own choice.
2 Likes
@pmjoen Me too. I’m a newbie to all this. But that’s all I’m after. I’ve had smart things app controlling my Schlage Locks for years. But I need a way to restrict access to the building to Daylight hours. I’ve downloaded the Rboy Universal zlock driver. But I don’t know what to do after that. Any advice from anyone on how to accomplish this simple task would be terrific. Thank you.
I did read about hubitat the other day. And I actually installed the app on my phone. But I didn’t think I could run smart things through hubitat, or vice versa. I thought I had to get a hubitat hub? I didn’t know anything about replica. I will cruise around the habitat forums and see what I can see and learn. Any advice from anyone who’s reading this would be appreciated. I just want to restrict my building so that users with codes can only unlock it between 8:00 a.m. and 5:00 p.m. Schlage locks.
To use HubiThings Replica, a Hubitat Hub is required.
