The package is not following the hass versions you should be able to update hass to 0.115.
1 Like
Thank you for all the work you’ve put into this. It’s a huge help.
Is there a release notes somewhere for the new version? Just wanted to get an idea of what to expect and didn’t see anything on the Synocommunity site.
1 Like
Hi everyone,
again a super thank you to Fredrike for the package. I have read up on the https://github.com/home-assistant/hassio-addons/issues/1543 - with failing upgrades of Conbee & conbee2 and the fact that the “our” setup is not supported.
My question to you all - have you updated the deconz past 5.0 and succeeded? I have tried several times and it does not work. I get the libQt5Core.so.5 error according to the GitHub comments these errors will continue. I have no idea but am happy to test things and support with coffee 
Coffee sounds good, I have a preliminary idea on how to get it running…
It is a bit of a hack, but will share more details once I’ve tested it some more (I don’t have a conbee stick so can’t fully test it).
Edit: The problem is that s6 seems to block ldconfig and LD_LIBRARY_PATH . I had it working for a few minutes but it wasn’t persistent. I think the deconz has to be run outside of hass.
Edit2: I was wrong, the issue is that the kernel < 3.17 can’t run QT5 (https://stackoverflow.com/a/55402240). I might be able to build a special Docker image with the right support. But I don’t know who will maintain it…
2 Likes
.Hi @fredrike!
The new package version from Synocommunity has indeed been shown as an available update by DSM, but the update fails everytime I try it. DSM complains with the following text: “Failed to update “Hass.io”. This package is not published by Synology Inc.” It detects the update, shows current version and the new version and yet is not able to perform it.
I’m not sure if this is DSM problem or SynoCommunity problem. I did update it (had version 202003 before) by uninstalling the package and installing it again from Synocommunity. This way it worked like a charm.
I thought it’s worth to mention this for the others that will try to update it.
My system is DSM 6.2.3-25426 Update 2 running on DSM216+II.
Thanks again for your awesome work!
But yes @fredrike - it finally is showing up as it should! Excellent news!!!
Congrats on this! It was really strange to have BETA tag in package and nowhere in configuration options for build was it visible…
There is still a beta tag in your picture, but I hope it will work fine.
Unfortunately not. The only change is the uninstall process that is supposed to remove all helper containers.
1 Like
Blind…
That was probably it! Thanks! It was set still to Synology. IMO it’s actually some inconsistency. It permits installs from other sources and from other publishers as Synology, but doesn’t permit updates. Weird.
Something Synology should look at I think.
1 Like
There is no beta tag here though so we might have reached stable.
2 Likes
Yes, it looks like the first image (on list of updates) is showing for what updates are (in this case BETA) and if yo click on it, there is no more beta there.
I’ll update my recording setup now.
Works perfect and no more BETA tag!
1 Like
What’s the link to your recording? Would like to add it to the first post.
Any suggestions on backing up before moving from beta 20191224-1 to current 20200910-2? I went into Supervisor and created a snapshot and downloaded it to my iMac. Anything else to do as a ‘just in case’ measure?
That should be enough, but as a matter of fact, you don’t even need back up.
This upgrade is not touching your HA installation, this upgrade is just new SPK script for installing Supervisor. And it’s not directly related to any specific Hass.io version.
Then again, having regular backup is always a good thing.
2 Likes
Thanks. I’m all for redundant backups. Currently have backups of the Docker folder and Hassio ones onto external on the Synology 
Update was quick and very painless
1 Like