HUSBZB-1 Z-Wave firmware portion update

Configuration Z-Wave
22

I just set up Home Assistant the other week with a husbzb-1 that I’ve had laying around for a few years. Came across this post and was curious about the S2 support being added in the newer firmware versions since it seemed like it was working on mine.

My husbzb-1 has firmware 4.32, but my S2 devices will say they connected with S2 and show that as their security level. Is this not reporting correctly? Or is there missing features in the earlier firmware? And should I upgrade if I want it to be working correctly with my locks?

23

Are you using OZW or zwave2js? I’m using zwave2jsmqtt, the config options would let me generate and store S2 keys, but nothing would connect above S0_legacy. I just finished the update, but haven’t tried to re-pair any of my S2 devices yet.

24

I started with ZwaveJS then switched to ZwaveJS2mqtt the other day for the nice control panel…but under security level it says S2 Authenticated. My firmware is a tad bit newer than the OP it looks like so I guess it’s possible it was added between those version.

25

Has anyone saved the 500 series SDK in a .zip that they can share? The current link is dead. I emailed silabs support in the hopes they can deliver. Would love to crib the latest version of 6.71 (or whatever the latest actually is).

26

The link I posted is still working.

27

I updated as well and all worked great! I will add that everyone should just use TP28, search here or on the other forum in the post linked here, it is a LOT easier, it’s on the back towards the USB and works great…

Now, I tried to readd my Kwikset 888 locks in S2. I went and made sure in zwavejs I had S2 keys for all 3 fields, restarted it to be safe, unpaired the lock, factory reset, and then paired again with the top security option to try s2 first and I still get s0

here are the logs, anyone have an idea?

2022-01-30T21:23:19.078Z CNTRLR   The inclusion process was stopped
2022-01-30T21:23:19.080Z CNTRLR   finished adding node 35:
                                    basic device class:    Routing Slave
                                    generic device class:  Entry Control
                                    specific device class: Secure Keypad Door Lock
                                    supported CCs: 
                                    · Basic (0x20)
                                    · Door Lock (0x62)
                                    · User Code (0x63)
                                    · Manufacturer Specific (0x72)
                                    · Version (0x86)
                                    · Z-Wave Plus Info (0x5e)
                                    · Device Reset Locally (0x5a)
                                    · Security (0x98)
                                    · Powerlevel (0x73)
                                    · Firmware Update Meta Data (0x7a)
                                    controlled CCs: 
2022-01-30T21:23:19.081Z CNTRLR » [Node 035] Assigning SUC return route...
2022-01-30T21:23:20.059Z CNTRLR   [Node 035] Cannot configure Z-Wave+ Lifeline association: Node does not suppor
                                  t associations...
2022-01-30T21:23:20.060Z CNTRLR   [Node 035] Beginning interview - last completed stage: None
2022-01-30T21:23:20.060Z CNTRLR   [Node 035] new node, doing a full interview...
2022-01-30T21:23:20.061Z CNTRLR » [Node 035] querying protocol info...
2022-01-30T21:23:20.075Z CNTRLR « [Node 035] received response for protocol info:
                                  basic device class:    Routing Slave
                                  generic device class:  Entry Control
                                  specific device class: Secure Keypad Door Lock
                                  node type:             Routing End Node
                                  is always listening:   false
                                  is frequent listening: 1000ms
                                  can route messages:    true
                                  supports security:     false
                                  supports beaming:      true
                                  maximum data rate:     100000 kbps
                                  protocol version:      3
2022-01-30T21:23:20.086Z CNTRLR   [Node 035] Interview stage completed: ProtocolInfo
2022-01-30T21:23:20.087Z CNTRLR » [Node 035] querying node info...
2022-01-30T21:23:20.142Z CNTRLR « [Node 035] node info received
                                  supported CCs:
                                  · Z-Wave Plus Info
                                  · Manufacturer Specific
                                  · Device Reset Locally
                                  · Security
                                  · Powerlevel
                                  · Firmware Update Meta Data
                                  controlled CCs:
