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

[BeardedConti (BeardedTinker)]

A lot of people have issues like this…

This will not help, but just to confirm - I’m running CORE 2021.2.1 and CORE 2021.2.2 - both with supervisor 2021.02.6 - and all are working OK. My DSM version on both machines is 6.2.3-25426 Update 2.

All addon’s working great, latest releases…

[fredrike (Fredrik Erlandsson)]

@blavak68

i was create directory dev/init then give the 777 prermission, did not help, moreover after reboot Synology directory dev/init is disappeared

Please don’t tag me if there is no reason for me to react/respond.

@fredrike

@fredrike: this * integration/special setup doesn’t work, fix it!

Not a community effort in helping out or debugging the issues, just high expectations on fixing stuff.
Wich have made me lose faith and interest in this, I built it to help you guys, but don’t quite feel the love…

[blavak68]

i have only one difference, my DSM version is DSM 6.2.3-25426 Update 3,
do you think that’s it? and is it going to make a change/downgrade on update 2 ?

[dagnelino (Daniele)]

supervisor-2021.02.6
core-2021.2.2
DSM 6.2.3-25426 Update 3
Docker 18.09.8
duckDns & Mosquitto not working anymore

[crosshelder (Helder Rodrigues)]

Plus one in the same situation. should just have stay quiet and all was working. Updated and now only problems.

Where do we ask synology to update container?

[rdekruyf (Robbin)]

For a quick and temporary fix yesterday I downgrade supervisor to 2021.01.7. Be aware to create a snapshot first, some of my Add-ons where gone after doing this. After downgrade click on install they where back including the settings.

For downgrade use the Terminal & SSH add-on it’s still installing with the latest supervisor and execute:
ha supervisor update --version 2021.01.7

Unfortunately overnight Home Assistant automatically updates supervisor back to 2021.02.6. So do not rebooting any addons then it keeps working.

[fridolin]

Interesting, because I did the same, just went down to 2021.1.5, like described a couple of posts above. Automatic updates are off and downgrading worked fine. Just the error stayed and restarting or rebooting the whole Synology did not change anything.

Afterwards I even did one step further and also downgraded core as well, but this didn’t change the result either.

[Zeooo]

It also worked fine for me until I restarted an addon (DuckDNS by update). Have you tried restarting it? On the other hand, have you installed the addons from HA or by manually deploying docker?

Thanks!

[dagnelino (Daniele)]

it’s working! Many thanks, simple downgrade with docker > Hassio CLI > terminal

THANKS!

[blavak68]

thx, very good “hack” -), is possible to disable the automatic update somewhere ?

[rdekruyf (Robbin)]

I think I found a solution for that. ssh into your Synology.
Run the follow command to find the id for the supervisor container: docker container ls
The go into that folder: docker exec -it *id* bash
Then edit this file with: vi /usr/src/supervisor/supervisor/misc/tasks.py

Delete the lines:
RUN_UPDATE _SUPERVISOR = 29100
self.sys.scheduler.register .....etc...... supervisor

Then reboot the container.

[Zeooo]

How have you done to reinstall the addons? I just did that with DuckDNS but when starting it tells me that the configuration is missing. Have you stopped the docker from DSM first and then reinstalled? Or as?

[blavak68]

you make nothing with docker
1- you must have "last good snapshot "
2- then install addon Terminal & SSH (not SSH & Web Terminal)
3- from Terminal & SSH execute:
ha supervisor update --version 2021.01.7
4- then you restore only all addons from “last good snapshot”

• when you not have “last good snapshot” have to make new config

everything should be OK … until:

• the next supervisor update (based on info from “rdekruyf” happens every night)
• and subsequent restart of the addon (is depend from you)

[thunderdanp]

Edit: I’m sorry if this is duplicative of @blavak68 post above, but knowing my frustration with this issue I thought it might help someone

I’m back up to full functionality. What worked for me was:

Downgrading to Supervisor 2021.01.7 as described by @rdekruyf
Restoring a snapshot from 5 days ago (2021-02-05, I cannot recommend Hassio Google Drive Backup enough)
Upgrading to Supervisor ver. 2021.02.1 (I had migrated to Zwave JS and needed a 2021.02 version)

I hope this proves useful for those of you also having trouble.

[anschein]

does the addons restart work?or if upgrading to the new version and don`t reboot the addons?

[thunderdanp]

@anschein I am able to restart without the new version of Supervisor being installed, I just have the notification on the Dashboard tab of Supervisor that an update is available.

Edit: @anschein upon further review I don’t think I understand your question

[anschein]

i mean in the supervisor ver.2021.02.1,can you reboot the addons?i have some connection problem with my MQTT broker and need a new version can reboot the addon

[thunderdanp]

@anschein yes, my addons are restarted and functioning normally

[anschein]

Thx,and i tried every version SUP i can and found ver 2021.01.8 is work for me and safety reboot the addons…But i didn`t upgrade to the new version of supervisor.
So can i ask which addons reboot fine in 2021.02.1?

[miga (Giulio)]

like many others I have problems with the new supervisor. The problem did not occur until I restarted my synology.
I noticed that the new supervisor released in February bind the /dev:/dev path into the new containers (only in new ones or in those that the supervisor decides to recreate)

This thing creates problems for me with these addons:
-mosquito
-grafana
-esphome

I tried to delete the bind (dev: dev) but if I modify the container from docker / portainer the supervisor no longer recognizes the addon (the addon starts in this case)