Home Assistant Supervised (previously known as Hass.io) on Synology DSM as native package (not supported or working atm)

Tags: #<Tag:0x00007f326737c4b8> #<Tag:0x00007f3267383ba0>

Did you find a way, to access the addons folder?

Quick!! A tuto :slight_smile:

What is the minimal config of supervisor and of HA core which work with docker v.18.09 ?

You can’t run Supervisor in Docker.

Great ! :ok_hand: I’ll try now
Hassio_Supervisor is in a Docker, no?

Did you really not read anything of what was said above?
lol

Here is a quick guide on running HomeAssistantOS on Synology VMM (perhaps we can add this to the official documentation as this is an supportedTM installation method).

2 Likes

Hi ! Do you think i can run VMM on my ds713+ ? I try with the spk file but i have an error to install.

Thank you so much.
I don’t know which way I will follow with my HA, but right now, all that I know is that I’m so thankful. Thanks to you and your amazing work, I discovered HA. :pray: :+1:

1 Like

Hi, also from me and a couple of others not logged in the community - great work, fun and a very good way to get understanding and get going with home assistant. I agree with all that see it as a pity, but also want to highlight that everyone that built Home assistant are sharing the same goal.

If it would happen that you or someone else get an epiphany on how to make the installation work somehow I am all ears and would love to support with coffee/beer/patron.

I am (with several probably with me) on high end NAS but that is on the border that do not support VM.

and as for not feeling the love… you have it in the Swedish corner! :laughing:

1 Like

Just to conclude what I have written up there.
I’ve received my RAM extension (HyperX Impact HX318LS11IB/8), simply plugged it in and it after rebooting, the 218+ instantly showed 10GB RAM. Using Synology’s VMM to import the ‘hassos_ova-5.10’ OVA was quickly done and after waiting a couple of minutes for HomeAssistant to get prepared, the login screen was shown. Restoring a freshly taken snapshot from the old system was surprisingly simply (different to what I’ve experienced before) and the system was ready. I only had to update the URLs of my Influx/Grafana installation, because the VM has a different IP and that’s it. Updating each component and addon to the newest version went without problems and now I’m satisfied.

The VM normally takes 5-6% CPU load and 4 GBs of RAM. It works like a charm.

So what’s left is to again say thanks for the hass.io-Synology extension. It enabled me to start using HA and I’m not sure whether I would have started without it. But now I’m going to remove this package and continue using the VM way.

Thanks,
Fridolin

4 Likes

So as I said I’ve got my 4GB RAM so in total 6GB on DS218+. Running inside VM no problem at all.

Comparing how quick stuff loads Node-RED instance Dockerized running on Synology host system opens 600-700ms faster than the one running on virtualized as an addon (hence also Dockerized). But, overall, I must say, no issues at all.
You must keep in mind that I don’t have any video surveillance or something that may destroy the CPU.

My setup is Node-RED, Zigbee2MQTT (this one I kept running on host Synology (dockerized) as well as the MQTT Broker, as I’m lazy to re-pair all devices (haven’t found a way to recover devices list)), VSCode, SSH Terminal and few other Wi-Fi devices like Xiaomi, Slide curtains etc. so nothing special.

With Zigbee2Mqtt the only issue or smth unusual I noticed is the fact that logs were absent after line in the log like node ./index.js, usually it’s full of logs, so I didn’t like that either. But in Zigbee2MQTT if I asked to build a map it did build one, but with a coordinator only and that’s it (CC2531), no errors or so.
But it may be caused by the fact that I “mounted” USB stick after VM launch and not while it was in a disabled state. Anyway, never bothered trying to figure it out.

Guys, my DS 218+ processor load is always 65-95% after moving HomeAssistant to the virtual machine. Maybe I have wrong settings for the VM…

HomeAssistant -> Supervisor -> System:
Core CPU Usage 77.8%
Core RAM Usage 22.7%

That is not your VM usage it’s core usage. To check the vm usage login and use the command: “top”

There is a new docker release -> https://www.synology.com/en-in/releaseNote/Docker
Maybe they fixed the problem?

It does not, it is still the same Docker Daemon version 18.09.8

Yes, sorry. Please have a look to Resource Monitor screen shot. VMM load is always around 50%

As you assign 50% of your cpu (2 of 4 cores) to the virtual machine this is normal.

Have a look at the cpu load from the supervisor tab in home-assistant, that will show the real use.

I restarted the Virtual Machine, cleaned not used applications on Synology (docker) and the cpu load returned to normal.

1 Like

Please help !
I started hass.io on Xpenology with Main ITX J1900. after install hass.io on package center finish then login into hass via locall port:8123, but i can not install any addon with error “Failed to install addon” and my log as below
21-02-28 14:31:32 WARNING (MainThread) [supervisor.jobs] ‘ResolutionFixup.run_autofix’ blocked from execution, system is not healthy
21-02-28 14:31:32 ERROR (MainThread) [supervisor.homeassistant.api] Can’t update Home Assistant access token!
21-02-28 14:31:32 ERROR (MainThread) [supervisor.homeassistant.api] Can’t update Home Assistant access token!
21-02-28 14:31:51 WARNING (MainThread) [supervisor.jobs] ‘AddonManager.install’ blocked from execution, system is not healthy
21-02-28 14:34:32 WARNING (MainThread) [supervisor.misc.tasks] Watchdog/Application found a problem with observer plugin!

Read the bold text in the first post.