2022-01-30T21:23:20.144Z CNTRLR   [Node 035] Interview stage completed: NodeInfo
2022-01-30T21:23:20.146Z CNTRLR » [Node 035] Querying securely supported commands (S0)...
2022-01-30T21:23:20.329Z CNTRLR « [Node 035] received secure commands (S0)
                                  supported CCs:
                                  · Version
                                  · Battery
                                  · Door Lock
                                  · User Code
                                  · Association
                                  · Association Group Information
                                  · Notification
                                  · Configuration
                                  · Anti-Theft
                                  controlled CCs:
2022-01-30T21:23:20.330Z CNTRLR   [Node 035] Interviewing Manufacturer Specific...
2022-01-30T21:23:20.330Z CNTRLR » [Node 035] querying manufacturer information...
2022-01-30T21:23:20.395Z CNTRLR « [Node 035] received response for manufacturer information:
                                    manufacturer: Spectrum Brands (0x90)
                                    product type: 0x03
                                    product id:   0x0541
2022-01-30T21:23:20.396Z CNTRLR   [Node 035] Interviewing Version...
2022-01-30T21:23:20.396Z CNTRLR » [Node 035]   querying the CC version for Version...
2022-01-30T21:23:20.581Z CNTRLR   [Node 035]   supports CC Version (0x86) in version 2
2022-01-30T21:23:20.581Z CNTRLR » [Node 035] querying node versions...
2022-01-30T21:23:20.756Z CNTRLR « [Node 035] received response for node versions:
                                    library type:      Enhanced Slave (0x03)
                                    protocol version:  4.34
                                    firmware versions: 4.79, 65.6
                                    hardware version:  5
2022-01-30T21:23:20.756Z CNTRLR » [Node 035] querying CC versions...
2022-01-30T21:23:20.756Z CNTRLR » [Node 035]   querying the CC version for Basic...
2022-01-30T21:23:20.946Z CNTRLR   [Node 035]   does NOT support CC Basic (0x20)
2022-01-30T21:23:20.946Z CNTRLR » [Node 035]   querying the CC version for Door Lock...
2022-01-30T21:23:21.120Z CNTRLR   [Node 035]   supports CC Door Lock (0x62) in version 2
2022-01-30T21:23:21.120Z CNTRLR » [Node 035]   querying the CC version for User Code...
2022-01-30T21:23:21.291Z CNTRLR   [Node 035]   supports CC User Code (0x63) in version 1
2022-01-30T21:23:21.291Z CNTRLR » [Node 035]   querying the CC version for Manufacturer Specific...
2022-01-30T21:23:21.468Z CNTRLR   [Node 035]   supports CC Manufacturer Specific (0x72) in version 2
2022-01-30T21:23:21.469Z CNTRLR » [Node 035]   querying the CC version for Z-Wave Plus Info...
2022-01-30T21:23:21.642Z CNTRLR   [Node 035]   supports CC Z-Wave Plus Info (0x5e) in version 2
2022-01-30T21:23:21.642Z CNTRLR   [Node 035]   skipping query for Device Reset Locally (0x5a) because max implem
                                  ented version is 1
2022-01-30T21:23:21.642Z CNTRLR   [Node 035]   skipping query for Security (0x98) because max implemented versio
                                  n is 1
2022-01-30T21:23:21.642Z CNTRLR   [Node 035]   skipping query for Powerlevel (0x73) because max implemented vers
                                  ion is 1
