I’m looking for the ability to create routines that act differently based on the user code used to unlock. It seems like the beta edge driver will do this, right? Would you recommend switching from your main driver to the beta driver now?
I can wait for the beta changes to get rolled into the main driver, but I’m trying to assess whether you think you’ll actually have time this month, or if it might be later (or never) given your switch off of ST.
Yes, the beta driver exposes codeName as a trigger in Routines. I’ve been running the beta version since he published it in late January without any issues.
You can also use sharptools.io to write rules that can take actions based on codeName if you have the premium service.
Okay, I’ve switched to the beta driver and it is working well. It was simple to switch over and didn’t lose my code names. I suppose if the beta driver does get migrated to the standard driver I can easily switch back if necessary.
Interesting! I’ve been reluctant to switch from the v1 Drivers to the Beta Divers because my Code Names are so extensive across multiple locks/locations and I didn’t want to lose them (and have to type them all back in).
@Puzzling Are your Code Names “stock” (ex: Code 1, Code 2, etc.) or “custom” (ex: Bob, Tom, Nancy, etc.) ?
@philh30 You had mentioned a while back that switching to the Beta Drivers would cause the Code Names to be reset. Have the Beta Drivers evolved to retain the Code Names? Are you getting close to rolling the Beta Code into the Main Driver?
Yes, I have custom code names. I had to retype them once when I first switched from the stock driver to Z-Wave Lock PH. But switching from that to Beta didn’t affect the custom names.
I too was going to wait for the update, but the driver switch is so easy, I just opted for that. And can always switch back if it ever gets updated.
You can get the lock code names and slot associations from the ST CLI using devices:component-status. If they get reset, you can then re-add them using device:commands:nameSlot or devices:commands:updateCodes.
lockCodes "{\"1\":\"Bruce and Teri\",\"2\":\"Gladys\",\"3\":\"Sean\"}"
Won’t help on the transition from DTH to Edge (obviously), but it is certainly useful for backing up your codes periodically if you have more than a few programmed.
Hey guys, sorry for the noob question, but if i switch the driver from stock, to phils, will all of my routines associated to that lock be erased?
If you are running the stock Edge driver and switch to Phil’s, you will not lose your Routines. His driver is based on the stock driver and has all the capabilities of the stock plus more.
Your lock code names may be reset since the codeId to codeName relationship is maintained by the driver. Also, use his beta driver since it fixes an issue where lock code names are reset and exposes the code name used to unlock the lock as a trigger in Routines.
Finally figured out how to get my Schlage BE469NX off the old Device Handler. Got this driver set up but my device screen only shows its status and battery power. I don’t even have a settings option in the three dot drop down in corner. I verified that I have the correct driver. Am I missing something?
Sounds like you are running the stock Edge driver not this one. Please go to the API Browser+, select the Device Details and post the output here. I’m guessing your specific fingerprint may not be included in the driver so you’re falling back to the stock driver.
So, while you’re using Phil’s driver, the fingerprint shows the device didn’t pair properly to your hub so it defaulted to the base-lock profile which only has lock status and battery. I’d suggest that you exclude the lock from your hub and then do a factory reset on it before re-adding it. Until it pairs with the proper fingerprint, you won’t get a profile that exposes the Schlage specific settings.
I also recommend that your install Phil’s beta driver as it fixes a bug with lock code names resetting periodically and exposes the unlock code name as a trigger in Routines.
Thanks. I got it working and love the features. One more thing, most of the features were grayed out, that is until I use them in a routine, then they became useable. This isnt a big deal as I just ran a few routines to make them useable but for others that may have this problem.
There are a lot of capabilities exposed in his driver and it takes a few refreshes on the device panel to get them all populated from the lock. Setting them in a Routine is another way of getting them populated.
Glad you got it working!
@Starsetter this may be more than what you’re looking for, but I had outlined a method of making the Schlage Alarm work in Home Monitor
@philh30 Would it be possible to add this Kwikset 910 to your driver?
type:4003
mfr:0090
prod:0003
model:0236
Thank You!
Hi
@philh30 With Edge Driver “Z-Wave Lock PH BETA”, is possible to create a routine that is activated when I locked with the keypad´s lock?
Yes, it’s possible. What specifically are you looking to do?
