Yes I did not explicitly explain why I did not consider it. Let me add this to the post.
I used this device handler: https://github.com/ethayer/lock-manager/tree/master/devicetypes/ethayer/zwave-lock-reporting.src
He released a new version of his app and device handlers two months ago if you want to test it. I believe the notifications are still an issue. He mentioned he I going to post an update soon.
I used WebCORE to set up my notifications
This should never be required (rebooting the hub). I have never had to reboot a hub after assigning a Device Handler to a device.
Sometimes it does take time for the change in IDE to reflect on the Device when you open it in Things from the mobile app.
The way to resolve that is when you open the Device in Things, click on the Gear icon and then Save the Device. This will make sure that the device is indeed tied to the Device Type Handler that was assigned to it 
I updated my post to avoid misinformation. This is the part where I played with many variables at the same time and could have easily got confused on what was causing the issues I experienced. Thank you for correcting me!
More of just an observation
So many things happen and can go wrong on this platform, sometimes it’s hard to determine what the resolution to something is, especially if you are doing more than one thing at a time
Version 2 should be much easier to install (only 1 app), and doesn’t have the code99 issue.
It’s just not the official version yet, as I need to write an install guide for it, but it should be soon.
Good luck on your journey!
That is good news! Do you know if Lock Manager and Smart Lock from ST can co-exist? If yes, I will probably try lock manager beta2 right away!
They can co-exist, however changes made in SmartLock will be overritten by LockManager.
Example:
Create Code1 as ‘Emily’ in LockManager
LockManager will ask SmartLock to rename Code1 to ‘Emily’
Logs in SmartLock will show actions done by Code1 as ‘Emily’
Create Code2 as ‘Greg’ in SmartLock
LockManager will see an unexpected change in Code2 and delete ‘Greg’
EDIT:
Note, you do have to use the custom DTH at this point. There is a bug in the current SmartThings platform that makes the default DTH report wrong objects to the SmartApp. Using a copy and paste of the original SmartThings code in the IDE fixes this issue. Root cause unknown, likely SmartThings bug.
All necessary Device handlers are included in the beta-2 branch, including a special one for Yale to add more options to control various aspects of the lock.
Strongly considering this Yale 256 lock. Getting a new entry door shortly and since I have other access (garage door etc) I’m not worried about lockouts much as much as I do like the idea of no key for added security. Now, with that said, can anyone elaborate on the native app vs a paid Rboy app or other? Keeping everything stock, will I be able to assign codes, see status, and see who’s coming and going? I don’t need anything fancy, but I also don’t want to use an app that later in life when i’m old and not following Smartthings as much stops working. Wondering if this has developed/improved since this post started. Thanks.
You can use the native app to assign codes and see who’s coming/going.
For complete control and customization using an enhanced user code management app is better. If you’re using the RBoy App, we keep it up to date with ST’s platform and DTH changes on a regular basis and you can always contact our helpdesk if needed. The RBoy Apps user code management app works with the native app as well for viewing users/updates/history.
@mperceau-pub Please advise how exactly were you able to resolve ‘unlocked with code 99’ issue. Thanks.
@canuck certainly. The idea is to create a new device handler using the latest version of the smartthings zwave lock device handler, and then associate the newly created device handler with your device. Here are the steps you may take. There are more than one way to create a device handler ( from code vs github integration ). I am only explaining the “from code” way here, for its simplicity.
- go to https://account.smartthings.com and login
- go to the “My device handlers” tab
- click on “create new device handler”
- select the “from code” tab
- copy the code from https://raw.githubusercontent.com/SmartThingsCommunity/SmartThingsPublic/master/devicetypes/smartthings/zwave-lock.src/zwave-lock.groovy ( this is just the raw version of https://github.com/SmartThingsCommunity/SmartThingsPublic/blob/master/devicetypes/smartthings/zwave-lock.src/zwave-lock.groovy) into the textarea you see on screen.
- If you feel like it, you may edit the code to change the name of the device handler by editing “Z-Wave Lock” on line 17. For example you could call it “My Latest Z-Wave Lock”, to help differentiate this device handler from the stock “Z-Wave Lock” device handler.
- Also on line 17, you need to change the runLocally parameter from true to false. Not sure what this does, all I see is that you have an error preventing you from creating the device handler if you do not change this value.
- Click on create below the textarea.
- Now that you have created the device handler, you just need to associate it with your lock. I am assuming you already paired the device to your hub. To do this, go to “Devices”.
- click on your lock
- click on Edit at the bottom of the page
- locate the “Type” and change this value to the name of the device handler you created previously. User created device handlers show up at the bottom of the drop down menu.
- click on “Update” at the bottom of the screen.
This should do the trick, and allow you to use the latest version of the smartthings Z-Wave Lock device handler. This was the step that resolved the code 99 issue for me.
What’s your hub firmware version, its’ a bug in the firmware causing issues with local execution handlers. With the next firmware update it should fix itself.
I’ve been using User Lock Manager v4.1.5 for quite some time to manage some Lowe’s keypads for quite some time now. I just purchased a Yale YRD256. Would you recommend switching to the latest version of the app @jkp mentioned? I would need to still manage those old keypads.
So I’m pretty new to this, as in today years old. I’m currently using the ST locks app and would like to go about getting notifications as well. The instructions posted above is to resolve “unlocked with code 99”. I don’t think I have that issue. What are the necessary steps to add on notifications?
If you’re using the built in SmartThings SmartLocks app you should be able to see the history of codes being used from within the app itself under the History tab. It used to provide push notifications earlier but I believe that it no longer does it and I don’t think there’s no way to configure it from within SmartLocks.
If you have access to RBoy Apps, you can try out the Lock User Management (LUM) app which allows you to customize notifications (push and/or SMS) for individual users along with a host of other features. LUM is compatible with SmartLocks so you can use both simultaneously; review lock states, users/look at usage History through SmartLocks while creating custom actions, notifications and user schedules/types through LUM.