ZWA-2 Not Recognized by Home Assistant

[mortal marlin]

Recently received the ZWA-2 over the weekend and went to get it connected today. I’m currently using a Zooz 800 long range usb stick with no issues (ZST39 LR). Went through the instructions for migrating to a new stick on Zwave JS UI. When I remove the Zooz and plug in the ZWA-2, the computer will not recognize it. I’ve tested with a USB extension cable, without the extension, and with a powered USB hub. The blue light on top comes on and just flashes. With each different set up (extension, hub), I tested the Zooz stick to see if it still worked and it did. I’m a little lost at what to try at this point. I was hopeful it might have been an underpowered USB port but not sure at this point.

Hardware: Odroid N2+ with 2gb of RAM
HomeAssistant OS
Core: 2025.8.3
OS: 16.1
zwave-js-ui: 11.0.1
zwave-js: 15.10.0
Zooz stick is on the latest firmware.

[dark flint]

plug it in then run dmesg on the terminal and see if it gives any info about it being plugged in and/or any errors relating to it.
this will tell us if the kernel is seeing the device being plugged in at all or not.

[mortal marlin]

I’m new to the logs so I’m having some issues copying and pasting them from HA. Here is what I’ve got copied so far. Looks like it’s seeing the device if I understand this correctly. ttyUSB0 is my sky connect and ttyACM0 is the Zooz stick. @dark flint

[ 3161.221233] usb 1-1.1: new full-speed USB device number 20 using xhci-hcd

[ 3161.336140] cp210x 1-1.1:1.0: cp210x converter detected

[ 3161.338512] usb 1-1.1: cp210x converter now attached to ttyUSB0

[ 3176.580331] usb 1-1.4: new low-speed USB device number 21 using xhci-hcd

[ 3177.140347] usb 1-1.4: device descriptor read/64, error -32

[ 3177.340308] usb 1-1.4: device descriptor read/64, error -32

[ 3177.540280] usb 1-1.4: new low-speed USB device number 22 using xhci-hcd

[ 3177.636298] usb 1-1.4: device descriptor read/64, error -32

[ 3177.836281] usb 1-1.4: device descriptor read/64, error -32

[ 3177.940470] usb 1-1-port4: attempt power cycle

[ 3178.572228] usb 1-1.4: new low-speed USB device number 23 using xhci-hcd

[ 3178.572648] usb 1-1.4: Device not responding to setup address.

[ 3178.776910] usb 1-1.4: Device not responding to setup address.

[ 3178.980215] usb 1-1.4: device not accepting address 23, error -71

[ 3179.076227] usb 1-1.4: new low-speed USB device number 24 using xhci-hcd

[ 3179.076649] usb 1-1.4: Device not responding to setup address.

[ 3179.280642] usb 1-1.4: Device not responding to setup address.

[ 3179.484192] usb 1-1.4: device not accepting address 24, error -71

[ 3179.486081] usb 1-1-port4: unable to enumerate USB device

[ 3181.956020] usb 1-1.2: new full-speed USB device number 25 using xhci-hcd

[ 3182.151246] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device

[ 3883.686823] usb 1-1.2: USB disconnect, device number 25

[ 3909.764607] usb 1-1.2: new high-speed USB device number 26 using xhci-hcd

[ 3909.926684] hub 1-1.2:1.0: USB hub found

[ 3909.927048] hub 1-1.2:1.0: 4 ports detected

[ 3909.948720] usb 2-1.2: new SuperSpeed USB device number 4 using xhci-hcd

[ 3910.230684] hub 2-1.2:1.0: USB hub found

[ 3910.230826] hub 2-1.2:1.0: 4 ports detected

[ 3910.280586] usb 1-1.2.1: new full-speed USB device number 27 using xhci-hcd

[ 3910.438941] cdc_acm 1-1.2.1:1.0: ttyACM0: USB ACM device

[ 4047.482804] usb 1-1.2.4: new low-speed USB device number 28 using xhci-hcd