2022-01-30T21:23:21.642Z CNTRLR » [Node 035]   querying the CC version for Firmware Update Meta Data...
2022-01-30T21:23:21.811Z CNTRLR   [Node 035]   supports CC Firmware Update Meta Data (0x7a) in version 3
2022-01-30T21:23:21.811Z CNTRLR » [Node 035]   querying the CC version for Battery...
2022-01-30T21:23:21.980Z CNTRLR   [Node 035]   supports CC Battery (0x80) in version 1
2022-01-30T21:23:21.980Z CNTRLR » [Node 035]   querying the CC version for Association...
2022-01-30T21:23:22.148Z CNTRLR   [Node 035]   supports CC Association (0x85) in version 2
2022-01-30T21:23:22.148Z CNTRLR » [Node 035]   querying the CC version for Association Group Information...
2022-01-30T21:23:22.329Z CNTRLR   [Node 035]   supports CC Association Group Information (0x59) in version 1
2022-01-30T21:23:22.329Z CNTRLR » [Node 035]   querying the CC version for Notification...
2022-01-30T21:23:22.499Z CNTRLR   [Node 035]   supports CC Notification (0x71) in version 4
2022-01-30T21:23:22.500Z CNTRLR » [Node 035]   querying the CC version for Configuration...
2022-01-30T21:23:22.672Z CNTRLR   [Node 035]   supports CC Configuration (0x70) in version 1
2022-01-30T21:23:22.672Z CNTRLR   [Node 035]   skipping query for Anti-Theft (0x5d) because max implemented vers
                                  ion is 0
2022-01-30T21:23:22.692Z CNTRLR   [Node 035] Embedded device config loaded
2022-01-30T21:23:22.696Z CNTRLR   [Node 035] Interviewing Z-Wave Plus Info...
2022-01-30T21:23:22.696Z CNTRLR » [Node 035] querying Z-Wave+ information...
2022-01-30T21:23:22.757Z CNTRLR « [Node 035] received response for Z-Wave+ information:
                                  Z-Wave+ version: 1
                                  role type:       SleepingListeningSlave
                                  node type:       Node
                                  installer icon:  0x0300
                                  user icon:       0x0300
2022-01-30T21:23:22.758Z CNTRLR   [Node 035] Interviewing Battery...
2022-01-30T21:23:22.758Z CNTRLR » [Node 035] querying battery status...
2022-01-30T21:23:22.948Z CNTRLR « [Node 035] received response for battery information:
                                  level:                           100
2022-01-30T21:23:22.949Z CNTRLR   [Node 035] Interviewing Association...
2022-01-30T21:23:22.949Z CNTRLR » [Node 035] querying number of association groups...
2022-01-30T21:23:23.121Z CNTRLR « [Node 035] supports 2 association groups
2022-01-30T21:23:23.121Z CNTRLR » [Node 035] querying association group #1...
2022-01-30T21:23:23.304Z CNTRLR « [Node 035] received information for association group #1:
                                  maximum # of nodes: 1
                                  currently assigned nodes: 
2022-01-30T21:23:23.304Z CNTRLR » [Node 035] querying association group #2...
2022-01-30T21:23:23.471Z CNTRLR « [Node 035] received information for association group #2:
                                  maximum # of nodes: 5
                                  currently assigned nodes: 
2022-01-30T21:23:23.473Z CNTRLR   [Node 035] Checking/assigning lifeline groups: 1
                                  supports classic associations:       true
                                  supports multi channel associations: false
2022-01-30T21:23:23.473Z CNTRLR   [Node 035] Configuring lifeline group #1:
                                  group supports multi channel:  false
                                  configured strategy:           auto
                                  must use node association:     true
                                  must use endpoint association: false
2022-01-30T21:23:23.473Z CNTRLR » [Node 035] Assigning lifeline group #1 with a node association via Association
                                   CC...
2022-01-30T21:23:23.742Z CNTRLR   [Node 035] Lifeline group #1 was assigned with a node association via Associat
                                  ion CC
2022-01-30T21:23:23.751Z CNTRLR   [Node 035] Interviewing Association Group Information...
2022-01-30T21:23:23.752Z CNTRLR » [Node 035] Association group #1: Querying name...
2022-01-30T21:23:23.933Z CNTRLR « [Node 035] Association group #1 has name "Lifeline"
2022-01-30T21:23:23.934Z CNTRLR » [Node 035] Association group #1: Querying command list...
2022-01-30T21:23:24.112Z CNTRLR » [Node 035] Association group #2: Querying name...
2022-01-30T21:23:24.309Z CNTRLR « [Node 035] Association group #2 has name "Doorlock notify report"
2022-01-30T21:23:24.310Z CNTRLR » [Node 035] Association group #2: Querying command list...
2022-01-30T21:23:24.478Z CNTRLR » [Node 035] Association group #1: Querying info...
2022-01-30T21:23:24.648Z CNTRLR « [Node 035] Received info for association group #1:
                                  info is dynamic: false
                                  profile:         General: Lifeline
