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

proxy64 · November 15, 2020, 10:14am

Is this correct to have the supervisor on 2 lan ?

homeassistant is the one installed by the package hass.io, the second homeassistant-home-assistant1 is stopped, this one is a version without hassle.io I am using it until I can get hass.io working.
thanks for help to get it working

BeardedConti · November 15, 2020, 2:07pm

That’s ok.
I’ve posted it earlier:

Schlibib · November 15, 2020, 4:11pm

Finally i have everything working! I found a lot of useful information here to help me get the syno package to work properly.

I still have one concern that is related the firewall. In order to get everything to work with my home assistant to access different things properly i had to added my regular bridge and also hassio bridge to the synology firewall ip: 172.17.0.1-172.17.0.254 and 172.30.32.1-172.30.32.254 and i allow for ALL ports open. Is this just opening internal ports or also external ports?

I have denied all other ip and ports (expect local 192. IPs). Wondering if i should only allow certain ports or i risk some security issues opening all docker bridge IPs and ports?

pschmitt64 · November 15, 2020, 9:42pm

Awesome package indeed. Thanks for creating this Fredrike.
I used it for several months now and had to re-install for some unrelated reason recently and now it won’t complete on my Synology NAS. When launching your package from the Syno Community on my DS916+ NAS (DSM v: 6.2.3-25426 Updatye 2 ) the first Container you are executing (hassio_supervisor) gets stuck for hours on the following errors:

20-11-15 18:34:31 WARNING (MainThread) [supervisor.plugins.dns] Error on install CoreDNS plugin. Retry in 30sec
20-11-15 18:35:01 WARNING (MainThread) [supervisor.jobs] ‘Updater.fetch_data’ blocked from execution, system is not healthy

Any idea out to out of this nasty loop?

Thanks!

/Philippe

Kaladen · November 15, 2020, 10:55pm

Schlibib, you could use the firewall to set the bridges to location only further locking your firewall down. just the country you live in for example.

Kaladen · November 15, 2020, 11:00pm

Pschmitt64, until the supervisor container issue is resolved you will need to run an older version.

Edit the /usr/local/hassio/etc/hassio.json file on your NAS, i did so via ssh, change the file to match the below. remove the current supervisor container and image from docker after stopping the hass.io package in package manager. re-run the package to hopefully solve the issue.

{
    "supervisor": "homeassistant/amd64-hassio-supervisor:2020.10.1",
    "homeassistant": "homeassistant/qemux86-64-homeassistant",
    "data": "/volume1/Data/hass.io"
}

swim89 · November 16, 2020, 5:35pm

Hi @fredrike I followed your steps on my DS918+ (with DSM 6.2.3-25426 Update 2) but after installing it, I can see only a container on docker (called hassio_supervisor) and I can’t access to https://myServerIP:8123/.
I checked my firewall and it is turned off. What I have to check?

Thanks
Luca

antoshka · November 16, 2020, 5:46pm

@swim89
Apply changes for hassio.json from last message from @Kaladen and than run package again

fraenkDUS · November 16, 2020, 6:14pm

It works surprisingly well out of the box for me on DS920+ with DSM 6.2.3-25426 Update 2 and Docker 18.09.0-0513.

swim89 · November 16, 2020, 6:24pm

thanks! this solved my problems!!

proxy64 · November 17, 2020, 7:21am

Oups why amd64, what that means ?
Is this package only for NAS with amd processor (mine is a celeron) ?
If so why x86-64 for the home assistant ?

still not working with the workaround

ERROR (MainThread) [supervisor.core] Docker version '18.09.8' is not supported by Supervisor!

yuhwen1013 · November 17, 2020, 8:31am

it helps a lot!
thank u very much!

Kaladen · November 17, 2020, 8:39am

Amd64 and x86_64 in this case refer to the application built to run on 64bit capable x86 CPUs of which the celeron is one of them. Another option would be an arm cpu that does not run the x86 cpu code. For more in depth info search for arm vs x86 etc

The error you have posted is a normal and you can ignore it. home assistant is built for version 19 of docker but it still runs… Check further up for images of a normal start. There are other errors that are standard.

proxy64 · November 17, 2020, 10:29am

Thanks for this explanations

So I tried once again.

uninstall the package
delete old hass.io config folder
package inxtalled without run it
hassio.json modified with the tag 2020.10.1
run the package and wait a while to have all containers runnings
supervisor version 2020.10.1 running and all others container

HA first run

detect doesn’t works, so fill manually informations, then next
ERROR: Failed to save undefined
break first run, run it again and logon
Weather not working

