Home Assistant Supervised (previously known as Hass.io) on Synology DSM as native package (not supported or working atm)

fredrike · July 22, 2019, 7:23am

You should be able to remove it via the networks tab in the docker application.

uiguy · July 22, 2019, 8:32am

you need to go to the package application in your dsm desktop. Navigate to manual install, and then when requested, you need to selec the downloaded spk…

Jokerigno · July 22, 2019, 2:56pm

Hi all, can someone please tell me if remote connection using synology certificatr on hassio add on is still “safe”…i mean encrypted to the outside world?

I want to use vscode addon but I don’t want to explose my secrets.yaml to the world

fredrike · July 22, 2019, 5:01pm

Well SSL (or rather TLS nowadays) are just ensuring that the connection is encrypted (so no one can read the information transmitted) it does not protect against users that might access your installation due to for instance poor password.

Think like this, if you can enable the vscode addon, what means protects against someone else from doing the same thing.

Jokerigno · July 22, 2019, 9:00pm

OK so it is still encrypted. Got it.

For the password well I use a a-z 0-9 + symbol just to be sure.

tlf · July 22, 2019, 9:36pm

Thank you. Didn’t even think to check there!

fredrike · July 23, 2019, 8:14pm

I’ve added this to the uninstall part of the package too:

docker network rm hassio

MizterB · July 24, 2019, 12:07pm

I believe I have a working understanding of the issues with USB devices and some adding not starting up, so wanted to share some observations for corroboration with others.

It looks like when Hass.io starts up, it is detecting devices on the host system, and maps them back to the various containers that it spawns (supervisor, HA, and (some?) addons). This is what populates the “Hardware” Button popup in the UI at Hass.io->System-> Host System.

For USB serial devices (such as my ZWave stick), there is a recent commit that creates the /dev/serial/by-id links that are throwing the errors people mention (in my case, it directly prevents both Node Red and VSCode from starting, if you look at the Hass.io logs).

https://github.com/home-assistant/hassio/pull/1131

