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

[raphii (Raphael P.)]

Maybe you’re missing Audio Station? I know that there is a problem with snapcast, without audio station.

[fredrike (Fredrik Erlandsson)]

Works fine for me:

20-03-03 19:38:10 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
20-03-03 19:38:10 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/marcelveldt/hassio-addons-repo repository
20-03-03 19:38:10 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
20-03-03 19:38:15 INFO (MainThread) [supervisor.store] Load add-ons from store: 88 all - 0 new - 0 remove
20-03-03 19:49:48 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.106.4
20-03-03 19:49:48 INFO (SyncWorker_2) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.106.0 to homeassistant/qemux86-64-homeassistant:0.106.4
20-03-03 19:49:48 INFO (SyncWorker_2) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.106.4.
20-03-03 19:51:11 INFO (SyncWorker_2) [supervisor.docker.interface] Stop homeassistant application
20-03-03 19:51:18 INFO (SyncWorker_2) [supervisor.docker.interface] Clean homeassistant application
20-03-03 19:51:39 INFO (SyncWorker_7) [supervisor.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.106.4
20-03-03 19:52:05 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-03-03 19:52:05 INFO (MainThread) [supervisor.homeassistant] Successful run Home Assistant 0.106.4
20-03-03 19:52:05 INFO (SyncWorker_0) [supervisor.docker.interface] Cleanup images: ['homeassistant/qemux86-64-homeassistant:0.106.0']

[raphii (Raphael P.)]

Yep, update from 106.2 to 106.4 breaks HomeAssistant
I’ll dig deeper…

[jim.floris]

I added a folder hass.io/audio/external. This allowed me to start the homeassistant docker manually. The hassio_audio container continues to recycle.

Excerpt from supervisor log:

2020-03-03 17:01:51	stderr	e[32m20-03-03 17:01:51 INFO (SyncWorker_0) [supervisor.docker.audio] Start Audio homeassistant/amd64-hassio-audio with version 5 - 172.30.32.4e[0m
2020-03-03 17:01:47	stderr	e[32m20-03-03 17:01:47 INFO (SyncWorker_8) [supervisor.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - 172.30.32.3e[0m
2020-03-03 17:01:38	stderr	e[32m20-03-03 17:01:38 INFO (MainThread) [supervisor.misc.forwarder] Start DNS port forwarding to 172.30.32.3e[0m
2020-03-03 17:01:38	stderr	e[32m20-03-03 17:01:38 INFO (MainThread) [supervisor.dns] Start CoreDNS plugine[0m
2020-03-03 17:01:38	stderr	e[32m20-03-03 17:01:38 INFO (SyncWorker_0) [supervisor.docker.interface] Clean hassio_audio applicatione[0m
2020-03-03 17:01:37	stderr	e[32m20-03-03 17:01:37 INFO (MainThread) [supervisor.audio] Start Audio plugine[0m
2020-03-03 17:01:37	stderr	e[32m20-03-03 17:01:37 INFO (SyncWorker_3) [supervisor.docker.interface] Attach to homeassistant/amd64-hassio-dns with version 1e[0m
2020-03-03 17:01:37	stderr	e[32m20-03-03 17:01:37 INFO (SyncWorker_2) [supervisor.docker.interface] Attach to homeassistant/amd64-hassio-audio with version 5e[0m
2020-03-03 17:01:37	stderr	e[32m20-03-03 17:01:37 INFO (MainThread) [supervisor.host.apparmor] AppArmor is not enabled on hoste[0m
2020-03-03 17:01:37	stderr	e[32m20-03-03 17:01:37 INFO (MainThread) [supervisor.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}e[0m
2020-03-03 17:01:37	stderr	e[32m20-03-03 17:01:37 INFO (MainThread) [supervisor.host.sound] Update PulseAudio informatione[0m
2020-03-03 17:01:37	stderr	e[33m20-03-03 17:01:37 WARNING (MainThread) [supervisor.dbus.nmi_dns] No DnsManager support on the host. Local DNS functions have been disabled.e[0m
2020-03-03 17:01:37	stderr	e[33m20-03-03 17:01:37 WARNING (MainThread) [supervisor.dbus.rauc] Host has no rauc support. OTA updates have been disabled.e[0m
2020-03-03 17:01:37	stderr	e[33m20-03-03 17:01:37 WARNING (MainThread) [supervisor.dbus.hostname] No hostname support on the host. Hostname functions have been disabled.e[0m
2020-03-03 17:01:37	stderr	e[33m20-03-03 17:01:37 WARNING (MainThread) [supervisor.dbus.systemd] No systemd support on the host. Host control has been disabled.e[0m
2020-03-03 17:01:37	stderr	e[32m20-03-03 17:01:37 INFO (MainThread) [__main__] Setup Supervisore[0m
2020-03-03 17:01:35	stderr	e[32m20-03-03 17:01:35 INFO (SyncWorker_0) [supervisor.docker.supervisor] Connect Supervisor to hassio Networke[0m
2020-03-03 17:01:35	stderr	e[32m20-03-03 17:01:35 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attach to Supervisor homeassistant/amd64-hassio-supervisor with version 207e[0m
2020-03-03 17:01:35	stderr	e[32m20-03-03 17:01:35 INFO (MainThread) [__main__] Initialize Supervisor setupe[0m
2020-03-03 17:01:29	stdout	[services.d] done.
2020-03-03 17:01:29	stdout	[services.d] starting services
2020-03-03 17:01:29	stdout	[cont-init.d] done.
2020-03-03 17:01:29	stdout	[cont-init.d] udev.sh: exited 0.
2020-03-03 17:01:28	stderr	[17:01:28] INFO: e[32mUpdate udev informationse[0m
2020-03-03 17:01:27	stdout	[cont-init.d] udev.sh: executing... 
2020-03-03 17:01:27	stdout	[cont-init.d] executing container initialization scripts...
2020-03-03 17:01:27	stdout	[fix-attrs.d] done.
2020-03-03 17:01:27	stdout	[fix-attrs.d] applying ownership & permissions fixes...
2020-03-03 17:01:27	stdout	[s6-init] ensuring user provided files have correct perms...exited 0.
2020-03-03 17:01:27	stdout	[s6-init] making user provided files available at /var/run/s6/etc...exited 0.

hassio_audio log:

2020-03-03 20:12:37	stdout	[s6-finish] sending all processes the KILL signal and exiting.
2020-03-03 20:12:34	stdout	[s6-finish] sending all processes the TERM signal.
2020-03-03 20:12:33	stdout	[s6-finish] waiting for services.
2020-03-03 20:12:33	stdout	[cont-finish.d] done.
2020-03-03 20:12:33	stdout	[cont-finish.d] executing container finish scripts...
2020-03-03 20:12:33	stdout	[cont-init.d] adjust-audio-group.sh: exited 1.
2020-03-03 20:12:32	stdout	[cont-init.d] adjust-audio-group.sh: executing... 
2020-03-03 20:12:32	stdout	[cont-init.d] executing container initialization scripts...
2020-03-03 20:12:32	stdout	[fix-attrs.d] done.
2020-03-03 20:12:32	stdout	[fix-attrs.d] persistent-data: exited 0.
2020-03-03 20:12:32	stdout	[fix-attrs.d] persistent-data: applying... 
2020-03-03 20:12:32	stdout	[fix-attrs.d] applying ownership & permissions fixes...
2020-03-03 20:12:32	stdout	[s6-init] ensuring user provided files have correct perms...exited 0.
2020-03-03 20:12:31	stdout	[s6-init] making user provided files available at /var/run/s6/etc...exited 0.

[Krocko]

It is a problem with supervisor 207/hassio_audio version 7.
There is already a fix for this in hassio_audio version 8.
@fredrike it is discussed on discord in the dev_supervisor channel. Please have a look.

[raphii (Raphael P.)]

Adding a new folder external in hass.io/audio/ helps to start HA Core manually again.

@jim.floris

hass.io/audio/external

But hassio_audio keeps “bootlooping”

[raphii (Raphael P.)]

https://version.home-assistant.io/stable.json still reports “207” as stable.

[fredrike (Fredrik Erlandsson)]

Very strange, I upgraded from 106.0 -> 106.4 and that worked fine…

[Spiritus]

The workaround is to create empty folder ‘external’ inside /(hassio_folder)/audio/external

[trusty (Eugene)]

I already had the “external” and “internal” folders hass.io/audio folder. Anything other suggestion to get it working again?

[Mintz99]

Help, HAss.io audio not running on docker

Hi all , I need your help , i just updated HA to the latest release , and the system doesn’t come up anymore. It tries to start hass.io audio on a docker in synology , which has no audio. In the folder hass.io audio there is a folder with a file asound # Default to PulseAudio pcm.!default { type pulse hint { show on description "Default ALSA Output (Home Assistant PulseAudio Sound Server)" } } ctl.!default { type pulse } the log of the docker hass audio I…

Watchdog found a problem with PulseAudio plugin!

same problem.

[Umbe (Umberto)]

Thanks , and wonderful answer

Please note: Running Home Assistant (previously known as Hass.io) on a Synology NAS is not supported by us.

So no idea…

[Fizzblizz (Michael Kleinhenz)]

See here for a possible solution: Hassio fails to start after upgrade to 106.5

In short: there is a script running haywire when the host does not have the group audio (which is the case for most NAS systems, but not for “standard” Linux devices). Adding that group fixes the issue.

[vasjek (Vassili)]

I upgraded from 105 to 106.5 and had issue to start home assistant.
Creating group audio did solve bootloop issue in my installation.

[Jonas_Jorgensen (Jonas Jørgensen)]

@vasjek - can you share your groups.yaml? I can’t get it working

[raphii (Raphael P.)]

@fredrike maybe you can add this to the package: synogroup --add audio

as reference: https://global.download.synology.com/download/Document/Software/DeveloperGuide/Firmware/DSM/All/enu/Synology_DiskStation_Administration_CLI_Guide.pdf

[trisplay]

I think Fizzbblizz and vasjek are talking about the groups of DSM. Please correct me if I’m wrong.

[raphii (Raphael P.)]

PSA: to fix the latest supervisor update do this

Step 1: create a new folder named “external” in your “hass.io/audio” folder
Step 2a: create group “audio” with no user via DSM
or
Step 2b: create group “audio” via ssh with synogroup --add audio

[trisplay]

Step 1 worked for me. HA is working fine.
But the docker container Hassio-Audio:8 is bootlooping every 20sec.
Adding the audio group to dsm didn‘t help so far.
Does anybody know what this is for?

[Fizzblizz (Michael Kleinhenz)]

Yes, DSM (or better Unix groups in the underlying Linux system).