LOL, nope not really! Poke around in the IDE when you’re all done too, especially things like Live Logging.
Soooooo, it worked but I actually had to call it a zigbee lock. It wouldn’t recognize it as a zwave lock. Something strange with that I think. It is labeled zwave plus and a part number 99140-103 but when I changed it in the IDE to zwave it wouldn’t go online. For sh1t5 and grins I tried it as zigbee and it worked. Does that mean it’s actually zigbee and not zwave?
Oh now that’s interesting. Where did you get it? If the Zigbee Lock DTH worked, then it’s certainly Zigbee and not Zwave (and that’s not a bad thing either).
Is the box labeled as Zwave Plus or the module?
Wow, yep you sure have something swapped around. Was it new? When you look at the detail of that device in the IDE, do you see something like this:
You probably have a newer lock that I do based upon what looks like a mfg date in the lower right corner of that label.
I’ll be honest and let you know that I got rid of my Zwave lock for this Zigbee lock, and I’ve never ever had a problem since. There’s a long story behind that, but I think you’ll be just fine.
If you have a warranty return to Amazon, you may have some challenges with Amazon, so just be aware of that.
The one thing I may look at now that I see mine and yours is that I may change the DTH to Zigbee Lock Without Codes. SInce it doesn’t have codes, I’d hate for the DTH to be trying to constantly scan the device for them and cause unwanted battery drain. I’m going to experiment with one of the two I have.
EDIT!
Here’s an interesting find. Zigbee Lock is NOT a local device handler, but the Zigbee Lock Without Codes is local! I wonder when that changed.
So does that mean without codes operates local on the network?
Yup:
As ST does more to support local execution of device handlers, and especially Automations, Scenes, and other capabilities, this lock will be able to take advantage of those improvements as they happen over time.
I switched mine to without codes and works fine so far. Thanks for helping out a noob! I appreciate it. Now I need to solve what to do with my wink relays.
1 Like
I do have one more question. all other devices I have are zwave. This lock is the only zigbee device. What are the drawbacks to that?
There are no drawbacks at all. If the lock works and responds, then you should be just fine, especially if it’s relatively close to the hub. Over time if you add more zigbee devices, like bulbs or sensors, you should consider adding a zigbee repeater device like an outlet, switch, or wall plug. There are several really good ones out there.
Check out this topic as well, it may help understand how to get started with smarthings IDE and all
Hey thanks for the info. I successfully migrated all my devices over from wink. I just added a lock to make life easier. It always gets locked every night and unlocked at the right time for the nanny to arrive.
2 Likes
By switching it to without codes you lost the ability to program codes. Ideally when you your pair your lock it should automatically pick the right device handler for you (you don’t need to change it unless there’s a specific reason).
I think I know why it didn’t “ZigBee Lock” for your in the first post. I’ll submit a patch to SmartThings to fix it so it’ll pick it up automatically when you pair it next time. @johnconstantelo you have the same lock and I’m assuming you’re using ZigBee Lock for it along with LUM.
If you’re looking to program codes check out the Lock User Management (LUM) to manager your user and create custom actions and notifications for each user code. You can a do lot of cool user types like presence based or mode based so it’ll activate users when people are around (or not) , even unlock/lock doors when the presence status changes, scheduled codes and tons more (like having it announce on Alexa or Sonos/Bose when codes are used).
I’m pretty sure it’s just a fingerprint that needs added since these show up as a Thing and you need to change the handler. There are a couple discussions around here about this lock.
No. I only use LUM with my Iris keypad. These locks don’t have keypads, and are pretty basic.
Here are the locks I have. I don’t use these with Amazon ket, just ST:
https://www.amazon.com/Kwikset-Convert-Smart-Conversion-Amazon/dp/B071KLHWSP/ref=psdc_511306_t3_B07CPH6GWG
Here’s the model the OP has: (but with the zigbee module instead)
https://www.amazon.com/Kwikset-99140-103-Convert-Connect-Venetian/dp/B07CPH6GWG/ref=sr_1_1?dchild=1&keywords=Kwikset+Convert+zwave+plus&qid=1591443764&s=hi&sr=1-1
1 Like
Sorry for bumping an one-year old topic, but I have the same Kwikset Convert kit (Model on device at top says 450241, which a quick Google search also coincides with a Z-Wave Plus device). The online listing and the packaging of the item both say it’s Z-Wave, so I’ve tried pairing them as per instructions as such. No gravy.
I tried pairing instead as a Zigbee, which requires pressing the A button 4x. Still no gravy. Any solutions? Every thing in the instructions up until the pairing bit was progressing fine, with brand-new set of batteries to test. Even tried with the thing sitting on top of the Hub in case ‘distance’ was an issue.
One thing of concern is that while the red LED does light up after pressing the A button, it only stays on for up to 3-4 seconds. Is it supposed to be that short? Or did I get a dud…
I’ll try calling Kwikset Support as well, but figured the Samsung comm may have experience.
I had that issue with it. It worked after I did this
I’ve done that Door Handling process 3x and straight into pairing mode to no avail.
Tried holding that Program button 30s to reset as well, and do over the whole set up. No go.
Welp, I would contact Kwikset Support… but the place I bought the kit from gave me full refund, haha
A glorified paperweight for now.