#Schlage Zwave Plus pairing issues

1 messages · Page 1 of 1 (latest)

daring cape
#

For the life of me I can not get my Schlage Zwave Locks moved over from Smart Things to home assistant. They easily pair under smart things using the QR provisioning, but miserably fail in Home Assistant. I am a bit lost.

I originally did this in Zwave JS , but then moved to Zwave JS UI as the basic UI left me little information to go on.

Both ended in the same result: failure.

No matter what I select, the system keeps adding it with no security as a node it can only ping.

This includes me trying to tell ZwaveJSUI to only allow secure joins and doing a scan inclusion. Nada. Same result.

Im hoping others have experienced this pain.

Here are some basic details:

Provision JSON:

"securityClasses": {
  "s2AccessControl": true,
  "s2Authenticated": false,
  "s2Unauthenticated": false,
  "s0Legacy": false
},

To be clear - even tho Home Assistant adds it as this ping only node - the lock reports join failure every time. (red light).

Any help would be appreciated. Im a bit lost at this point on what to do and have moved them back to smarthings for now.

#

Giving 03 ChatGPT the logs I get this:

Nice—those logs are from Z‑Wave JS UI and they show why it’s failing:

The controller keeps trying S2 (S2_*) but fails to decode the SPAN/nonce frames, then gives up and probes S0, then goes non‑secure.

Every packet shows RSSI ~ –87 dBm and is routed through repeater node 13. That’s too weak for S2 bootstrapping.

Do this exactly (JS UI)
Exclude & wipe the lock

Control Panel → Remove/Exclude. On the lock: Schlage → Programming Code → 0 (or press the red enroll button).

If needed, factory reset the BE469ZP: remove battery, hold Schlage button, reconnect battery, wait for the green check/beep, release. Use the default PC from the label afterward.

Clear SmartStart entry

SmartStart page → delete any provisioning entry for this lock.

Force direct, low‑power inclusion

Put the USB stick within 6–24 inches of the lock (USB extension helps). Fresh alkaline batteries in the lock.

Control Panel → Add/Include

Click Advanced and turn OFF “Network‑wide inclusion (NWI)”.

Turn ON “Low‑power inclusion” (forces direct link, no repeaters).

Choose Strategy: Security S2.

Start inclusion. When prompted, enter the first 5 digits of the DSK and grant S2 Access Control.

Let the interview finish

If it stalls once, use Re‑interview node.

On the node page, confirm Security: S2 Access Control. If it says None/Non‑secure, exclude and repeat with the stick even closer.

Why this should work
Your log shows repeated failed to decode … SPAN during S2 and ACK RSSI: -87 dBm via node 13. S2’s nonce/SPAN exchange is very sensitive; routing + weak RSSI breaks it. Direct, low‑power inclusion in whisper‑range fixes that.

If you don’t see the Advanced toggles in the Include dialog, tell me your JS UI version and I’ll point to the exact spot. Also share how close the stick actually is during inclusion.

brave wyvern
#

Some people need to move the lock to within inches of the controller for inclusion, then move it back to the install location and rebuild its routes.

daring cape
#

Yah - that’s the hint I’m getting . Bit of a pain with my VM setup in the basement and the lock on the first floor

#

Think I’ll uninstall the lock and move it down there .

#

It’s an 800 controller btw

daring cape
#

Moving it closer did work, however it took me 5+ tries even with the radio on top of it. Happy to move on and hopefully forget about this..

brave wyvern
#

what SDK version of controller?