Sorry, of course @fredrike.
And thank you very much for the hint.
Amazing how easy it is. When you know it 
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.
YES，its working now！
Echoing @gerosaf. Is there a way to customize docker volume configurations for “homeassistant” container?
I am using letsencrypt container (linuxserver.io) to generate and renew certificates and use it in other containers by mapping the /etc/letsencrypt volume. Anytime the homeassistant is upgraded, the volume configuration is reset and HA does not start as it cannot find the certificate.
Great work, btw!
Moved across to this implementation a couple of weeks ago from an RPI based deployment.
All was good until I discovered it had stopped writing to my InfluxDB (Also in a Docker container on the same host).
However it could still write to the MariaDB which is a native install on the same SynologyNAS. So both DB’s have the same IP set in configuration.yaml but are talking to different ports.
Poking with the network it turned out it that the Home Assistant container couldn’t make a network connection to the Influx port on the IP for the Synology, but would talk to the MariaDB. Odd, since they’re the same IP…
But, it would talk directly to the IP of the InfluxDB container. Updating configuration.yaml with the actual IP of the InfluxDB container has resolved the problem, but it doesn’t explain why it wouldn’t talk to the host IP (which is how other systems access it).
This may help someone else, and if anyone know’s why it won’t work using the external IP the same way other servers do that would be useful to me to understand…
I just installed this and everything seemed to work fine. But when i log into Home Assistant there is no “hass.io” button which is usually below “Developer Tools”.
Now i have “supervisor” in it’s place but after opening i only see an empty page, not the add-on store or the other tabs i would expect.
Did i do anything wrong?
Edit: I just figured out the tab is supposed to be called “supervisor” now. Anyway, it still doesn’t have any content
Edit2: After reboot (stop Docker container) it’s okay now.
Hi and welcome.
I had the same experience when I first installed on Synology.
It took me three goes. The last one was a complete removal of docker and all containers and associated shared folders.
It then all came up as expected. Rock solid since then.
Worth checking out Bearded Tinker on youtube for a guide.
Hi guys,
I keep seeing an error in my main log:
20-03-15 08:59:09 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
shared memfd open() failed: Function not implemented
Seems to be related to PulseAudio? Do I need to do anything about it?
Just use the DSM Let’s encrypt client and add a DSM scheduled task to copy the certificates to the folder where the docker container stores its files.
See here: https://www.jens-bretschneider.de/hass-io-mit-lets-encrypt-zertifikaten-auf-synology-nas/
(sorry, German only. Use deepl.com to translate.)
Thanks!
I do not want to use DSM letsencrypt client as it does not support DNS validation. However, I can simply copy the certs from letsencrypt container to homeassistant container similar to the solution you referenced.
Hi,
I’m huge fan of hass.io in Synology
There are one issue on latest build ( 20191224-1 )
DS416play are officially not support Docker.
But It’s possible to using via manual package install.
When hass.io package install via package center (synocommunity ) there are docker package missing message on below.
Currently DS416play using 20191006-3c5c9bce from dropbox.
It tested in docker Docker ver 18.09.0-0506 / 17.05.0-0401
=============
The follwong packages are missing in the package server. Please contact the Synology support team for help.
Docker
I did without manually creating folders in hass.io/audio. In my case, it was enough to create an audio group in DSM before installation. Thanks to FizzBlizz! 
Can you give some more information on which package that enables Docker and I might be able to fix the issue.
Thanks for reply.
hassio_x64-6.1_20191006-3c5c9bce.spk are working very well with Docker 18.09.0-0506.
But, SynoCommunity version hass.io (291224-1) can’t be install due to missing docker notice.
I meant where did you find the Docker package?
There were issues with an old Docker package so I did pin the version on the SynoCommunity to Docker>=18.09.0-0506 it is very strange as it seems like you already have Docker 18.09.0-0506 installed.
Could you test the following (from an terminal on your NAS):
synopkg list|grep Dockersynopkg version Docker
This is my outputs:
$ synopkg list|grep Docker
Docker-18.09.0-0506: Docker is a lightweight virtualization application that gives you the ability to run thousands of containers created by developers from all over the world on DSM. The hugely popular built-in image repository, Docker Hub, allows you to find shared applications from other talented developers.
$ synopkg version Docker
18.09.0-0506
I’ve used the same workaround to let it work!
@fredrike: I’m working on a local Home Assistant Core installation, because I’m testing a Lutron integration which is requiring to modify also a dependency (pylutron.py).
Is there a way to updated the docker installation to my modified version when I’m ready, or it doesn’t make sense?
Move this to another topic.
Thanks for advice.
That docker are downloaded from below link:
https://usdl.synology.com/download/Package/spk/Docker/18.09.0-0506/
and my output are like below ( There are some Koreans but meaning are same as yours )
admin@DATA:~$ synopkg list|grep Docker
Docker-18.09.0-0506: Docker는 전 세계의 개발자들이 DSM에서 만든 수천개의 컨테이너를 실행할 수 있는 능력을 제공하는 경량형 가상화 응용 프로그램입니다. 인기있는 거대한 내장 이미지 리포지토리인 Docker 허브에서는 재능있는 다른 개발자들의 공유된 응용 프로그램을 찾을 수 있습니다.
admin@DATA:~$ synopkg version Docker
18.09.0-0506
For some reason, after several weeks and days of stable running hassio 106.6 i just now lost the dashboard in the supervisor, it does not show installed add-ons.
Also, the add-on store is not showing any results.
Nothing in the log-files, and the only change done recently is signing up and connecting to Nabu Casa. I offcourse disabled this, restarted the package from DSM, and so on. Still no data in the supervisor.
Also tried to restore to an 6 days old image, i know the store worked then, but even when restored, it does not show anything in dashboard, or in the add-on store.
Any ideas?
Oh, that’s really unfortunate. Usually the issue with the supervisor tab is resolved by restarting (either the package or sometimes the whole NAS). I don’t know what is causing this but it is a sync-problem between the supervisor and hass-core.
For some reason, upgrading the core to 107.7, and after that roling back to a 6 day old snapshot solved the problem and everything is working again.
Is this a Synlogy specific bug, or is it a Home assistant bug in general?