2022-01-30T21:23:24.648Z CNTRLR » [Node 035] Association group #2: Querying info...
2022-01-30T21:23:24.831Z CNTRLR « [Node 035] Received info for association group #2:
                                  info is dynamic: false
                                  profile:         Notification: Access Control
2022-01-30T21:23:24.847Z CNTRLR   [Node 035] Interviewing Door Lock...
2022-01-30T21:23:24.848Z CNTRLR » [Node 035] requesting lock configuration...
2022-01-30T21:23:25.033Z CNTRLR « [Node 035] received lock configuration:
                                  operation type:                Constant
                                  outside handles can open door: true, true, true, true
                                  inside handles can open door:  true, true, true, true
2022-01-30T21:23:25.033Z CNTRLR » [Node 035] requesting current lock status...
2022-01-30T21:23:25.219Z CNTRLR « [Node 035] received lock status:
                                  current mode:       Unsecured
                                  door status:        open
                                  bolt status:        unlocked
                                  latch status:       open
2022-01-30T21:23:25.225Z CNTRLR   [Node 035] Interviewing User Code...
2022-01-30T21:23:25.226Z CNTRLR » [Node 035] querying number of user codes...
2022-01-30T21:23:25.462Z CNTRLR   [Node 035] Interviewing Notification...
2022-01-30T21:23:25.462Z CNTRLR » [Node 035] querying supported notification types...
2022-01-30T21:23:25.643Z CNTRLR « [Node 035] received supported notification types:
                                  · Access Control
                                  · Power Management
2022-01-30T21:23:25.643Z CNTRLR » [Node 035] querying supported notification events for Access Control...
2022-01-30T21:23:25.859Z CNTRLR « [Node 035] received supported notification events for Access Control: 1, 2, 3,
                                   4, 5, 6, 8, 9, 10, 11, 12, 13, 14, 15, 19, 20, 21
2022-01-30T21:23:25.859Z CNTRLR » [Node 035] querying supported notification events for Power Management...
2022-01-30T21:23:25.916Z DRIVER   Dropping message with invalid payload
2022-01-30T21:23:25.965Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-30T21:23:26.186Z CNTRLR « [Node 035] received supported notification events for Power Management: 9, 10,
                                   11
2022-01-30T21:23:26.187Z CNTRLR » [Node 035] enabling notifications for Access Control...
2022-01-30T21:23:26.287Z CNTRLR » [Node 035] enabling notifications for Power Management...
2022-01-30T21:23:26.389Z CNTRLR   [Node 035] Interviewing Configuration...
2022-01-30T21:23:26.390Z CNTRLR   [Node 035] ConfigurationCC: Loading configuration parameters from device confi
                                  g
2022-01-30T21:23:26.398Z CNTRLR » [Node 035] querying parameter #33 value...
2022-01-30T21:23:26.608Z CNTRLR « [Node 035] parameter #33 has value: 959985720
2022-01-30T21:23:26.608Z CNTRLR » [Node 035] querying parameter #34 value...
2022-01-30T21:23:26.800Z CNTRLR « [Node 035] parameter #34 has value: 808464436
2022-01-30T21:23:26.801Z CNTRLR » [Node 035] querying parameter #35 value...
2022-01-30T21:23:26.986Z CNTRLR « [Node 035] parameter #35 has value: 1
2022-01-30T21:23:26.986Z CNTRLR » [Node 035] querying parameter #37 value...
2022-01-30T21:23:27.184Z CNTRLR « [Node 035] parameter #37 has value: 1
2022-01-30T21:23:27.184Z CNTRLR » [Node 035] querying parameter #47 value...
2022-01-30T21:23:27.372Z CNTRLR « [Node 035] parameter #47 has value: 0
2022-01-30T21:23:27.372Z CNTRLR » [Node 035] querying parameter #36 value...
2022-01-30T21:23:27.565Z CNTRLR « [Node 035] parameter #36 has value: 30
2022-01-30T21:23:27.571Z CNTRLR   [Node 035] Interview stage completed: CommandClasses
2022-01-30T21:23:27.572Z CNTRLR   [Node 035] Interview stage completed: OverwriteConfig
2022-01-30T21:23:27.573Z CNTRLR   [Node 035] Interview completed
2022-01-30T21:23:27.573Z CNTRLR   [Node 035] The node is ready to be used
28