One thing I don’t understand, when I install the container homeassistant latest (without hassio), it’s the same version 0.117.5 but it’s running well, no bug at the first boot, weather is working and all other things. And yet it’s the same version in the package 0.117.5

HA log

Error handling request
5:01:06 PM – helpers/system_info.py (ERROR) - message first occurred at 5:00:57 PM and shows up 2 times
Timeout on /homeassistant/options request
5:00:07 PM – Hass.io (ERROR) - message first occurred at 4:58:23 PM and shows up 7 times
Error handling request
5:00:02 PM – components/onboarding/views.py (ERROR)
https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned Cannot connect to host aa015h6buqvih86i1.api.met.no:443 ssl:default [Try again]
5:00:02 PM – /usr/local/lib/python3.8/site-packages/metno/__init__.py (ERROR)
Received message for unregistered webhook 86f019272e25547f90de0d0ecc03f27615dad5e9c267db1924b26b216616788c from 192.168.1.6
4:59:52 PM – Webhook (WARNING)
Can't read discover info:
4:59:17 PM – Hass.io (ERROR)
Error requesting Home Assistant update data: Cannot connect to host updater.home-assistant.io:443 ssl:default [Try again]
4:59:09 PM – Updater (ERROR)
Can't read panel info:
4:59:03 PM – Hass.io (ERROR)
Can't read last version:
4:58:53 PM – Hass.io (WARNING)
Not connected with Hass.io / system too busy!
4:58:23 PM – Hass.io (WARNING)
Setup of hassio is taking over 10 seconds.
4:58:17 PM – /usr/local/lib/python3.8/asyncio/events.py (WARNING)

There especially a lot of error in the DNS container log, here some of them

2020-11-17 09:56:50,stdout,[ERROR] plugin/errors: 2 github.com. A: dial tcp 1.1.1.1:853: i/o timeout

2020-11-17 09:56:50,stdout,[INFO] 127.0.0.1:50734 - 29126 "A IN github.com. udp 39 true 2048" NOERROR - 0 30.000310009s

2020-11-17 09:56:50,stdout,[ERROR] plugin/errors: 2 . NS: dial tcp 1.1.1.1:853: i/o timeout

2020-11-17 09:56:50,stdout,[INFO] 127.0.0.1:39300 - 19313 "NS IN . udp 17 false 512" NOERROR - 0 30.000462162s

2020-11-17 09:56:50,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: dial tcp 1.1.1.1:853: i/o timeout

2020-11-17 09:56:50,stdout,[INFO] 127.0.0.1:53299 - 63520 "HINFO IN 7035042365311457975.343355304969126724. udp 67 true 2048" NOERROR - 0 30.000279446s

2020-11-17 09:56:50,stdout,[ERROR] plugin/errors: 2 version.home-assistant.io. AAAA: dial tcp 1.1.1.1:853: i/o timeout

2020-11-17 09:56:49,stdout,[INFO] 127.0.0.1:34866 - 5757 "AAAA IN version.home-assistant.io. udp 54 true 2048" NOERROR - 0 30.000356523s

2020-11-17 09:56:48,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: dial tcp 1.1.1.1:853: i/o timeout

2020-11-17 09:56:48,stdout,[INFO] 127.0.0.1:42208 - 9578 "HINFO IN 7035042365311457975.343355304969126724. udp 67 true 2048" NOERROR - 0 30.000301373s

2020-11-17 09:56:43,stdout,[ERROR] plugin/errors: 2 . NS: dial tcp 1.1.1.1:853: i/o timeout

2020-11-17 09:56:43,stdout,[INFO] 127.0.0.1:57803 - 43085 "NS IN . udp 17 false 512" NOERROR - 0 30.000299653s

2020-11-17 09:56:42,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: dial tcp 1.0.0.1:853: i/o timeout

2020-11-17 09:56:42,stdout,[INFO] 127.0.0.1:58191 - 54441 "HINFO IN 7035042365311457975.343355304969126724. udp 67 true 2048" NOERROR - 0 30.000309092s

2020-11-17 09:56:39,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: dial tcp 1.1.1.1:853: i/o timeout

2020-11-17 09:56:39,stdout,[INFO] 127.0.0.1:49949 - 51926 "HINFO IN 7035042365311457975.343355304969126724. udp 67 true 2048" NOERROR - 0 30.000505949s

2020-11-17 09:56:38,stdout,[ERROR] plugin/errors: 2 . NS: dial tcp 1.0.0.1:853: i/o timeout

2020-11-17 09:56:38,stdout,[INFO] 127.0.0.1:54006 - 30760 "NS IN . udp 17 false 512" NOERROR - 0 30.000324072s

