Hello - I have 6 Kiwkset 914 locks...they're a bit older, but working okay. One radio module died (I moved some around to check).
Now, I ordered a ZW Plus radio module off the Flea-bay... and when I installed it, it said it's a Schlage module (however it works..kind of... in the lock).
But, being a used Schlage module... it doesn't show me all the passcodes, etc... nor did it give me security questions on the inclusion process. Is it possible to "convert" this module from thinking it's a Schlage to Kwikset? especially since they're physically the same? The model number on it is: 450241
Do you know that it's a Schlage? I don't know a way to tell this for sure, but looking up a part number you can find on the board (or trying a few until you find something) might help. I ask because all I really see in your screenshots is that it paired with the Schlage driver. This is matched by a "fingerprint," which generally includes manufacturer and device IDs plus command classes the device supports, but if nothing was an exact match (or multiple vendors share the same; probably not likely with big names like this), it's possible it went with something close — and that could have been this one, even if that's not what you have.
You can change the driver under "Type" on the device detail page. It's generally a good idea to run the "Configure" command (if the driver offers one) after changing the driver out. You can try this if you think it might actually be a Schlage. There are dedicated Schlage drivers and also the Generic Z-Wave Lock driver that you could try.
Of course, being eBay, it's also possible this is really what you got.
This will not happen unless it supports S2. The newer Schlage locks do; I think the Z-Wave Plus revision was released around 2019. But there are years of "classic" Z-Wave models before that, which only support S0 and will pair as such without prompting. You can check the "Security" column on the Z-Wave Details page to see for sure. If it says "None," that's a problem and could explain why it doesn't work. If it says "S0," that's not ideal in general but is the minimum you need for devices like locks, and it might be all yours supports.
You should at least be able to get a list of code positions and whether a code exists there or not, even if it can't retrieve the code. You can then use the Delete Code command to delete the corresponding code position, and use either the device detail page or an app like Lock Code Manager to add your own. (I can't remember if mine were capable of reading the default/built-in code--which I removed first thing and don't have a way to check now. Maybe someone else can remember better. I wouldn't be surprised if it was normal not to be able to, but anything you set from the hub should work.)
...well, "work" as well as Schlage Z-Wave locks are reported to in the event that this is one and you have one of the unlucky models. (They work well for some, less so for others, possibly depending on firmware, which you cannot upgrade.)
Can't be. Schlage doesn't have modules like Kwikset and Yale (and maybe others like Alfred, but not Schlage). And Kwikset and Yale aren't pin compatible.
Thanks for the quick response - I did the "type" change, configured....waited a few minutes... lock worked, codes worked, etc... but lock didn't report its status correctly in the Habitat dashboard (I did re-add it to the dashboards...)...