HUSBZ-1 does not function at at all about supervisor HOT 10 CLOSED

Hass config?

from supervisor.

Did you ever get this working? I'm having the same issue with the same setup.

from supervisor.

from supervisor.

It's encouraging that yours worked. Following the instructions, I created /etc/udev/rules.d/99-usb-serial.rules:

SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="8a2a", SYMLINK+="zwave"
SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="8a2a", SYMLINK+="zigbee"

And updated my configuration.yaml:

zwave:
  usb_path: /dev/zwave

zigbee:
  device: /dev/zigbee

But the HA dashboard still reports "The following components and platforms could not be set up: zigbee, zwave" after a restart. I'll keep futzing with it.

from supervisor.

I got it working without aliases by modifying my configuration.yaml:

zwave:
  usb_path: /dev/ttyUSB0

zha:
  usb_path: /dev/ttyUSB1
  database_path: zigbee.db

from supervisor.

from supervisor.

this ever get fixed? i can't get it to work... z-wave appears to be, but no zigbee

from supervisor.

from supervisor.

@jaredjensen, your udev rules aren't doing what you expect. They were both matching and ending up with the symlinks both pointing to the same node (the last configuration presented by the USB device).

I ended up with a /etc/udev/rules.d/99-usb-serial.rules of:

# For Linear HUSBZB-1. Creates:
#      /dev/zwave0zig1_00  (for zwave)
#      /dev/zwave0zig1_01   (for zigbee)
SUBSYSTEMS=="usb", ENV{.LOCAL_ifNum}="$attr{bInterfaceNumber}"
SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="8a2a", SYMLINK+="zwave0zig1_%E{.LOCAL_ifNum}"

I used a verbose name as a hint to myself in the future about which config is zwave (0) vs zigbee (1).

I additionally have two other Z-Wave USB sticks, which I match more simply with:

# Z-Stick Gen2
SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0001", SYMLINK+="zwavegen2"

# Z-Stick Gen5
SUBSYSTEM=="tty", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", SYMLINK+="zwavegen5"

from supervisor.

Closing this issue, reasoning: This issue predates HassOS.
If this is still an issue, feel free to open a new one with some recent logs.

Thanks 👍

from supervisor.