well I think the issue is it doesn’t support S2, that stinks, for some reason I thought the Kwikset 888 did… I need to try the Kwikset 620, and I haven’t had these but a few months and don’t have the boxes…

29

I got the Kwikset HC620 today and S2 is working after this update… I had to move it a little closer to pair, but once I did it was fine. Nice to have S2 working!

30

Hi

I must start by pointing out, that i am very new to this :slight_smile:

I am trying to do the exact same, but i am unable to pass through the USB device. When i run “./ncp.py scan” i receive an exception.

image
image713×115 30.5 KB

I have added Oracle VM VirtualBox Extension Pack in the same version as VirtualBox and added the USB device as a “USB 3.0”.

Hope you are able to clerify.

31

Not sure exactly. For me using VirtualBox I just enabled the USB device from the icons in the bottom right corner of the VM window (not inside VM, but on host). From there I activated USB for the zigbee device and it worked for me.

32

Just stumbled upon this thread. I have all the required software and drivers installed, but VirtualBox simply will not load the drivers for the HUSBZB-1 stick. It shows up in device manager as no drivers loaded. I can force load them by right clicking the .inf file and then Install, which it does, but the device still cannot find the drivers. This is Windows 10 w/latest updates running on VirtualBox 6.1.34 hosted on Fedora Linux.

Any ideas or suggestions would be greatly appreciated.

33

Did you make sure to install the VirtualBox Extension Pack? Have you gotten your HUSBZB-1 working at all or is this your first time setting it up? If this is your first time, I would suggest getting it working first, since this thread is about updating the firmware, which is a bit advanced.

34

Hi David, thank you for your reply. I have been using VirtualBox for some years and yes, I updated the Extension Pack as well as the Guest Additions. It had been months since I last used it so I spent a few hours updating Windows 10 as well.

As there were several Windows CP210x zip files available, I decompressed them all and found the one that supported Windows 10. This would be the one named CP210x_Universal_Windows_Driver.zip which claims both Windows 10 and Windows 11 support.

While this firmware update is indeed quite advanced, it’s no harder than flashing ESP based smart plugs with ESPHome, of which I have done many. This is actually a bit easier. No dremel required. :wink: Unfortunately, I have not gotten that far yet, as until the VirtualBox Windows can load the drivers I cannot continue. I don’t have a real Windows computer, only Linux boxes. I wanted to make sure all was working on the software side before adding the “reset” button to the HUSBZB-1. I do have an old lap top that my ex-wife left. I think it has Win7 on it. I will try to fire it up in the next few days and see what happens there. Not sure it’s even bootable until I find it. lol.

This stick has only been used for Zigbee devices until a few days ago. So far, 38 zigbee devices. I just added two Z-Wave plugs/extenders a few days ago. I also bought 4 of the Kwikset 620 smart locks, but they are still in their boxes for now.

Thanks again.

35

I should also note that I did perform successfully, the zigbee side upgrade of the stick a few days ago. I used the python3 script straight on Fedora 34 without any docker. Worked great and was very easy to do.

Back to the Z-Wave side. My stick has firmware v4.32 on it presently. I have been having to restart the ZWaveJS service several times per day as it suddenly develops ACK issues and can no longer communicate with the smart plugs. I was hoping the F/W update might correct this issue.

