Installation of Hassio on Synology NAS

dearlk · July 4, 2019, 2:26pm

Restarting the hassio/homeassitant docker container didn’t work but supervisor did.
I was able to see the correct route setup after that and hassio GUI also came well.

Now i ran into other errors after restoring my hassio backup from raspi here on NAS broke the hassio and frontend no more assessible. May be some other problems.

I thought restoring the hassio backup should work without any issue.

Any idea?

fredrike · July 4, 2019, 3:01pm

Restart the Synology package reinits the route (route add -net 172.30.32.0/23 gw 172.30.32.1), don’t manage the Docker containers via the Synology Docker package as there are magics that needs to be set.

What does the logfile say? You probably need to modify the ip-addresses.

dearlk · July 4, 2019, 3:40pm

not sure what went wrong. tried uninstalling the package and reinstalling… i see below logs of supervisor after new install but no hassio gui and neither homeassistant docker container anymore …

.io setup
19-07-04 15:36:09 INFO (MainThread) [__main__] Setup HassIO
19-07-04 15:36:09 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/amd64-hassio-supervisor with version 167
19-07-04 15:36:09 INFO (SyncWorker_0) [hassio.docker.supervisor] Connect Supervisor to Hass.io Network
19-07-04 15:36:11 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.systemd1 on /org/freedesktop/systemd1
19-07-04 15:36:11 ERROR (MainThread) [hassio.utils.gdbus] DBus return error: b'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files\n'
19-07-04 15:36:11 WARNING (MainThread) [hassio.dbus.systemd] Can't connect to systemd
19-07-04 15:36:11 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.hostname1 on /org/freedesktop/hostname1
19-07-04 15:36:11 ERROR (MainThread) [hassio.utils.gdbus] DBus return error: b'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.hostname1 was not provided by any .service files\n'
19-07-04 15:36:11 WARNING (MainThread) [hassio.dbus.hostname] Can't connect to hostname
19-07-04 15:36:11 INFO (MainThread) [hassio.utils.gdbus] Introspect de.pengutronix.rauc on /
19-07-04 15:36:11 ERROR (MainThread) [hassio.utils.gdbus] DBus return error: b'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name de.pengutronix.rauc was not provided by any .service files\n'
19-07-04 15:36:11 WARNING (MainThread) [hassio.dbus.rauc] Can't connect to rauc
19-07-04 15:36:11 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: set()
19-07-04 15:36:11 INFO (MainThread) [hassio.host.apparmor] AppArmor is not enabled on host
19-07-04 15:36:11 INFO (SyncWorker_1) [hassio.docker.interface] Attach to homeassistant/qemux86-64-homeassistant with version 0.95.4
19-07-04 15:36:11 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/a0d7b954 repository
19-07-04 15:36:11 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/core repository
19-07-04 15:36:11 INFO (MainThread) [hassio.store] Load add-ons from store: 59 all - 59 new - 0 remove
19-07-04 15:36:11 INFO (MainThread) [hassio.addons] Found 2 installed add-ons
19-07-04 15:36:11 INFO (SyncWorker_2) [hassio.docker.interface] Attach to homeassistant/amd64-addon-configurator with version 3.4
19-07-04 15:36:11 INFO (SyncWorker_3) [hassio.docker.interface] Attach to homeassistant/amd64-addon-mosquitto with version 4.3
19-07-04 15:36:11 INFO (MainThread) [hassio.updater] Fetch update data from https://s3.amazonaws.com/hassio-version/stable.json
19-07-04 15:36:12 INFO (MainThread) [hassio.snapshots] Found 1 snapshot files
19-07-04 15:36:12 INFO (MainThread) [hassio.discovery] Load 0 messages
19-07-04 15:36:12 INFO (MainThread) [hassio.ingress] Load 0 ingress session
19-07-04 15:36:12 INFO (MainThread) [__main__] Run Hass.io
19-07-04 15:36:12 INFO (MainThread) [hassio.misc.dns] Start DNS port forwarding for host add-ons
19-07-04 15:36:12 INFO (MainThread) [hassio.api] Start API on 172.30.32.2
19-07-04 15:36:12 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
19-07-04 15:36:12 INFO (MainThread) [hassio.core] Hass.io reboot detected
19-07-04 15:36:12 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
19-07-04 15:36:12 INFO (MainThread) [hassio.core] Hass.io is up and running

