SCHLAGE BE469ZP Woes - RESOLVED - UNKNOWN NODE REMOVAL -- HUSBZB-1

Configuration Z-Wave
1

I’ve scoured the forums, Reddit, and every blog I possible could… But I’m still running into major issues with this device & trying to get it on my ZWave Network.

I believe my issue isn’t with the inclusion/exclusion process, per se (I have a network key, it’s in the config and showing the config_entities now), but the fact that I screwed up when originally adding the device(key was in the config but not in the core_entities file)… Oddly enough, it created both nodes despite that fact. (see below)

So it appears that when I originally added the device, it showed as failed on the lock, but was actually added “properly” … I tried to add it as a non-secure device too, which also worked (but I wasn’t checking the logs or the zwcfg file – stupid me). So my next step was to factory reset the lock … I checked the zwcfg file at this point(added it both securely and insecurely) and noticed that two new nodes had been added, but had already reset the lock!

Here’s where the problem comes in … I have two nodes, one that’s not secure & one that’s secure for this device… only the one node(s) is showing on the HomeAssistant Front End (Node13) and (Node 14) is in the zwcfg file but not showing at all. I’m unable to exclude the nodes, even with the lock’s exclusion process … But I’m also unable to remove them, Node 13 is showing as is_failed: true … And I assume if I could see 14 it would also show the same value.

So when I click “remove failed node” in HomeAssistant, it runs but then errors out:

2020-01-12 15:34:25.688 Detail, Node013, Queuing (Controller) Remove Failed Node
2020-01-12 15:34:25.688 Info, ControllerCommand_RemoveFailedNode
2020-01-12 15:34:25.688 Detail, contrlr, Queuing (Command) ControllerCommand_RemoveFailedNode: 0x01, 0x05, 0x00, 0x61, 0x0d, 0x62, 0xf4
2020-01-12 15:34:25.689 Detail, Notification: ControllerCommand - Starting
2020-01-12 15:34:25.689 Detail, 
2020-01-12 15:34:25.689 Info, contrlr, Sending (Command) message (Callback ID=0x62, Expected Reply=0x61) - ControllerCommand_RemoveFailedNode: 0x01, 0x05, 0x00, 0x61, 0x0d, 0x62, 0xf4
2020-01-12 15:34:25.692 Detail, contrlr,   Received: 0x01, 0x04, 0x01, 0x61, 0x18, 0x83
2020-01-12 15:34:25.692 Detail, 
2020-01-12 15:34:25.692 Warning, contrlr, WARNING: Received reply to FUNC_ID_ZW_REMOVE_FAILED_NODE_ID - Command failed
2020-01-12 15:34:25.692 Detail, Node131,   Expected callbackId was received
2020-01-12 15:34:25.692 Detail, Node131,   Message transaction complete
2020-01-12 15:34:25.692 Detail, 
2020-01-12 15:34:25.692 Detail, contrlr, Removing current message
2020-01-12 15:34:25.692 Detail, Notification: ControllerCommand - Failed
2020-01-12 15:34:50.439 Detail, Node013, Queuing (Controller) Remove Failed Node
2020-01-12 15:34:50.439 Info, ControllerCommand_RemoveFailedNode
2020-01-12 15:34:50.439 Detail, contrlr, Queuing (Command) ControllerCommand_RemoveFailedNode: 0x01, 0x05, 0x00, 0x61, 0x0d, 0x63, 0xf5
2020-01-12 15:34:50.439 Detail, Notification: ControllerCommand - Starting
2020-01-12 15:34:50.440 Detail, 
2020-01-12 15:34:50.440 Info, contrlr, Sending (Command) message (Callback ID=0x63, Expected Reply=0x61) - ControllerCommand_RemoveFailedNode: 0x01, 0x05, 0x00, 0x61, 0x0d, 0x63, 0xf5
2020-01-12 15:34:50.443 Detail, contrlr,   Received: 0x01, 0x04, 0x01, 0x61, 0x18, 0x83
2020-01-12 15:34:50.443 Detail, 
2020-01-12 15:34:50.443 Warning, contrlr, WARNING: Received reply to FUNC_ID_ZW_REMOVE_FAILED_NODE_ID - Command failed
2020-01-12 15:34:50.443 Detail, Node131,   Expected callbackId was received
2020-01-12 15:34:50.443 Detail, Node131,   Message transaction complete
2020-01-12 15:34:50.443 Detail, 
2020-01-12 15:34:50.443 Detail, contrlr, Removing current message
2020-01-12 15:34:50.443 Detail, Notification: ControllerCommand - Failed
2020-01-12 15:34:51.841 Detail, Node013, Queuing (Controller) Remove Failed Node
2020-01-12 15:34:51.842 Info, ControllerCommand_RemoveFailedNode
2020-01-12 15:34:51.842 Detail, contrlr, Queuing (Command) ControllerCommand_RemoveFailedNode: 0x01, 0x05, 0x00, 0x61, 0x0d, 0x64, 0xf2
2020-01-12 15:34:51.842 Detail, Notification: ControllerCommand - Starting
2020-01-12 15:34:51.842 Detail, 
2020-01-12 15:34:51.842 Info, contrlr, Sending (Command) message (Callback ID=0x64, Expected Reply=0x61) - ControllerCommand_RemoveFailedNode: 0x01, 0x05, 0x00, 0x61, 0x0d, 0x64, 0xf2
2020-01-12 15:34:51.845 Detail, contrlr,   Received: 0x01, 0x04, 0x01, 0x61, 0x18, 0x83
2020-01-12 15:34:51.845 Detail, 
2020-01-12 15:34:51.845 Warning, contrlr, WARNING: Received reply to FUNC_ID_ZW_REMOVE_FAILED_NODE_ID - Command failed
2020-01-12 15:34:51.845 Detail, Node131,   Expected callbackId was received
2020-01-12 15:34:51.845 Detail, Node131,   Message transaction complete
2020-01-12 15:34:51.845 Detail, 
2020-01-12 15:34:51.845 Detail, contrlr, Removing current message
2020-01-12 15:34:51.845 Detail, Notification: ControllerCommand - Failed

