All Articles on Synology DSM (native package)


Some user on has managed to make a DSM package that installs on the Synology NAS. Here is how to install the package and get around of the issues with USB and add-ons.

You need to install Docker on your Synalogy first, if not this addon will not start.

It’s now super easy to get Hass.IO up and running on a Synology NAS with this package, and I will show you how to install it and if you have USB devices plugged into it (Z-wave or Zigbee) and getting an error when you are trying to start an addon.

First you have to downloade the DSM package here

Everything is quite straightforward but make sure to create a Shared Folder to use for data storage and select that in the first dialog.



And in the end, you press Apply. If you have a docker instance of Home-Assistant running on your NAS then you have to stop it before can start. This is because of ports conflicts.

Now you should be able to connect to your from http://yourip:8123

If you try to start an addon, in my case Visual Studio Code and got an error message:

ERROR (SyncWorker_3) [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-RFXCOM_RFXtrx433_A1XZHX4D-if00-port0”: lstat /dev/serial/by-id/
usb-RFXCOM_RFXtrx433_A1XZHX4D-if00-port0: no such file or directory”)

I do have an RFXcom, ZigBee2Mqtt and Z-Wave stick to my NAS, so your output from /dev/serial will differ.

To get the addons to work you have to log in to your NAS from an ssh session and type:

ln -s /dev/ttyUSBXX /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0

Change your correct USB and by-id device from the error message that your generates.

After the devices are added under /dev/serial/by-id you should be able to start the addons.