Well I don’t know if it’s impossible on specific synology chips. But it’s alot harder. I had it almost working but docker package that had to manually created in an ubuntu env needed one file that I couldn’t get to work.
User chickenporn made a nice guide on how to do it with the not officially supported chips. After 3 weeks on and off I bought 218+ was too much of a hassle.
So I use docker on DSM for these activities, and for some unknown reason I always have DSM open in a tab on my browser. I guess it’s what you are use too.
Worth noting, I have been using HA for a year or so now and I still crash it a lot! 
1 Like
If the arm device can run docker I should be able to make hass.io run on it too.
Glad you like it!
Don’t worry about the issues. I’ve stated in post #2 that:
Just installed this, and it seems to be working. But i do get the following error when i click on the Superviser menu option. Am i missing something?
Also noticed that my log has a lot of errors attempting to connect to an unknown IP. My IP scope is 192.168.1.x
2020-06-11 21:56:18 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /supervisor/options request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed (‘172.30.32.2’, 80)]
I followed the guide in the top that describes these issues… But now my hassio_supervisor container keeps restarting it self all the time.
Hey @Da9L! Glad you got it installed! Please read post number 2 (back from July 2019) - both issue you are having and question in regard to 172. network are explained there.
1 Like
Hi BeardedConti - I actually managed to fix it. I had already tried the explanation in Post 2 which didn’t fix it for me, but after i did a complete reinstallation of the package along with docker, I got it working. Must have missed something somewhere in the first try.
I have another issue now, which is the first one described in Post 2. However my Synology firewall have never been enabled on the NAS and i do not have Adguard/PiHole anywhere on my network.
I do however have a Synology Router, which has the Firewall enabled. I do not have the option to disable that though.
EDIT : Just noticed that what i think I’m experiencing is not missing internet access, but what seems to be some DNS not working. I cannot ping google.com from hassio_cli but i can ping its ip address.
EDIT2 : I managed to solve this too somewhat. After adding my routers ip address to /etc/resolv.conf on the homeassistant container via the terminal, i can now ping dns names from it, which makes Home Assistant also able to do stuff that requries that. Like the default weather card wasn’t working because it couldn’t resolve api.met.no… Problem is that this dns server entry gets removed if i restart Home Assistant
1 Like
Can someone maybe tell how you make a permanent DNS entry in /etc/resolv.conf that doesn’t get reset everytime in the homeassistant container? I’ve read that it is supposed to reset, as /etc/resolv.conf is supposed to be controlled by the system. But there must be somewhere i can set some custom dns entry in it, that also sticks upon reboot
You can add entries via the cli. Install the Terminal addon and run:
ha dns options --locals dsn://192.168.1.1
2 Likes
Hi fredrike, Hi @all
i am new to Hassio but installing the packed worked fine for me. What frustrated me was that i cannot seem to see the addon store and install the addon that allow me to edit the config. Do you have any clue on what i have to do ?
When you open supervisor, do you see anything or you get empty page?
There could be two issues for that @Shadowstrider - can you for start check your hassio_supervisor container in Docker. Check if it’s running and also if it’s restarting maybe.
If that works, please check log file for supervisor.
Other problem could be networking issue. Did you maybe check post #2 in this thread?
Thanks, i was expecting it somewhere else. Last time i installed it the supvervisor site was empty. I found it now and it is working. Even managed to connect my LCN
1 Like
Sorry but I try to use an addon for monitoring the versions of my dockerpackages, but this addon needs
-v /var/run/docker.sock:/var/run/docker.sock
As far as I saw Its only mounted in the supervisor but I cant get it work on the homeassistant container . so any help is welkom to let this work with the native DSM package. Here you can find the addon I try to use. I know you can use portainer but I want to use version controll so if there is an update I can send a notification to my phone.
https://github.com/ualex73/monitor_docker
This is not addon - this is HACS component if I’m not mistaking. docker.sock looks OK and it should be more or less same for Synology Docker implementation.
So you see all containers except homeassistant? When you open Docker, do you see it there or is it missing?
Since 4 days, i got trouble with zwave (not starting) and SSH util… not starting, so i cleaned the maps /server/hassio completely and reinstall Hassio beta again. Too bad docker Homeassistant does not start, manually starting… immediatele stop and error look at log: Start container homeassistant failed: {“message”:“Bind mount failed: ‘/volume1/server/hass.io/tmp/homeassistant_pulse’ does not exists”}.
What went wrong?
It is indeed a hacs component. All containers working great home Assistant is present but volume docker.sock isn’t in there I tried to add it manual but with no luck because its a sock and not a file.
docker.sock should be here - you need telnet/ssh to access it:
/var/run/docker.sock - so in /var/run folder
nope it isn’t there only audio and s6 are in there
On what Synology are you running this? And what is Docker version installed?
I’ve a DS415+ and I have Docker 18.09.0-0513 and hassio package version 20191224-1
No idea whats wrong, but wen I look in the Docker GUI on my synology I see that the /var/run/docker.sock:/var/run/docker.sock only is mounted on the supervisor container and not on the homeassistant container and thats wat I need to reallize if I read it correctly on the hacs component instructions
Your setup is same as mine…
If you are using hass.io, you will not be able to add this volume mapping. At least not without some serious changes to the code (somewhere).
This looks like it was written for use in Home Assistant Core version.
Mapping (and creating of homeassistant container) is controlled not by user, but by Supervisor. And Supervisor has this mapping but will not help you with this integration.
There are ways for adding new volume mapping to running container you can search for them on the net - I haven’t done it so far.