How do I add Schlage BE469 to HA with Zooz 800 Series Long Range USB Controller?

[invisible999 (Irakli)]

I have:

1. Zooz 800 Series Long Range USB Controller
2. Schlarge BE469
3. HAOS

I did the following:

• Added Z-Wave JS UI via Add-on, added sucessfuly
• Went to UI of Zwave JS - configured the device in the settings section by providing USB device path. Device is configured correctly, here are logs

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-zwave-js-ui: starting
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-zwave-js-ui successfully started
s6-rc: info: service zwave-js-ui: starting
s6-rc: info: service zwave-js-ui successfully started
s6-rc: info: service discovery: starting
[20:39:08] INFO: Starting the Z-Wave JS UI...
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
2024-04-03 20:39:10.045 INFO APP: Version: 9.9.1
2024-04-03 20:39:10.052 INFO APP: Application path:/opt
  ______  __          __                      _  _____     _    _ _____ 
 |___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
    / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |  
   / /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |  
  / /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_ 
 /_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|

2024-04-03 20:39:10.102 WARN STORE: scenes.json not found
2024-04-03 20:39:10.149 INFO APP: Listening on port 44920 protocol HTTP
2024-04-03 20:39:10.181 INFO MQTT: MQTT is disabled
2024-04-03 20:39:10.184 WARN BACKUP: Store backup is disabled
2024-04-03 20:39:10.186 WARN BACKUP: Nvm backup is disabled
2024-04-03 20:39:10.212 INFO Z-WAVE: Connecting to /dev/ttyACM0
[20:39:10] INFO: Starting NGinx...
Logging to file:
	/data/store/logs/zwavejs_2024-04-03.log
2024-04-03 20:39:12.333 INFO GATEWAY: Driver is READY
2024-04-03 20:39:12.334 INFO Z-WAVE: Z-Wave driver is ready
2024-04-03 20:39:12.334 INFO Z-WAVE: Controller status: Driver ready
2024-04-03 20:39:12.344 INFO Z-WAVE: Scanning network with homeid: 0xcbfd5300
2024-04-03 20:39:12.347 INFO Z-WAVE: [Node 001] Is alive
2024-04-03 20:39:12.350 INFO Z-WAVE: [Node 001] Value added 1-32-0-currentValue => undefined
2024-04-03 20:39:12.392 INFO Z-WAVE: [Node 001] Ready: Zooz - ZST39 LR (800 Series Long Range USB Controller)
2024-04-03 20:39:12.394 INFO Z-WAVE: Controller status: Scan completed
2024-04-03 20:39:12.394 INFO Z-WAVE: Network scan complete. Found: 1 nodes
2024-04-03 20:39:12.397 INFO Z-WAVE-SERVER: ZwaveJS server listening on 0.0.0.0:3000
2024-04-03 20:39:12.405 INFO Z-WAVE: Z-Wave server started
2024-04-03 20:39:13.356 INFO Z-WAVE-SERVER: DNS Service Discovery enabled
2024-04-03 20:39:13.472 INFO Z-WAVE: Next update scheduled for: Thu Apr 04 2024 00:00:00 GMT-0700 (Pacific Daylight Time)
[20:39:22] INFO: Successfully send discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2024-04-03 20:39:37.743 INFO APP: GET /health/zwave 301 3.801 ms - 191
2024-04-03 20:40:07.803 INFO APP: GET /health/zwave 301 1.045 ms - 191
2024-04-03 20:40:37.855 INFO APP: GET /health/zwave 301 0.540 ms - 191
2024-04-03 20:41:07.898 INFO APP: GET /health/zwave 301 0.662 ms - 191
2024-04-03 20:41:37.935 INFO APP: GET /health/zwave 301 0.802 ms - 191
2024-04-03 20:42:07.967 INFO APP: GET /health/zwave 301 0.531 ms - 191
2024-04-03 20:42:38.000 INFO APP: GET /health/zwave 301 0.493 ms - 191
2024-04-03 20:43:08.038 INFO APP: GET /health/zwave 301 0.719 ms - 191
2024-04-03 20:43:38.073 INFO APP: GET /health/zwave 301 0.794 ms - 191
2024-04-03 20:43:45.426 INFO Z-WAVE-SERVER: Starting logging event forwarder at verbose level
2024-04-03 20:43:50.996 INFO Z-WAVE-SERVER: Stopping logging event forwarder
2024-04-03 20:43:57.041 INFO Z-WAVE: Controller status: Secure inclusion started
2024-04-03 20:44:08.111 INFO APP: GET /health/zwave 301 0.518 ms - 191
2024-04-03 20:44:38.152 INFO APP: GET /health/zwave 301 0.836 ms - 191
2024-04-03 20:44:41.670 INFO Z-WAVE: Controller status: Inclusion stopped
2024-04-03 20:44:48.966 INFO Z-WAVE-SERVER: Starting logging event forwarder at verbose level
2024-04-03 20:44:55.996 INFO Z-WAVE-SERVER: Stopping logging event forwarder
2024-04-03 20:45:08.186 INFO APP: GET /health/zwave 301 0.566 ms - 191

And a screenshot

Then I went to Zwave JS UI → settings, generated S2 Unauthenticated, S2 Authenticated, S2 Access Control, S0 Legacy codes. Saved, rebooted the system. Seems all good.

• Then I went to Devices and Services → add integration. I unchecked Use the Z-Wave JS Supervisor add-on, put ws://a0d7b954-zwavejs2mqtt:3000 as server URL. It added sucessfuly

• I went to the lock, did factory reset.

In HA I click to Add device from the screen above, it starts scannig.
Go to the lock, hit Schlarge button, the deadbolt extends, I enter programming code, green led starts flashing, I press 0 and after several seconds get red checkmark that lock is not enrolled.

I tried at least 10 times. Same outcome.

The lock is about 4 ft away from the HA box. Batteries are fresh - reading of voltage is 5.8V.

What I am doing wrong? Do I need to correct anything to sucessfuly enroll the lock.

This controller and lock are only two Z-wave devices in the house/setup.

[NathanCu (Nathan Curtis)]

answer here:

Schlage BE469 Zwave (non plus) locks terrible at reporting lock status (don't report or varying delays from short to loooong)

The 469 Non plus ONLY supports S0 whisper join. So you MUST use S0 (or it wont exchange the lock keys correctly) and S2 didn’t exist when this thing was originally built. Whisper Join means within 6" (they turn the radio signal strength WAY down on purpose). I have one Non plus left - my others have been replaced with ZPs. For that one lock and my garage door openers I have a 50’ LAN cable so I can bring my actual HA box and coordinator next to the device - then I just stick my ZWave coordina…

This particular lock has some special considerations.

[invisible999 (Irakli)]

Thank you very much. Will answer there.

[Alain_Raymond]

Also replied to you in the other thread, but if your lock was included in another network before (and I guess this was this case since the BE469 is the 10 years old version of the newer BE469+) you MUST do the exclusion process before being able to include it again in a new network (using S0 only as stated above). The factory reset wont help, it only clears the user codes / user parameters, but the lock stays “locked” to the old network, so you really have to exclude it first.

The exclusion process is the same procedure as the inclusion process (Schlage button → programmer code → 0) but with z-wave-js ui in exlusion mode instead of inclusion mode. Once excluded, you can do the inclusion procress.

Had the same issue when switching from vera lite to z-wave-js ui and wasted so much time figuring this!

[invisible999 (Irakli)]

Yes, there should be a KB article detailing this. And I found Z-wave experience considerably more challenging and user-unfriendly compared to Zigbee.