New Smartthings Hub can see Kwikset 910 door locks, but not control them

Maybe I should do a reset of my v3 hub? And I’m wondering if I should pick up a v2 hub instead…

I also have a V2 hub.

That Lowes clearance sale was fantastic… lots of new toys.

V2 has a faster processor but v3 has WiFi. You can see the forum posts on v2 vs v3 and take a call. But since you have 2 non functional locks at this time maybe it will be worth using a v2.

RBoy,

Sorry for the delay – I have been swamped with projects and events and have a little time tonight to try pairing my Kwikset 910 with my SmartThings Hub (v3). After following the five steps you outlined, here is what shows up in Live Logging:

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:19:08 PM: debug detecting status for 80c2b2ad-4218-43f0-9206-6936e6db9099 : true

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:19:08 PM: debug updated called

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:19:00 PM: debug No devices to add, verified devices: [:]

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:19:00 PM: debug detecting status for 80c2b2ad-4218-43f0-9206-6936e6db9099 : true

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:19:00 PM: trace in ssdpDiscover

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:19:00 PM: debug scheduled run, numberOfRuns: 7

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:19:00 PM: trace in discovery

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:45 PM: debug No devices to add, verified devices: [:]

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:45 PM: debug detecting status for 80c2b2ad-4218-43f0-9206-6936e6db9099 : true

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:45 PM: trace in ssdpDiscover

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:45 PM: debug scheduled run, numberOfRuns: 6

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:45 PM: trace in discovery

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:38 PM: debug No devices to add, verified devices: [:]

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:38 PM: debug detecting status for 80c2b2ad-4218-43f0-9206-6936e6db9099 : true

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:38 PM: trace in ssdpDiscover

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:38 PM: debug scheduled run, numberOfRuns: 5

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:38 PM: trace in discovery

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:31 PM: debug No devices to add, verified devices: [:]

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:31 PM: debug detecting status for 80c2b2ad-4218-43f0-9206-6936e6db9099 : true

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:31 PM: trace in ssdpDiscover

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:31 PM: debug scheduled run, numberOfRuns: 4

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:31 PM: trace in discovery

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:25 PM: debug No devices to add, verified devices: [:]

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:25 PM: debug detecting status for 80c2b2ad-4218-43f0-9206-6936e6db9099 : true

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:25 PM: trace in ssdpDiscover

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:24 PM: debug scheduled run, numberOfRuns: 3

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:24 PM: trace in discovery

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:20 PM: debug No devices to add, verified devices: [:]

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:20 PM: debug detecting status for 80c2b2ad-4218-43f0-9206-6936e6db9099 : true

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:20 PM: trace in ssdpDiscover

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:20 PM: debug scheduled run, numberOfRuns: 2

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:20 PM: trace in discovery

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:17 PM: debug No devices to add, verified devices: [:]

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:17 PM: debug detecting status for 80c2b2ad-4218-43f0-9206-6936e6db9099 : true

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:17 PM: trace in ssdpDiscover

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:17 PM: debug scheduled run, numberOfRuns: 1

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 9:18:17 PM: trace in discovery

9:17:45 PM: info Waiting on events…

9:17:45 PM: info For past logs for individual things go to the My Devices section, find the device and click on the Events link on the device information page.

9:17:45 PM: info This console provides live logging of your SmartThings.

What do you think is happening?

Thank you,
Geoff

I forgot to mention that I “supposedly” have paired my Kwikset 910 with the hub – however, the device status on the app reads “Checking status…” and when I tap the lock in the app, the error “Can’t connect to device. Check device and try again.” flashes for a second and then disappears.

Last thing I’ll share here: I am able to easily add these Kwikset 910 locks to my Vivint Sky panel, where I can not only see them but control them from the panel. I can see messages negotiating keys, etc., when they are added. Clearly these door locks with with my Vivint Sky panel – but not with my 2018 (v3) SmartThings Hub! I have sent an email to Samsung Support looking for extra help on this. Since it appears that you all have v2 of the SmartThings Hub, perhaps this has something to do with v3?

Geoff

