Just KO'ed new driver to take into account Lithium, Alkaline and NiMH batteries for the Kwikset 914. You can access on git here: GitHub - iamnof1/hubitat-kwikset-914-zigbee Happy using and updating. (note: I first paired and installed my 914 using Generic Zigbee Lock from Hubitat then changed the driver to this one).
1 Like
Got error:
Commented out line 176 and it appears to work.
Was getting battery 180% on old driver. Now 100%.
Also a nit, typo.
Glad it's working for you. FYI, the typo is due to the built-in description for the codeLength attribute on the Lock Codes capability (from the hub / I can't make a change for that). If you have another lock (not using this driver) and check it you'll see the same "hub" typo there. Not sure who at Hubitat needs to be aware of it. Git is updated with that line removed - thanks.
1 Like
FWIW, that doesn't seem to be the case. Unless @TArman is running a different version of the hub platform from my hubs, which are on 2.4.4.133.
@gopher.ny @aaiyar mine on 2.4.4.133 (though my locks are Z-wave not Zigbee) it has the same typo I'm using the generic Z-wave lock driver
Set Code Length
Pin code length
Maximum pin code lentgh for this lock *(NUMBER)
1 Like
I see lentgh on every lock driver in 2.4.4.133
1 Like
Here’s the driver I’m using:
It’s the built-in driver. On 7 locks. None of them have the misspelling.
@bcopeland - what’s going on here?
1 Like
Will look into
1 Like
Yea.. I have no idea where this misspelling is coming from.. It's correct in all the code.. Yet I can confirm it on my hub.. Very strange ..
3 Likes
Now you just need to figure out which kind of battery I last put in the lock without my having to open it and look!
Why isn't it happening on my hub? 7 locks - all on "Generic Z-Wave Lock" - length is spelled correctly on them all. I've tried both Safari and Chrome as browsers.
Very good question, of which I don't have an answer for yet.. I was assuming it was a community driver issue but I saw it on mine which is using Generic Z-Wave Lock driver.
1 Like
I'm also using the build in Generic Z-wave lock driver
@bcopeland on my test C5 this misspelling shows up on the Built in Virtual lock Driver (chrome and Edge) as well
Strange indeed!
FWIW, the spelling issue is also on the (native) Yale Zigbee Lock driver.
1 Like
I'm feeling left out of this misspelling club .....
1 Like
Ha.. It was corrected on 4/25/2023.. But there wasn't a DB update for it.. So all hubs (or restored hubs) that were setup before that date will have the incorrect spelling.. Any hubs setup after that date will have the correct spelling..
4 Likes
so what i'm hearing is this is an early adopters Easter Egg
2 Likes
Wow!
At least we have an explanation. The Z-Wave radio on my original C-8 Pro died sometime early in 2025. I restored zigbee to the new C-8 Pro, but re-paired all my z-wave devices.
1 Like
