Update driver class name for keyWe Z-Wave Lock so it installs properly.
Bruce, do we need to exclude and to include the KeyWe to take advantage of this change?
Thanks!
Scott
If you already have it joined and running, there's nothing that needs to be done.
Yeah, its Joined, but it doesn't really work. I just switched to the KeyWe driver (from the generic driver) and tried configure with no real luck.
I'll exclude it tomorrow and try to rejoin it.
Thanks Mike!
Scott
1 Like
Did you hit the configure button after changing the driver?
1 Like
Yup, hit it when I checked the device on the Generic Zwave Lock driver, with no change in operation, and then swapped to the KeyWe specific driver and hit it again.
Honestly, I had a heck of a time getting this thing to join in the first place, so I'm not entirely sure it's joined completely/correctly in any case.
I'll dig out the manual, do a reset, and rejoin the device.
Thanks for the suggestion however!
S.
But your first post said z wave? So the change was on z wave but you have zigbee?
Fixed. Sorry, was only on my first cup of coffee.
It's Z-wave, the KeyWe only comes in Zwave as I recall.
S.
1 Like
How did you get a hold of one of these vapor devices? As far as I can see they still haven't shipped to backers and are not for sale elsewhere.
1 Like
They definitely shipped one to me, and there are two or three others on here with them as well.
I got mine on KickStarter and I received my unit some time in late June/Early July (as I recall).
I like it a lot, although I haven't gotten it to fully link up with Hubitat yet.
Update #27 on June 30th indicated that all rewards had been shipped.
It's also available on Amazon: https://www.amazon.com/KeyWe-Smart-Door-Lock/dp/B07BFCRPVH/ref=sr_1_1?keywords=KeyWe&qid=1572441672&sr=8-1
S.
1 Like
Does it come with RFID tags or do you have to buy those separately? Thanks.
I think mine came with 2 or RFID tags, but that was part of the Kickstarter I think, and I'm not sure what ships with the Amazon listed units.
Scott
1 Like
It's getting trashed on Amazon. You're having no problems with it?
Nope. Works great, but then I don't really use any of the doors I have smart locks on, so that's not much of a data point. I like the auto lock feature, the minimalist appearance, and the integrated contact sensor....but...the rest of it, RFIDs, phone unlocking, etc I haven't even looked at.
S.
mechanically it's one of the better built locks, and one of the quietest as well.
I don't like the auto lock feature, and with that turned off the device cannot be locked from the touch screen, if that's not the case then I don't know how to configure that in their app.
Anyway, because of that issue this lock never got deployed to production...
Arrrgh! Excluded it, tried inclusion....failed to find it. Factory reset the lock, and tried including it to no avail. Just now moved one of my z-wave repeaters closer and ran a Zwave repair. If I cant get this thing included again, I'm probably going to replace it. Love how it looks...but arrrgggghhhh!
Note: Above was typed for brevity, rest assured there were many exclude, include, reset, curse vociferously iterations!
S.
I think I know why it's not pairing. Theres a Nexia Platinum 850 Thermostat that is a Zwave hub on its own, joined as a secodary contoller, I bet that thing is interfering...its useless anyway, so If I cant get a join with the relocated repeater, I may turn off Zwave on the Nexia.
I've had a Hubitat for awhile (gen 4) but never did migrate (from the few SmartThings sensors and lights) like I had planned until recently. Once I got the few basics down through trial-and-error and reading the docs/community where necessary, I've started ordering an item here and there for Hubitat automation. While reading the latest posts, I ran across this thead.
A little while later (most of it spent looking for the KeyWe docs buried in my storage room as they don't exist online) I just had to sign into the community to say "THANK YOU" to whoever is responsible (Mike?) for getting the KeyWe lock working with Hubitat. I bought the lock when it was on Kickstarter and was not thrilled with the idea of a 3rd party having web control of my door lock. So I only used it with NFC (I've worn one of the wrist bands 24x7 since it was installed), have a passcode set for backup, and just tested the 3 keys the first day and carry one just in case the battery dies.
Now I have automation setup in Rules Machine to trigger on my arrival sensor, wait for me to get to the front door (motion), and automatically unlock the front door. Wonderful for when I have my hands full of items rather than having to get the NFC at the right point on the lock which also required twisting the band on my wrist.
Thanks again,
Bill
I imagine you are only waiting for motion a few minutes after presence is detected to auto unlock?
Correct.
Wait for events: Front Porch Monoprice Sensor active --> timeout: 0:05:00
IF (Front Porch Monoprice Sensor active(F) [FALSE]) THEN
Unlock: Front Door Lock
END-IFIt appears that I can create new lock codes with the KeyWe device in Hubitat, but I can't see them listed as lockcodes under the 'Current States' of the device and therefore they are not available to the Lock Code Manager app. I've tried 'Refresh' and 'Get Codes' in the device to no avail. Up until today I've only used a single lock code (position 1). To test, I just manually deleted all lock codes (not including position 1) and created a lock code (position 2) directly on the KeyWe to see if I could retrieve it. No dice.
Is there something I'm missing or is this a limitation of the KeyWe?
Have you tried clearing codes and setting the code using Lock Code Manager instead of directly on the KeyWe?