dearlk · July 4, 2019, 4:11pm

ok, sorted it out… there was SSL error.

btw, how can i change the port for hassio in this setup? reason is that my existing setup is using default 8123 and i dont want to change it until everything is setup on NAS using ssl and everything. i would want to expose hassio on other port something like 9123 so that i can setup separate ssl on different domain on this setup to ensure everything is working.

Streetchat · July 4, 2019, 4:17pm

Hi all.
Problem here too on a synology DS1010+ (DSM 5.2) intel atom x64 and 3GB of RAM.

Docker is working with other container. So i stopped them all.

I created /volume1/hass.io shared folder and disabled the user home service (and lost the cloud sync by the way).
I installed the latest package 20190701-alpha and it went well.
When i start it, a container of hassio_supervisor is created and try to start then stop, then start, then stop,…

in the docker log of the synology:
‘’’
Jul 4 18:05:01 synology docker[18768]: ERRO[2023696] Handler for POST /containers/create returned error: Invalid --security-opt: “apparmor=unconfined”
Jul 4 18:05:01 synology docker[18768]: ERRO[2023696] HTTP Error: statusCode=500 Invalid --security-opt: “apparmor=unconfined”
Jul 4 18:05:01 synology docker[30196]: FATA[0000] Error response from daemon: Invalid --security-opt: “apparmor=unconfined”
Jul 4 18:05:02 synology docker[18768]: ERRO[2023697] Handler for GET /containers/{name:.*}/json returned error: no such id: homeassistant/amd64-hassio-supervisor
Jul 4 18:05:02 synology docker[18768]: ERRO[2023697] HTTP Error: statusCode=404 no such id: homeassistant/amd64-hassio-supervisor
Jul 4 18:05:03 synology docker[18768]: WARN[2023698] Your kernel does not support OOM notifications: There is no path for “memory” in state
Jul 4 18:05:08 synology docker[18768]: ERRO[2023703] Handler for POST /containers/create returned error: Invalid --security-opt: “apparmor=unconfined”
Jul 4 18:05:08 synology docker[18768]: ERRO[2023703] HTTP Error: statusCode=500 Invalid --security-opt: “apparmor=unconfined”
Jul 4 18:05:08 synology docker[30707]: FATA[0000] Error response from daemon: Invalid --security-opt: “apparmor=unconfined”
‘’’

Not really sure thet this docker can handle hass.io.

regards

dearlk · July 4, 2019, 4:57pm

ok, all good.

installed synology package 20190701-alpha.spk
supervisor and homeassisnt docker containers are setup.
forwarded external 9123 to hassio 8123 and setup ssl as well
everything seems to be working as of now post setup.
will test for next few days and feedback.

great thank to you @fredrike for all your hardwork in creating and making Synology package available for hassio setup on NAS.

Big thanks!!!

fredrike · July 4, 2019, 7:49pm

You should upgrade to DSM 6.1. What version of Docker are you running?

If an upgrade of DSM is not possible remove L22-23 from /var/packages/hassio/script/hassio.sh but I’m doubtful that your old Docker can run hassio.

Streetchat · July 4, 2019, 9:06pm

hi,

DSM 5.2 is the latest version on this synology.
Docker version is 1.6.2-0036

There is no hassio.sh script in /var/packages/hassio/scripts.
But there is one in /var/packages/hassio/target/bin/

I’ll try with this one

fredrike · July 4, 2019, 9:08pm

That is what I meant.

Sorry but I’m not very hopeful.

Streetchat · July 4, 2019, 9:15pm

In fact, line 22-23 contains this:
${SUPERVISOR}
}

i doubt i can remove them

fredrike · July 4, 2019, 9:17pm

