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

Got things up and running, but the supervisor doesn’t show the add-ons, tried to add repositories but that’s also not possible.

Maybe little bit offtopic, but I’m suggesting to switch from DS218+ to a Raspberry Pi 4. So I’m more flexible where to place the server in the house, because zigbee connection from the basement is not quite good.

What do you think about the performance difference?

Hello, it might sound a stupid question, but how do you uninstall it?

I’m a bit newbie with Docker, I need help trying to remove the docker container instances that got created when I installed Home Assistant on my Synology NAS.

Hassio_Supervisor (homeassistant/amd64-hassio-supervisor) restarts itself immediately and I’m unable to deleted it. All other containers (hassio_DNS, hassio_cli, hassio_audio, hassio_multicast etc …) seem to be recreated automatically.

Please help:)

Hi,

Did you stop it and delete it from the Package Center from Synology?

I just did, it worked, thank you!
I didn’t think to look for it there …

1 Like

Yes, but the error is in the supervisor, so that should be expected.

I don’t know where the file is, the folders where I have installed hassio are empty

thx!

You have to use telnet (ssh) to connect to Synology - putty for example.
After connecting type sudo vi /usr/local/hassio/etc/hassio.json to open hassio.json.
SUDO is used to give your user ability to save changes.

After you finish editing, press ESC and then :wq! to write changes and quit.
Type exit to close session, and that should be it (I hope).

So, just as I’m nosy and trying to figure how some do see this error, and others not, @pschmitt64, @proxy64 @Kaladen and @swim89 - what is your Synology devices?

Is it maybe newer 2020 model (920, 620, x20,…)?

918 here, it looked like the updater.pl script was breaking for some reason.

the update notes mention “Add process lock for update + fix timeout (#2215)” as the only change to the updater.

I am having problems updating to 0.118.2. I have done several updates and now I ge th error in the log from supervisor. WARNING (MainThread) [supervisor.jobs] ‘HomeAssistantCore.update’ blocked from execution, system is not healthy

It will not even let me save a snapshot.

Any suggestions?

1 Like

@BeardedConti I’m using DS918+ (with DSM 6.2.3-25426 Update 2)

2 Likes

@BorderConti DS716+ DSM 6.2.3-25426 Update 2

1 Like

What version of Supervisor you have? 2020.11.2, 2020.11.0 or 2020.10.0?
I’ve seen this error 2 times in last day but when others tried to install add-ons. Version was 2020.11.2.

1 Like

same error on latest supervisor and 0.118.1 - cant update ha to 0.118.2
20-11-23 10:16:13 WARNING (MainThread) [supervisor.jobs] 'AddonManager.update' blocked from execution, system is not healthy
cant update addon
20-11-23 11:00:24 WARNING (MainThread) [supervisor.jobs] 'AddonManager.update' blocked from execution, system is not healthy

1 Like

I created issue on github


This way of home assistant is not officially supported, so it will be good if all users reported also there on this issue
1 Like

Fixed mentioned above (to edit hassio.json) and add :2020.10.0 to the first line will fix it.

And BTW - since Synology is unsupported platform, your ticket will just be closed, no matter how many people upvote it or not.

EDIT: and yes, the ticket was closed.
But at least we now know that until Synology release newer version of Docker (and it will not, ever), we have system that will be intentionally blocked by HA from updates to give us time to correct Docker version.

At least that’s how I’ve read the comments on the issue.

2 Likes

Well, that really sucks. Has Synology come right out and said they never intend to update the Docker version?

Supervision version 2020.11.2

ok I edited the hassio.json file with the following command

sudo vi /usr/local/hassio/etc/hassio.json to open hassio.json
added :2020.10.0

:wq! and exited…

When I restart the Synology… Hassio starts but it takes a really long time but appears to have worked but the Supervisor page is blank?

Is this expected?