The logs don’t show any pairing happening, you can also try to open the IDE -> Hubs -> List Events and see if you’re seeing any pairing events related to your lock. It may be an issue with the pairing of the v3 hub causing an incomplete pairing. Maybe @posborne has a suggestion?

@G.Pasarescu, the “Anti-theft” feature is enabled on the lock which prevents it from being added to another controller. To fix this you need to associate it back to your Vivent system and disable the “Anti-theft” protection. Then you should be able to remove it from Vivent and bring it back to the ST Hub.

1 Like

Fantastic! Thank you. I will try that and then get back to you.

Hey everyone – sorry for the long delay.

I was finally (a few months ago) able to reassociate the Kwikset 910 Smartcode Z-wave locks with my Vivint Sky Panel but without the anti-theft protection enabled. Then I excluded the locks from my Vivint Sky Panel.

The other piece that was really important was moving the SmartThings Hub within a foot of my Kwikset locks when I added them. Finally, the SmartThings Hub could see them and then add them to its Z-wave mesh. They are now working with my SmartThings network.

Thanks again, everyone!

I have similar problems with myV3 hub systems. When I initially set mine up the system would not recognize wifi for the setup process so I just plugged it into the router. I guess the only way to set it up is to remove the lock from the door and bring it next to my hub since I can only use the hub while it’s plugged into the router. This seems like quite a mess. Do any of the tech support team members monitor this blog? these issues should be being resolved by Smartthings not bloggers.

I don’t know if SmartThings tech support monitors these forums, but it is true that to associate Z-Wave door locks with the SmartThings Hub you need to bring them right next to the hub (or bring the hub to them). It has something to do with the initial negotiation of keys. Once the locks have been paired to the SmartThings Hub, then you should have no problems controlling them through SmartThings, even though they are no longer located right next to the hub.

As for why you are having wireless issues with your v3 hub, I encourage you to search the forums. My v3 hub works just fine on my wireless network. That was how I was able to move it to my door locks when I initially paired them to the hub.

Good luck!

There are way more than two shards now. Everyone should use

https://account.smartthings.com

And it should automatically direct you to the correct shard for your account. :sunglasses:

2 Likes

It should be https, ST has disabled the http site (wonder why they don’t redirect it).

2 Likes

Fixed above. Thanks for the correction. :sunglasses:

1 Like

If you have not figured this out I was having an issue where could pair and see the device but control wouldn’t work steady. Had the hub sitting on top of my WiFi router moved the hub about 2 ft and works like a charm.

Did you disable the anti theft in the Vivint panel? Or is it something you do with in the lock?

The only way I found to disable the anti-theft protection on my locks was to add them back to the Vivint panel, making sure at the panel to disable the anti-theft protection. Then, when I removed them from the Vivint panel, I was able to add them to my SmartThings v3 Hub.

I am having some similar issues with my Kwikset 910 locks. I have them paired to the hub and can see them with no problem. The both show connected and the status even updates in Smartthings when I operate the locks. However, I am unable to control them with smartthings. When I try to control them, it looks like it is trying then appears to timeout. I have move the hub within 2 feet of each lock and added a repeater, but still the same result. Did I miss something?

I’ve installed 9 Kwikset 909/910 locks over the years, usually with no problem. The 10th was a bear. Could be seen in the app but would not operate. When this happened a couple of years ago, a Smartthings guru told me to check the “Raw Description” line in the page for the device under “my devices” in Smartthings web interface. If first entry is "zw:F " then device is connected but not securely even though status is reported to be “ONLINE.” Cannot operate lock, check battery, nothing in that situation. Needs to read: “zw:Fs” meaning there is both a connection and a secure connection.

I tried connecting, perhaps 50 times, before finally getting the “zw:Fs” and all now works fine. Those initial 49 times, would get a connection but not a secure one, would have to exclude, and try again.

I had become convinced I had a defective lock but it turns out distance from hub was critical for this particular lock. Cannot be too far, obviously. But, also, too close did not work. For me, 12 inches (but not 6 inches or 18 inches) finally worked. I have the v3 hub so that made adjusting proximity easier as lock stayed on the door.