Tony_B you aren’t insane. When I moved from the Vera to smartthings this Kwikset 910 is the only device left off because it literally brings the entire SmartThings ecosystem down completely (everything becomes unresponsive in the system as the batteries die). And yes the batteries die quickly as well. I’ll perhaps give a call in to see if indeed the device is by default categorized incorrectly (not lock or hard-wired, etc).
Update: Wow the web and even this forum is littered with many 910 horror stories specific to SmartThings v2, v3 hub draining battery like crazy. You’d really think Kwikset and Samsung would work together to prevent these things. I called Kwikset and they said to just call Samsung since their issue.
Log of things to try again day 1 02-13-2019: I’m turning off “Device Health” in smartthings classic to see if it helps, as well as uninstalling any SmartApps I don’t recognize. I’m also telling the Alexa SmartApps to forget this device since I don’t use Alexa with it. I’m also after adding it, repairing the z-wave network, and replacing the batteries (doing a complete boot of the lock).
Update morning 02-14-2019: Battery did indeed die/shrink very quickly and became offline according to smartthings. I removed the Alexa SmartApp altogether, and rebooted the hub with a new set of batteries. Strangely enough the battery seems stable the last 4-5 hours. Maybe it was the Alexa SmartApp! Or perhaps there is an order in doing things and you need a sufficient number of reboots on the lock and hub side of things. Will report back if as simple as removing poor old Alexa. If it is Alexa I see no obvious way to remove a specific device from being used by Alexa. Note I did check to see if securely attached (zw:Fs under Raw Description) and it was. Still though if this doesn’t work others have suggested pairing within inches to see if it helps. For what it is worth to log my device also says “ZWAVE_S0_LEGACY” which given its age I assume makes sense. (secure legacy, S2 generally being quite new)
Update afternoon 02/14/2019: After adding back on Amazon Alexa the battery is still stable. I did notice Alexa on bootstrap does say “Subscribing to Device Health events for device InsideDoor (XXXX) using activity event” which perhaps had me slightly concerned but doesn’t seem to be presenting a problem yet. Not 100% I care to figure out why it works so nicely now. Perhaps in the past was too quick to give up / remove from system after a few battery drains. (or didn’t reboot both devices multiple times or give the zwave network enough time to repair itself)
Update evening 02/16/2019. Yup same problem. Batteries down to 60% and went offline according to smartthings. Take out battery pack and put it back in and sure enough it is online again but of course the Kwikset unit is warning me about low batteries at this point with the red lights/etc. Replaced batteries and leaving Alexa out completely until I have some more data. This happens very fast so won’t take longer than a few more days between updates which is nice in a way.
Update evening 02/18/2019. Yup same problem. Therefore ruled out Alexa. This time I did a Kwikset 910 factory reset and brought an extension cord with the Smartthings hub within 1/2 inch of the lock to unpair, repair, re-add, and repair. If this is the problem, Samsung’s IDE is really bad because none of the codes have changed, so that means Samsung doesn’t expose this state to the customer, not even in their debug IDE, which really sucks.
Update late afternoon 02/19/2019. Looking pretty darn good. Have relocated hub back to initial location after having it sit for 12 hours within a few feet of the lock. Maybe there really is something to needing to be paired within inches of the device, despite numerous z-wave plus repeating devices between the original location and lock. It really really stinks though if that is it, because that means that Samsung does not expose this quassi-paired issue on the debug IDE page (not even to their guys on the phone I spent over an hour on the phone with today).
Update 02/20/2019. I switched out the small zwave chip module for the newer zwave plus module Kwikset includes in their latest 910 locks. (NOTE this is EXTREMELY easy and doesn’t even involve undoing any screws you can do it while still attached to the door just as easy as removing the battery pack) This seems to fix the issue and at least gives me my sanity back on my actual door while I continue to troubleshoot why the old module doesn’t operate with SmartThings correctly for other folks that have this problem. (on a spare lock that is just sitting around) The newer zwave plus isn’t automatically recognized by SmartThings as anything other than a “Z-Wave Lock” whereas the older 910 board did indeed say Kwikset 910 Contemporary Lock. Based on the Kwikset 910 operating just fine on its own and operating fine with the Mi Casa VeraLite, I still think this is a bug that nobody wants to solve/is to lazy to solve because it involves older hardware. I’ll likely, for my own edification, use a Zwave sniffer since Samsung/SmartThings couldn’t figure out anything on the phone looking at the backend of the controller. I do wonder if there is some command that isn’t sent cleanly to the lock so it keeps it from going to sleep properly under certain circumstances, or if there is indeed some kind of polling/etc issue. Perhaps the newer hardware is more resilient, but given that these 910 devices work with older hubs I think likely Samsung should compensate like the other hubs do rather than ask everyone to call Kwikset to replace the hardware (which is what they told me on the phone yesterday).
