Linear HUSBZB-1

(use the one without serial enumeration)
https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers

I’m pretty sure I just manually installed the driver instead of running the setup. This is probably the same version as you’re running though. These instructions say to unplug the stick after the restore and plug it in again to initialize changes. Maybe you’re missing that step? The only other thing I can think of is that I was using a local admin account on my laptop and I’m on Win10 x64. If you can’t figure this out, you can set the quickstick up as secondary and then shift it to primary. If you use a Minimote, check out this thread…

It looks like Aeon Labs only has backup software for Windows, but you can do as I just suggested instead of doing a backup/restore. I use Zensys Tools for the primary shift, which is also a Windows app, so you will need to find some other software that can do the primary/secondary shift.

those are the ones I’ve tried, just to be sure I’m redownloading and reinstalling these drivers (since the PIDs in the INF don’t match my device, I’m forcing it to install the driver.

restoring it does do something at least, though all I can see is that it changes the Network Role from RealPrimary to None.

What is the PID of the device you are using? Mine is 8a2a

I do notice that when I run the zensys tool with the nortek stick, this shows up in the log:

01:20:49.057: Exception: CmdZWaveEnableSuc is not implemented in the Z-Wave Device

so I’m not sure if that is normal or a sign of a bad stick.

I plan to add a couple devices tonight, so I’ll check once OH is offline (quickstick is in a Fedora box).

I’m pretty sure I remember that too. Will confirm.

Were you unplugging/plugging the quickstick after the restore, as the instructions instruct? In thinking through all the possibilities, I thought of two more things. There’s an enable/disable checkbox in the backup tool. I believe I read this locks the device for editing, so make sure it is unchecked for the quickstick when doing the restore. The other thing is that I’m pretty sure I had done a reset of the quickstick in Zensys Tools before doing the restore. Maybe that helped me to be able to do the restore.

Yeah, unplugged it after each restore, waited about 1 second and replugged.

I think this is the best indicator that something is wrong with the stick, all that happens if I click that checkbox is an “exclamation” popup dialog that says Set Config Enable Error. I get similar errors if I try the Read Setting button as well.

I’ve tried that as well before each restore. Nothing works. I’ll probably wait until I have a day with the house to myself and go around the house repairing all my devices to the new stick, or I’ll return it.

Thanks for your help

And that was the trick. I followed the steps you laid out in:

and it all seems to run correctly now, though I do get a lot of the following errors:

08:44:17.617 [ERROR] [sage.AssignSucReturnRouteMessageClass] - NODE 75: AssignSucReturnRoute command failed.
08:44:17.623 [ERROR] [sage.AssignSucReturnRouteMessageClass] - NODE 27: AssignSucReturnRoute command failed.
08:44:17.629 [ERROR] [sage.AssignSucReturnRouteMessageClass] - NODE 11: AssignSucReturnRoute command failed.
08:44:17.635 [ERROR] [sage.AssignSucReturnRouteMessageClass] - NODE 30: AssignSucReturnRoute command failed.
08:44:17.642 [ERROR] [sage.AssignSucReturnRouteMessageClass] - NODE 43: AssignSucReturnRoute command failed.
08:44:17.648 [ERROR] [sage.AssignSucReturnRouteMessageClass] - NODE 95: AssignSucReturnRoute command failed.
08:44:17.654 [ERROR] [sage.AssignSucReturnRouteMessageClass] - NODE 79: AssignSucReturnRoute command failed.
08:44:17.660 [ERROR] [sage.AssignSucReturnRouteMessageClass] - NODE 29: AssignSucReturnRoute command failed.
08:44:17.666 [ERROR] [sage.AssignSucReturnRouteMessageClass] - NODE 12: AssignSucReturnRoute command failed.
0

but everything seems to work. It was scary wiping my zstick but it looks like the backup I took did work so I’m able to swap it back in if the quickstick dies.

now on to fiddling with zigbee, I think I have a long thread to read through

I see a lot of these too. But I also saw them on the zstick.

Other than the main Zigbee thread, there are a few threads from people trying to setup Zigbee on the HUSBZB-1.

I added a couple more devices tonight, shutdown OH, and put the quickstick in my laptop. I also get these errors, so not a sign that the stick is bad or a lead to why the restore wasn’t working.

My PID was also 8A2A.

In a support ticket from Aeon Labs, I had asked about restoring to the quickstick. In response, the tech included this in his reply “It pretty much a save state, so if the controllers NodeID is 51, thats what the backup file would have saved.” If the backup is just a memory dump of the nodes in the network, maybe the restore worked for me because I already had the quickstick in the same network (same as you have now done) when I tested the restore. Once I knew I had a good backup of the zstick, I played with so many things that it’s a little cloudy how exactly I got to the point to where I could backup/restore between the sticks. But you might have success with the restore now that it’s on the same network. Anyhow, glad you got the zwave migrated!

Can you give me a list of a few of these - I’d like to check something as I have a better understanding of the routing now…

I posted the log in a ticket on your website.

Thanks, but…

In this case, contrary to my usual stance, I don’t think the log will tell me much more than the request failed. What I’m interested to know is if there’s anything common about the devices that fail - are they battery devices, or a specific type of mains device, or… Is it always the same devices that fail, or does it work with some devices some times and not others?

I believe that some devices will not work with this request for starters, and I probably need to stop sending it to some device types…

(I will take a look at the log when I get a chance though, but about to go on holiday for a few days on the way to the SmartHome event at the weekend).

My files rollover about every 1.5 days. In this data set, it does not look like this affects a specific device model (some devices of a specific model got the error and some did not). However, the devices receiving this error were all mains powered devices, and it was a large percentage of them. There was also one node that is not in OH that got the error… I’ll need to check to see if it is on the stick next restart. It does not appear to be the same devices each time, but I could try to confirm this, if you’d like something more concrete.

I put this all in a spreadsheet, if it’s of any use, including the following errors (the data was filtered on ‘failed’):
Assign return routes failed.
Assign SUC return routes failed.
AssignReturnRoute command failed.
AssignSucReturnRoute command failed.
Delete return routes failed.
Delete SUC return routes failed.
DeleteReturnRoute command failed.
DeleteSUCReturnRoute command failed.
NodeNeighborUpdate FAILED

Yes, it would be really interesting to get an idea of what these nodes are to see if it ties in with my suspicions. I don’t want to ask you to do too much on this, but if it looks like it’s always/mostly the same set of devices, it would be interesting to get the list of which ones you think they are…

Thanks.

Turns out no. The backup is good because I restored my ZStick after the migration procedure and its fine. I noticed that during the migration I lost node19 somehow so I tried restoring the Quickstick but it just wiped it. I redid the migration and luckily all the nodes transferred this time.

Got it working yay! I have a bunch of old SmartThings devices that have been languishing and now at least the 3 plug in outlets have been put to use. I’m looking forward to being able to get the motion sensors and door sensors added too, though from what I’ve read they aren’t added yet.

1 Like

I’m looking for the best solution to have Z-Wave and Zigbee in one go - the Linear HUSBZB-1 looks perfect. The product page does indicate the Z-Wave frequency to be the USA variant. Is there a European variant? Does this mean everybody on this thread lives in the USA? It’s weird I can’t find any indications on this :neutral_face:

From the Operation Manual, the HUSBZB-1 uses 908.42 MHz / 916 MHz for zwave (yep… I’m in the USA!).

What about the newer xiaomi aqara zigbee sensors?

Would they be compatible?

Are they REALLY ZigBee? The current Xiaomi sensors are not 100% ZigBee compatible.

I just found out about this device and ordered one. It will serve as a back up zwave stick at the least, but…

For the ZigBee. Would anyone know what ZigBee Standard it is using? Is it ZigBee 3.0? Or Using ZigBee HA or ZigBee Light Link?

I would like to possibly try and pair the stick to my Osram Lightify RGBW recessed lights if possible.

It’s using (from memory) 5.4 of the Silabs stack which will be ZigBee-Pro.

Shouldn’t be a problem - the binding is being used with a number of devices and I’ve tested against a number of different Osram bulbs.

Device Description
Busch-Jaeger 6711 Relay Insert
Busch-Jaeger 6735 Control Element (1-channel)
Busch-Jaeger 6735/01 Control Element (1-channel, battery-operated)
Busch-Jaeger 6736 Control Element (2-channel)
GE Bulbs
Hue Bulbs Color LED Bulb
Hue Motion Sensor Motion and Luminance sensor
Innr Bulbs note1
Osram Bulbs
SmartThings Plug Metered Plug
SmartThings Motion Sensor CentraLite 3325-S Motion and Temperature sensor
SmartThings Contact Sensor Contact and Temperature sensor
Tradfri Bulbs
Tradfri Motion Sensor
Trust Bulbs note1
Ubisys modules D1 Dimmer, S1/S2 Switch modules