I order everything from hardkernel. Here is my BOM:
ODROID-N2+ with 4GByte RAM
80x80x10.8mm cooling fan with 2pin connector
128GB eMMC Module N2 Linux
USB3.0 eMMC Module Writer
12V/2A power supply EU plug
What you mean by soldering ?
Thanks for your answer, I have tried what you tell me and now it opens the supervisor part, but it does not let me install anything at all, it tells me:
Failed to install addon
Unknown error, see supervisor
and eb supervisor I get the following:
There is also the problem that I cannot access from the iOS app.
Thanks for the help.
What do you see in log of Supervisor? You need to check there.
What problem?
Sorry I forget to create jobs.json!!
Now I fix it!!
thanks your help!! 
1 Like
I’m testing my DS918+ running VM Debian 10. Just replace the ol’ Synology with 16GB memory (I know it not recommended, but hey it works) so sparing single core + 4GB memory seems to work nicely. I Will let you guys the outcome. So far I have seen no one used this method, so this is a first. I will use the supervised method for installing HASSIO and hopefully work nicely following the supported methods.
1 Like
Its working quite nicely, will upload all my current HA setup to the VM version and see how it goes compare to the on running on Synology Docker.
Synology VM running 1 core + 4GB memory for Debian 10
Supervisor is up and running
Best part this is the supported supervised version since we are following the guideline on Debian 10 as instructed on ADR 0014
Will try to adjust memory and core to see what is best for HASSIO running
1 Like
People are using VM’s to run HASSIO on Synology, but glad to know you got it working too.
In regard to 16GB RAM, my recommendation is to stress test. It’s not enough for system to boot up or say it has 16GB, you must try and use around 12-14GB to be sure it will not crash.
Try spinning off few VM’s and Dockers so that total amount of RAM used is at or near 12 or 14GB.
Problem is not just motherboard but also CPU that doesn’t know how to properly address extra unsupported RAM.
Regarding the 16GB been discussed on Reddit and one person actually perform a test for 12 GB which actually excell it. I forget which reddit discussion but its proven by that person using a stress test script which actually shown 12GB memory are used (He only used 12 instead of 16GB in which 8GB + 4GB)
And that’s the problem. I know that 10-12GB (depending on the model) work’s fine although not supported. The problem is not if it will show RAM available or not, but what will happen when you go above 12, 14 or 16GB in your case of RAM use.
Even if others tested it, you have to test and by test I don’t mean standard memory test, but real memory usage test by loading enough applications in memory to really fill in 14GB of RAM.
As I said (and there a tons of threads on the internet) - problem is CPU - DS918+ uses J3455
and check there maximum supported RAM + RAM speeds…
Yes, it may work but also be aware that it can also fail when you fill up your RAM.
Synology is very quirky about RAM.
I have 16 GB in my synology DS218 + for 2/3 years now. I never had problems.
The reason why some change only one of the two ram banks is because synology advises against doing so. However, I have changed both without problems.
yup changing mine into 2x8GB…
Hi, the workaround has been given by @fredrike
A nice youtube tuto by @BeardedConti : https://www.youtube.com/watch?v=a01qvvDS7QQ&pbjreload=101 .
I hope it helps 
2 Likes
Thank you!
THIS IS NOT Hass.Io on Synology DSM method
This method is not recommended (running Debian 10 on VM Synology), somehow installing is a breeze. However, making the HA usable is another problem in itself. In my case, several function module from HACS doesn’t seem to work at all. For example, localtuya 100% disabled, and the device somehow can’t connect or get some input. Spotify Integrations also result from errors when API connections need to be done. Auto Detection which being detected right away when I’m running HA Core on Synology not being detected (Synology, Samsung TV) Xiaomi Gateway can be detected but upon restart create an error occurs.
Again that is my test and by the end of the day, it’s better to run HA Core on Synology or Hass.Io synology DSM (native package)
so that the container receives an address the same as in the local network, and is visible from the local network
This thread is for running hass.io package. You can create new thread for running HA Core with macvlan.
And hassio package “includes” already necessary network management for everything to work - by utilizing internal docker network and host network for HA.
I just did my install on Synology NS220+ last night. homeassistant couldn’t talk to hassio_supervisor. Tried all the above instructions about deleting and recreating the hassio network manually on DSM 6.2.3-25426. Didn’t work. Deleted and reinstalled the package clean multiple times. I noticed that hassio_supervisor was putting itself in the hassio network AND the default bridge network. removing hassio_supervisor from the default bridge was the trick for me. stopped all containers, restarted hassio_supervisor, and everything worked as expected.
Hi,
rookie here. So I’m running this through docker on my synology NAS. Trying to update to the lastest version from within the Supervisor “dashboard”. Nothing happens when i press “Update”.
What I´m I missing, what do i need to do to update to de suggested release?
*I also tried downloading that same new version 2021.1.5 från the registry in the docker-app on my NAS. But shutting down the current running release and starting the new one instead did not work, so i guess I’m missing something critical… Help approciated!
1 Like
I have the same problem. Also Docker on Synology NAS. Do we need to uninstall and install a fresh copy?
1 Like