August Smart Lock Pro always added as Z-Wave switch

Hi all - I wonder if anybody has seen this issue. I tried adding smart lock pro thru Z-wave. Both SmartThings hub and August App were both complaining that each cannot do S2 protocol, hence defaulting to S0 (even if I entered the DSK code correctly). Also even at S0 the device showing was Z-wave switch that does not work.

So whether I tried using the secure setup for S2 or just skipping to go to S0 directly, it does not work and kept showing Z-wave switch (tried more than 20x without luck in showing as z-wave lock even once).

August support thought I have a defective lock, hence sent a replacement with same behavior.

Any ideas? Thanks!

1 Like

That almost always means that the specific “fingerprint“ of the device has not been included in the appropriate edge, Driver, so it’s just picking the lowest common denominator Z wave device, which is a switch.

I’m very tired today, so I’ll have to leave it to others to help you with the next steps, but begin by going to the advanced page of the official web interface, and see what fingerprint shows there. The following FAQ explains how to do that:

FAQ: Manufacturer/Model Shows All Zeroes

But the main point is that yes, that happens, most commonly when your specific model has a fingerprint which has not yet been listed in the official edge driver.

Thanks, @JDRoberts for your suggestion!

I followed your shared steps, including getting the lock closer to hub. However, multiple retries yielded the same that is detected as z-wave switch and manufacturer code as all zeroes.

If you or anyone have other ideas or steps for me to try please let me know. I have attached some screenshots for reference.


Uploading: IMG_89D621BDA239-1.jpeg…


Same exact problem.
In fact, mine has been working for 2 yrs, and I tried to refresh it the other day as it wasn’t working when trying to unlock the door remotely.
I deleted and tried to re-add add have the same issue, over and over, as you exactly described.
Would also appreciate some guidance on repairing this!

Since you are still showing zeroes in the fingerprint (the combination of the manufacturer code and the model), the pairing is failing to complete.

At this point the best thing is probably to open an official support ticket. :thinking:

The first person you get will just be a general Samsung employee working from a script who may not know much about smartthings. But persevere, and eventually the ticket should get escalated to a smartthings engineer who can hopefully help.

You can open a ticket through either the email or phone information on the following page

Let us know how it goes!


Not closer to the hub, it needs to be right next to the hub! Either move the hub to the lock or the lock to the hub. Also make sure you have a beaming repeater very close to the lock when you finally get it to pair.

Yes, I literally had the lock sitting few inches away from the the hub with same results. This was done multiple times with instances of reboot of both hub and lock. I even had to factory reset both with same results.

Thermostat and light switch were done similarly (ie right next to hub) with successful results.

Anyway, I had opened a ticket and provided their requested details. Will post anything helpful found here…


Just a quick update on this. I had opened a ticket with Smarthings Support. I was asked and about to reproduce the issue today, but it now works!

I asked them if they did any on my hub and waiting for a response.

Fortunately, I have installed universal z-wave lock driver from RBOY apps a while back. It did not help as well before. I just checked today and looks like I got an updated driver dated 11/24/2023. This may have helped fix my issue as it is the driver used. I’ll update further but may help anyone seeing similar problem…

1 Like