Are you sure ?
The last version is 0.118.5
Glad to hear that you got it working!
Yes, it can do that. Not something I prefer, but in last few years I only remember one issue with it.
Ok, another “nail in the coffin”.
Main developers of hass are working actively to stop this “hack”. I’m not really sure how we should proceed now. Not all synology models support running a vm (although that hack would be a fun one). @BeardedConti what do you think we should do?
I suggest we don’t add this PR.
This file you’re adding disables all checks that help supervised installations stay up to date and make sure the supervisor won’t break the host OS.
Synology OS is not supported by Hass.io. Users should instead run HassOS in a VM if supported by their Synology or run Home Assistant Core.
Even making it a tiny bit easier to do this hack means you’re sending people in the wrong direction, filled with broken things that then end up reflecting bad at Home Assistant.
I’m running my main homeassistant as ha core in Docker. And are using hass (hass.io) just to manage my addons.
3 Likes
Worked great for my DS420+. Don’t see the point of their objection to the PR, though, if their list of “supported systems” is anyway quite narrow. A simple disclaimer that this is an unofficial implementation would do, IMHO.
3 Likes
What a load of bs… If home assistant continues to make stupid breaking changes to support less clients, it will quickly lose people.
I think this PR is a great way of going around that stupid implementation. Keep up the good work Fredrik.
3 Likes
i’m sure, I left an older version because i have a problem with an integration i use
1 Like
In my Synology (DS218+) I cannot use VMs, except if I take the expansion unit (DX517), but at the moment I don’t think I could afford it
I personally don’t understand what they have against this method running on Synology
@fredrike I have been using your package since October 2019 and it has always worked wonderfully
the only thing i see as wrong is that we don’t have the latest version of docker because synology doesn’t update it, and despite this it always worked well
2 Likes
Yes only fews model,
and it’s not free ! You have to pay a license
Same situation here : Synology 415+ , Docker V18 nos compatible, supervisor health issue etc.
Happy to say that BeardedConti method workaround worked perfectly (thanks) and another big thank to Fredrike and to this community.
My aim is to use my 5 Squeezebox Touch trough HA and my tube amps 
Let’s see when Synology will upgrade to Docker 19.
Thanks all
gmonno
Works with 2020.12.6
I have been using this package for almost a year now, much to my satisfaction. Many people have been asking me about this and it’s a great way for people, already owning a Synology to enter HA relatively easy, without having to purchase new hardware or get into the official installation procedures. As much as I appreciate working within protocols and do feel ‘hacking core’ is a sin, in any piece of software, it does get ‘the spare tire on’ for now.
@balloob just posted this on the PR:
a lot of people will start to complain that they cannot run hassio anymore, which is the opposite of what we al want isn’t it?
In a perfect world where we have all the time in the world and unlimited resources, sure we would want people to run Home Asssistant Supervisor on every system in the world. However, we don’t have all the time. If you know what you’re doing, fine that’s great. But don’t steer people with less experience down a road that with challenges they are not capable of solving on their own.
When (not if) they encounter a problem that they can’t solve, they think Home Assistant is broken. Doesn’t matter if we tell them they run an unsupported system. We get the complaints.
We all want Home Assistant to evolve, get better, support more things. That also takes time. With our limited time we need to choose how we can have the biggest impact and serve the most people. Trying to make things work with outdated and unsupported Linux kernels does not fit.
I’m not sure how to do this best but perhaps we should create a petition that we want to keep this option.
1 Like
Hi all!
I’ve just installed this package and when I try to a install any addon from Add-on Store recieve next error message:
Failed to install addon
Unknown error, see supervisor
System log:
Supervisor Version 2020.12.dev0503
How could be solved this error?
Thank you in advance!
SOLVED
EVERYONE, first, go here and vote thumbs-up for this post:
To check how many of the people who are using this have interest to keep it working.
My video for hassio on Synology has 22.000 views. We will probably not get more then 20 votes there.
I started writing something there, but decided to not do it.
At the end, anyone who is using hass.io package you created, can very easily make this hack and get system back working.
If this is fixed now, there will probably be next issue in a week, months or half a year.
I really understand what they say in regard to people asking for support for unsupported version.
The issue here is not HA, or this package. Problem is Docker version for HA and Synology is really doing nothing to upgrade it to version 19.x They are the ones who should do something about it. But with DSM 7.0 approaching, not sure that they will invest time into this (if they didn’t do anything until now).
I’m not prepared to do hack upgrade of Docker as I risk much more problems and I’m also not prepared to recommend it to anyone even if they are aware of the consequences.
What HA devs did, by enabling us this ignore flag, is really a lot already.
Stopping Pull request is not cool, but I do get it why they want to do it - offload any unnecessary issues by people NOT reading or understanding what they are doing.
I would upvote Pull request to pass myself, especially after you’ve added disclaimer.
My current machine can’t run VM and even if it could, I wouldn’t do it. Other option is SynoCommunity package - currently 0.114 version with some integrations not working - again - would and will not use.
Core, that’s OK, it works very well, but having addons out of box is better.
I will keep it running for as long as I can. After that… Who knows…
10 Likes
One thing to note, running a VM based on the HassOS OVA does result in a working system. HOWEVER, there is some issue with the Synology hypervisor implementation which does not allow the system to detect the virtualization correctly and thus does not load the QEMU guest tools. This limits the usability of accessing the system, and taking proper snapshots. (You can run the QEMU guest tools perfectly fine, it pauses the system for snapshots correctly, but does not survive a reboot)
So, right now the VM support is not 100% either on the Synology devices that do support running VMs.
EDIT: By default it does not work right. However you can turn off the Hyper-v Enlightenments and it works right and loads the guest tools. From Synology:
I did some testing and found that this issue is due to the option “Enable Hyper-V Enlightenments” found under DSM > Virtual Machine Manager > Virtual Machine > edit the VM in question > General > click the Gear button next to “CPU(s).”
NOTE: This option cannot be altered while the virtual machine is powered on. Please shut down the VM before editing it or the checkbox will be greyed out.
2 Likes
Same exact issue.
I tried the jobs.job patch and no luck 
It should be a file named jobs.json with the contence:
{"ignore_conditions": ["healthy"]}
I’ve updated the #2:nd post with your fix (https://community.home-assistant.io/t/hass-io-on-synology-dsm-native-package/125559/2#unhealthy).
2 Likes
And don’t forget to restart Supervisor - not Home Assistant.