[ 4048.006826] usb 1-1.2.4: device descriptor read/64, error -32

[ 4048.194793] usb 1-1.2.4: device descriptor read/64, error -32

[ 4048.382801] usb 1-1.2.4: new low-speed USB device number 29 using xhci-hcd

[ 4048.466792] usb 1-1.2.4: device descriptor read/64, error -32

[ 4048.654778] usb 1-1.2.4: device descriptor read/64, error -32

[ 4048.759036] usb 1-1.2-port4: attempt power cycle

[ 4049.366740] usb 1-1.2.4: new low-speed USB device number 30 using xhci-hcd

[ 4049.367257] usb 1-1.2.4: Device not responding to setup address.

[ 4049.571201] usb 1-1.2.4: Device not responding to setup address.

[ 4049.774723] usb 1-1.2.4: device not accepting address 30, error -71

[ 4049.858723] usb 1-1.2.4: new low-speed USB device number 31 using xhci-hcd

[ 4049.859232] usb 1-1.2.4: Device not responding to setup address.

[ 4050.063175] usb 1-1.2.4: Device not responding to setup address.

[ 4050.266691] usb 1-1.2.4: device not accepting address 31, error -71

[ 4050.268706] usb 1-1.2-port4: unable to enumerate USB device

[ 8640.552405] hassio: port 8(veth86030d5) entered blocking state

[ 8640.552423] hassio: port 8(veth86030d5) entered disabled state

[ 8640.552455] veth86030d5: entered allmulticast mode

[ 8640.552586] veth86030d5: entered promiscuous mode

[ 8640.654086] eth0: renamed from vethe73ed6a

[ 8640.656334] hassio: port 8(veth86030d5) entered blocking state

[ 8640.656352] hassio: port 8(veth86030d5) entered forwarding state

[dark flint]

we dont need to look at the full dmesg, do a fresh replug of the zwa-2 the run it. this means the most recent lines at the bottom of the dmesg will be in reference to what ther kernel is doing when the device is plugged in

[mortal marlin]

That was way easier. Here is what it came back with on the last lines:

[10746.743206] usb 1-1.2.3: new low-speed USB device number 32 using xhci-hcd
[10747.267187] usb 1-1.2.3: device descriptor read/64, error -32
[10747.455183] usb 1-1.2.3: device descriptor read/64, error -32
[10747.643165] usb 1-1.2.3: new low-speed USB device number 33 using xhci-hcd
[10747.727200] usb 1-1.2.3: device descriptor read/64, error -32
[10747.915190] usb 1-1.2.3: device descriptor read/64, error -32
[10748.023386] usb 1-1.2-port3: attempt power cycle
[10748.631130] usb 1-1.2.3: new low-speed USB device number 34 using xhci-hcd
[10748.631667] usb 1-1.2.3: Device not responding to setup address.
[10748.835676] usb 1-1.2.3: Device not responding to setup address.
[10749.039103] usb 1-1.2.3: device not accepting address 34, error -71
[10749.123110] usb 1-1.2.3: new low-speed USB device number 35 using xhci-hcd
[10749.123670] usb 1-1.2.3: Device not responding to setup address.
[10749.327676] usb 1-1.2.3: Device not responding to setup address.
[10749.531091] usb 1-1.2.3: device not accepting address 35, error -71
[10749.533038] usb 1-1.2-port3: unable to enumerate USB device

[dark flint]

oof, looks like you might have a dud. have you tried a different cable other than the included one? unlikely but you never know maybe the cable is bad?

[mortal marlin]

So you were right about the cable. Replaced with one I had sitting around and now it’s showing up in Home Assistant. That’s the last thing I would have expected.

Thanks for the help! Hopefully this can help others.

[dark flint]

excellent, glad we have a winner. I wouldn't have really expected it either. but was worth testing before considering RMA'ing it. good luck with your setup 🙂

[dark flint]

if you don't mind me asking. where did you order it from?

just in case others have the same problem and its potentially a specific batch or something.

[mortal marlin]

Ordered from ameriDroid on 8/14/25