May 31 20:27:37 HomeAsstPi 7ac754141e6f[788]: This response was from IP 192.168.254.5, reporting an IP address of 192.168.254.5.
May 31 20:28:32 HomeAsstPi 7276868babc3[788]: 2022-06-01T00:28:32.797Z CNTRLR » [Node 003] pinging the node...
May 31 20:28:33 HomeAsstPi 7276868babc3[788]: 2022-06-01T00:28:33.833Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
May 31 20:28:33 HomeAsstPi 7276868babc3[788]:                                   n 100 ms.
May 31 20:28:34 HomeAsstPi 7276868babc3[788]: 2022-06-01T00:28:34.942Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
May 31 20:28:34 HomeAsstPi 7276868babc3[788]:                                   n 1100 ms.
May 31 20:28:37 HomeAsstPi 7276868babc3[788]: 2022-06-01T00:28:37.066Z CNTRLR   [Node 003] ping failed: Timeout while waiting for an ACK from the controller (
May 31 20:28:37 HomeAsstPi 7276868babc3[788]:                                   ZW0200)
37

Is the Nortek GoControl being sold on Amazon a different device… as I just bought it with firmware 4.32 on it?

I’m also confused as I’ve seen forum posts from as far back as 2018 that this thing was discontinued.

I bought this off Amazon and had planned to return it because I found a UZB-7 I had laying around. So I bought the conbee 2. I hooked them both up and moved everything over. The conbee 2 has been even more rock solid than the Hubitat radio was. I also moved Hue bulbs to it to add repeaters…so there’s that.

The UZB-7 had issue after issue…dropping devices like they never existed. It wouldn’t interview my schlage lock fully whatsoever. I never had issues outside of occasional drops on Hubitat. Hubitat and RM just couldn’t keep up with my home.

I figured with the Nortek already sitting and waiting for UPS that it couldnt hurt to rule out zwave js vs the stick, I already centrally located my Raspi 4 to the spot Hubitat sat for over a year. I put it and the Conbee on 6 ft extension cables. The Nortek has been perfect…interviewed my lock properly and hasn’t had one unresponsive or dropped device.

So now I have a zigbee radio just sitting and no way am I moving whats working… my zigbee devices are taped on the wall and the manufacturer made the bright design decision to put the reset button next to the tape smh.

Is this a new Nortek device? I can’t imagine Amazon has stock 4 years later…and it’s still advertised on Nortek’s website.

If not should I be looking for a 700 series stick as I don’t want something that isn’t being supported, but it does work lol. I just want to make sure with all the changes coming that I’m future proof with my zwave. Should I keep this and wait for something 800 series next year? :thinking:

38

I’m seeing this issue on my HUSBZB-1 as well having to restart ZWaveJS2MQTT as well. Also seeing issues including nodes where it doesn’t start and times out. Devices are also delayed having long RTT values. Have you been able to solve your issues?

39

It disappeared on its own after some update. Sorry not to be of any help. I only have two ZWave smart plug relays, and one smart lock, which I have yet to install.

My RPi4 HA server is located in a disconnected garage from my house and I use TubesZB router to get the Zigbee side into the house. Works perfectly, but having one Z-Wave relay in the garage, cannot connect to the other one in the M.Bedroom of the house, just a mere 20-25 feet away. I am going to try to swap their positions just in case one is bad. Also, fortunately I plan on installing the Z-Wave smart lock on the upstairs door of the garage, so this one should not be an issue…hopefully.

40

So if I upgrade the firmware on my USB stick, will I have to re-include devices? Or will they all be there just as they were before the upgrade, with the same device ID # they had before. I know Home Assistant database will still have references to all the devices, the I believe the USB stick also stores links to each included device.

41

After I updated, my devices were still there and I didn’t need to re-interview.

1 Like
42

I upgraded the firmware today. Very fast and not too hard at all, especially using TP28 on the back side of the USB stick. Now showing version 6.10 for zwave. All my existing devices and settings were kept, so it was pure plug and play. I was able to do an NVM backup just fine using the Home Assistantant ZwaveJS UI interface.