Very strange, I upgraded from 106.0 -> 106.4 and that worked fine…
The workaround is to create empty folder ‘external’ inside /(hassio_folder)/audio/external
2 Likes
I already had the “external” and “internal” folders hass.io/audio folder. Anything other suggestion to get it working again?
same problem.
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…
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.
I upgraded from 105 to 106.5 and had issue to start home assistant.
Creating group audio did solve bootloop issue in my installation.
I think Fizzbblizz and vasjek are talking about the groups of DSM. Please correct me if I’m wrong.
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
1 Like
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?
Yes, DSM (or better Unix groups in the underlying Linux system).
Use ssh to get to a shell in your DSM, then do a cat /etc/group and make sure the audio group is listed there. If it is not, you did not create the group. On my DSM, the Unix group was created by using the control panel and adding a group.
Hi Fredrik!
I did the following actions, and ended up with some problems:
I got my synology ds 218+ the other day, and quickly set it up with docker, and home assistant, as i realized this is not what i wanted, and Hassio is, i uninstalled it, and set up Hass.io through your package!
altough, DSM package manager says hass.io Beta is running, i cant access the site throgh IP:8123, i am getting: ERR_CONNECTION_REFUSED
Also in DSM notification panel, im getting this message a few minutes after rebooting the NAS saying Hassio_DNS har stopped working.
Checking the docker containers after the hassio install, i see “Homeassistant” is not running, and cant be started, Hassio audio is stuck in a reboot-loop. And Hassio DNS also loops.
Any ideas?
Currently uninstalling everything on the NAS except my UniFI cloud key to start over!
Hm i suspect my initial hass.io install was corrupted, due to the repository being very unstable.
Trying to re-install the package again now, im getting a message in the package manager saying the package is missing from the repo.
Trying to access the URL manually, im getting a 502 bad gateway static cloudflare error rmessage.
Managed to re-install the package, but getting the same errors.
What am i missing?
Now its working! hassio-audio runs stable.
After adding the group audio to DSM, creating the folders /audio/external AND /audio/internal/states the hassio-audio container runs.
Fount it in the containers’ log that mounting of this folder failed.
Thanks for all your help!
2 Likes
How to setup a static ip as I am running into some issues with the adguard addon?
Thank you! This boot looping was driving me insane, I was thinking that all the work I’d done configuring HASS was going to be for nothing, but this has saved me!