When your Alarm mode is set to Off, the sensitivity is going to show as unsupported. Toggle your alarm mode to an active mode and you can see/set the sensitivity.
The code name/id support for routines can only be done using custom implementations as I had mentioned earlier (despite what others may claim). We’re working on those enhancements (and more). However if you’re using the rules api or external apps like sharptools etc then you should be able to create rules with names and id’s without any issues from the lock capability, just the SmartThings routines/scenes need custom implementation as they aren’t sophisticated enough to access that embedded information at this time.
1 Like
I was using the LUM for the last 4 years on 2 locks, Obviously when they made the change eralier this year I lost access. I did not realise the change was coming as I have never had an issue with the setup and never logged in to the site to find the update. Once I noticed I was unable to get access to the codes, alerts etc I started to mess with the program. I honestly cant say what order I followed and when I did what but at some point I ended up deleting the app from my system. I founfd this forum and kept watching for updates. I was still able to use the stored codes on the lock but didnt have access to do much more. I recently checked back and saw there was a beta version out and decided to try that. Once I installed the drivers I was able to get more access to the lock, but the code entry option said unsupported. I was at least getting notifications that some users were unlocking the door some only said code number unlocked the door. I had some time last night so i decided I was going to remove the lock from smarthings, factory reset and then load it back with the rboy drivers. after messing around for a while I was finally able to get it installed and the option for code entry was not selectable. I was unable to find anywhere to set codes though. I tried switching to the default drivers which gave me lessoptions and back to rboy drivers and now the code entry option says unsupported again. Is this due to the drivers being a beta? Or am I missing something? my lock is a SCHLAGE BE469ZP CEN 626 Connect Smart Deadbolt With Alarm Inbuilt. I was able to program codes in manually on the lock itself and each one sent me a notification that it was programed into the lock so some things are working.
1 Like
When it says unsupported that mean the lock didn’t respond to the “feature discovery” request. Most likely it’s due to packet loss since your model does support that feature. Do a zwave repair and then pull down on the device page in the ST mobile app to trigger a refresh and it’ll eventually show up when the lock responds.
1 Like
The ST app has an application called Smart Lock Guest Access (SLGA) that can be used for programming codes. If it’s not on your favorites tab, check on the Life tab. If it’s not there as well, use the + to add it to the Life tab and you can then also add it to your Favorites tab.
Once you have it available, click on the app. It should display your lock and it’s current lock status. Click on the drop down arrow in the upper left corner and you can select Lock codes which will lead you to the programming dialog.
SLGA is nearly completely useless. One lock at a time and no visibility into the code after it’s set, no unlock actions or differentiation by code used. It barely functions to set codes, really slowly. We really need the replacement for LUM from rBoy and I patiently hope and wait.
I completely agree. Being in Australia, I don’t even have the choice of SLGA.
I’m going to try some of the options Posted here but not being too technical, I hope I don’t mess it all up. Will try on the laundry door just in case.
If someone has a step by step, I’m sure there are a lot of us in Aus who would really get some value from it.
Using a Yale Assure lock with zwave module connected to SmartThings and rBoy’s LUM.
thanks everyone…Had been using rBoy’s LUM but was unable to use SLGA as it is not available in Australia. Used the info here and on the seam thread, and was able to connect by ST account to Seam quite “seamlessly”. I did notice, however that the two consoles, console.seam.co and dashboard.seam.co do not synchronise, so whatever is created in one does not show up in the other. I followed the links to the dashboard and it had a very different view that what was specified early in the seam thread but was able to figure it out fine… I am very happy that I can now create codes and remove them easily from this dashboard, but I do notice that under the Activity section for each lock, it shows no activity, even if I use one of the test codes I set up. I guess it’s not a huge deal for me as it is my house not a STR or AirBNB, but if I don’t get notified that a code is being used to open the door like I did with LUM, it would be good to log into the dashboard and see the code being used there… right now, it seems that any of the access codes could be used and there is no record of the activity.
That being said, I am grateful for @sybohy for making this available for us… at least I can manually create or remove codes without going to the physical lock.
@maddie @RBoy Any updates? We appreciate all you all do. Would be helpful if there was more of an update section on your website. I know timelines can be tough, but any info is better than no info. Thanks!
How/where did you get the new code?
Not sure what you mean? I bought an original license. Logged on to Rboy’s website w/ my credentials and enrolled for the new Device Driver.
I’m logged in as well, but don’t see where to enroll for the new Device Driver. Thanks for the quick response btw.
Click on this link to login to RBoy’s site, and there will be a link in the first bullet point where you can enroll and install the new driver.
The new driver is for replacing the universal device thing handler, not lum. Correct?
Correct. Just a driver, not an app.
1 Like
I have installed the new RBoy beta drivers for my Schlage Z-Wave Camelot door lock. It shows the following controls:
- Lock State: Locked
- Code Entry: Enabled
- Audio: Enabled
- Auto Lock: Enabled
- One Touch Lock: Enabled
- Alarm Mode: Off
- Tamper Alert: Not Tampered
- Battery: 88%
I have LUM still installed from before (v07.15.05) , and reconfigured to work with my new Schlage Door Lock device. However, I still see the “No network connection” error when I try to enable LUM.
How do I get LUM to work with the new RBoy beta drivers?
Thanks!
You don’t. All Groovy SmartApps were shutdown in January of 2023.
OK … So, are there instructions somewhere on how I use the new RBoy beta drivers to manage user access to my door lock?
The beta driver and the paid production version offer different features. Lock code slot IDs and names are not exposed for Routines in the beta version for example.
You should refer to this topic [RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Ke starting at post 1591 for information about the different driver capabilities. There are also some examples of Routines using the paid production version of the driver.
Adding codes in the ST app is done using the Smart Lock Guest Access (SLGA) tile. It offers only adding/deleting codes with none of the features that were offered in LUM.
Oh, great. So after studying up for days trying to figure out a way to program my Schlage lock to restrict access to certain hours of the day, and being pointed in the direction of Rboy, I paid for the Rboy drivers only to discover that they really don’t do anything more than the smart things app already does! (Not only that, I signed up for a $6 monthly fee for Rboy, and have to realizing this was a waste of time dead end that there’s no way to unsubscribe, apparently, on the Rboy website.) What am I missing? All I want is a way to restrict user access to my building based on time of day. Is there an app out there that still does this? Can anyone help me? And I’m not a home automation techie so plain English would be a big help. Thanks in advance.
It’s annual.
1 Like