For all locks. Your solution would be SLGA or another third-party lock code manager. You can find options via a search in this forum.
Universal Enhanced Z-Wave Plus Lock Driver - v20231116
- (New) Added support for new Yale & Assa Abloy Biometric series and Z-Wave Plus (zw3) models
- (New) Added support for more sleepy locks (e.g. Popp Keypad)
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
@RBoy I just paid for the new license (having been a Legacy user), went through the steps on your page. Driver is loaded (did the refresh, features started to appear). I have a Schlage lock (BE469), but I don’t see the menu of options in your example screenshot. Just the initial page with toggle buttons. When I use the 3 dots and open settings, there are only four things shown. The first item just says null. The Schlage configuration options also says null. What am I doing wrong?
What menu are you referring to? You may be confusing routines/automation features with configuration options. Also make sure you’ve switch your driver to the new driver if you have the legacy and new one installed at the same time.
Ya I guess I assumed there would be more options in the device. I see now the options you showed are part of setting up routines. I will also double check that I don’t have both drivers loaded (I did start with the legacy, then changed to the new enhanced). Thanks!
Universal Enhanced Z-Wave Plus Lock Driver - v20231124
- (Enhanced) Improved support for Z-Wave Plus Popp Strike Lock (POPE 021501) with automatic relock and dry contact sensor (door open/close) reporting, including support for FLiRS and sleepy mode
- (Enhanced) Updates for new HubCore firmware
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
Universal Enhanced Z-Wave Plus Lock Driver - v20231127
- (New) Added support for TLJ Access Control locks (Deadbolt, Lever and Keypad) including reporting Door Position Sensor (DPS) and RFID card usage
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
its been awhile since i’ve been here. i’ve set notifications to be sent when my Schlage door locks are unlocked. notifications used to state the name assigned. now it just sends “Unlocked by Code xx”.
how do i get back to say the actual assigned name? does this have to do with me probably still using “legacy drivers” as opposed to having a paid subscription?
With the new architecture, the driver maintains the relationship between the codeSlot and the codeName. When you change drivers, those relationships are reset to the default of “Code XX” for each slot. You can change the names using Smart Lock Guest Access (SLGA) in the mobile app, the nameSlot command for the lock in the Advanced Web App, or the nameSlot command in the ST CLI for Windows/Mac/Linux.
I still have the old Legacy Driver installed but it’s not in use - does anybody know how to uninstall it?
You can delete drivers from the Hub section of the Advanced Web App or using the ST CLI.
Universal Enhanced Z-Wave Plus Lock Driver - v20231130
- (New) Added custom layout for Popp Strike Lock with option to set relocking time (1 to 59 seconds)
- (Fix) Fixed relocking issue with Popp Strike Lock
- (Fix) Fixed tamper reporting with Popp Keypad with cover is removed
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
I have a Yale Conexis L1 with the Z Wave Module, I was recently forced to move from the legacy drivers to the Edge drivers and am currently using the “Wave Lock PH Beta” driver. I’ve also tried the standard ZWave lock and also the non-beta PH drivers. Since switching to Edge drivers my door lock batteries are now going flat every couple of days, previously they would last months. If I disconnect SmartThings the batteries life is again extended. I’m guessing the drivers are polling the lock too often and wiping out the battery life. Would upgrading to the @RBoy driver possibly fix this issue?
I do not know if this is related, but with my schlage locks I once paired them without S2 security and they would go through batteries like crazy. When I reset them and paired them with S2 the batteries last forever. I do not have any explanation as to why this happened on my locks? I use rboy drivers in both instances.
Hmm we’ve been seeing poor battery life as well.
If the lock supports Z-Wave Plus, be sure that it is paired at the proper S2 security level as suggested in the other post. To verify, use the API Browser+ and check the details of your device. A properly paired device will show “NW Security Level ZWAVE_S2_ACCESS_CONTROL” or “NW Security Level ZWAVE_S2_AUTHENTICATED”. If it doesn’t support S2, it should say “NW Security Level ZWAVE_LEGACY_NON_SECURE”.
If all that looks good, I would suggest downloading the ST CLI to do driver logging for whichever driver you are currently using that might be associated with the battery drain. Once you have the CLI on your computer, use the command “smartthings edge:drivers:logcat”. You will be prompted for your hub and then a driver selection. That should show if there are a continuous set of commands being sent/received from the lock. Once you collect the logs, submit them in the topic for the driver you are using.
FYI, Phil’s released Z-Wave Lock PH driver has the equivalent function of his beta driver now.
19 Z-Wave Lock PH 58b24fe2-78dc-413c-bd11-ed386676ef9e 2023-07-11T11:59:28.79917092 c09d2a68-e32c-4366-a4fc-ea4731b96ec3
20 Z-Wave Lock PH BETA 59869ce8-ee90-4c26-b465-19b7b071d521 2023-07-11T12:00:03.303563971 c09d2a68-e32c-4366-a4fc-ea4731b96ec3
bep@debian12:~$ st edge:drivers:logcat
───────────────────────────────────────────────────────────────────────────────────────
# Label Name Device Id
───────────────────────────────────────────────────────────────────────────────────────
1 SmartThings Hub - FamilyHub SmartThings Hub 37a17c82-dfd0-4d9e-9b5d-cebc6e482acf
2 SmartThings Hub SmartThings Hub 2ca01359-7f67-469e-9887-172e72b0423f
───────────────────────────────────────────────────────────────────────────────────────
? Select a hub. 2
──────────────────────────────────────────────────────────────────────────────
# Driver Id Name
──────────────────────────────────────────────────────────────────────────────
1 b874bb3e-37ae-4c96-9ea4-65ef9ac1e2e2 Aeotec Door Window Sensor 7 ZWA008
2 caabad91-9ac2-4232-b14a-6f451301f1b3 Alexa Multi-Trigger v0.1
3 6342be70-6da0-4535-afc1-ff6378d6c650 Aplicaciones Virtuales Mc
4 c856a3fd-69ee-4478-a224-d7279b6d978f bose
5 e67c842f-49a5-4083-95f0-c8137ae3c2f6 Edge Counter Utility V1.1
──────────────────────────────────────────────────────────────────────────────
6 e120daf2-8000-4a9d-93fa-653214ce70d1 GE Z-Wave Motion Switch/Dimmer
7 5ad2cc83-5503-4040-a98b-b0fc9931b9fe GE Z-Wave Switch/Dimmer/Fan/Outlet
8 4eb5b19a-7bbc-452f-859b-c6d7d857b2da Harman Luxury
9 7beb8bc2-8dfa-45c2-8fdb-7373d4597b12 JBL
10 cd898d81-6c27-4d27-a529-dfadc8caae5a Philips Hue
──────────────────────────────────────────────────────────────────────────────
11 dbe192cb-f6a1-4369-a843-d1c42e5c91ba SamsungAudio
12 c21a6c77-872c-474e-be5b-5f6f11a240ef Sonos
13 0fd9a9a4-8863-4a83-97a7-5a288ff0f5a6 Virtual Devices V2
14 572a2641-2af8-47e4-bfe5-ad83748fd7a1 Virtual Switch
15 d9c3f8b8-c3c3-4b77-9ddd-01d08102c84b Wemo
──────────────────────────────────────────────────────────────────────────────
16 038a9312-66c8-4a30-9299-b346d57f28a9 Z-Wave Associator
17 7ca45ba9-7cfe-4547-b752-fe41a0efb848 Z-Wave Device Config Mc
18 2575f638-2ebb-429c-91a2-9bff827396a0 Z-Wave Explorer
19 58b24fe2-78dc-413c-bd11-ed386676ef9e Z-Wave Lock PH
20 59869ce8-ee90-4c26-b465-19b7b071d521 Z-Wave Lock PH BETA
──────────────────────────────────────────────────────────────────────────────
21 c2bd9557-7c38-4663-8c84-bf75d4740202 Z-Wave Sensor CS
22 f2e891c6-00cc-446c-9192-8ebda63d9898 Zigbee Switch
──────────────────────────────────────────────────────────────────────────────
? Select a driver. 20
connecting... connected
2023-12-08T21:58:58.670324858+00:00 TRACE Z-Wave Lock PH BETA Received event with handler capability
2023-12-08T21:58:58.685423108+00:00 TRACE Z-Wave Lock PH BETA Z-Wave command(0c116a2e) queued for radio transmission: CC:Door Lock, CID:0x01
2023-12-08T21:58:58.688215379+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: c51f9d0f-8e2b-4966-9644-6d5f5d889eeb [71] (Front Door Lock)> received command: {"args":{},"capability":"lock","command":"unlock","component":"main","positional_args":{}}
2023-12-08T21:58:58.689233254+00:00 TRACE Z-Wave Lock PH BETA Found CapabilityCommandDispatcher handler in zwave_lock
2023-12-08T21:58:58.690231608+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: c51f9d0f-8e2b-4966-9644-6d5f5d889eeb [71] (Front Door Lock)> sending Z-Wave command: {args={door_lock_mode="DOOR_UNSECURED"}, cmd_class="DOOR_LOCK", cmd_id="OPERATION_SET", dst_channels={}, encap="AUTO", payload="\x00", src_channel=0, version=1}
2023-12-08T21:58:58.697243171+00:00 DEBUG Z-Wave Lock PH BETA Front Door Lock device thread event handled
2023-12-08T21:58:58.700178254+00:00 DEBUG Z-Wave Lock PH BETA driver device thread event handled
2023-12-08T21:59:00.029507607+00:00 TRACE Z-Wave Lock PH BETA Z-Wave command(0c116a2e) transmit status: TRANSMIT_COMPLETE_OK
2023-12-08T21:59:02.913880250+00:00 TRACE Z-Wave Lock PH BETA Z-Wave command(3eb7602f) queued for radio transmission: CC:Door Lock, CID:0x02
2023-12-08T21:59:02.915922771+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: c51f9d0f-8e2b-4966-9644-6d5f5d889eeb [71] (Front Door Lock)> sending Z-Wave command: {args={}, cmd_class="DOOR_LOCK", cmd_id="OPERATION_GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2023-12-08T21:59:02.918768313+00:00 DEBUG Z-Wave Lock PH BETA driver device thread event handled
2023-12-08T21:59:03.375549521+00:00 TRACE Z-Wave Lock PH BETA Z-Wave command(3eb7602f) transmit status: TRANSMIT_COMPLETE_OK
Thanks for this, I have looked and it currently stating ZWAVE_S0_LEGACY, I need to find out if the original Gen 1 Z Wave module supports S2, otherwise I may have to buy the newer Gen 2 Z Wave module that definitely does. I’ll have a look at the ST CLI as that may help me figure out also, I need to do something as its costing me a fortune in batteries 
I have the Kwikset 916 smart code zwave deadbolt and am trying to use the keypad to disarm the SHM, I have the @RBoy universal zwave lock driver installed but don’t seem to have this option
Thanks! Was hoping to use the keypad on the lock like another alarm keypad vs just using the unlock to trigger. I do not want a manual unlock to disarm…