HASSIO (Home Assistant Supervised) for Synology DSM 7 (Unsupported Installation but allows updates and fully functional)

docker-compose.yaml

version: '3'

services:
    hassio:
        image: homeassistant/amd64-hassio-supervisor
        container_name: hassio_supervisor
        privileged: true
        security_opt:
            - seccomp:unconfined
            - apparmor:unconfined
        environment:
            - HOMEASSISTANT_REPOSITORY=homeassistant/qemux86-64-homeassistant
            - SUPERVISOR_SHARE=/PATH/TO/FOLDER/A
            - SUPERVISOR_NAME=hassio_supervisor
        volumes:
            - /PATH/TO/FOLDER/A:/data
            - /var/run/docker.sock:/var/run/docker.sock
            - /var/run/dbus:/var/run/dbus

Please note, I am a relatively new home assistant user. I read somewhere, that when using the supervisor, you shouldn’t do any updates outside from it, like manual docker updates, watchtower etc. Greetings Von: dwl99 ***@***.***> Gesendet: Dienstag, 28. September 2021 18:17 An: maeneak ***@***.***> Cc: Florian Mätschke ***@***.***>; Comment ***@***.***> Betreff: Re: maeneak/docker-compose.yaml @dwl99 commented on this gist.

…

________________________________ Sorry, I'm a bit confused - which of these procedures and in what order should we follow for an upgrade? have you tried: docker-compose down docker rm $(docker stop $(docker ps --filter name=hassio* -q)) docker rm $(docker stop $(docker ps --filter name=homeassistant -q)) i also added docker rm $(docker stop $(docker ps --filter name=addon* -q)) here docker-compose up --detach Thanks, that all seemed to go OK. Supervisor shows Home Assistant Core Version core-2021.6.6 Newest Version core-2021.9.7 and Supervisor Version supervisor-2021.09.0 Newest Version supervisor-2021.09.4 - is the version of Home Assistant Core meant to be that old? I previously restored a backup from a DSM6 Hassio installation which had to include HA Core or it wouldn't proceed. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://gist.github.com/851e883eca7cddd7114f7eaed201ca9d#gistcomment-3908085>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABZHJFAX7DVYYPK7UW72DILUEHTARANCNFSM5B65XJAQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

Thanks - my Home Assistant Core version was outdated but I successfully updated it via the "update" button! I didn't want to risk it with the Supervisor version.

Starting hassio_supervisor ... error

ERROR: for hassio_supervisor Cannot start service hassio: Bind mount failed: '/PATH/TO/FOLDER/A' does not exists

ERROR: for hassio Cannot start service hassio: Bind mount failed: '/PATH/TO/FOLDER/A' does not exists
ERROR: Encountered errors while bringing up the project.

Please help. Thank you

Starting hassio_supervisor ... error

ERROR: for hassio_supervisor Cannot start service hassio: Bind mount failed: '/PATH/TO/FOLDER/A' does not exists

ERROR: for hassio Cannot start service hassio: Bind mount failed: '/PATH/TO/FOLDER/A' does not exists ERROR: Encountered errors while bringing up the project.

Please help. Thank you

You need to create a folder in your NAS, give it the appropriate permissions then edit the script with the path to the folder. For instance, the line in my docker-compose.yaml reads
- SUPERVISOR_SHARE=/volume1/hassio

Starting hassio_supervisor ... error
ERROR: for hassio_supervisor Cannot start service hassio: Bind mount failed: '/PATH/TO/FOLDER/A' does not exists
ERROR: for hassio Cannot start service hassio: Bind mount failed: '/PATH/TO/FOLDER/A' does not exists ERROR: Encountered errors while bringing up the project.
Please help. Thank you

You need to create a folder in your NAS, give it the appropriate permissions then edit the script with the path to the folder. For instance, the line in my docker-compose.yaml reads - SUPERVISOR_SHARE=/volume1/hassio

Thanks :-)

I keep getting error messages about hassio supervisor containers stopping unexpectedly every few minutes. When I looked at the running containers thare are several instances of hassio supervisor. Any idea what's going on?

Note that I added the following to the hassio node under services because I wanted the supervisor container to be automatically restarted if it crashes.

restart: always

So:

services:
    hassio:
        image: homeassistant/amd64-hassio-supervisor
        container_name: hassio_supervisor
        privileged: true
        restart: always
        ....

Starting at error
/volume1/hassio$ docker-compose up --detach
permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.project%3Dhassio%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied

Please help, thanks

Use this guide instead: https://mariushosting.com/how-to-install-home-assistant-supervisor-on-your-synology-nas/

Hold on, this guide is asking for donations to download a 34 byte/character jobs.json file taken from an issue in the original project's repository? That's ridiculous to have to pay for a file containing {"ignore_conditions": ["healthy"]}

Hold on, this guide is asking for donations to download a 34 byte/character jobs.json file taken from an issue in the original project's repository? That's ridiculous to have to pay for a file containing {"ignore_conditions": ["healthy"]}

It does now, but didn't when I originally posted.

Hi,
I just tried this install method and also the guide from https://mariushosting.com/how-to-install-home-assistant-supervisor-on-your-synology-nas/, but I'm getting an error when I try to open the Add-ons page.

The page stays blank for a while, then it shows a Troubleshooting page.

If I look at the network tab on DevTools, I see the it failed to load "...:8123/api/hassio/app/entrypoint.js" with error 502 (Bad Gateway).

I am running DSM 6.2 on Synology 718+. There are 7 hassio containers running.

There seems to be some error regarding the Supervisor...

Any help would be appreciated.

I want to avoid the VM approach, because it'll use a lot more resources from my NAS.

To refresh installation docker-compose down then docker-compose up --detach. Supervisor will not remove containers on docker-compose down. Use: docker rm $(docker stop $(docker ps --filter name=hassio* -q)) docker rm $(docker stop $(docker ps --filter name=homeassistant -q))

Hi,
If i make it on working system i lost all HA setting ?
Where docker-compose.yaml should be placed ?