2020-11-17 09:56:36,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: dial tcp 1.0.0.1:853: i/o timeout

2020-11-17 09:56:36,stdout,[INFO] 127.0.0.1:43000 - 57918 "HINFO IN 7035042365311457975.343355304969126724. udp 67 true 2048" NOERROR - 0 30.000378538s

2020-11-17 09:56:33,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: dial tcp 1.0.0.1:853: i/o timeout

2020-11-17 09:56:33,stdout,[INFO] 127.0.0.1:50206 - 27899 "HINFO IN 7035042365311457975.343355304969126724. udp 67 true 2048" NOERROR - 0 30.000306915s

2020-11-17 09:56:32,stdout,[ERROR] plugin/errors: 2 . NS: dial tcp 1.1.1.1:853: i/o timeout

2020-11-17 09:56:32,stdout,[INFO] 127.0.0.1:55106 - 11470 "NS IN . udp 17 false 512" NOERROR - 0 30.00035763s

2020-11-17 09:56:30,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: dial tcp 1.1.1.1:853: i/o timeout

2020-11-17 09:56:30,stdout,[INFO] 127.0.0.1:50859 - 33053 "HINFO IN 7035042365311457975.343355304969126724. udp 67 true 2048" NOERROR - 0 30.209458448s

2020-11-17 09:56:27,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: read udp 127.0.0.1:38383->127.0.0.11:53: i/o timeout

2020-11-17 09:56:27,stdout,[INFO] 127.0.0.1:38962 - 25127 "HINFO IN 7035042365311457975.343355304969126724. udp 56 false 512" NOERROR - 0 2.00058788s

2020-11-17 09:56:24,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: read udp 127.0.0.1:51557->127.0.0.1:5553: i/o timeout

2020-11-17 09:56:24,stdout,[INFO] 127.0.0.1:33251 - 26255 "HINFO IN 7035042365311457975.343355304969126724. udp 56 false 512" NOERROR - 0 2.005182006s

2020-11-17 09:56:21,stdout,[ERROR] plugin/errors: 2 github.com. A: read udp 127.0.0.1:46871->127.0.0.1:5553: i/o timeout

2020-11-17 09:56:21,stdout,[INFO] 172.30.32.2:55583 - 45023 "A IN github.com. udp 28 false 512" NOERROR - 0 6.001346657s

2020-11-17 09:56:21,stdout,[ERROR] plugin/errors: 2 github.com. AAAA: read udp 127.0.0.1:41952->127.0.0.1:5553: i/o timeout

2020-11-17 09:56:21,stdout,[INFO] 172.30.32.2:55583 - 45648 "AAAA IN github.com. udp 28 false 512" NOERROR - 0 6.001356658s

2020-11-17 09:56:21,stdout,[ERROR] plugin/errors: 2 github.com. AAAA: read udp 127.0.0.1:48636->127.0.0.11:53: i/o timeout

2020-11-17 09:56:21,stdout,[INFO] 172.30.32.2:49899 - 29688 "AAAA IN github.com. udp 28 false 512" NOERROR - 0 6.001394122s

2020-11-17 09:56:21,stdout,[ERROR] plugin/errors: 2 github.com. A: read udp 127.0.0.1:50734->127.0.0.1:5553: i/o timeout

2020-11-17 09:56:21,stdout,[INFO] 172.30.32.2:49899 - 29126 "A IN github.com. udp 28 false 512" NOERROR - 0 6.001799691s

2020-11-17 09:56:21,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: read udp 127.0.0.1:53299->127.0.0.1:5553: i/o timeout

2020-11-17 09:56:21,stdout,[INFO] 127.0.0.1:43871 - 63520 "HINFO IN 7035042365311457975.343355304969126724. udp 56 false 512" NOERROR - 0 2.001134841s

2020-11-17 09:56:21,stdout,[ERROR] plugin/errors: 2 version.home-assistant.io. AAAA: read udp 127.0.0.1:34866->127.0.0.1:5553: i/o timeout

2020-11-17 09:56:21,stdout,[INFO] 172.30.32.2:58967 - 5757 "AAAA IN version.home-assistant.io. udp 43 false 512" NOERROR - 0 6.001728928s

2020-11-17 09:56:21,stdout,[ERROR] plugin/errors: 2 version.home-assistant.io. A: read udp 127.0.0.1:33328->127.0.0.11:53: i/o timeout

2020-11-17 09:56:21,stdout,[INFO] 172.30.32.2:58967 - 5157 "A IN version.home-assistant.io. udp 43 false 512" NOERROR - 0 6.001313757s

2020-11-17 09:56:20,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: read udp 127.0.0.1:42208->127.0.0.1:5553: i/o timeout

