Two questions about the Kiwkset 916, First of all, if the lock is manually locked or unlocked, that doesn't update in Hubitat. Is there some way to make it refresh it's status?
Second issue is in the Lock Code Manager app. I set two codes in the app. Both are stuck on Job Pending, however the code for the first user I entered works, but not the second.
Yes. The only way it won't is if it's a non-zwave plus module then you need to install the poller app.
Delete all codes on the lock through the lock itself, then re enter them on the device page itself. Then use LCM..
Did you pair the locks with the hub right by them? Were they just recently paired?
Both issues sound like the lock and hub aren't talking to each other properly. I'd recommend pairing them with the hub right there (say within a foot or so). You can remove the inside module from the door and take it to the hub to do so. After pairing, the hub will poll the lock for all the current codes. Wait for that to finish. Set your lock codes and verify the jobs show complete in LCM. Put the lock back on the door. Toggle the lock and then immediately do a Z-Wave repair for just that device. See if things are better.
You should clarify if it is Zigbee (1.2 or 3.0), Z-wave, or Z-wave plus. Mine are Zigbee and report status immediately.
I deleted the codes in the lock, then re did them in Hubitat under devices, and it shows up in lock code manager. But at that point, lock code manager seems pointless.
As far as pairing, it was just installed last night, so yes, a new install. But the door is about 15 feet from the hub, and it does respond to the button in the app. I also put a virtual button with a rule to refresh the door status, and that is working. Not ideal, but a temporary work around.
The lock is a Z-Wave plus.
When I use the Z-Wave poller app, there is no option for locks. I only have options for dimmers and switches.
The Z-Wave Poller app is not needed, nor intended, for Z-Wave Plus devices. 
Please be sure to click CONFIGURE on the Lock's Device Page on your Hubitat Hub. The CONFIGURE command will not provide any visual feedback. Behind the scenes, it will tell the Z-Wave Plus lock how to report status updates back to the Hub. This may help to resolve the issue of the lock not reporting its status changes automatically.
Pair it as a Generic Z wave lock and it will work great.
The 916 is also sold as a Zigbee device so the drivers can get confusing. The lock will try to pair as a Schlage, but that won't work.
@calinatl - Thank you. That solved both issues. I didn't catch the fact that it did pair it as a Schlage lock. I switched it to generic Z-Wave, and it now it updates in about 3 seconds, and the lock code manager app works.
Well LCM is more for doing multiple locks at once as well as scheduling..
Hmm... 3 seconds is a long time to be honest. Can you post your z-wave details page in its entirety?
After changing the driver type, did you remember to press CONFIGURE on the device details page for the lock? Any time a driver type is changed and saved, it is important to click CONFIGURE to make sure the device is 'configured' to report its status updates back to the hub correctly.
The delay time is not an issue, and it's no different than any other device that i have. If I turn a switch on at the wall, it takes a couple seconds for that to update on my phone.
Lock code manager is working great now too. I was able to add other users and codes with no problem.
Do you have any ghosts in your mesh?
I'm not sure how to check for that. But, all of my other devices take a second or two to show a change of state in the app if they've been pushed or activated at the device itself, so this is not functioning any differently.
Post your z-wave details page in it's entirety (use windows snip)
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
