Schlage door lock is Active/Ready - but not responsive #3288
Replies: 3 comments 22 replies
-
|
@ksbuchanan it looks like you're missing a few steps. Between steps 4 and 5, after excluding/removing the node you must do a full factory reset on the lock, which usually means removing the battery connector and replacing it while holding the Schlage button. The inside Schlage LED should flash red and the outside keypad should show the green check mark. On Step 6, make sure you're using "secure inclusion", which is a toggle under "add node". Make sure you have a network key set under Supervisor -> Z-wave -> configuration -> network_key. This is usually set by default on Zwave-JS. See my thread here: Having said that, this is the way it is supposed to work. I have tried over 30 times to get my lock to use secure inclusion, even holding my Z-Wave stick directly against the antenna traces on the PCB of the Schlage lock, and it just refuses to include securely. It finishes the interview process, but will not allow locking/unlocking or proper status reports. Mine (BE469) is an older non-plus Z-wave device. Is it possible that's part of the problem? Some people have reported success with zwavejs2mqtt, but I have no need for MQTT currently and I thought that was just a wrapper around zwave-js anyway. Any thoughts on this? |
Beta Was this translation helpful? Give feedback.
-
The name is misleading. You don't need to use MQTT - using zwavejs2mqtt with the default websocket connection works just fine. zwavejs2mqtt has a control panel UI that lets you do a bunch more than HomeAssistant at the moment. Both use this library under the hood. That said, the HA integration had a bug in the first .9 versions that made it impossible to include securely. Make sure you're up to date. |
Beta Was this translation helpful? Give feedback.
-
|
Ok - I have tried your suggestion several times and I am running the latest
version. I can get it joined - but it still doesn’t operate. It will
join with and without secure connection; secure connection seems to be more
stable and non secure will eventually report as dead.
Ughh…so disappointing.
On Tue, Sep 14, 2021 at 2:23 AM AlCalzone ***@***.***> wrote:
I have no need for MQTT currently
The name is misleading. You don't need to use MQTT. zwavejs2mqtt has a
control panel UI that lets you do a bunch more than HomeAssistant at the
moment. Both use this library under the hood.
That said, the HA integration had a bug in the first .9 versions that made
it impossible to include securely. Make sure you're up to date.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3288 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKF2FU3GZMTVIOUQ452ASFLUB3S6HANCNFSM5D67A2MQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Kevin
|
Beta Was this translation helpful? Give feedback.
-
|
@ksbuchanan to be fair, every single other Z-wave thing I've tried in HA has worked perfectly. This lock is a bad first thing to try. @AlCalzone thanks for the tip; so should I be using zwavejs2mqtt even though I'm not actually using mqtt? I like using the "preferred" solution unless/until I have a really strong understanding of things. What do you mean when you say the first .9 versions? Do you mean > .9 of zwavejs2mqtt, or the regular zwave-js plugin? I'm running Z-Wave JS 0.1.40, but I tried the secure inclusions on 0.1.31 - 0.1.36. |
Beta Was this translation helpful? Give feedback.
-
Should is a strong word. You can use it if you want more control than the official integration gives you.
Fuck there are so many versions involved. I meant the HA versions 2021.9.x @ksbuchanan Locks won't work unless they are included securely. If that doesn't work for you, open an issue and post the requested logs. |
Beta Was this translation helpful? Give feedback.
-
|
@AlCalzone haha, OK, well that's darned useful information. I just updated to 2021.9.6 from 2021.8.x, so that was probably the problem. I haven't tried since the update, so I'll try now. Did every version of HA Core before 2021.9.x have this problem? |
Beta Was this translation helpful? Give feedback.
-
|
The secure inclusion issue mentioned only affects 2021.9.0-3. 2021.8 does not have any problems. |
Beta Was this translation helpful? Give feedback.
-
|
I have tried at least 40 times to get this included with HASS OS, and it's just not happening. Today I finally felt like I got some more useful messages with the latest zwave-js plugin, but it still never went anywhere. System Info: First attempt: second attempt: attempt 3: On my latest attempts, the keypad gives me a red 'x' after 3-5 seconds and doesn't try to include securely. I have tried both This is beyond frustrating. Can someone tell me where to find the entire log on HASS OS? The plugin only gives the last ~100 lines or so. It seems like it does something different every single time. |
Beta Was this translation helpful? Give feedback.
-
|
Looks different, but the end result is the same: This time, the device just doesn't respond to the nonce request. |
Beta Was this translation helpful? Give feedback.
-
|
I don't remember if we went through this already, so here it goes: If your stick is not yet on a USB extension cord, try doing that and put it away from metallic surfaces. Especially USB3 ports are prone to interfere with Z-Wave traffic. Even worse when the stick is in a server rack or something. |
Beta Was this translation helpful? Give feedback.
-
|
OK, all (2) of the USB ports on this NUC are USB3, so I tried plugging the stick in through a USB2 hub away from the NUC and it didn't help. Then I uninstalled the Z-Wave-JS plugin and installed zwavejs2mqtt, and that didn't work either, but all of my S2 devices stopped working (Z-Combo smoke detectors and door/window sensors). I uninstalled zwavejs2mqtt and re-installed the official zwave-js plugin and my S2 devices still don't work. Then I noticed that the new Supervisor config for the zwave-js plugin now has fields for s0_legacy_key and all 3 S2 keys in addition to the network_key, which was the only field available previously. Does that mean there were no S2 keys previously? I have an HA backup and it has the network_key in the options.json portion of the core_zwave_js portion of the backup, but no other keys. Is there any way to recover those keys so that I don't have to exclude/re-pair all my S2 devices? My dog freaks the hell out when I pair my smoke detectors because they make so much damned noise. At this point I've pretty much given up on the lock. |
Beta Was this translation helpful? Give feedback.
-
|
If you weren't using zwavejs2mqtt previously and haven't configured S2 keys, then your devices weren't included with S2. Take this with a grain of salt, since I'm not using HA. |
Beta Was this translation helpful? Give feedback.
-
|
That's true about the addon, and also true if you were included with a prior version of node-zwave-js that didn't support S2. When you uninstall an addon the persistent data store is removed, I believe, which means the network cache was lost. When moving to zwavejs2mqtt, or going back to a uninstalled zwave-js addon, the network cache needs to be rebuilt before the devices will be usable in HA. This means all battery devices need to wake up and be re-interviewed. |
Beta Was this translation helpful? Give feedback.
-
Ok, so to start with I am new to HA and I read articles and watched youtube videos - and expected it to be 'a challenge'. But, I have worked in IT for 30 years, so I know that it would be either be perfect - or a train wreck!! I am running on 3 days experience (total) with HA, so any advise or request for info, will probably need very explicit steps! :-)
After trying to join and failing (many times), I found a 'pattern' of how to unenroll the device and re-join to HA! Here was my steps that I followed:
My Problem
When I send a Lock or Unlock command, the lock doesn't respond.
I am running HA 2021.9.1, with Nortek Z-Wave/Zigbee combo USB stick. The lock is the only device I have connected, and based on this - I'm not encouraged to buy more!
Some please help advise - what else can I do?
Here is the log file:
Beta Was this translation helpful? Give feedback.
All reactions