#ZWave smart lock not adding properly in zwavejs

1 messages · Page 1 of 1 (latest)

rocky stump
#

Not sure if maybe my zwave device is outdated, but when I'm attempting to add a new smart lock (Schlage BE469ZP), the enrollment process fails with no security and zwavejs2mqtt just shows unknown manufacturer and shows none of the devics information. My Zwave stick is an Aeon DSA02203-ZWUS Labs Z-Wave Z-Stick Series 2 USB Dongle.

I get the following error: Expected message was not received within the corresponding timeout

I saw some posts to increase the timeout in zwavejs settings, but that does not seem to help.

astral furnace
rocky stump
#

I don't think so. My other devices are an inwall switch and 2 thermostats, the UI shows none of them have security

#

Let me get the logs

#

zwave-js-ui: 9.27.2.b0ade31
zwave-js: 14.3.2

#

Done a lot of resetting, exclusions, inclusions, hard resets, etc.

astral furnace
#

In those logs it's currently node 10?

#

All of the S2 messages are basically failing. Not sure if you have a network connectivity problem. This device in particular seems to be known to have problems.

rocky stump
#

@astral furnace so it shouldn't have anything to do with my zwave USB stick being outdated or anything? I did get it in 2014

astral furnace
#

Not sure. S2 is supposed to be purely software supported. I see S2 commands coming and going, so I would say no. On the other hand, I've seen other people report replacing their older sticks works. Not sure that's the first thing I would try. Do you have a USB extension cable connected?

rocky stump
#

I do

#

But I even brought the device to the USB stick, sitting right next to it and attempting all of this

woven heart
#

Did you try factory resetting the lock yet?

rocky stump
#

I did

woven heart
#

I think this is a bug that has been fixed in the latest release.

#

Or the one before that, but definitely not in 9.27.2 / 14.3.2

rocky stump
woven heart
#

Nope

#

.7/.6

rocky stump
#

let me just pull laetst image then

#

zwave-js-ui: 9.27.7.d3d7049
zwave-js: 14.3.6

That's what the UI is telling me with zwavejs/zwavejs2mqtt:latest

#

Let me try the lock now.

#

nah, still got the timeout 😦

#

Think I'm going to give up and get a different lock

woven heart
#

Share a new log first. I can't yet exclude that this is a driver bug. There have been a few recently

rocky stump
woven heart
#

a new one on the latest version

rocky stump
#

Got it. Should I exclude then attempt to re-add the device fresh?

rocky stump
#

@woven heart here's my updated log. newest version, I excluded then attempted to re-include the lock

woven heart
#

Ok that does not look like a driver bug. Did you factory reset the lock again before attempting inclusion?

rocky stump
rocky stump
#

@woven heart I got a new lock, same issue. Swapped out my zwave stick and the second lock came right up. I imagine it's just my old out-of-date zwave stick in the end.