2020-11-17 09:56:20,stdout,[INFO] 127.0.0.1:48596 - 9578 "HINFO IN 7035042365311457975.343355304969126724. udp 56 false 512" NOERROR - 0 4.000791028s

2020-11-17 09:56:19,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: read udp 127.0.0.1:60341->127.0.0.11:53: i/o timeout

2020-11-17 09:56:19,stdout,[INFO] 127.0.0.1:41060 - 28563 "HINFO IN 7035042365311457975.343355304969126724. udp 56 false 512" NOERROR - 0 6.001907757s

2020-11-17 09:56:16,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: read udp 127.0.0.1:43500->127.0.0.11:53: i/o timeout

2020-11-17 09:56:16,stdout,[INFO] 127.0.0.1:37672 - 54441 "HINFO IN 7035042365311457975.343355304969126724. udp 56 false 512" NOERROR - 0 6.001195619s

2020-11-17 09:56:13,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: read udp 127.0.0.1:55740->127.0.0.11:53: i/o timeout

2020-11-17 09:56:13,stdout,[INFO] 127.0.0.1:45997 - 51926 "HINFO IN 7035042365311457975.343355304969126724. udp 56 false 512" NOERROR - 0 6.002554295s

2020-11-17 09:56:10,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: read udp 127.0.0.1:57741->127.0.0.11:53: i/o timeout

2020-11-17 09:56:10,stdout,[INFO] 127.0.0.1:40787 - 57918 "HINFO IN 7035042365311457975.343355304969126724. udp 56 false 512" NOERROR - 0 6.00196991s

2020-11-17 09:56:07,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: read udp 127.0.0.1:50964->127.0.0.11:53: i/o timeout

2020-11-17 09:56:07,stdout,[INFO] 127.0.0.1:38781 - 27899 "HINFO IN 7035042365311457975.343355304969126724. udp 56 false 512" NOERROR - 0 6.001449888s

2020-11-17 09:56:04,stdout,[ERROR] plugin/errors: 2 7035042365311457975.343355304969126724. HINFO: read udp 127.0.0.1:36278->127.0.0.11:53: i/o timeout

2020-11-17 09:56:04,stdout,[INFO] 127.0.0.1:40621 - 33053 "HINFO IN 7035042365311457975.343355304969126724. udp 56 false 512" NOERROR - 0 6.001594654s

2020-11-17 09:55:58,stdout,"linux/amd64, go1.15.3, 054c9ae-dirty
"
2020-11-17 09:55:58,stdout,CoreDNS-1.8.0

2020-11-17 09:55:58,stdout,.:5553

2020-11-17 09:55:58,stdout,.:53

2020-11-17 09:55:58,stdout,[WARNING] plugin/hosts: File does not exist: /config/hosts

2020-11-17 09:55:57,stdout,[services.d] done.

2020-11-17 09:55:57,stdout,[services.d] starting services

2020-11-17 09:55:57,stdout,[cont-init.d] done.

2020-11-17 09:55:57,stdout,[cont-init.d] corefile.sh: exited 0.

2020-11-17 09:55:56,stdout,[cont-init.d] corefile.sh: executing... 

2020-11-17 09:55:56,stdout,[cont-init.d] executing container initialization scripts...

2020-11-17 09:55:56,stdout,[fix-attrs.d] done.

2020-11-17 09:55:56,stdout,[fix-attrs.d] applying ownership & permissions fixes...

2020-11-17 09:55:56,stdout,[s6-init] ensuring user provided files have correct perms...exited 0.

2020-11-17 09:55:56,stdout,[s6-init] making user provided files available at /var/run/s6/etc...exited 0.

fraenkDUS · November 17, 2020, 11:09am

What’s your Docker and Synology network config? Any firewall, security, dns/network addons?

proxy64 · November 17, 2020, 1:38pm

Diskstation:
LAN1 192.168.1.xxx (LAN2 not connected)
Lan mask 255.255.255.0
Firewall disable

Docker:
Nodered running
Homebridge running
HomeAssistant version without hassio stopped during hassio test

nothing else

fraenkDUS · November 17, 2020, 1:48pm

What about the Docker network configuration? Did you try the second bullet point of this note: Hass.io on Synology DSM (native package)

proxy64 · November 18, 2020, 12:07am

Yes thank you so much @franenkDUS
That did it ! now it’s running

pschmitt64 · November 18, 2020, 2:37am

Thanks for you help Luke. I will give this a try.

jvbragt · November 18, 2020, 10:56am

Got things up and running, but the supervisor doesn’t show the add-ons, tried to add repositories but that’s also not possible.