hass.io on Synology

__note.md

This information is depricated in favor of a Synology package, official support thread is here: https://community.home-assistant.io/t/hass-io-on-synology-dsm-native-package/125559

There is an active PR to merge the package into https://synocommunity.com/.

_intro.md

Example on getting hass.io to run on an Synology NAS (with arch x86_64)

All commands are run in and sudo environment (sudo su -).

# CHANGE THIS ACCORDINGLY
DATA="/usr/local/share/hassio"

URL_VERSION="https://s3.amazonaws.com/hassio-version/stable.json"

HOMEASSISTANT_DOCKER="homeassistant/qemux86-64-homeassistant"
HASSIO_DOCKER="homeassistant/amd64-hassio-supervisor"

# Read infos from web
HASSIO_VERSION=$(curl -s $URL_VERSION | jq -e -r '.supervisor')

# Pull supervisor image
docker pull "$HASSIO_DOCKER:$HASSIO_VERSION" > /dev/null
docker tag "$HASSIO_DOCKER:$HASSIO_VERSION" "$HASSIO_DOCKER:latest" > /dev/null

# Write config
mkdir -p $DATA/etc
cat > $DATA/etc/hassio.json <<- EOF
{
    "supervisor": "${HASSIO_DOCKER}",
    "homeassistant": "${HOMEASSISTANT_DOCKER}",
    "data": "${DATA}"
}
EOF

The startup script below should be added as an User defined script under Task Scheduler and started at startup.

startup_script.sh

#!/bin/sh

# CHANGE THIS ACCORDINGLY
DATA="/usr/local/share/hassio"

# Load configs
CONFIG_FILE=$DATA/etc/hassio.json

runSupervisor() {
    HOMEASSISTANT="$(jq --raw-output '.homeassistant' ${CONFIG_FILE})"
    HASSIO_DATA="$(jq --raw-output '.data // "/usr/share/hassio"' ${CONFIG_FILE})"

    APPARMOR="--security-opt apparmor=unconfined"

    /usr/local/bin/docker rm --force hassio_supervisor > /dev/null || true
    /usr/local/bin/docker run --name hassio_supervisor \
        --privileged \
        $APPARMOR \
        --security-opt seccomp=unconfined \
        -v /var/run/docker.sock:/var/run/docker.sock \
        -v /var/run/dbus:/var/run/dbus \
        -v ${HASSIO_DATA}:/data \
        -e SUPERVISOR_SHARE=${HASSIO_DATA} \
        -e SUPERVISOR_NAME=hassio_supervisor \
        -e HOMEASSISTANT_REPOSITORY=${HOMEASSISTANT} \
        ${SUPERVISOR}
}

start_hassio () {
    SUPERVISOR="$(jq --raw-output '.supervisor' ${CONFIG_FILE})"

    HASSIO_IMAGE_ID=$(/usr/local/bin/docker inspect --format='{{.Id}}' ${SUPERVISOR})
    HASSIO_CONTAINER_ID=$(/usr/local/bin/docker inspect --format='{{.Image}}' hassio_supervisor || echo "--")

    # Fix routing
    route -vn |grep 172.30.32.0 >/dev/null || \
        route add -net 172.30.32.0/23 gw 172.30.32.1

    # Run supervisor
    ([ "${HASSIO_IMAGE_ID}" = "${HASSIO_CONTAINER_ID}" ] && /usr/local/bin/docker start --attach hassio_supervisor) || runSupervisor 
}

while true; do
    start_hassio
    sleep 1
done

@gwystyl

The spk installed perfectly on my DS218+. Starting up worked also. I created a user with my name and then I get stuck.
When I click on Hass.io in the menu on the left, nothing happens. Also "unused entities" stays blank, so I can't add my entities using the Lovelace UI.
Any idea why this happens? Please let me know if there's anything I can do to provide you with usefull feedback.

I have a standard Home Assistant instance running in docker, but I stopped it before trying to install the spk from Hass.io.

Check in with the support thread at https://community.home-assistant.io/t/hass-io-on-synology-dsm-native-package/125559 and update to the latest version (hassio_x64-6.1_20190709-1.spk).