So i was super sad to find there was no zigbee integration with the kwikset locks (I bought the āwrongā lock). So i figured iād take a stab at this.
Iām currently using this with the 910 kwikset smartcode lock (i tried to make it semi-generic): device type
things are pretty rough right now. but it locks, unlocks, reports battery status, temperature (whaaaat?). I donāt think its properly updating status 100% of the time, so i wouldnāt recommend relying on it for reports of lock/unlock status 100% yet.
Iāve only spent a few hours on it so far. Iām sure iāll make frequent updates soon. Let me know what your experience is.
click on the āconformity documentā for the PDF
I got the proprietary control4 version by accident so im still waiting for the lock. However once I get it Iād love to collaborate on the ST device type. I see the github so Ill do that once i get it!
@sebirdman Just sent an email to the Kwikset product manager requesting their zigbee implementation information! I have been using the device type and it works well for the basics! I am trying to get up to speed with groovy, ZCL, device type programing.
@ajd394 awesome! let me know what they say. I think the main things to get working would be changing the lock passcode remotely and a way to push updates to smartthings instead of pollling for status.
I have that same Control4 Zigbee Kwikset lock that I have used with Control4 for several years and I would ālikeā to switch to using this lock with ST. Iām not clear from your post, did you found out this Control4 version was incompatible and exchange it for a āgenericā Kwikset Zigbee lock that does work with ST? Any idea if I am just out of luck trying to use the Control4 Zigbee Kwikset lock?
I was hoping to use the DeviceType by sebirdman to try to make this lock work with ST.
@bfmorgan i returned the c4 version without testing it. I would be interested to know if it works with this device type! I did some quick research to understand what make c4 zigbee different at the application layer but i is unclear. I wouldnt be surprised if they were the same/similar device.
I saw the device type code by sebirdman on github, but I did not have any idea what to do with it. I did a quick look at the ST developers info and saw the explanations of building apps and device types. I built the sample app to control a light from a door open/close switch and it worked fine with a light on my system, so I did the app correctly.
But for the devicetype by sebirdman, I could not see if there was any way to access it so I just did a copy and paste into a newly created empty devicetype on the ST site. But I am not quite sure on how to install it. When I go to install, the options are āvirtualā or one of the (non-lock) devices that I already have installed.
I thought that I needed to have a devicetype on the system (āinstalledā somehow) ābeforeā I can pair my lock with the ST hub. So Iām not clear how I am supposed to load the devicetype since I seem to only have options to install it for devices already on my system or for a āvirtualā device.
Am I missing something about the process of installing a devicetype?
Once youāve copied the code in and hit āsaveā, then click āPublishā -> āFor Meā. That āinstallsā the DeviceType into ST for you to use. The virtual stuff on the right is for testing the code only; it creates a virtual environment for testing, so ignore that.
Now that itās installed, you can pair your lock. It might automatically find and use the new DeviceType; but it might show up as just a āThingā or unknown. If it doesnāt automatically select the new DeviceType, then go to the āMy Devicesā tab in the IDE and click on your lock. On the next page, choose āeditā and it will let you use a drop down to assign your new DeviceType. You should be good to go!
Thanks! It took a lot of time and trial and error, but I got the lock attached to ST as a āThingā and I manually applied the device typeā¦
ā¦it doesnāt actually work (when I take actions form the ST app screen nothing happens on the actual lock), but at least now I can see debug logs and maybe I can figure out whether the problem is a difference in the Kwikset Control4 Zigbee lock or something else.
Thanks again.
I will report back when I make progressā¦or give up.
]