I have connected a BE469ZP Schlage lock to the ST however it shows up as a switch and not a lock. I obviously can’t unlock and lock the door when the hub sees the device as a switch. I have excluded and reconnected three times and each time it connects as a switch. I have plugged the hub in right next to the lock to assure a close communication so there is no interference from anything else.
Any suggestions???
I have 2 of these locks and both work flawlessly.
There is an online interface at https://account.smartthings.com/login - Login with your Samsung account information
Go to My Locations - Select the location (you may only have one)
Go to My Devices - Find your lock in the list and select it to see various settings & attributes for the device.
Note what it says to the right of Type… mine says Z-Wave Lock. If yours is not saying that, you can select the Edit button at the bottom and change it. Be sure to select Update at the bottom.
You can set up your lock codes and manually control your locks in the new SmartThings app using Smart Lock Guest Access smartapp. Go to SmartApps, select the “plus” at the top, and select Smart Lock Guest Access. Once you have it installed, to change lock codes, touch the word “LOCKS” at the top left and a drop-down menu will appear.
2 Likes
Change the DTH over in IDE to zwave lock and see if that helps.
These BE469ZPs are S2 Z-Wave Locks, did you enter the DSK (Device Specific Key) during the Inclusion? S2 is now standard on most Hubs and a failure to input the DSK during enrollment could result in odd behavior for the S2 Device you are including.
The DSK on this Lock is found on the interior label next to the barcode and your Programming Code. Also, this Lock is enrolled via the red Learn Button that is found underneath the battery cover (some people still try and use Schlage Button + Prog. Code + 0, which is the old method).
1 Like
If it’s showing up a zwave generic device (switch) it means that the pairing process is having an issue and some information is getting lost during the communication process making ST default to a generic device handler. There are many tell take signs for this including a lack of MSR or corrupted raw description.
Try these steps:
- Reboot the hub
- Exclude the lock or do a factory reset
- Bring the lock within 5ft if your hub
- Open the ST app, click on + -> Devices -> Scan nearby and it should work. Note this will pair it using S0 which is okay. If you want to pair it using S2 then use the Generic Z-zwave option but I would start with the straight forward pairing first.
Since you have the BE469ZP you may benefit from the enhanced zwave lock device handler which will give you access to the advanced features in your lock like the built in alarms, auto lock, vacation mode etc. [RELEASE] Universal Enhanced Z-Wave Lock Device Handler
1 Like
GOD BLESS YOU, Brothah!
I’ve (unfortunately) paired this stupid door lock two dozen times over the years. Today my lock decided that it identified as a light bulb. This was driving me crazy and your solution worked.
(Your link was wrong, but your solution worked.)
IDE login: [
Samsung account
Regarding “but your solution worked”, what is the solution? My Schlage Connect Century lock is adding to ST as a switch. I’ve searched for suggestions/solutions, but haven’t come across anything that has worked yet. It’s now April, 2024, and Smartthings is using the edge drivers etc, which is the driver I need, and what are the steps for my v3 hub to recognize the Schlage lock as a lock and not a switch? Even if the steps are long and complicated, I’m willing to try because I’ve spent days trying to figure out without success so far. Thanks in advance!
I’m sure that’s very frustrating. 
The solution in the post you are referring to is from the old architecture and is no longer available.
In most cases, when a device pairs as a Zwave switch it means that the pairing failed and therefore SmartThings is just trying to treat it as a lowest common denominator device.
So the first thing to do is to check and see what device SmartThings thinks it is. Those instructions are in the following community FAQ.
FAQ: Manufacturer/Model Shows All Zeroes
Read that and follow the instructions there.
If you determine that the pairing did fail, then you will have to remove the lock from your SmartThings account and try pairing it again. That can be tricky with Schlage locks as they can be finicky. You will almost certainly need to have the lock within 10 feet of your hub so that they can correctly exchange the security key.
But before we get into that, start by reading the FAQ and see if it is indeed a failed pairing. 
1 Like
Thank you so much for pointing me to the FAQ link above. Indeed, my advanced info shows all zeros. I will try to get the hub closer, and change the battery on the lock etc, as suggested. Unfortunately I won’t be able to try/debug until about 2 weeks from now since I just left on a trip. I will follow up and post. Thanks again.
Update 2 weeks later: Wow, amazing it works now! I tried to exclude and add again, and got the error before (added as switch and all the IDs are 0). I then changed to new batteries, same failure. Then I did a factory reset of the Schlage lock. I was shocked when I excluded and re-added and it worked the first time! I then re-added some codes, tested manual unlock/lock and app unlock/lock, and everything is working. I had spent many hours, and probably 20+ attempts, moving the hub 1" away, 3ft away, 15ft away, etc. Nothing worked until I did a factory reset of the Schlage lock. Thanks again for the most recent reply, and also all the previous postings from others. It gave me hope to continue debugging and trying, until success today!
1 Like