hass.io - /dev/serial not exposed within homeassistant docker

[ghost]

@BaQs commented on Dec 27, 2018, 7:06 PM UTC:

Home Assistant release with the issue:
hassio v 1.4.0
home assistant v0.84.6

Last working Home Assistant release (if known):
none

Operating environment (Hass.io/Docker/Windows/etc.):
raspberry pi - hassio official image

Component/platform:
z-wave usb dongle
rfxtrx (rfxcom) usb device

Description of problem:
As I want my installation to be reboot-proof, I changed /dev/ttyUSBx or /dev/ttyACMx to /dev/serial/xxx

but /dev/serial is not exposed within homeassistant's container.

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

zwave:
   usb_path: /dev/ttyACM0
  #  device: /dev/serial/by-id/usb-0658_0200-if00
   network_key: !secret zwave_network_key 

rfxtrx:
   device: /dev/ttyUSB0
  #  device: /dev/serial/hoby-id/usb-RFXCOM_RFXtrx433_A1K5NSX-if00-port0
  #  debug: true

Traceback (if applicable):

Additional information:

This issue was moved by frenck from home-assistant/home-assistant#19609.

[bobzer]

Would love to see this fix
maybe just add :
str(self.sys_config.path_extern_share):
{‘bind’: ‘/dev/serial/by-id’, ‘mode’: ‘rw’},
to homeassistant.py at line 74 ?

[WaaromZoMoeilijk]

@bobzer Where would this fix go on hassio running on an ubuntu VM? I have multiple homeassistant.py's

[bobzer]

in this file : hassio/hassio/docker/homeassistant.py
https://github.com/home-assistant/hassio/blob/267791833e95f84ec1b52cd10f6f50dbfa39c027/hassio/docker/homeassistant.py
line 74

[WaaromZoMoeilijk]

Thank you sir,

I found that this also works (without exposing /dev/serial... weird, is does work when i specify the /dev/serial/by-id/device in hass)
#911

Also applied your fix, should be a success ^^

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[pvizeli]

@ezraholm50 yes, udev is running inside home assistant container and create such folders

[KennethLavrsen]

I do not understand why this is marked as wontfix. The /dev/serial is NOT exposed inside the home assistant container. When I do a SSH to the container it is not listed in ls /dev
And it is not shown when you look at the hardware button popup under the hass.io->system tab
I have two serial devices and sometimes one gets recorded before the other and end up as ttyACM0 or ttyACM1. The right and easy way to do it in Ubuntu land is to use the symlink under /dev/serial/by-id but these are not exposed to Home Assistant. I have seen this requested many times in the forum and noone ever found a way to fix it. There is a very good reason to fix this

[jtscott]

Agreed with @KennethLavrsen

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.