And my hassio setup also crashed, I had updated node-red that didn’t want to boot anymore. And saidly node-red req atleast supervisor v2021.02.0 … so I am out of luck I guess?
I really, really hate it how home assistant is going with this stupid, ugly “we do not support it” approach. This is just the end of home assistant I am guessing… which I hope it will not be but I can just cannot imagine that this is going the right way.
hi, I also followed this advice from @rdekruyf and I had no problems.
Personally I only commented on the line about the update
I tried to restart the supervisor several times, both from its button and from docker. your problem doesn’t happen to me. are you sure you haven’t done something wrong?
do you see lines like this in the log?
i think it is possible that the file will be overwritten if you do a supervisor update manually
How did you realize this? I updated Docker , but the Containers aren’t starting anymore… the necessary supervisor container isnt there anymore…
do not update docker! It messed up all my containers and is not a solution for my use DS918+
First of all, this is not my repository, I just found it and its work for me.
What I did?
The only problem I encountered was the incorrect working time of the container
If you are just using this for home assistant I guess it is fine but I am running a whole lot more containers and that made a big mess with env stuff being erased and containers unable to start. This could be because I am using the BTRFS file system.
For everyone, read this first: https://github.com/markdumay/synology-docker/issues/42
And if all of us ask for a new docker update we might be able to get it 
?
https://www.synology.com/en-global/form/inquiry/feature
Fill it out !
I just checked the log, but this line saying ‘ignoring Supervisor updates’ is not there. Also restarting HA did not bring up this line.
But I checked the file I modified and both lines are still gone. So I hope I messed up something yesterday and today it’ll survive the 24h limit.
On the other hand, my system seems to be somehow fishy. I’m happy that my automations are back to normal, but all of my history graphs are empty, just showing the message ‘loading data’. But only in case that there is more than one sensor shown. If I remove all but one, the curve is nicely displayed. But once I add a second sensor, the curve disappears and it is back to ‘loading data’. I have no idea, where this could be coming from.
I just wanted to say, that I love your work and appreciate second you spend on this! Please don’t listen to people, who get everything for free, and still aren’t able to say “thank you”. I don’t know what others say, but I can say myself, that YOUR WORK is making my experience of home assistant much better, than many other integrations. Thanks to you I have a free unused raspberry pi, I have a much better working system, and hence less energy costs. Your work is awesome!!!
Thank you !
Hey @fredrike, I love your work too and will never complain ! Because of your hard work we are able to use this wonderfull piece of software on our synologys…
Don’t lose faith or interest in this just because some people does not understand the whole process of this thing.
I think many are just not understanding that someone, like you, did all this because he is passionate, and FOR FREE… You know, some are just not developers and not really intelligent… But you seems to be, so just be it again and don’t lose it
I would be glad to help, but I’m afraid my knowledge is not enough to be helpful. If you need anything (not complicated) I can do. I have a Syno with docker. Please let me know
Hi guys,
Same thing as you but worse : after update and reboot of the syno, supervisor won’t load in HA (so cannot install SSH terminal addon), hassio_cli container won’t start (no other container except homeassistant and hassio_supervisor works…), so no CLI to downgrade supervisor, I’m in a bind here… I’d love to downgrade supervisor and stop updates, but don’t know what to try anymore.
The containers that won’t start all show this :
Start container hassio_cli failed: {"message":"failed to create endpoint hassio_cli on network hassio: adding interface docker13d27a3 to bridge hassio failed: could not find bridge hassio: route ip+net: no such network interface"}.
Thanks a lot for any pointers
Remove the Hassio addon from package manager, delete all the containers related to your HA setup. Remove the hassio network and reinstall the addon, wait 30 minutes and all should be a little better.
Thanks @nivong it worked !
Now I’m going try to downgrade the supervisor and see if I get all functions back.
In the meantime I installed HA on a Debian virtual machine and restored a snapshot (all went great), I’m only a few tweaks away from having a solid backup system ^^
God I love this community, HA is awesome, thanks to all who participate !
Hey folks. I know that on Synology we can run a proper virtual machine, not dockerized.
Why it’s not recommended way to go? I know that Docker is quick and easy to manage, but I guess VMs are officially supported platforms, and Synology with Docker is not and 18th version of Docker is not helping with that either. Shall we all just use VM version of Hass.io instead and enjoy full compatibility and no hacks at cost of a little more memory/CPU consumption?
Just a few weeks ago, when we had similar struggle, I asked the same question and got more or less the same reply. This way here provided an easy and convenient way to quickly set up HA and I’m glad that someone came up with this idea.
But somehow I got tired of always hearing that my setup would not be supported and therefore updating is risky. I’ve seen many github issues simply being closed saying ‘not supported - go somewhere else’. Also it’s still not clear, whether this approach can be used running DSM 7.
I have a system running in a VM on a PC and this works pretty fine. During the last days, I’ve converted an ext4 HDD to btrfs and ordered a RAM extension to be able to try a HA VM on a Synology. I’ve heard that some users experienced heavy CPU loads on the Syno running the VM, but others were totally happy. So I will give this a try.
It’s somehow funny that a friend tried to convince me to use OpenHab and I did not listen and told him how nicely HA can be used.
I think it started with the fact that there are great developers like @fredrike who also pass on their knowledge and try to make HA possible for as many users as possible.
On the other hand, I understand that HA developers only focus on the platforms they support.
What I don’t understand is why the developers of HA do everything they can to ensure that non-supported platforms no longer work.
As a user I am happy with my HA and don’t need any upgrades but the supervisor is automatically upgraded.
If I block the supervisor upgrade, for example, I am no longer offered Node Red in the add ons. Or I can no longer make a backup.
If I allow the automatic supervisor upgrades, some add ons no longer work after a restart.
A devil’s circle and this is where my understanding for the HA developers ends.
Same, like. OK, notify us on the fact that platform is not supported etc. But, please, do not make more obstacles. But I guess they want that so people don’t stand even a chance to run it so never come for support 
Kinda makes sense but they definitely underestimate users that work around all those obstacles and still are coming back to their Github Issues
Anyway, 100 EUR RAM upgrade is on the way, my time worth way more than that, so I’ll just setup HA OS on VM and hope it will run smoothly without any hiccups. As I have DS218+ and default 2GB is not enough to run VMs, so a 4GB upgrade (min possible) is needed.
This is partially incorrect. Home Assistant can run in 2 different ways on Synology systems, that both are supported. 1) is using a VM, however, as some alright pointed out: That isn’t a viable option on all systems.
The other support method is using Docker: Home Assistant Container, documented in the official documentation even; Here: https://www.home-assistant.io/installation/alternative#synology-nas
The option offered in this topic/package is called: Home Assistant Supervised. Home Assistant Supervised is not viable to run on a Synology NAS, which is the main cause all the above problems everybody is experiencing.
Lastly, a Core Python application could be run as well. So from the 4 available installation methods, only 1 is not viable (which this topic however does cover). All others are viable options.
But if I understand it correctly only the supervised version enables addons and other stuff.
As without it, well, experience requires way more tinkering.
Currently, I run an unsupported version of the Supervised one, which basically got broken apart since the last update. So I end up running all the Mqtt and Mqtt2Zigbee and Node-red as separate manually launched in Docker instances, but the main thing that annoys me that I can’t show these tools Web UIs in HA UI, aside from iframe_panel which obviously doesn’t work with Nabu Casa as I need to make a proper Proxy config in HA. Is there any guide on how to modify the proxy of the HA server?
@frenck, I thought the Docker version of Synology is no longer up to date for HA. Now I am confused.