The issue appears to be that the programmatic device mapping of the host /dev/serial/by-id/* into the created containers fails because Synology does not provide the /dev/serial path on the host DSM. I worked around this by using Task Manager to run the following script as root at boot time, which creates the missing path, and symlinks back to usable device name for my serial device.

#!/bin/bash

# This script should be run by root at boot time

# Required because Synology does not create /dev/serial/by-id symlinks on the host system

# Create the directory for symlinks

mkdir -p /dev/serial/by-id

# Symlink for ZWave stick - update with the correct device details for based on Hass.io error logs

ln -s /dev/ttyACM0 /dev/serial/by-id/usb-0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffad-if00

This workaround has solved my problem of certain addons not starting up. However, there is an additional issue where sometimes there would be no hardware devices mapped back into the supervisor and HA containers when started up, which prevented my USB stick from being detected at all. This can be observed by running docker inspect against either of those containers. If broken, you will see an empty “Devices” list. If working, you will see it full of hardware references. I went through multiple container restarts, service restarts, and reboots, to get the devices to map in correctly.

For me, everything is working now, but I haven’t confirmed the ‘missing hardware’ is no longer occurring across multiple reboots (they take too long for me, and it got late). If I have other observations in the coming days I will share. In the meantime, I hope this is helpful and other can share their findings as well.

fredrike · July 24, 2019, 5:51pm

Great find!

It would be interesting to see if there is some way to find 0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffad-if00 directly on Synology (wo the logs from hass.io) if so I could create the symlinks when the package starts.

I don’t have a USB-stick to test with but I’m accepting donations , if someone finds a command that lists the USB devices I’ll wrap the rest up.

Alwin_Hummels · July 25, 2019, 7:14am

I’ve got simillar problems with mine, FRXCom and Z-wave works but cant’t install addons:

19-07-25 07:00:05 INFO (MainThread) [hassio.core] Hass.io is up and running
19-07-25 07:02:57 INFO (SyncWorker_0) [hassio.docker.interface] Clean addon_15ef4d2f_esphome-dev application
19-07-25 07:03:11 ERROR (SyncWorker_0) [hassio.docker] Can't start addon_15ef4d2f_esphome-dev: 404 Client Error: Not Found ("linux runtime spec devices: error gathering device information while adding custom device "/dev/serial/by-id/usb-0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffa0-if00": lstat /dev/serial/by-id/usb-0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffa0-if00: no such file or directory")

19-07-25 07:03:57 INFO (SyncWorker_10) [hassio.docker.interface] Restart homeassistant/qemux86-64-homeassistant
19-07-25 07:05:29 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-07-25 07:11:49 INFO (SyncWorker_19) [hassio.docker.interface] Clean addon_a0d7b954_vscode application
19-07-25 07:12:22 ERROR (SyncWorker_19) [hassio.docker] Can't start addon_a0d7b954_vscode: 404 Client Error: Not Found ("linux runtime spec devices: error gathering device information while adding custom device "/dev/serial/by-id/usb-0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffa0-if00": lstat /dev/serial/by-id/usb-0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffa0-if00: no such file or directory")
19-07-25 07:15:10 INFO (SyncWorker_9) [hassio.docker.interface] Clean addon_a0d7b954_vscode application
19-07-25 07:15:20 ERROR (SyncWorker_9) [hassio.docker] Can't start addon_a0d7b954_vscode: 404 Client Error: Not Found ("linux runtime spec devices: error gathering device information while adding custom device "/dev/serial/by-id/usb-0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffa0-if00": lstat /dev/serial/by-id/usb-0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffa0-if00: no such file or directory")

any help is welcome

vstoms · July 25, 2019, 7:29am

log in to your Synology from an ssh session, and type:

ln -s /dev/YourdeviceUSB /dev/serial/by-id/usb-0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffa0-if00

Alwin_Hummels · July 25, 2019, 9:09am

Thanks for your answer I’ve this with no luck:

~# ls -all /dev/serial/by-id/
total 0
drwxr-xr-x 2 root root 100 Jul 25 08:58 .
drwxr-xr-x 3 root root  60 Jul 25 08:38 ..
lrwxrwxrwx 1 root root  12 Jul 25 08:38 usb-0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffad-if00 -> /dev/ttyACM0
lrwxrwxrwx 1 root root  12 Jul 25 08:58 usb-FTDI_FT232R_USB_UART_AC2JPUV7-if00-port0 -> /dev/ttyUSB1
lrwxrwxrwx 1 root root  12 Jul 25 08:40 usb-RFXCOM_RFXtrx433_A11AB1SY-if00-port0 -> /dev/ttyUSB0

Alwin_Hummels · July 25, 2019, 10:29am

After a couple restart it seems to work now thanks for helping fixing this

fredrike · July 25, 2019, 9:17pm

Restart of your nas or of hass.io?

How did you figure out the mapping from /dev/ttyUSB1 etc?

Alwin_Hummels · July 28, 2019, 9:59am

Sorry for my late reply,

I looked at hassio by hardware and found this:


    /dev/serial/by-id/usb-0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffa0-if00
    /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AC2JPUV7-if00-port0
    /dev/ttyS0
    /dev/ttyS2
    /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A11AB1SY-if00-port0
    /dev/ttyUSB0
    /dev/ttyUSB1
    /dev/ttyS3
    /dev/ttyS1
    /dev/ttyACM0

input:
disk:
gpio:
audio:

I use a DS415+ with a USB Hub and connected a Aeontec Z-wave stick, a RFXCom and a P1 serial cable

Cinamon · July 28, 2019, 10:35am

@Alwin_Hummels did you restart the package or your nas to fix the problem?

Alwin_Hummels · July 28, 2019, 10:56am

only the package several times I did this on the docker manager BTW
Not the package on the package store i only used that for installation and after that I only used the webinterface and or docker.

fredrike · July 28, 2019, 12:50pm

What do you see if you issue lsusb?

Alwin_Hummels · July 28, 2019, 1:08pm

Bus 001 Device 002: ID 8087:07db Intel Corp. 
Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID f400:f400  
Bus 002 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 005: ID 0658:0200 Sigma Designs, Inc. 
Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 002 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

laurentdb · July 28, 2019, 4:41pm

I have the same issue as you. I have restarted a couple of times my NAS, the Hassio containers without success.

It sounds that we have the same kind of USB devices.

19-07-28 16:14:25 ERROR (SyncWorker_17) [hassio.docker] Can’t start addon_a0d7b954_nodered: 404 Client Error: Not Found (“linux runtime spec devices: error gathering device information while adding custom device “/dev/serial/by-id/usb-0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffad-if00”: lstat /dev/serial/by-id/usb-0658_USBDevice_ffffffd1ffffffb2ffffffdbffffffad-if00: no such file or directory”)