Core: Home Assistant Not Restarting in Docker Image Z-Wave Issue

[grangemd]

Home Assistant release with the issue:
0.85.1

Last working Home Assistant release (if known):

Operating environment (Hass.io/Docker/Windows/etc.):
Unraid Docker

Component/platform:
Z-Wave

Description of problem:

When I updated to 0.85.0 and 0.85.1 I have begun to have massive Z-Wave problems. I am using the Aeotec Z-Wave stick. I have hand numerous problems with devices being stuck in the probe state. Also now when I restart the docker image it fails. I get and execution error stating that tty/ACM0 cannot be found so to fix it I have to reboot the PC. It has become quite the issue.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

[jonare77]

I also have these problems. When rebooting my docker host the Aeotec comes up either as ACM0 or ACM01. Editing the configuration with the following does nothing.

zwave: usb_path: /dev/ttyACM1

Almost seems like this setting is ignores. It defaults and demand ttyACM0

[kpine]

Because it is ignored. The path is configured in .storage/core.config_entries not configuration.yaml.

For Aeotec (and other Sigma based sticks), avoid headaches by using /dev/serial/by-id/usb-0658_0200-if00 instead of /dev/ttyACM0. It will not change.

[rpitera]

For Aeotec (and other Sigma based sticks), avoid headaches by using/dev/serial/by-id/usb-0658_0200-if00 instead of /dev/ttyACM0. It will not change.

@kpine - Is this just for Docker or will this work with VirtualBox setups too? I'm running into the exact same issue with my Aeotec stick bouncing between /dev/tty/ACM0 and /dev/tty/ACM1 on VM machine restarts.

[rpitera]

Never got a response, but /dev/serial/by-id/usb-0658_0200-if00 seems to work in Virtualbox in case it helps anybody.

[webdjoe]

@grangemd have you tried this solution:

Because it is ignored. The path is configured in .storage/core.config_entries not configuration.yaml.

For Aeotec (and other Sigma based sticks), avoid headaches by using /dev/serial/by-id/usb-0658_0200-if00 instead of /dev/ttyACM0. It will not change.

[Therealram]

I had the same issue using an Aeoteck USB stick in Virtualbox that I just set up. I was really scared that my whole zwave network would need to be readded. But thankfully I found this and made the change! I'm still having a weird issue where randomly my most recently added entities are saying "entity not available" and I can't find their zwave information anywhere. But for now I at least have half of them back online

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.