Husbzb-1 issues

Configuration Z-Wave
,
1

I am having difficulty setting up the Nortek/GoControl husbzb-1 for zwave and Zigbee with home assistant. I’ve spent 16+ hours searching for an answer. And testing various possibilities. I know it reads like many people have these dongles working with home assistant images.

For starters, I’ve verified the dongle works as expected without errors under windows 10 and OS X 10.13 and 10.15. Even windows 10 VMware Fusion under OS X 10.15. The Cp210x drivers load fine, and the zwave tools work without any issue under windows.

The primary error message is when HASSIO is loading the dongle.
“cp210x: ttyUSB0: failed set request 0x3 status: -32”
“cp210x: probe of ttyUSB0 failed with error -32”

This same error occurs on the following fresh installations I’ve tested. Brand new installs each.

  1. OSX 10.13 VMware Fusion 7.1.3 with latest 4.13 vmdk

  2. OSX 10.15 VMware Fusion 12.0 with latest 4.13 vmdk

  3. Windows 10 Virtual Box with latest 4.13 OVA

  4. OSX 10.15 Docker for Mac with latest 4.13 vdi

  5. OSX 10.15 VMware Fusion 12.0 with older 4.11 vmdk

  6. OSX 10.15 Virtual Box with latest 4.13 ova

  7. Ubuntu 16.04.02 (no home assistant installed)

The Ubuntu install confirms this is a linux specific USB driver issue. And both the vmware and the docker images unfortunately are running linux drivers, not installed directly on OSX or windows. To reiterate the Windows and OSX drivers work just fine.

What does work

  1. OSX 10.15 docker 4.13 vdi, using serial port redirection from OSX. ( host side /dev/cu.GoControl_zwave mapped to guest side /dev/ttys0)

I have confirmed that VMware Fusion grabs the USB device away from the host, when it’s set to attach directly to the guest OS. The /dev entries disappear and the logs shows the device removed from OSX.

The 0x3 error is a basic line set, where linux is attempting to open an invalid serial port line option very early in the process. -32 appears to just indicate that the USB mounting will be stalled/cancelled. so the ttyUSB0 never gets created.

There has to be some linux driver option, or configuration step that’s not document anywhere on home assistant site. Why would linux have an invalid driver setting, and where are they set? When windows and OSX are just fine?
Any help would be greatly appreciated. As this is a deal breaker if home assistant will not work for me with the dongle.

2

I have this same problem periodically AFTER the Nortek is set up. It will work for a while and then fail in this way. I am using Virtual Box to run HASS. Did you even figure out a fix?

1 Like
3

Get a usb extension cable. USB ports are notorious for interference and causing weird problems.

4

Have you had this same issue and fixed it with an extension cable?

5

I had different but similar issues. But dozens and dozens of people have had random issues fixed with an extension cable. Start there no matter what.

6

Ah OK. Good idea. I will try it.

7

So USB extension didn’t work. It seems to be related to the HubZ losing connectivity to the VM after a period of time. It can be fixed temporarily by restarting the VM.

8

I’ve always had this problem, even with a very good extension cable on Windows 10. I already have the latest Windows device drivers and the latest version of VirtualBox 6.1. It works great for several days in a row… eventually, get these errors, requiring me to restart the VM completely.

Has anyone figured out a way to prevent this from happening?

9

Same issue here. the ZWave hub fails, and I get the same errors. Sometimes I can detach and re-attach the ZWave hub and it will start working. Other times I cannot get it to work, and I’ll spend an hour or two messing around with it. It’s very annoying.