Remove line 14-15 (https://github.com/SynoCommunity/spksrc/pull/3732/files#diff-64318662aad5687adf02e90732152b9cR14)

Streetchat · July 4, 2019, 9:27pm

Ok, done.

not better, the container start then stop, then start…
and this time, i see no logs in /var/log/docker/docker.log

At each boot, docker create new folders with new numbers in /volume1/@docker/containers, deleting old ones.

Timx · July 5, 2019, 5:11pm

Just installed this! @fredrike tnx for making hassio possible.

Will start testing

Timx · July 5, 2019, 5:46pm

Where are all the files installed?

Is there a way I can reach them through filestation?

fredrike · July 5, 2019, 10:55pm

Do you mean the config files? They are installed where you told the installer (/volume1/hass.io is the default).

Should we improve that dialog or perhaps create a new share for it?

jnvd3b · July 6, 2019, 3:46am

having the same issue i am sure i am doing something wrong but i created a folder and when i installed the package directed the installer there. ran it and HA is up and running fine (seemingly) but when i go into that folder it’s empty.

got it working just had my permissions messed up on the folder originally and had to reinstall the package
cool i will report back with how it is working

Daskew78 · July 6, 2019, 6:09am

It installs okay but I’m getting the following errors and the “Hass.io” page is blank:
Sat Jul 06 2019 07:01:03 GMT+0100 (British Summer Time)
https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/1.9/ returned Cannot connect to host aa015h6buqvih86i1.api.met.no:443 ssl:None [Try again]

Sat Jul 06 2019 07:01:03 GMT+0100 (British Summer Time)
Retrying in 16 minutes

Sat Jul 06 2019 07:01:09 GMT+0100 (British Summer Time)
Setup of hassio is taking over 10 seconds.

Sat Jul 06 2019 07:01:14 GMT+0100 (British Summer Time)
Timeout on /supervisor/ping request

Sat Jul 06 2019 07:01:14 GMT+0100 (British Summer Time)
Not connected with Hass.io / system to busy!

Sat Jul 06 2019 07:01:24 GMT+0100 (British Summer Time)
Timeout on /homeassistant/options request

Sat Jul 06 2019 07:01:34 GMT+0100 (British Summer Time)
Timeout on /supervisor/options request

Sat Jul 06 2019 07:01:44 GMT+0100 (British Summer Time)
Timeout on /homeassistant/info request

Sat Jul 06 2019 07:01:44 GMT+0100 (British Summer Time)
Can’t read last version:

Sat Jul 06 2019 07:01:54 GMT+0100 (British Summer Time)
Timeout on /ingress/panels request

Sat Jul 06 2019 07:01:54 GMT+0100 (British Summer Time)
Can’t read panel info:

Sat Jul 06 2019 07:02:04 GMT+0100 (British Summer Time)
Timeout on /discovery request

Sat Jul 06 2019 07:02:04 GMT+0100 (British Summer Time)
Can’t read discover info:

Any ideas?

Daskew78 · July 6, 2019, 6:36am

A reinstall resolved the above but I am unable to run plugins. I keep trying to run the Plex plugin and get this error:

|Information|2019/07/06 07:24:22|User|Delete image homeassistant/qemux86-64-homeassistant:latest|
|Error|2019/07/06 07:33:48|User|Start container addon_a0d7b954_plex failed: {“message”:“driver failed programming external connectivity on endpoint addon_a0d7b954_plex (050c7d5914c5281e505fa36be1fc6a31b2a7ec060d57b4d042f7d7a648244198): Error starting userland proxy: listen udp 0.0.0.0:32414: bind: address already in use”}.|

What else could be using the port?

Timx · July 6, 2019, 7:31am

root@Homeserver:~# ln - s /volume1/@appstore/hass.io volume1/hass.io
ln: target ‘volume1/hass.io’ is not a directory

I want to be able to acces those files from my Windows PC.
Is that possible?

When I installed tha package i didnt get an option to pick a location

fredrike · July 6, 2019, 8:03am

Yes you did.

Try ls /volume1/hass.io