thanks anyway
@dave-castle I can start the wireguard addon, what is your issue?
Perhaps try the 20190813-6dd0666c version…
Thanks so much for putting this together, it’s fantastic.
I am encountering an occasional issue though. I’ve connected Hass.io to Homekit and all works fine initially but over time it switches in Homekit to “no response”. Hass.io continues to run fine but the Homekit connection dies and a restart doesn’t help. I’d thought it was due to a different add-on that wasn’t working as when I disabled that it all seemed fine. But a few days on and it’s gone back to no response. Before I pick this up as a Hass.io / homekit issue I wanted to see whether anyone else using this package is having similar issues.
that’s weird, my docker version is on 18.09.0-17.05.0-0401. Downgraded to your dropbox shared version, how to get on the newest?
issue is:
19-09-09 15:15:49 INFO (SyncWorker_1) [hassio.docker.interface] Clean addon_a0d7b954_wireguard application
19-09-09 15:15:52 ERROR (SyncWorker_1) [hassio.docker] Can’t start addon_a0d7b954_wireguard: 404 Client Error: Not Found (“linux runtime spec devices: error gathering device information while adding custom device “/dev/net/tun”: lstat /dev/net/tun: no such file or directory”)
Do you now if there is a way to force the update? I’m not seeing a new version on my Synology.
Hi guys,
yesterday i get my new DS218+ (2x2TB WD Red, 2GB + 8GB RAM), installed the DSM with standard, Bfsr, SHR.
Then installed DOCKER and then manual the #hassio_x64-6.1_20190709-1.spk#
Created Shared folder, allowed the groups #administrators# + #users# to read + write
Replayed the backup of my hass.io what is still running on a raspberry and …
it runs!!!
Thank you Fredrik for sharing 
3 Likes
Hi @fredrike thanks for your job !!! It’s great 
But there is a problem with de DSM UI with the resources monitor, show the bond of hassio, but not the total of bandwidth used. It’s possible to repair ?
Thanks
PD: I’m Running DSM 6.2.2-24922 Update 3
I dont said anything sorry. I switched clicking in the name
German only from what I see… US folks are still at 17.x
Strange, I had to fix some zwave problems, so wanted to start ozwcp… before doing so I checked if I can ssh to homeassistant and apparently iot does not work (it worked after migration to Synology). Apparently the add on is stopped and cannot be started (spiining circle and then returning to non started screen). I tried to reinstal, same result. I checked this also on docker side (from DSM) and was not able to start ssh package. I’m getting error: Container does not exist. itried to restore it from snapshot, same result… I tried then to check what might be wrong just installing another, previously not used addon (I tried Frneck’s SSH & Web Terminal) with exactly same result… cannot start addon neither from hassio or docker with the same errors… I’ve seen that some time ago @Cinamon reported similar issue. Anyone else noticed ssuch problem? Any idea how to fix?
@fredrike I’ve just installed your package in my Synology, but now for some reason it doesn’t sign in to Home Assistant cloud ('Unable to reach the Home Assistant cloud.).
Before installing your package I gave a try to another Home Assistant build made for Docker, but I COMPLETELY uninstalled it.
Cloud is perfectly reacheable and working when used from a normal Desktop Web browser.
Is the homeassistant-dns container running?
1 Like
Uninstall the addon and make sure it’s docker container also is removed.
Then it should work again otherwise we need more log information to be able to help you.
Perhaps my mistake, but… if I put my DuckDNS domain under http: in the configuration.yaml file am I not supposed to reach Home Assistant ALSO when using a LAN HTTPS IP address?
I ask because I noticed that no matter if I am in the same LAN I must always use the DuckDNS IP otherwise I get that error displayed. 
Hej Fredrike,
I have started and stopped Hass.io from the package centre and the hassio supervisor (several times). Still the Hassio button does not show in the HomeAssistant.
I am running the hassio_x64-6.1_20190805-63550c41,
The Z-Wave dongle is working, The zigbee is not. I have a Deconz dongle for zigbee and it is not descovered - I will try myself first and see if it can be found.
btw. Awsome work…! Lyfter hatten!
I updated to your last version and so far no more error with my usb stick zigbee2mqtt Thanks a lot !
Make sure you are running the latest version of docker, Synology had a faulty version.
At the end it helped by deinstalling/reinstalling (which also someone posted) - so if not restarting works, deinstalling might. Next step’ll be deconz.
… feels a lot faster than on the RPI too 
… now also the Conbee stick works. found it in the hardware list in Hass.io - just thought if you still need to here that reg. feedback on the latest changes.