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.
Did you ever get node-red to start? I am getting “bad gateway”… but haven’t done any longer error checking. just if you found a solution?
Yes, NodeRED works fine. Just make sure to disable ssl and set secret credential_secret
Ex.
{
"credential_secret": "123",
"dark_mode": false,
"http_node": {
"username": "",
"password": ""
},
"http_static": {
"username": "",
"password": ""
},
"ssl": false,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"require_ssl": true,
"system_packages": [],
"npm_packages": [],
"init_commands": []
}
1 Like
I was to early with the conbee - it seems not to be working. I can go into the phoscon app and that works. It has been difficult in the past to add lights etc. but now it is not working at all.
I then saw that the phoscon app shows “firmware not connected” and I have tried to reset but also that does not work.
Checking the usbdevices.txt file only shows the Z-Wave dongle but under Hassio/system/hardware I found the other… or at least thought so.
Has anyone gotten conbee to work with this setup? Zwave is working fine!
I get zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state in regular time intervals. Also checked the deCONZ - Official thread. Now I am not clear if it is an issue here, i.e. that the USB is not found properly, if it is conbee/deconz.
… after some checking around I found the following workaround:
sudo insmod /lib/modules/usbserial.ko
sudo insmod /lib/modules/ftdi_sio.ko
Running those and restarting deconz container made my conbee show up also. If I have understood it correctly - I need to run that after every newstart of Synology or?
It is safe to say that … I don’t know what I did or why it is working, thought you might understand 
Thanks!
Great!
Insmod is loading drivers mut it is quite strange that Synology does not load this automatically.
I’m ready to try this to replace my daily driver (Docker on Synology). Can I just turn off my HASS docker container and install the package and it should work? Can I still manage my other (not related to HASS) containers from Synology DSM?
Hi. I’m new to the thread but I’ve been using and very much enjoying the hassio package you created for the past few months. Thanks for all your hard work on that.
I got it working perfectly with Deconz and dongle on an Xpenology baremetal setup. Even hassio updates were working until a few weeks ago when an update failed.
Since then I can’t get the Hassio screen. I’ve been through the fixes described in this thread and from searching online. I was wondering if anyone had any ideas? The Hassio_supervisor is running as is home assistant container, but the only log entry I get is the following.
2019-09-28 03:12:53 ERROR (MainThread) [homeassistant.components.hassio] Missing HASSIO environment variable.
No matter what I seem to do, including a full wipe and reinstall, nothing works. Can anyone give me a hint at what to look for?
It is working for now. It Will be intersting if by the next update my synology does it Will stop working.
Running on docker is working like a charm othervice!
@fredrike is it possible to update hassio as normal once this package is installed?
Also looking to install pihole on here. Is it possible, currently getting the error:
dnsmasq: cannot read /etc/dnsmasq.d//01-pihole.conf: Permission denied
It sounds like it is the Synology Docker issue. Make sure that you are not running the August version.
Yes the only way is the normal way. The package gives full hass.io experience.
I’ve been testing the piehole addon and it works fine. I’m not sure what you are doing to get that error message.
I confirm. All add-ons work fine with this package, including pihole.
Thanks I will have a bit more of a play with it to see if I can find out the issue.
- Out of interest for uninstallation of this, would it be remove the package
- remove any remaining docker containers (docker rm)
- remove any relating docker networks (docker network rm)
Then done? Are there any files which need to be removed for example if I want to fresh install? If so where are they located?
Thanks
So I suppose the missing HASSIO environment varialble isn’t something that can just be typed in, is it? I am using the July version… only thing left is to move my config to a different folder and see if a fresh install with no config works…
Read the last 20 posts or so in this topic. You have the broken Docker package that Synology released in August, down- or upgrade it it will work.
I’m planning to move from my hassio from a RPi2 to buying a Synology. Could I then install this package and then restore from my full snapshot?
