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

Krocko · January 2, 2020, 3:07pm

Is there a chance to get this in a docker-compose file?
How must this docker-compose file look like?

gorg · January 3, 2020, 10:51pm

I had a working setup of hass.io on Ubuntu/Docker but was really pleased to find this package so began moving everything over. I don’t have a complex setup but brought over a backup and things initially looked good. I’ve battled over the Christmas period to get things working, I have some kind of DNS resolution issues, and today have even tried reinstalling everything (Docker/Hass.io package and a fresh/clean/blank Home Assistant install). From this vanilla install I have gathered a few details from the logs of what I see, but I cannot work out what the problem was. Thanks in advance for your help @fredrike!

20-01-03 22:06:36 INFO (MainThread) [hassio.snapshots] Found 0 snapshot files
20-01-03 22:06:36 INFO (MainThread) [hassio.discovery] Load 0 messages
20-01-03 22:06:36 INFO (MainThread) [hassio.ingress] Load 0 ingress session
20-01-03 22:06:36 INFO (MainThread) [hassio.secrets] Load Home Assistant secrets: 1
20-01-03 22:06:36 INFO (MainThread) [__main__] Run Hass.io
20-01-03 22:06:36 INFO (MainThread) [hassio.api] Start API on 172.30.32.2
20-01-03 22:06:36 INFO (MainThread) [hassio.supervisor] Update Supervisor to version None
20-01-03 22:06:36 INFO (SyncWorker_6) [hassio.docker.interface] Update image homeassistant/amd64-hassio-supervisor:193 to homeassistant/amd64-hassio-supervisor:None
20-01-03 22:06:36 INFO (SyncWorker_6) [hassio.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag None.
20-01-03 22:06:38 ERROR (SyncWorker_6) [hassio.docker.interface] Can't install homeassistant/amd64-hassio-supervisor:None -> 404 Client Error: Not Found ("manifest for homeassistant/amd64-hassio-supervisor:None not found").
20-01-03 22:06:38 ERROR (MainThread) [hassio.supervisor] Update of Hass.io fails!
20-01-03 22:06:38 CRITICAL (MainThread) [hassio.core] Can't update supervisor! This will break some Add-ons or affect future version of Home Assistant!
20-01-03 22:06:38 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
20-01-03 22:06:38 INFO (MainThread) [hassio.core] Hass.io reboot detected
20-01-03 22:06:38 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
20-01-03 22:06:38 INFO (MainThread) [hassio.core] Hass.io is up and running
20-01-03 22:06:53 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home Assistant Docker!
20-01-03 22:06:53 INFO (SyncWorker_9) [hassio.docker.interface] Start homeassistant/qemux86-64-homeassistant
20-01-03 22:07:09 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
20-01-03 22:16:45 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-01-03 22:16:50 WARNING (MainThread) [hassio.updater] Can't fetch versions from https://version.home-assistant.io/stable.json: Cannot connect to host version.home-assistant.io:443 ssl:None [Try again]
20-01-03 22:16:53 INFO (MainThread) [hassio.supervisor] Update Supervisor to version None
20-01-03 22:16:53 INFO (SyncWorker_0) [hassio.docker.interface] Update image homeassistant/amd64-hassio-supervisor:193 to homeassistant/amd64-hassio-supervisor:None
20-01-03 22:16:53 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag None.
20-01-03 22:16:55 ERROR (SyncWorker_0) [hassio.docker.interface] Can't install homeassistant/amd64-hassio-supervisor:None -> 404 Client Error: Not Found ("manifest for homeassistant/amd64-hassio-supervisor:None not found").
20-01-03 22:16:55 ERROR (MainThread) [hassio.supervisor] Update of Hass.io fails!
20-01-03 22:19:41 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-01-03 22:19:46 WARNING (MainThread) [hassio.updater] Can't fetch versions from https://version.home-assistant.io/stable.json: Cannot connect to host version.home-assistant.io:443 ssl:None [Try again]
20-01-03 22:22:45 INFO (MainThread) [__main__] Stopping Hass.io
20-01-03 22:22:45 INFO (MainThread) [hassio.api] Stop API on 172.30.32.2
20-01-03 22:22:45 INFO (MainThread) [hassio.misc.forwarder] Stop DNS forwarding
20-01-03 22:22:45 INFO (MainThread) [hassio.core] Hass.io is down
20-01-03 22:22:45 INFO (MainThread) [__main__] Close Hass.io
20-01-03 22:27:40 INFO (MainThread) [__main__] Initialize Hass.io setup
20-01-03 22:27:41 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/amd64-hassio-supervisor with version 193
20-01-03 22:27:41 INFO (MainThread) [__main__] Setup HassIO
20-01-03 22:27:41 WARNING (MainThread) [hassio.dbus.systemd] No systemd support on the host. Host control has been disabled.
20-01-03 22:27:41 WARNING (MainThread) [hassio.dbus.hostname] No hostname support on the host. Hostname functions have been disabled.
20-01-03 22:27:41 WARNING (MainThread) [hassio.dbus.rauc] Host has no rauc support. OTA updates have been disabled.
20-01-03 22:27:41 WARNING (MainThread) [hassio.dbus.nmi_dns] No DnsManager support on the host. Local DNS functions have been disabled.
20-01-03 22:27:41 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: set()
20-01-03 22:27:41 INFO (MainThread) [hassio.host.apparmor] AppArmor is not enabled on host
20-01-03 22:27:41 INFO (SyncWorker_1) [hassio.docker.interface] Attach to homeassistant/amd64-hassio-dns with version 1
20-01-03 22:27:41 INFO (MainThread) [hassio.dns] Update resolv from Supervisor
20-01-03 22:27:41 INFO (MainThread) [hassio.misc.forwarder] Start DNS port forwarding to 172.30.32.3
20-01-03 22:27:41 INFO (SyncWorker_1) [hassio.docker.interface] Stop hassio_dns application
20-01-03 22:27:50 INFO (SyncWorker_1) [hassio.docker.interface] Clean hassio_dns application
20-01-03 22:27:53 INFO (MainThread) [hassio.dns] Start CoreDNS plugin
20-01-03 22:28:02 INFO (SyncWorker_5) [hassio.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1
20-01-03 22:28:02 INFO (SyncWorker_2) [hassio.docker.interface] Attach to homeassistant/qemux86-64-homeassistant with version 0.103.5
20-01-03 22:28:02 INFO (MainThread) [hassio.store.git] Clone add-on https://github.com/hassio-addons/repository repository
20-01-03 22:28:02 INFO (MainThread) [hassio.store.git] Clone add-on https://github.com/home-assistant/hassio-addons repository
20-01-03 22:28:07 ERROR (MainThread) [hassio.store.git] Can't clone https://github.com/home-assistant/hassio-addons repository: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --depth=1 --recursive --shallow-submodules -v https://github.com/home-assistant/hassio-addons /data/addons/core
  stderr: 'Cloning into '/data/addons/core'...
fatal: unable to access 'https://github.com/home-assistant/hassio-addons/': Could not resolve host: github.com
'.
20-01-03 22:28:07 ERROR (MainThread) [hassio.store] Can't load from repository core
20-01-03 22:28:07 ERROR (MainThread) [hassio.store.git] Can't clone https://github.com/hassio-addons/repository repository: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --depth=1 --recursive --shallow-submodules -v https://github.com/hassio-addons/repository /data/addons/git/a0d7b954
  stderr: 'Cloning into '/data/addons/git/a0d7b954'...
fatal: unable to access 'https://github.com/hassio-addons/repository/': Could not resolve host: github.com
'.
20-01-03 22:28:07 ERROR (MainThread) [hassio.store] Can't load from repository https://github.com/hassio-addons/repository
20-01-03 22:28:07 INFO (MainThread) [hassio.store] Load add-ons from store: 0 all - 0 new - 0 remove
20-01-03 22:28:07 INFO (MainThread) [hassio.addons] Found 0 installed add-ons
20-01-03 22:28:07 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-01-03 22:28:12 WARNING (MainThread) [hassio.updater] Can't fetch versions from https://version.home-assistant.io/stable.json: Cannot connect to host version.home-assistant.io:443 ssl:None [Try again]
20-01-03 22:28:12 INFO (MainThread) [hassio.snapshots] Found 0 snapshot files
20-01-03 22:28:12 INFO (MainThread) [hassio.discovery] Load 0 messages
20-01-03 22:28:12 INFO (MainThread) [hassio.ingress] Load 0 ingress session
20-01-03 22:28:12 INFO (MainThread) [hassio.secrets] Load Home Assistant secrets: 1
20-01-03 22:28:12 INFO (MainThread) [__main__] Run Hass.io
20-01-03 22:28:12 INFO (MainThread) [hassio.api] Start API on 172.30.32.2
20-01-03 22:28:12 INFO (MainThread) [hassio.supervisor] Update Supervisor to version None
20-01-03 22:28:12 INFO (SyncWorker_10) [hassio.docker.interface] Update image homeassistant/amd64-hassio-supervisor:193 to homeassistant/amd64-hassio-supervisor:None
20-01-03 22:28:12 INFO (SyncWorker_10) [hassio.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag None.
20-01-03 22:28:15 ERROR (SyncWorker_10) [hassio.docker.interface] Can't install homeassistant/amd64-hassio-supervisor:None -> 404 Client Error: Not Found ("manifest for homeassistant/amd64-hassio-supervisor:None not found").
20-01-03 22:28:15 ERROR (MainThread) [hassio.supervisor] Update of Hass.io fails!
20-01-03 22:28:15 CRITICAL (MainThread) [hassio.core] Can't update supervisor! This will break some Add-ons or affect future version of Home Assistant!
20-01-03 22:28:15 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
20-01-03 22:28:15 INFO (MainThread) [hassio.addons] Phase 'system' start 0 add-ons
20-01-03 22:28:15 INFO (MainThread) [hassio.addons] Phase 'services' start 0 add-ons
20-01-03 22:28:15 INFO (SyncWorker_13) [hassio.docker.interface] Start homeassistant/qemux86-64-homeassistant
20-01-03 22:29:01 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
20-01-03 22:29:01 INFO (MainThread) [hassio.addons] Phase 'application' start 0 add-ons
20-01-03 22:29:01 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
20-01-03 22:29:01 INFO (MainThread) [hassio.core] Hass.io is up and running
20-01-03 22:33:24 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version None
20-01-03 22:33:24 INFO (SyncWorker_10) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.103.5 to homeassistant/qemux86-64-homeassistant:None
20-01-03 22:33:24 INFO (SyncWorker_10) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag None.
20-01-03 22:33:25 ERROR (SyncWorker_10) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:None -> 404 Client Error: Not Found ("manifest for homeassistant/qemux86-64-homeassistant:None not found").
20-01-03 22:33:25 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
20-01-03 22:40:16 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-01-03 22:40:21 WARNING (MainThread) [hassio.updater] Can't fetch versions from https://version.home-assistant.io/stable.json: Cannot connect to host version.home-assistant.io:443 ssl:None [Try again]
20-01-03 22:40:23 INFO (MainThread) [hassio.supervisor] Update Supervisor to version None
20-01-03 22:40:23 INFO (SyncWorker_5) [hassio.docker.interface] Update image homeassistant/amd64-hassio-supervisor:193 to homeassistant/amd64-hassio-supervisor:None
20-01-03 22:40:23 INFO (SyncWorker_5) [hassio.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag None.
20-01-03 22:40:25 ERROR (SyncWorker_5) [hassio.docker.interface] Can't install homeassistant/amd64-hassio-supervisor:None -> 404 Client Error: Not Found ("manifest for homeassistant/amd64-hassio-supervisor:None not found").
20-01-03 22:40:25 ERROR (MainThread) [hassio.supervisor] Update of Hass.io fails!

Anders_Christensen · January 3, 2020, 11:20pm

Which DNS servers are you using on your docker / Synology ?

Simular issue here
https://github.com/home-assistant/hassio-installer/issues/7

gorg · January 4, 2020, 8:16am

My Synology isn’t doing it’s own DNS, but my router is using the Cloudflare Quad 1 (1.1.1.1) and 1.0.0.1 servers.

I’m not sure if/where the configuration could even be applied with Docker on Synology, any ideas? I couldn’t find the config file mentioned in that GitHub issue

Noorbertt · January 5, 2020, 7:37am

Hello,

I got a issue on 6.2.2 DSM.
I try to use wireguard add-on and I receive a error

“500 Server Error: Internal Server Error (“linux runtime spec devices: error gathering device information while adding custom device “/dev/net/tun”: no such file or directory”)”

https://github.com/hassio-addons/addon-zerotier/issues/3

There is a way to update the native app?

gorg · January 5, 2020, 6:50pm

My Synology uses the upstream DNS from my router, 1.1.1.1 and 1.0.0.1 (Cloudflare Quad 1). I’ve been testing with commands like this:

docker exec -ti hassio_supervisor ping -c1 www.google.com
ping: bad address 'www.google.com'

docker exec -ti homeassistant ping -c1 www.google.com
ping: bad address 'www.google.com'

I’ve created an /etc/docker/daemon.json as per the article with the Google Public DNS and restarted Docker but it doesn’t seem to have made any difference:

20-01-05 18:44:58 INFO (MainThread) [__main__] Stopping Hass.io
20-01-05 18:44:58 INFO (MainThread) [hassio.api] Stop API on 172.30.32.2
20-01-05 18:44:58 INFO (MainThread) [hassio.misc.forwarder] Stop DNS forwarding
20-01-05 18:44:58 INFO (MainThread) [hassio.core] Hass.io is down
20-01-05 18:44:58 INFO (MainThread) [__main__] Close Hass.io
20-01-05 18:45:52 INFO (MainThread) [__main__] Initialize Hass.io setup
20-01-05 18:45:53 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/amd64-hassio-supervisor with version 193
20-01-05 18:45:53 INFO (MainThread) [__main__] Setup HassIO
20-01-05 18:45:53 WARNING (MainThread) [hassio.dbus.systemd] No systemd support on the host. Host control has been disabled.
20-01-05 18:45:53 WARNING (MainThread) [hassio.dbus.hostname] No hostname support on the host. Hostname functions have been disabled.
20-01-05 18:45:53 WARNING (MainThread) [hassio.dbus.rauc] Host has no rauc support. OTA updates have been disabled.
20-01-05 18:45:53 WARNING (MainThread) [hassio.dbus.nmi_dns] No DnsManager support on the host. Local DNS functions have been disabled.
20-01-05 18:45:53 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: set()
20-01-05 18:45:53 INFO (MainThread) [hassio.host.apparmor] AppArmor is not enabled on host
20-01-05 18:45:53 INFO (SyncWorker_1) [hassio.docker.interface] Attach to homeassistant/amd64-hassio-dns with version 1
20-01-05 18:45:53 INFO (MainThread) [hassio.dns] Update resolv from Supervisor
20-01-05 18:45:53 INFO (MainThread) [hassio.misc.forwarder] Start DNS port forwarding to 172.30.32.3
20-01-05 18:45:53 INFO (SyncWorker_4) [hassio.docker.interface] Stop hassio_dns application
20-01-05 18:45:56 INFO (SyncWorker_4) [hassio.docker.interface] Clean hassio_dns application
20-01-05 18:45:57 INFO (MainThread) [hassio.dns] Start CoreDNS plugin
20-01-05 18:46:01 INFO (SyncWorker_3) [hassio.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1
20-01-05 18:46:01 INFO (SyncWorker_2) [hassio.docker.interface] Attach to homeassistant/qemux86-64-homeassistant with version 0.103.5
20-01-05 18:46:01 INFO (MainThread) [hassio.store.git] Clone add-on https://github.com/hassio-addons/repository repository
20-01-05 18:46:01 INFO (MainThread) [hassio.store.git] Clone add-on https://github.com/home-assistant/hassio-addons repository
20-01-05 18:46:07 ERROR (MainThread) [hassio.store.git] Can't clone https://github.com/home-assistant/hassio-addons repository: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --depth=1 --recursive --shallow-submodules -v https://github.com/home-assistant/hassio-addons /data/addons/core
  stderr: 'Cloning into '/data/addons/core'...
fatal: unable to access 'https://github.com/home-assistant/hassio-addons/': Could not resolve host: github.com
'.
20-01-05 18:46:07 ERROR (MainThread) [hassio.store] Can't load from repository core
20-01-05 18:46:07 ERROR (MainThread) [hassio.store.git] Can't clone https://github.com/hassio-addons/repository repository: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --depth=1 --recursive --shallow-submodules -v https://github.com/hassio-addons/repository /data/addons/git/a0d7b954
  stderr: 'Cloning into '/data/addons/git/a0d7b954'...
fatal: unable to access 'https://github.com/hassio-addons/repository/': Could not resolve host: github.com
'.
20-01-05 18:46:07 ERROR (MainThread) [hassio.store] Can't load from repository https://github.com/hassio-addons/repository
20-01-05 18:46:07 INFO (MainThread) [hassio.store] Load add-ons from store: 0 all - 0 new - 0 remove
20-01-05 18:46:07 INFO (MainThread) [hassio.addons] Found 0 installed add-ons
20-01-05 18:46:07 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-01-05 18:46:12 WARNING (MainThread) [hassio.updater] Can't fetch versions from https://version.home-assistant.io/stable.json: Cannot connect to host version.home-assistant.io:443 ssl:None [Try again]
20-01-05 18:46:12 INFO (MainThread) [hassio.snapshots] Found 0 snapshot files
20-01-05 18:46:12 INFO (MainThread) [hassio.discovery] Load 0 messages
20-01-05 18:46:12 INFO (MainThread) [hassio.ingress] Load 0 ingress session
20-01-05 18:46:12 INFO (MainThread) [hassio.secrets] Load Home Assistant secrets: 1
20-01-05 18:46:12 INFO (MainThread) [__main__] Run Hass.io
20-01-05 18:46:12 INFO (MainThread) [hassio.api] Start API on 172.30.32.2
20-01-05 18:46:12 INFO (MainThread) [hassio.supervisor] Update Supervisor to version None
20-01-05 18:46:12 INFO (SyncWorker_2) [hassio.docker.interface] Update image homeassistant/amd64-hassio-supervisor:193 to homeassistant/amd64-hassio-supervisor:None
20-01-05 18:46:12 INFO (SyncWorker_2) [hassio.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag None.
20-01-05 18:46:15 ERROR (SyncWorker_2) [hassio.docker.interface] Can't install homeassistant/amd64-hassio-supervisor:None -> 404 Client Error: Not Found ("manifest for homeassistant/amd64-hassio-supervisor:None not found").
20-01-05 18:46:15 ERROR (MainThread) [hassio.supervisor] Update of Hass.io fails!
20-01-05 18:46:15 CRITICAL (MainThread) [hassio.core] Can't update supervisor! This will break some Add-ons or affect future version of Home Assistant!
20-01-05 18:46:15 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
20-01-05 18:46:15 INFO (MainThread) [hassio.core] Hass.io reboot detected
20-01-05 18:46:15 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
20-01-05 18:46:15 INFO (MainThread) [hassio.core] Hass.io is up and running

gorg · January 6, 2020, 3:57pm

So bizarrely my DNS issues with the docker containers seems to have been fixed by disabling the Synology DSM Firewall. @fredrike does your package do anything in relation to the Firewall or could it do any more in terms of default config do you think?

fredrike · January 7, 2020, 10:57am

As I’ve written in post#2:

fredrike:

The installation process does not play nice with the Synology Firewall (or Adguard/PiHole) and could show errors like this below. Make sure to disable the Firewall before starting the installation (thanks @ohminy for pointing this out).

Copy to clipboard
[hassio.utils.dt] Can’t fetch freegeoip data: Cannot connect to host http://ip-api.com/ ssl:None [Try again]
[hassio.updater] Can’t fetch versions from https://version.home-assistant.io/s

and

I don’t know what is going on with the firewall but I do modify the routing: spksrc/spk/hassio/src/hassio.sh at 2269c99bbbf7d310844001b03f1c45cf220d5715 · fredrike/spksrc · GitHub

fredrike · January 7, 2020, 11:04am

I do not know how this can be made into a docker-compose file, given the way hass.io works I don’t think it is.

This package is a re-write against https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh and is using this as a start-stop service: https://github.com/fredrike/spksrc/blob/2269c99bbbf7d310844001b03f1c45cf220d5715/spk/hassio/src/hassio.sh

gorg · January 7, 2020, 1:49pm

Thanks @fredrike and sorry for not reading the notes in this thread more carefully! As much as I like Discourse for this forum I do find it easy to miss important details in long threads.

I wonder if I could help summarise the installation notes into a single document, glad to see the pkg is on Github, perhaps a Readme/Install doc would be useful?

fredrike · January 7, 2020, 1:56pm

Yes an install note, would be good (I’ve tried to compile everything into the second post in this thread). The first 10 posts or so in this thread is “where do I find the configuration” although the install dialog explicitly asks for that. So I’m not very hopeful that more documentation would help much.

Please send me a PM so we can discuss it more.

Steve_Huang · January 10, 2020, 3:18am

Hi, total newbie here. I have installed hass.io on my synology docker and I tried to write a simple py script to run as a command_line sensor. I placed the py script using synology file station in the hass.io file folder and in the configuration.yaml sensor section I put down the following:

platform: command_line
name: KH
command: “python3 /usr/share/hassio/kH.py”
scan_interval: 3600

It seems no matter how I change the path to my script, home assistant can’t find it. I keep on getting Command failed: python3 /usr/share/hassio/kH.py. Can anyone tell me how to find the right path?

Thanks

fredrike · January 10, 2020, 6:39am

Your configuration in hass is mounted into the folder mounted as /config so move your python script to the same location as the configuration and Chand the path to that.

Steve_Huang · January 10, 2020, 3:01pm

Thanks a lot. This totally works now!

fxstein · January 11, 2020, 1:28pm

@fredrike Thanks a lot! Works like a charm, including various core and community add-ons I have installed. Way more scalable for larger deployments than the RP4.

One question for you: Have you considered making the source available via github? Would be happy to help in any way you see fit to make this happen.

fredrike · January 12, 2020, 9:03am

I’m glad that is works for you (too)! I guess it’s starting to be close to stable so I could migrate my own installation onto the package

Yet another “I’m to lazy to catch up a thread” (or perhaps this is becoming incomprehensible)
The code have always been on github the problem is that the spkrc people are unable to give feedback on how to make it fit into a Synology package in their repository. Would really appreciate all help available to push them to approve my pr.

fxstein · January 12, 2020, 12:58pm

Yeah a thread with 396 replies and an endless scrolling message board is beyond full comprehension for mere mortals.

Having said so, I have replied to your PR and added some support to it. If there is anything I can help/contribute to making this happen, please don’t hesitate to point me to it. I have multiple Synology platforms running and this is by far the most comprehensive install for hassio (or any other HA solution) I have been dealing with (outside of the original RPI install, that unfortunately does not scale to larger HA environments with hundreds of devices).

fxstein · January 12, 2020, 1:04pm

One more thing: I would recommend you put a link to the PR and a little request for support from the hassio community at the very top of this thread as part of your very first post. Its hard to find inside so many replies.

Might also be a great idea to upload the latest build to your github repo under releases - like you did for the very first build. I’d prefer than very much over dropbox. And add a link to the releases page of your repo to your top post.

If you like I’d be happy to start another thread to explain my experience/setup and why we need to support this, just don’t want to step over your work.

Michael_Griffin · January 14, 2020, 4:32am

@fredrike OK, with the help of some people on the home assistant discord, I think I finally figured out what was causing my supervisor to restart every 4-5 minutes.

Basically, I’m running Watchtower (https://containrrr.github.io/watchtower/), which is monitoring my other Docker containers. It normally shouldn’t mess with the hassio containers, except that the supervisor is running as homeassistant/amd64-hassio-supervisor (implied latest tag) instead of homeassistant/amd64-hassio-supervisor:195. As soon as I add the version tag to the running hassio_supervisor container, I have no issues whatsoever with the supervisor restarting.

I’m not sure of the appropriate solution here.

If I manually update https://github.com/fredrike/spksrc/blob/7abccb3988f59f16613d1ef40d05b528833fae33/spk/hassio/src/hassio.sh#L38 to be ${SUPERVISOR}:195, I get the behavior I want. I could update the script to something like jq -r .hassio ${CONFIG_DIR}/updater.json to read the version, but then the supervisor doesn’t automatically update itself without a synology restart.
Watchtower supposedly has a way to add a label that will tell it to skip a particular container (https://containrrr.github.io/watchtower/container-selection/). Would it be possible to add a shim so that I can add this custom label to the running Docker container?

fredrike · January 14, 2020, 6:21am

Great find!

I’ll add a note about this in post #2…

The solution should be to tell watchtower to ignore all home assistant related (I’ll have a look at how it can be done). Adding lables is not something I can do (I think) it would be better to ask the hass.io guys about this as it is the supervisor that manage all the containers.