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

fredrike · August 31, 2019, 1:34pm

Let’s how stable this is I had some issues with the supervisor that restarts and recreate homeassistant and then do this solution dissappear.

I think I need a chat with the hassio developers to see what is going on.

Gnusse · August 31, 2019, 1:55pm

Hi, am trying to install the package but i cant get it to work…
Im runnign version 20190813-6dd0666c.

In docker i got two images after installation: Amd64-hassio-dns and amd64-hassio-supervisor
I only have one container and its stopping and starting every 2 secound, its the supervisor

What im i missing?

harbri · August 31, 2019, 2:21pm

I’m having exactly the same when installing the package from scratch…

fredrike · August 31, 2019, 3:33pm

I’ll investigate and take that in consideration when creating the next version, stay tuned.

althaus · August 31, 2019, 3:49pm

After a reboot of my NAS I’m also trapped in only supervisor/dns running. HA got stopped and doesn’t come back.

raphii · August 31, 2019, 9:50pm

just created an account to say: thank you, you are awesome!

fredrike · September 1, 2019, 5:48am

Thank you!

Hi all, we will fix this issue in next Docker package update. The workaround is to apply environment value in Docker UI.

As it is confirmed that the issue is with environment variables so I will not build a new package instead I offer two solutions:

Run this script as a task once hass.io is started:

CONFIG_FILE="/usr/local/hassio/etc/hassio.json"

if docker --version|grep 18.09.6 >/dev/null; then
    NEWENV="\"TZ=`date +"%Z"`\""
    NEWENV+=",\"HASSIO=hassio\""
    NEWENV+=",\"HASSIO_TOKEN=$(jq -r .access_token "$(jq -r .data ${CONFIG_FILE})/homeassistant.json")\""

    DOCKER_JSON="/var/packages/Docker/target/docker/containers/$(docker inspect homeassistant |jq -r '.[0].Id')/hostconfig.json"
    TMP_FILE=$(mktemp)
    jq --argjson newenvs "[${NEWENV}]"  '.Env += $newenvs' ${DOCKER_JSON} > $TMP_FILE

    docker stop homeassistant
    mv $TMP_FILE $DOCKER_JSON
    docker start homeassistant
fi

Replace the hassio.sh file with this one: hassio.sh · GitHub (curl https://gist.githubusercontent.com/fredrike/b23aacac7bd2d386ea00e138320202df/raw/hassio.sh >/var/packages/hassio/target/bin/hassio.sh && chmod +x /var/packages/hassio/target/bin/hassio.sh will do this autmatically).

I do not know what is going on here but it is probably due to the bug introduced in the Docker 18 package. I suggest that you downgrade Docker as described above.

If you have the homeassistant container the above should work. Otherwise downgrade Docker until Synology have a working Docker version.

Thank you, and welcome to the community!

A side note, I’m looking for an offsite backup location for approx 500GB data, if someone have spare place send me a PM (perhaps we can trade offsite storage ).

althaus · September 1, 2019, 11:36am

Hm… the container is gone, too. I’ve just got the ha:0.98.1 image left. This may be my own fault as I’ve removed the old ha:latest 3 gig image manuall, but according to the log ha was just stopped. Not really sure where it has gone. Should the supervisor be able to create the container again or is that the broken part related to the Docker upgrade?

fredrike · September 1, 2019, 11:53am

The supervisor will only create the ha container the first time (or if config.json is missing)…

althaus · September 1, 2019, 12:44pm

Ok. Didn’t got supervisor to recreate the container. So I went down the hard way, downgraded Docker and started from scratch with a backup of the hass.io folder. Now I’m back where I started, but 1 hour older, a lot wiser and with backups of the container config.

abeishuizen · September 1, 2019, 11:16pm

I am not able to install addons after adding the environment variable HASSIO_TOKEN to the homeassistant container.
The error message I get:
/run.sh: line 51: HASSIO_TOKEN: unbound variable
Any idea to workaround this issue?

fredrike · September 2, 2019, 4:15am

Downgrade Docker. That will be the solution until Synology fixes the variable bug.

rdekruyf · September 2, 2019, 10:28am

I love this package, change from docker version to this package with the benefits of Hass.io thanks a lot!
Only my Google Asssistant integration is not working anymore.

Delete all the existing projects and data and follow this steps again: https://www.home-assistant.io/components/google_assistant/

Successful create a TEST app only its not linking with HA, in the final stap.

Anyone else have issues or works the google ass integration fine?

Bakker · September 2, 2019, 12:19pm

Just downgraded Docker en re installed, don’t tick delete all. And you’ll be good to go, reinstall older version and everything should be like before.

fredrike · September 2, 2019, 4:10pm

Could be a routing issue, is your hass accessible from the outside via base_url in configuration.yaml?

dave-castle · September 2, 2019, 4:13pm

This workaround is not working with 0.98.2.

Clicking on Hass.io addons got me this → "Unable to load the panel source: /api/hassio/app/entrypoint.js. "

and also different other issues:

2019-09-02 18:00:21 ERROR (MainThread) [homeassistant.components.hassio.handler] /homeassistant/options return code 403.
2019-09-02 18:00:21 ERROR (MainThread) [homeassistant.components.hassio.handler] /supervisor/options return code 403.
2019-09-02 18:00:21 ERROR (MainThread) [homeassistant.components.hassio.handler] /homeassistant/info return code 403.
2019-09-02 18:00:21 WARNING (MainThread) [homeassistant.components.hassio] Can’t read last version:
2019-09-02 18:00:21 ERROR (MainThread) [homeassistant.components.hassio.handler] /ingress/panels return code 403.
2019-09-02 18:00:21 ERROR (MainThread) [homeassistant.components.hassio.addon_panel] Can’t read panel info:
2019-09-02 18:00:23 ERROR (MainThread) [homeassistant.components.hassio.handler] /discovery return code 403.
2019-09-02 18:00:23 ERROR (MainThread) [homeassistant.components.hassio.discovery] Can’t read discover info:

fredrike · September 2, 2019, 4:18pm

It is probably not due to 0.98.2…

But downgrade Docker, this issue is on Synology and not much we can do about it.

dave-castle · September 2, 2019, 4:20pm

when downgrading will I lose my docker configurations!?

fredrike · September 2, 2019, 5:05pm

No, you probably will not lose anything.

I’ve repacked the 17.05 Docker package for convenience so you can “upgrade” the 18.09.0 into the 17.05 version (so no need to uninstall).

You can manual install this file and “everything” should be working again (I’ve not had time to verify that everything is running 100% yet).

Edit: I had to remove the homeassistant container and remove the config.json from the hass.io folder. But everything else seems to be working fine after the “upgrade”.

Gnusse · September 2, 2019, 5:41pm

@fredrike i’m running docker 17.05.0-0401 and installed “hassio_x64-6.1_20190813-6dd0666c.spk” When i press the hassio button a blank screen shows without any error messages

I’m i missing something?