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

@CraftDemon @lachyzee

I had the same error: Stop and restart the supervisor container.

I tried and couldn’t get the wyzesense to work with this native package (Synology does not support hidraw). Eventually created an vm and everything worked. Just a FYI.

Hi fredrike,
I want to grate your great job, I installed Hass.io on a Synology one month ago and it works fine, althoungh I didn’t install the jadahl’s driver for zigbee2mqtt and today I finally succeeded configuring Alexa.
Thanks a lot

1 Like

Eventually got it all working after multiple stops and restarts of supervisor! Thank you.

1 Like

Hey again! So i got Hassio working now, and it feels great!

Quick question, where do i find the: “addon configuration”?

This description is from the Deconz add on package:

"If you’re using Home Assistant you may find the correct value for this on the
Supervisor -> System -> Host system -> Hardware page. It is recommended
to use a “by-id” path to the device if one exists, as it is not subject to
change if other devices are added to the system.

  1. Replace null in the device option in the add-on configuration and specify
    the device name in quotes: e.g. something like
    "/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_XXXXXXXX-if00" , "/dev/ttyUSB0" , "/dev/ttyAMA0" , or "/dev/ttyACM0" .
  2. Click on “SAVE” to save the add-on configuration.
  3. Toggle the “Show in sidebar” to add it to your Home Assistant side bar.
  4. Start the add-on."

This is more of a hass-supervisor question, but scroll to the bottom of https://hassio.local/hassio/addon/core_deconz there you will find the options for the addon (the link will most likely not work but you get what I mean).

You can find the devices that have been identified (you might need to install the serial device package) at https://hassio.locale/hassio/system and press HARDWARE.

Sure, that should be easy, the strange thing is that I’m running 0.106.5 without that group so I don’t think that is needed. (Upgraded from 0.105.x to 0.106.4 and everything worked for me).

Thank you, found the settings part of the file way below the description after having read it for the 100th time late last night :stuck_out_tongue:

Seems to be running like a clock now, but stumbled upon a problem with My Forticlient on my old work-laptop not allowing the content of the deconz admin page to load.

After i have re-installed it, it should be all good :slight_smile:

Hi,
I am still running on the 20190701-alpha version still works like a charm.
Also no possible errors when upgrading this to the SynoCommunity Beta version?

@frederike, first of all thank you for your effort to develop and provide this package.
It also allowed me to install HA and Hass.io on my Synology NAS.

I hope I am not completely wrong in this thread with my request.
Unfortunately, I haven’t found detailed instructions on how to downgrade to a previous HA version due to a problem.
After many hours of searching, I have only found “high level” explanations, such as Portainer or Compose.
But I have not installed either of them yet.
As I am not an expert, I am looking for the easiest and safest method and a manual for it.
If you or someone else from the community can help me I would be very grateful.

1 Like

Änyone got the conbee2/deconz solution for Zigbee working?

I got the stick installed correctly, But when i set 2 Aqara devices in pair-mode, it really doesnt look like the deconz software is searching, even tough the splash-screen with “3min” comes up. (someone wrote on another forum, that it should count down from 3 mins? Mine does not!)

This is from my log in deconz addon:

At the bottom of the log, i triggered a search again, but i cant really see the action in the log, anything om doing wrong?