Any ideas/suggestions? I think if I can get both nodes removed, I’d be able to add the lock. But I’m not quite sure how to go about doing that at this point. Since I can’t remove the failed node & one node doesn’t even show up on the front end.

Thanks for any tips/suggestions!

1 Like
2

I figured it out – I’ll edit this post with a full write up. Hopefully it will be of some use to others, my guess is that it will. I’ve intentionally messed with the lock & tried a few different scenarios, I’ve been able to recover from each of them.

EDIT ONE:
I HAVE A HUSBZB-1 – This method should work for other sticks, but will require you to find the drivers for Windows 10. I believe the SilLabs Zwave Controller supports pretty much all sticks. But don’t quote me on that.

PROBLEM & RESOLUTION:

PROBLEMS:
So I had a multitude of issues in comparison to most of the users that seem to experience problems with this lock …
1.) I added the lock as both a normal zwave node & a plus node
2.) I factory reset the lock (as the above two “failed” initially), which wouldn’t allow me to exclude the lock.
3.) I had an Unknown Probe (Node 13) that I couldn’t delete with the “Remove Failed Node” button.
4.) Node 14 was the ZWave Plus Node for the Lock, but wasn’t being displayed by Homeassistant.

So taking all those into account, I assumed if I could get the two nodes off the controller, it would pair.
RESOLUTION:
1.) Scour the forums, open topics, try 101 different things… get frustrated, then sit back and relax for a day or two. – This is a joke, it’s basically what I did.

2.) If you’re a Windows 10 User – You need two pieces to the puzzle … A driver so Windows 10 will recognize your USB Stick/Controller & the Zwave PC Controller.

CP210x USB to UART Bridge VCP Drivers - Silicon Labs – Windows Driver for the HUSBZB-1 … It probably supports a plethora of other controllers too, since SilLabs is a fairly large manufacturer.

https://hf-files-oregon.s3.amazonaws.com/hdpthesmartesthouse_kb_attachments/2019/12-10/e2117ab0-ae3c-4cde-a6aa-589466f88941/ZWavePCController_v5_39.zip – ZWavePCController … Feel free to run this in SandBoxie or VirtualBox (you can pass the USB Stick through) if you’re concerned.

You can download it directly from the Zooz website too (How to Perform an OTA Firmware Update on Zooz Devices - Zooz Support Center)… The link above is on this page, right hand side. Zooz is a reputable brand, so I trusted them enough to install outside of the Sandbox.

3.) Once you get the Driver & Software Installed – Plug the stick into the Windows 10 Machine, Click the Gear Icon, select the USB/Serial device listed, there isn’t one try hitting the Refresh button.

4.) After that, click Network Management, find your “Failed” devices … Use the Remove Failed Node button & BAM, the Node(s) should be gone. If they aren’t yet “Failed” you can use this device to FORCE them to a failed status & then remove them.

5.) Close the Program, plug the stick back into your PI/Server.

6.) Edit the zwcfg_XXXXX file, by removing the previously failed nodes…

7.) Start Home Assistant – Other guides recommend EXCLUDING the Schlage Lock before adding, I tried it both ways & both were successful. Needless to say, I suggest EXCLUDING first & then adding just to be safe.

8.) Profit.

– If these links ever die, feel free to message me directly and I will provide the software.

