Search for Dropbox link in this thread. It should be version from December 2019.
That’s ok/normal - Synology spk is definitely not on the list of supported installations.
Picking back up a project isolating alexa commands to the local network.
I’m curios how to resolve the issue with node rd and alexa local on port 80 as an add-on to Hassio native. Synology requires port 80 for its use. I can set nr to another port, but alexa can’t discover.
I’ve read some other threads about using macvlan and moving HA to a subnet block. Is this the right path?
Thanks
jwb
Thanks!!.. This also solved my problem… it took me a while to realise that ‘force-stop package’ is something else than ‘stop package’ but after that, all is back to normal! finally
@BeardedConti i’m running xpenology on an HP server with 8Gb of RAM.
It took me allot of time to discover that the problem was on the hass.io container because HA was running the default config and the duckdns and nodered (default config) addons
Yes, i did read about the error and restarting does solve the issue (some times), but it comes back again, and again and again. some times the supervisor is running and the page is blank, restarting does not solve this issue only a new installation.
I got an funny bug with the supervisor, lets say that supervisor was on the version 10.1. I received a alert to upgrade to the version 10.1 (when the container was already on that version) but the supervisor was saying that it was on the 10.2!!
Actually the containers were not stopped they were constantly rebooting, dns, cli, multicast and audio.
How do you upgrade to HA 0.115? Is Hass.io on synology updated at the same time or do we have to wait for the package to be updated?
Great news!
The spk package have been updated and is finally out of beta. It should show up as an update trough trough Synology’s Package Center (note that the spk have little to do with the hass versions).
Alternative download link is: https://packages.synocommunity.com/hassio/2/hassio.v2.f22259[apollolake-avoton-braswell-broadwell-broadwellnk-bromolow-cedarview-denverton-dockerx64-geminilake-grantley-purley-kvmx64-x86-x86_64].spk
9 Likes
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.