SmartThings Community

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

(Geoff) #10

Ok, so I was able to log in to the SmartThings IDE online here (https://graph.api.smartthings.com/), using my Samsung Account, but when I click on My Hubs, I see the following text:

You don’t have any hubs yet. Please use the SmartThings mobile app to claim your hub.

Yet, when I go to the SmartThings app on my iPhone, I can see the SmartThings Hub. It looks like it’s connected. How do I “claim” it?

I can also see my only other Z-wave device in the SmartThings app (my Kwikset 910 door lock), but when I go to SmartThings IDE online and click on My Devices, I see the following text:

You don’t have any devices yet. Add one now.

Thank you for any and all help with this! I’m willing to completely start over with the hub if needed to get this working properly.

0 Likes

(mike ricchino) #11

what does it show if you go to this address? https://graph-na02-useast1.api.smartthings.com/

edit: I should add more detail… there are actually 2 IDE addresses in order to reduce server load on Smartthings side. If nothing shows up, like you are describing, it normally shows up on the other server.

0 Likes

(Geoff) #12

Ok, another update:

Be sure not name your location “Home”, since this title is also used by SmartThings. Once I updated the location name to something else (“Our House”), all of a sudden I could see my Hub and my door lock. The door lock is listed as Z-Wave Lock for device type.

Now just figuring out how to open IDE Live Logging…

0 Likes

(Geoff) #13

Ok, found Live Logging, and a bunch of logs were created when I paired my Kwikset 910 with the SmartThings app.

When I try to unlock the door lock from the SmartThings app, here is the only log file that is generated:
0b952f14-d108-467f-9c1e-577d52e01549 7:22:47 AM: trace [DTH] Executing unlock() for device Front

After several seconds, I see the “Couldn’t connect to Front. Try again later” error in the SmartThings app.

When I try to manually unlock the door, nothing is logged in Live Logging. Nothing happened again when I tried manually locking the door.

Every few minutes I see the following in Live Logging:
0b952f14-d108-467f-9c1e-577d52e01549 7:25:10 AM: trace [DTH] Executing ‘reloadAllCodes()’ by Front

0b952f14-d108-467f-9c1e-577d52e01549 7:25:10 AM: trace [DTH] Executing refresh() for device Front

0b952f14-d108-467f-9c1e-577d52e01549 7:25:10 AM: debug Returning commands for lock operation get and battery get

However, when I check out the device status in the SmartThings app, battery reads 0% and the door status is listed as Unlocked (even though it is really locked).

My Vivint panel has not yet been taken down or turned off. I wonder if I need to go back in and exclude these door locks several times (or turn off the panel completely) to make sure there is no interference between the Vivint panel (which used to be paired with the door locks) and my v3 SmartThings Hub?

0 Likes

(mike ricchino) #14

Battery life always reports 0. that’s just a ST bug.

I suggest adding a new device handler and smart app in the IDE. Directions here: https://github.com/ethayer/lock-manager

These custom devices give a lot more features than the stock ST device type.

0 Likes

(www.rboyapps.com - Make your home your butler!) #15

Sounds like the lock isn’t responding or the response isn’t reaching your hub.

Custom handlers address a specific need. It would be to bring out additional functionality or fix bugs in the locks firmware or other issues. There are many really good/updated handlers out there but getting the basic lock / unlock functionality working would be the first step.

Did you try to look for error messages while pairing the lock? How far is your lock from the hub?

Try these steps:

  1. Exclude your lock
  2. Reboot and power cycle your hub
  3. Reset your lock / remove batteries for 5 minutes
  4. Open IDE Live Logging
  5. Pair your lock and see what messages are printed and copy paste them back here.

Don’t forget steps 2 and 3 and I’ve seen at times these help with some troublesome locks.

0 Likes

(Geoff) #16

Thank you, Mike. I started working the instructions in the link you sent and will have to get back to it when I return from work.

I have a hard time believing that both of my Z-Wave modules for my two door locks have failed at the same time. Yet I feel like the basic functionality should be working with SmartThings. The only thing that makes sense to me is that, somehow, there is a link or tie to the Vivint Z-Wave network – even though I excluded them at the very beginning and there are no Z-Wave devices paired with the Vivint panel.

Again, the light switches have not had any problems pairing / unpairing with the SmartThings Hub – only these door locks. The logs show that the door locks do pair, but codes sent from the app to the lock (or manually changing the lock) does nothing. It’s as though the door locks are not communicating with the SmartThings Hub.

Here is my latest log entries pairing the door lock using the updated SmartThings app:

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 8:20:07 AM: debug detecting status for 5fdf1ab0-5002-4919-84c2-b0157b52cb37 : true

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 8:20:06 AM: debug updated called

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 8:20:06 AM: debug No devices to add, verified devices: [:]

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 8:20:06 AM: debug detecting status for 5fdf1ab0-5002-4919-84c2-b0157b52cb37 : true

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 8:20:06 AM: trace in ssdpDiscover

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 8:20:06 AM: debug scheduled run, numberOfRuns: 6

d4cbbde8-c5d8-48e0-b9ac-d5792f449e53 8:20:06 AM: trace in discovery

Now it seems to be stuck on “Checking Status…”, which is better than before – at least it seems like it’s trying to check the status of the lock (which should be “unlocked”).

0 Likes

(Geoff) #17

Hi RBoy,

The hub is only 5 feet from the door lock. I just removed the door lock and re-added it to the hub using the updated SmartThings app on iOS, but now it’s stuck on “Checking status…” in the iOS device (and according to the Live Logging). Clicking on the tile in the app reads:

“Can’t connect to device. Check device and try again.”

0 Likes

(www.rboyapps.com - Make your home your butler!) #18

Don’t worry about the status in the ST mobile app. The new app uses something called Health Check capabilities. Long story short ignore the app status since it’s in BETA and has many bugs so the status will keep varying.

Your determining test will be, are you seeing a response from the lock in your logs. Once you start seeing that you’re golden.

It’s possible that the pairing process is leaving the lock in an uninitiated state. It’s been known to happen with Schlage locks esp the FE599 and even other devices, rare, but it could be happening with your Kwikset module. A key thing to look for would be if you notice any security failure or key exchange failure or any error in the logs while pairing.

See my previous post for the 5 steps you should try to isolate setup issues with the hub.

0 Likes

(mike ricchino) #19

Yeah it sounds like you will need to reset the lock again.

I believe the procedure for that is to remove the batteries, then reinstall them while holding the lock button. Kwikset 910 lock problems

0 Likes

(www.rboyapps.com - Make your home your butler!) #20

I would recommend one more step.

Instead of using the new SmartThings app, use the Classic app to pair your lock. The reason being that the Classic app notifies you if the hub has an error during the pairing process, like a key exchange or secure inclusion error.

Since both your lock modules are having trouble I’m beginning to wonder if there is an issue with the v3 hub and your specific module during the pairing process.

If so you may need to contact ST support to dive deeper into your hub logs to see what’s going on and where the pairing may be failing.

0 Likes

(Terry Grant) #21

I recently grabbed the 910 at Lowe’s for $45. Paired and works flawlessly. Use the SHM. Also shows “Locked” or “Unlocked” and battery level in the Classic App

1 Like

(www.rboyapps.com - Make your home your butler!) #22

That’s a really good deal BTW. Is this with the v3 hub?

0 Likes

(Terry Grant) #23

No V2. Sorry if I didn’t follow the thread close enough…

0 Likes

(Geoff) #24

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

0 Likes

(mike ricchino) #25

I also have a V2 hub.

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

0 Likes

(www.rboyapps.com - Make your home your butler!) #26

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.

0 Likes

(Geoff) #27

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

0 Likes

(Geoff) #28

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.

0 Likes

(Geoff) #29

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

0 Likes