EDIT TWO:

MAKE SURE YOU HAVE A NETWORK KEY IN core.config_entries… Otherwise this will fail over and over.

EDIT THREE: I tried utilizing Open Zwave Control Panel too, I wasn’t able to remove the failed nodes via that method … The only method that worked for me was the above method, which makes a lot of sense. You’re basically doing DIRECT interfacing with the device via a very very well designed piece of software. I’m probably going to install it on a Windows 10 VM & do all of my configuration via the Zwave PC Controller moving forward, since it has so much more in terms of features in comparison to the Home Assistant UI. But that’s neither here nor there for now.

EDIT FOUR: If you can’t get the driver installed, try these instructions found:

  1. Download Silicon Labs drivers
  2. Extract drivers to a folder (I’ll use C:\CP210x_Windows_Drivers as an example)
  3. Open Windows Device Manager (Win+X, M)
  4. Right-click on “Other Devices > HubZ Z-Wave Com Port” and select “Update driver”
  5. Select “Browse my computer for driver software”
  6. Select “Let me pick from a list of available drivers on my computer”
  7. Leave “Show All Devices” selected and click “Next”
  8. Click “Have Disk”
  9. Enter the folder name where you extracted the downloaded drivers: C:\CP210x_Windows_Drivers
  10. Select “Silicon Labs CP210x USB to UART Bridge” and click “Next”
  11. Windows will prompt that it cannot confirm the device ID, click “Yes” to proceed.
  12. Repeat steps 4-11 for device “HubZ ZigBee Com Port”
1 Like
3

I literally have the same hardware (Windows 10, HUSBZB-1, Schlage lock I can’t remove). I’m stuck at the driver install though - I’ve tried on two different computers and while the driver installs and ends up in the Windows folder, Windows refuses to use it for anything. Because no devices end up using the driver, the Windows 10 app you have here doesn’t pick up any devices.

I’m wondering how your device manager looks with the USB driver installed. Mine has the Zigbee + Zwave devices showing as two line items with driver issues. My attempts to force your driver to install have not been successful. Not sure if I should give up and try doing this in a VM using pass through like you suggested :-\

4

Hey James,

What about trying these steps?

  1. Download Silicon Labs drivers
  2. Extract drivers to a folder (I’ll use C:\CP210x_Windows_Drivers as an example)
  3. Open Windows Device Manager (Win+X, M)
  4. Right-click on “Other Devices > HubZ Z-Wave Com Port” and select “Update driver”
  5. Select “Browse my computer for driver software”
  6. Select “Let me pick from a list of available drivers on my computer”
  7. Leave “Show All Devices” selected and click “Next”
  8. Click “Have Disk”
  9. Enter the folder name where you extracted the downloaded drivers: C:\CP210x_Windows_Drivers
  10. Select “Silicon Labs CP210x USB to UART Bridge” and click “Next”
  11. Windows will prompt that it cannot confirm the device ID, click “Yes” to proceed.
  12. Repeat steps 4-11 for device “HubZ ZigBee Com Port”

I’ll take a screenshot of my device manager later today, hopefully these steps work!

5

Thanks - I found those instructions on Amazon and was just about to post it myself. Anyhow, yes - it did! I’m still tinkering around to get the lock added… next step is to reset to factory and pray.

Regardless, I needed these instructions for some other zwave devices that didn’t want to disappear. Thanks so much for the detailed writeup!

6

Not a problem! Glad you got the software to work!

Try removing the node before adding it, if that doesn’t work… I’d make sure you have a Network Key in the core.config_entries.

Post back if you can’t get it added, I went through a few different scenarios for the hell of it & was able to recover/add it after each… So I’ve got a few additional things you can try.

7

You called it! The network_key was set to NULL. Got it all up now! Thanks.

8

Awesome, glad you got it working!

9

First of all, thanks a lot to pnelson for writing this and finding the solution in how to remove unknown nodes in a z-wave controller.

I am writing an update to the instructions that are here. The software that you will find now in the zooz website, will be one from Silicon Labs, but it called Simplicity Studio, and whiting this software you will find the Z-Wave PC Controller. But for this, you need to download and install it, be patient, it might take some time. To do this, the software will ask you to install something (I don’t remember now due I was in my desperate moment to make things work), but you need to select “install by technology type” and here select Z-Wave. Another way, if you are already in the main window and cannot find it, go to Tools and select add/remove tool and it will bring you to the screen where you can select “install by technology type”.

After the Z-wave tool is installed, you will find it in Tools and scroll down to find it. Now you will be able to be in the Z-Wave PC Controller tool.

Here you can find a guide on how to do what I just explained here https://help.aeotec.com/support/solutions/articles/6000226205-z-wave-command-class-configuration-tool-download-