For future reference see @RBoy original description. Any code set at the lock and not through software appears as “*”. Only way to get code to appear is to delete and re–add through software as you found out.
It does not change any user names or codes. It just reloads the existing codes and then they show up in the device table. I had a lot showing as “*” due to loading the codes directly at the lock when I was having driver issues. Deleting and re-adding via SLGA resolves the problem so now all codes appear with the correct user name.
1 Like
I am familiar with the capabilities of the RBoy driver. My specific question was whether the limitation on the BE469 (which is not present on the BE469ZP) was a limitation of the hardware, firmware, or driver, a question that both @h0ckeysk8er and @rBoy answered nearly three weeks ago. The reason for my interest was that I have been debating whether to revise the existing HubiThings Replica driver so that it works with the newer features and capabilities in RBoy’s driver.
For clarity for anyone else who might see this, the above statement is meant to apply only to the Schlage BE469, not to the BE469ZP, from which the updated driver can read codes that are set on the lock using the keypad. (These are the only two models I’m currently familiar with, so I can’t comment on any other locks.)
Is this still the only way to accomplish lock code scheduling? Is there not a way to do this using only routines?
I wouldn’t say this is the only way, but I haven’t found a better way. I think paying for a full SharpTools account would be easier and keep all the logic in one place, but my preference is allowing my users to just use the ST app without having to worry about a second interface. I think @RBoy is still working on LUM but (as far as I know) nothing firm has been announced so it could be available tomorrow, it could be never. I don’t think lock code scheduling is possible with just routines at this point.
We’re actually working on building scheduling into the driver so it has local control and doesn’t need the cloud. Working through some technical issues with edge and the UI.
We’re also testing pushing scheduling onto the lock itself so it can work without the hub but can’t promise this one as it highly dependent on lock capabilities.
2 Likes
I was a previous Lifetime License holder… did not see a way to indicate that at all, or receive any sort of discount for migrating to the new license type… so it’s apparently $7.99/year, which is still very reasonable.
How do I find the non-Legacy driver channel? Is it the one automatically presented when you log in with the new license credentials? Are both drivers named “Universal Enhanced Z-Wave Lock”? Very confusing and unclear process and website, to be honest… and I would consider myself an advanced user.
The legacy migration driver is only available via the migration faq page. The driver and channel name both contain the word Legacy
The latest driver is available when you click on the driver name. The channel and driver name do not contain the word Legacy.
While it’s possible to have both drivers installed at the same time it’s not recommended to have a smoother pairing process.
Hello RBoy, I have a Schlage BE469, not the ZP. I am trying to understand what I will get by purchasing a yearly license versus just using the “legacy” driver. One thing I really like would be to see the code that is assigned to a user, but I believe that is a device limitation. Thanks, Chris
See this post for the starting list of new features and then every other release post which adds more. There are no planned updates for the Legacy migration drivers as they are now at parity with the groovy DTH’s.
For Schlage non-ZP models (BE469, BE468 and FE599) you can see the codes assigned to the users/slots on the device page with the new driver when they programmed through SmartThings (SLGA, Advanced Web App, SmartApps etc), it just can’t read them back from these 3 locks models when the codes are programmed directly on the lock.
Thanks for the clear explanation. That’s what I wanted to know. If I set the codes through the “legacy migration” drive and update to the newer one, will it read the codes I set or will I have to enter them in again?
Sorry, one more question - I used to be able to “disable” a code but leave it in the lock or LUM - is that a feature that might come back in the new driver?
- Every time you “change” a driver SmartThings will wipe all information stored by the driver clean so you’ll need to re-enter everything again
- That’s an app feature but we’re working on seeing if it’s possible to make it a driver feature in future
Hi, The old platform LUM had an option for auto-lock to set the amount of time before it relocks. Up to 3 minutes if I remember correctly. Is there a way to do this now with RBoy Edge driver? (I didn’t see one on Advanced UI) Or maybe this can be added in the future?
My lock defaults to 30 secs which is not always ideal.
Use Routine for that. I am showing you 2 options for time delay, for IF and/or THEN. Use any you like or find that works better for you
Universal Enhanced Z-Wave Plus Lock Driver - v20230827
- (Fix) Some Yale lock models unable to control Audio features
Please make sure that your lock is within 20ft of a buffering device/repeater for best performance and reliability.
NOTES
- This version of the enhanced driver is only available via the new platform Drivers license (refer to website for details). If you have an active subscription, the new driver will be automatically pushed to your hub within 24 hours
- Refer to the previous release notes for more driver details. New features are not available in the Legacy Migration drivers.
- See the first post for a full list of available features by lock/model
Copyright (c) RBOY APPS
Thanks Milan I will give this a try. Hopefully this capability can be included as a setting in a future driver or app release as it was on the old platform though.
Hi, @RBoy got your driver the otherday as I thought it might do something ive wanted my lock (YALE CONNEXIS) to do for ages…
Basically get the app to tell me who has unlocked door via their fob/card etc…
it does it but via ‘code 1’, ‘code 2’
How can i rename these to be actual names?
i can get an automation to say ‘code 2’ has unlocked door and message me that code 2 is Jack Jones or wotnot, but Id like to change the actual code or ID
im sure its been answered, but this thread is mahoosive!
You can do it via the SLGA app (if it’s available in your region) or via the Advanced web app using the nameSlot command. See rboyapps.com/migration for more details
In addition to Smart Lock Guest Access (native to SmartThings), you can set the code and name using the Rule Engine in SharpTools if you’re looking for an automated approach. SharpTools has a setCode command which has arguments: [slot, ‘code’, ‘name’].
2 Likes
Universal Enhanced Z-Wave Plus Lock Driver - v20230925
- (New) Added support for new Yale & Assa Abloy Z-Wave Plus models
- (Fix) Some Audio controls for some Assa Abloy models
- (Fix) Improvements for latest hub core edge firmware update
Please make sure that your lock is within 20ft of a buffering device/repeater for best performance and reliability.
NOTES
- This version of the enhanced driver is only available via the new platform Drivers license (refer to website for details). If you have an active subscription, the new driver will be automatically pushed to your hub within 24 hours
- Refer to the previous release notes for more driver details. New features are not available in the Legacy Migration drivers.
- See the first post for a full list of available features by lock/model
Copyright (c) RBOY APPS
2 Likes