Hey there - I have a KwikSet smart lock (two actually) from Vivint. Vivint states this is a newer model of the 912. Should I see more in the control panel than this? Pics attached of both lock and control screen.
That’s a bug with the ST Smart Lock/mobile app. nothing to do with the device handler. Kill your ST mobile app and restart it and it will update itself or remove and reinstall the smart locks app.
Click on refresh. It’s working fine here. When your lock reports the capabilities it will automatically show up. Maybe your hub is having trouble communicating with the lock.
Should I just give it time? I tried refreshing with no success.
I have tried both of those suggestions multiple times. When I restart it reports correctly. Then it never changes again. It should change dynamically based on the locks status. Not useful at all in its current state.
If the status of the device is reported correctly on the things page, that’s where the device handler hands it off to the smart lock app.
What you’re seeing is a bug in the ST Smart Lock app/ST Mobile App/firmware. If the device state is showing correct inside the smart lock app but not on the summary page that’s an issue with the app.
Try to uninstall and reinstall the smart lock app or report it to ST support so they can fix it. The bug with the hub firmware/local execution smart lock app, when it interacts with a device handler that runs in the cloud the smart lock app doesn’t always update itself properly.
Edit: we’ve also reported the issue to ST.
Depends on how the lock reports itself to SmartThings. If it reports the MSR as a Kwikset lock you may see a few more tiles pop up once the lock responds to the capabilities discovery request. If it reports itself as a Vivint MSR or if the firmware in the lock doesn’t respond to the capabilities request then you may not see any more titles.
You can PM me the logs from your IDE Live Logging when you click on the Refresh tile or email it to our support desk and we can check out what your lock is reporting back to ST.
Hi RBoy. I recently purchased an August Pro. I was able to modify the standard “zwave lock” device handler to report the lock as a contact sensor in order to be able to manage door open/close events for SHM. I would like to do more such as use the method of locking to switch to away. Does your handler for August provide info regarding keypad vs manual, any info regarding which user/slot opened/closed, etc? Anything beyond door open/close that would swing me to sign up?
thanks! Jason
Sent you a PM. Much appreciated!
@RBoy is that something that I can do as well (PM logs)? The Yale functions are still not there and now the one touch lock doesn’t work on the front door which is necessary for nursing coverage that leaves during shift change.
That an ST hub pairing error it’s not able to communicate with your lock properly. Reposition your lock to the hub and also reboot the hub.
@RBoy any ideas? All I have is this:
That isn’t our device handler. Our device handler will look like the images on this post (the tiles may be blank based on your locks capabilities but the location will not change).
I downloaded it direct from your website. But I will remove all of the code reinstall and see hat happens.
I add / remove the the over ten times. Luckily and finally added without error
Now I can remote my lock
Video link
2 Likes
@RBoy well this is my sheepish response - I had copied the SA code into the DH so it must have been using the default basic Z-Wave lock DH.
I did figure out though, that I could log into the web and manually change the device type, so when I selected your DH everything started populating correctly.
Question - would you be able to state whether the code is the SA or DH in the first paragraph of the code? I can’t imagine I am the only one that does this…but if I am than wow I have issues.
1 Like
Attempting to update from v3.05.01 of Universal Z-Wave Lock Device Handler to v4.00.00 in use with my Schlage BE369:
I got a list of 127 Groovy compilation errors on clicking “Save” after pasting in the new code in IDE.
Here’s the first three errors (click arrow to reveal)
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
script_dth_metadata_7fb2d32e_4f69_414c_a282_5b94c9b0fada: 1954: The method with default parameters “java.lang.Object setCode(java.lang.Object, java.lang.Object, java.lang.Object)” defines a method “java.lang.Object setCode(java.lang.Object, java.lang.Object)” that is already defined.
. At [1954:1] @ line 1954, column 1.
def setCode(codeID, code, codeName = null) {
^
script_dth_metadata_7fb2d32e_4f69_414c_a282_5b94c9b0fada: 13: Repetitive method name/signature for method ‘java.lang.Object clientVersion()’ in class ‘script_dth_metadata_7fb2d32e_4f69_414c_a282_5b94c9b0fada’.
@ line 13, column 1.
def clientVersion() {
^
script_dth_metadata_7fb2d32e_4f69_414c_a282_5b94c9b0fada: 362: Repetitive method name/signature for method ‘java.lang.Object turnOptions()’ in class ‘script_dth_metadata_7fb2d32e_4f69_414c_a282_5b94c9b0fada’.
@ line 362, column 1.
private turnOptions() {
^
The update instructions stated “For best performance please exclude and re-pair the lock after upgrading the code.” so I didn’t exclude my Schlage BE369 prior to updating the DTH code.
Steps I had to take to get myself out of this pickle:
- In my SmartThings mobile App, disabled / removed all SmartApp connections to the lock device, including removing both Rboy’s Schlage Lock Alarm Mode and Sensitivity Change and Monitor SmartApp and Door Lock Code User Management with Unlock Notifications, Advanced Scheduling and Automatic Lock/Unlock SmartApp.
- Excluded my Schlage BE369 from my hub’s Z-Wave network
- In IDE > Device Handlers, removed Universal Z-Wave Lock With Alarms
- Full fresh install of Universal Z-Wave Lock With Alarms Device Handler v4.00.00, and updated Door Lock Code User Management with Unlock Notifications, Advanced Scheduling and Automatic Lock/Unlock SmartApp code to v6.01.01. Schlage Lock Alarm Mode and Sensitivity Change and Monitor SmartApp was already v1.02.02 so I left that alone.
- Paired my Schlage BE369 (using “Add a Thing” in SmartThings mobile app) and set up all codes, settings, etc. again. Checked and everything seems to be working as normal.
- Had a shot of whiskey.
This is not a complaint, just a user report. Hope it helps.
1 Like
My MSR has a number but I am not seeing the Doorsense. Where would I see it? Under Things?
Thank you very much for your feedback Keith. You’re correct, this would be the ideal way to setup the new handler for best performance.
I did take a look at the issue you had reported, it appears to be a copy-paste issue. Somehow the old code and the new code were both merged in the same handler leading to the “that is already defined” error message when you tried to save it.
If folks are looking to upgrade instead of doing a clean install, we did come up with an alternative method which is a little easier than a clean install:
- In the IDE → My Devices → Click on your device → Scroll down and click Edit → modify your lock device to use the standard “Z-Wave Lock” device handler
- Upgrade your RBoy Universal Enhanced Z-Wave Lock code in the IDE. Don’t forget to click on
Saveand thenPublish - Go back to your device in the IDE → My Devices → Click on your device → Scroll down and click Edit → modify your lock device to switch to the upgraded RBoy “Universal Z-Wave Lock With Alarms” device handler.
With this procedure you can avoid the click on Configure/Save steps as when switching device handlers SmartThings automatically does that step for you. Plus it avoid any issues with “caching” old code by the platform.
We’ve also taken some feedback included the words “DEVICE HANDLER” on the first line of the code so that folks don’t accidentally publish a device handler in SmartApps or vice versa.
I hope this helps.
5 Likes