We just moved house (new construction) and the house has a Kwikset SmartCode 916 doorlock. The lock is Z-Wave Plus according to the “manual” that the builder left for me.
After getting my hub out of the box it was packed away in, I waited for the hub to update to the latest version, then started adding the lock to the hub (I’m using the new SmartThings app). There are no other devices connected to the hub at the moment, the hub is about 6 feet away from the lock with only a single hollow-core wood door between the lock and the hub.
I was disappointed to be told by SmartThings that my lock is old and I should buy a newer one for better security. I though Z-Wave Plus was the latest.
The lock got added fairly quickly, but in the new app it has been showing as “Checking status…” for at least 20 minutes.
Looking in the IDE the only data value shown is:
- networkSecurityLevel: ZWAVE_S0_LEGACY
which looks ominous (legacy?).
Most of the current state fields are empty (except checkInterval is set to 3600s).
Here are some of the other fields from the IDE:
|Name|KwikSet Door Lock|
|Device Network Id|3F|
About 30 minutes after adding the lock, it finally showed status both in the IDE and in the app. Then I tried to unlock it via the app and it went back into “Checking status…” and then “Unknown”. And the lock never actually unlocked. And about 20 minutes later when I re-checked in the app, it is showing as “Locked” (the unlock never happened but at least it is now showing the correct lock/unlock state).
An additional data field showed up after the initial 30 minute delay:
- fw: 4.10
I’m guessing that is the firmware version.
During all this I have received three notifications from the new app on my phone, each one saying “Updated code 1 in Front doorlock at House”. It’s true that there is (or was) a single code set in the lock (before it was added to SmartThings). But why would SmartThings be updating it in the lock? And why would it do it three times?
Should I expect this lock to work eventually? Did it default to the wrong DTH? Has it been chugging down terabytes of data for a firmware update? Is this just another thing that doesn’t work in the new app?
Thanks … Mike