What is wrong with pi-hole?
What is UPD?
I’m currently working on a native package to get hass.io installed as a Synology application, stay tuned 
2 Likes
I get an error at pi-hole:
[cont-init.d] 31-pihole-ftl.sh: executing...
Failed to set capabilities on file `/usr/bin/pihole-FTL' (Not supported)
usage: setcap [-q] [-v] [-n <rootid>] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN> ]
Note <filename> must be a regular (non-symlink) file.
[cont-init.d] 31-pihole-ftl.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
-----------------------------------------------------------
Oops! Something went wrong.
We are so sorry, but something went terribly wrong when
starting or running this add-on.
Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
A synology package would be great!
Great progress @fredrike! I hope to try it out this weekend. Looking forward to Syno package. 
1 Like
I’m not sure what kind of error that is. It does not look like an Synology issue.
Looking forward to your release a Synology hassio docker package
And we have a package!
There are still things to tweak but this should get you started. The package is just a wrapper around the commands on gist.
I highly recommend that you create a share to store the data in (configured via the installation dialog).
3 Likes
Perfect! I am gonna try it! I will let you know!
Update:
It works perfect!
Maybe an option to add a option to add usb devices?
1 Like
What do you mean? Ain’t you able to access USB-devices? Which in particular?
FIY: For anyone still getting the blank hass.io (entrypoint.js) page after installing this package. Make sure you have “enable user home service” unchecked in your Synology settings (Control Panel -> User -> advanced tab)
It appears that having this checked will create the $DATA environment variable that the package installation scrips need to use instead. Since the variable name is already in use the scripts will fail.
Please correct me if I’m wrong about that but turning it off appears to have fixed it for me.
1 Like
I’m not using the $DATA variable. But, there is an issue with the start-up script I’m working on an updated version.
Edit: New version, hassio_x64-6.1_20190701-alpha.spk is available.
Edit2: The file have been updated and should work now.
1 Like
After uncheck “enable user home service”, hass.io menu appeared ^^. Playing with 20190628 version while waiting 20190701 get fixed.
I can’t find the config folder and configuration.yaml to apply my old setting. Please help!
Oh, sorry about that. I had a power outage so I never managed to test it before shipping.
Will try to update the latest version.
Regarding hassio access, it turns out that the hassio-container stops and I think that is the issue. I’m having a hard time to see that the user folders would affect.
How have you configured the data location when you did the installation? I highly recommend that you create a share and store the configuration (data dir) there.
1 Like
Hi, I moved everything this weekend from home assistant (with synology docker) to hassio with your package and everything works (Synology ref : DS418Play) !
Thanks a lot for your work
2 Likes
Great that it works for you (I’m actually are having some trouble to migrate my docker ha to this version for instance doesn’t auto discovery and mqtt work as expected in the spk version).
If everything is working from the 20190628 version don’t touch the updates (there seems to be some magic going on that might break when updating).
The 20190628 version can be started, but the 20190701 startup failed.
Ok let me know if you need some details of my conf.
Addons working : Configurator, Log Viewer, MQTT Server & Web Client, Node-Red, Pi-hole, Plex Media Server, SSH Server, TasmoAdmin.
I have a zigbee2mqtt container that i kept as a “classic” docker container, not integrated in hassio.
1 Like
Thanks a lot, i found it ^^ When i did the installation, only an dialog appear to ask for the path to install the package, it said: “/volume1/hass.io” and i went with that default configuration.
Everything seems working from the 20190628 version, i wonder what new in updated version?
I rewrote the startup script to make it more resistant but I didn’t have ability to test it.
That is really great! Will try to do the same.
1 Like