172.30.32.2 - - [09/Mar/2020:00:36:08 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510410 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:09 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510411 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:10 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510412 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:11 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510413 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:12 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510414 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
00:36:13:151 Current channel 15
00:36:13:159 Device TTL 3777 s flags: 0x7
172.30.32.2 - - [09/Mar/2020:00:36:13 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510415 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:14 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510416 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:15 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510417 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:16 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510418 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
00:36:17:171 Search sensors done
172.30.32.2 - - [09/Mar/2020:00:36:17 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510419 HTTP/1.1" 200 45 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:18 +0100] "POST /api/95F04B0110/sensors HTTP/1.1" 200 93 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:18 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510420 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
00:36:19:639 send permit join, duration: 59
172.30.32.2 - - [09/Mar/2020:00:36:19 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510421 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:20 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510422 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:21 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510423 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:22 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510424 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:23 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510425 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:24 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510426 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:25 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510427 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:26 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510428 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"
172.30.32.2 - - [09/Mar/2020:00:36:27 +0100] "GET /api/95F04B0110/sensors/new?_=1583710510429 HTTP/1.1" 200 36 "http://192.168.1.21:8123/api/hassio_ingress/v_L8u32wCI3J6fmGODZe4H5DxJEt5-aBXKx-8CSGqJM/pwa/devices-sensors.html?_v=fc464a7b5d2873c5b32080f1a825d315607bbe29,2,1,0&gwid=00212EFFFF053DDB" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36"

Solved my own problem by adding the Conbee2 stick to a 5meter long USB extension cord (its a power ampllifing cord, but i dont think that actually affects it).

Also to add the Aqara sensors, i had to spam/flood the conbee stick with retrys to make it catch the signals. Im really currious how they will perform.

@Fredrike, thanks for all your great soft! In the past I have been working with Hassio with the plugins Influx & Grafane on RPi3B for some time. I used Telegraf to send mqtt data to that Influx so that Grafana can visualise all this. Works very fine but I need to restrict Influx to keep the data only for a few days or the Pi gets in trouble.
To solve this I installed the Hassio Docker on my Synology (IP: 123.123.123.111) and in the Hassio installed the plugins Influx & Grafane. Things work but I have some problems.
I have to confess that I’m not an expert and relatively new to Docker.

-1- typing in the browser http://123.123.123.111:8888 does not connect to Influx (it worked well with RPi3B)
-2- typing in the browser http://123.123.123.111:3000 does not connect to Grafana (it worked well with RPi3B)
-3- typing in the browser http://123.123.123.111:8086 does not connect to Hassio (it worked well with RPi3B)
Can this be solved ?

-4-
On the RPi I used the next “write to Influx” statement in Telegraf … on Hassio I can’t write to its Influx because I can not get in contact on port 8086 … how to solve this ?
[[outputs.influxdb]]
urls = [“http://123.123.123.444:8086”]
database = “datadb”
skip_database_creation = false
timeout = “5s”
precision = “s”
username = “xxx”
password = “yyy”

-5-
In Grafana I’m missing some visualisation plugins …
When I click on “Find more plugins on Grafana.com” I get an error:
grafana.com is blocked
grafana.com refused to connect.
ERR_BLOCKED_BY_RESPONSE
I have a .ZIP file but don’t know if & how I can get it in.

I’m loving this. Really solid since installation.

What I can’t get to work is the HA ping integration for presence.

Is there something I need to do differently to when running HA on Rpi to be able to use ping?

Is this a docker network issue?

I’m new to HA and this package. But i want to try it out.
I have it working and running, but when i go to the webpage 8123 for the first time it asks for a username and password. But i didn’t set one.
Is there a default one or do i need to configure it somewher?
I have read the manual, but cannot find how to do this.

No they are basically the same, the SynoCommunity version supports automatic upgrades (of the package not HA or HA-core).

I guess you mean @fredrike :slight_smile:, you are welcome!

Have a look at this: Installation - Home Assistant. You need to install the Terminal & SSH from the addon-store (but that is step 7. in the installation doc (Installation - Home Assistant) so I guess that is already done :stuck_out_tongue:.

Great that it works for you!

I just tested ping natively on the docker container and it works…

You should be able to test it with this command from a ssh session (change 192.168.1.1 to the ip of your target):

sudo docker exec -it `sudo docker ps |grep homeassistant/qemux86-64-homeassistant|awk '{print $1}'` ping -c 5 192.168.1.1

Is it Home-Assistant that asks for a password? That is strange, the blank installation will ask you to configure an user.

1 Like

I think i had some home assistend docker leftovers from some years ago. Deleted all folders whit hass or homeassistent in the name, and now i need to setup a username and password.

1 Like

Sorry, of course @fredrike.
And thank you very much for the hint.
Amazing how easy it is. When you know it :wink:

Now its working! hassio-audio runs stable.
After adding the group audio to DSM, creating the folders /audio/external AND /audio/internal/states the hassio-audio container runs.

YES,its working now!

Echoing @gerosaf. Is there a way to customize docker volume configurations for “homeassistant” container?

I am using letsencrypt container (linuxserver.io) to generate and renew certificates and use it in other containers by mapping the /etc/letsencrypt volume. Anytime the homeassistant is upgraded, the volume configuration is reset and HA does not start as it cannot find the certificate.

Great work, btw!