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.
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.
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!
I try to switch from docker to vm but when I start the VM it stuck in console at Booting from Hard drive.
I have a DS716+ like @fredrike. Is there someting I can do to get it work?
I follow the little tutoriel from this thread.
It’s stuck at what console? If you are installing VMM or creating VM, you really have no need to use console at any point. Everything is done through DSM web interface.
You probably haven’t waited long enough for everything to get downloaded and installed. Try accessing it on http://homeassistant.local:8123 or IP address it got from DHCP.
@fredrike has messaged us letting everyone know this guide no longer works. Please do not use this guide. Anyone willing to make a new guide, please do so over in the Community Guides section of the forums.
