How to add zwave/zigbee USB to hassio docker

Configuration
,
1

There’s a previous thread on this topic, but it’s 2 years old, so maybe things have changed.

Following the instructions on this page, it works well -all the docker containers are up and running. And the installer “Requirements” notes page does say that " Access USB devices: done by the installer". This part I’m not sure about. When I look at the System>Host Hardware Info in HA, it does pickup on the USB zwave/zigbee stick along with the correct paths, but it doesn’t show up in HA as a device or integration like it does with just the HA-Core docker image.

This page does say to modify the configuration.yaml file to add zwave (and similarly zigbee) which I did do:

# Example configuration.yaml entry
zwave:
  usb_path: /dev/ttyUSB0 
  device_config: !include zwave_device_config.yaml

But when I verify the config, it doesn’t like the config file path.

I’m missing something. I think the best thing to do would be just to edit the ‘docker run’ file for the hassio installation and add the devices with the below two lines - but I don’t see a way to do that from within the script linked above.

--device=/dev/ttyUSB0 \
--device=/dev/ttyUSB1 \

Maybe this is a dead-end, maybe I just stick to HA-Core with no supervisor and no add-on panels, but that does seem like it would make things much easier to administer HA.

2

As usual, time will heal all wounds and solve problems…sometimes. Replying here in case someone else runs into similar problems.

I figured out that since HA was seeing the /dev devices in the Hardware info screen, it was just a matter of adding the zwave and ZHA controllers in integrations.

I am so pleased to get this working - it’s been a struggle the past couple days trying to migrate from the silo of HA-Core container, but I am finally at peace to have supervisor and add-ons working now. Now to get busy moving things over from ST.

And if anyone who has a GoControl CECOMINOD016164 HUSBZB-1 USB Hub wonders about the mappings on Ubuntu 18 - it’s:

zwave:
  usb_path: /dev/ttyUSB0
zha:
  usb_path: /dev/ttyUSB1
3

But you realize those paths can change right?

Thsts why its best to add the devices by-id or by setting up a persistent path in a udev rule. That way no matter what the “real” device path is it will always be seen correctly by HA.