gdntx Posted January 8, 2016 Posted January 8, 2016 Night before last I went to bed and executed the macro to turn all of my lights off - same way I do every night. About 6 minutes after they were off and I turned one more light off manually my Kwikset door unlocked on it's own. Of course I set straight up in bed wondering if the door was about to be opened, but I know I had not heard the beeps of a code being pushed in, so I figured something had gone wrong. This is what I find in the log. I'm running a 994i v4.2.30 software with a zwave add in. The Kwikset lock and a repeater are the only Zwave devices in the house. I've got about 30 Insteon devices. What would cause the communication shown in the log with the lock and why would it have unlocked? I assume that the ISY issued the command - not sure. Here is the log right before and just after the event. Sorry that paste of the log didn't work well - here is excel version attached. insteon log.txt
Teken Posted January 8, 2016 Posted January 8, 2016 Night before last I went to bed and executed the macro to turn all of my lights off - same way I do every night. About 6 minutes after they were off and I turned one more light off manually my Kwikset door unlocked on it's own. Of course I set straight up in bed wondering if the door was about to be opened, but I know I had not heard the beeps of a code being pushed in, so I figured something had gone wrong. This is what I find in the log. I'm running a 994i v4.2.30 software with a zwave add in. The Kwikset lock and a repeater are the only Zwave devices in the house. I've got about 30 Insteon devices. What would cause the communication shown in the log with the lock and why would it have unlocked? I assume that the ISY issued the command - not sure. Here is the log right before and just after the event. Sorry that paste of the log didn't work well - here is excel version attached. Nothing has been appended to your reply.
gdntx Posted January 8, 2016 Author Posted January 8, 2016 It wouldn't let me upload an excel extension so I renamed it .txt - it really is an excel file though - have to open with Excel.
Teken Posted January 8, 2016 Posted January 8, 2016 Out of curiosity what does the system indicate for battery level via the Admin Console? How long has this unit been in production in your home? Has this ever happen before? If you remove the batteries measure all of them and report back what the voltage is when compared to what the Admin Console says.
gdntx Posted January 8, 2016 Author Posted January 8, 2016 The system indicates a battery level of 50%. The batteries were replaced in late November/early December. I installed the lock on the door back in May I believe and added the zwave control to ISY a month or two after that and got it communicating via the ISY. It has never happened before to my knowledge. Will have to see if I can measure the batteries manually.
Teken Posted January 8, 2016 Posted January 8, 2016 The system indicates a battery level of 50%. The batteries were replaced in late November/early December. I installed the lock on the door back in May I believe and added the zwave control to ISY a month or two after that and got it communicating via the ISY. It has never happened before to my knowledge. Will have to see if I can measure the batteries manually. Thank you for those data points as it will lay the ground work for next steps.
gdntx Posted January 8, 2016 Author Posted January 8, 2016 I had to go look up my order, but the lock is a Kwikset Smartcode 916 Touchscreen.
Teken Posted January 8, 2016 Posted January 8, 2016 I had to go look up my order, but the lock is a Kwikset Smartcode 916 Touchscreen. I would encourage you to send out an e-mail to Kwikset and relay the same information to them. Inquire if there are any recalls and if this condition has ever been seen. Ask specifically how the lock set is supposed to respond in a low power state. This is important as most consumer grade devices follow specific guidelines not seen in a commercial space. Specifically some locks must operate in a fail safe vs fail secure fashion. Meaning if the battery was to die it would be in a fail secure mode where the lock set does not release but stays in the locked position. You will notice some vendors do the opposite where if the lock is in a low battery state it will unlatch the lock set. There are various reasons and scenarios where this would be good vs bad. But speaking for myself only I don't believe a lock set should ever fail open upon a failure or power loss. A number of years ago I was tasked with a team to validate and test many commercial lock sets and some consumer grade units. Its safe to say the outcome was a little surprising and hence my feed back to you. Please forward this information to the vendor so at least you have it documented and they offer next steps and guidance.
elvisimprsntr Posted January 8, 2016 Posted January 8, 2016 I haven't had an issue with the same Kwikset 916 and ISY-994iZW. The two are only 8 feet apart with direct line of sight, so I didn't need a repeater. My lock battery level is also at 50%. The key to battery life is making sure the deadbolt has minimal resistance. I've found Duracells run longer than any other brand. We'll see if they stay that way now that Rupert Murdoch owns Duracell
gdntx Posted January 8, 2016 Author Posted January 8, 2016 So to check and be sure - are you saying the two messages were generated from the lock and the ISY just happened to pick them up and then it unlocked on it's own? I thought the messages were from the ISY - did some sort of check and then issued an unlock, which it did.
gdntx Posted January 8, 2016 Author Posted January 8, 2016 Yes - that is correct - I locked the device manually at 10:26:03 - after turning on a hallway light. The two events that are problematic and unlocked the door with no request were at 10:25:31 and 10:25:42. I gave a few lines of the log before that to show there had been no activity for a few minutes after I turned all the lights off when going to bed.
Teken Posted January 8, 2016 Posted January 8, 2016 Yes - that is correct - I locked the device manually at 10:26:03 - after turning on a hallway light. The two events that are problematic and unlocked the door with no request were at 10:25:31 and 10:25:42. I gave a few lines of the log before that to show there had been no activity for a few minutes after I turned all the lights off when going to bed. I would submit the logs to UDI and also engage Kwikset as I stated above. Time permitting please do measure each battery and indicate the same here.
stusviews Posted January 8, 2016 Posted January 8, 2016 Can you replicate the Kwikset unlocking after being locked?
gdntx Posted January 8, 2016 Author Posted January 8, 2016 The lock works fine from every other aspect and locks and unlocks as requested, but this unlock was at night and was in no response to any request for me or anyone else. It was just a random unlock by either the lock or the ISY - leaving my house and family unprotected. I'm not aware of it ever happening before and it has not happened since.
stusviews Posted January 9, 2016 Posted January 9, 2016 If you can't replicate the unlocking based on what the log shows (e.g., events immediately preceding the unlocking), then I don't believe that submitting the log is going to provide any help. I'd also consider that at 50% the battery level is quite low. But, like Teken, I can't imagine a device such as a household door lock being fail safe and not fail secure. Again, I agree with Teken that you should consult the Kwikset company
elvisimprsntr Posted January 9, 2016 Posted January 9, 2016 Are you using a third party phone app to control your locks? E.g., Mobilinc with an iBeacon or Geofence to set a variable to trigger a program to unlock.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.