No, that sounds strange. Try restarting the hassio package a few times it usually helps.
Is Lets encrypt and configurator broken?
can’t install, just loading…
Yes that works fine, i copy the most of the elements from my pervious HomeAsssitant and there every work fine.
What a great initiative! Since I started with HA in DSM Docker I dreamt of hass.io. Seems now this becomes possible! A big thank you to @fredrike and I keep fingers crossed this won’t be dropped in the future and will become developed as a community project to make it evolve with HA and DSM updates and make it ‘resistant’ to changes of the 3rd party software it relies on (hass.io, DSM, Docker etc). Perhaps even HA devs will support the project. I think Synology is popular enough to deserve such an official support. Not everyone likes RPi or wants to have one running in parallel with a Synology runnning 24/7…
I’ll wait until it becomes more stable without the need of restarting the package to fix some unknown issues (I know magic issues happen, but when the solution is to restart it means the bug is still there somewhere and is waiting to be tracker down) and until it supports Docker 18 (or DSM will correct it).
Anyway - again great job and I’m really hoping it will stay maintained and will get better and better in time.
Have you considered putting the package in some more ‘user friendly’ / more visible space like synocommunity.com or others? We could then install it directly from DSM without downloading and uploading to DSM.
Cheers!
1 Like
Thank you for the kind words.
I would say that it is “as stable as it gets”. There are issues with USB-devices but I’m still waiting for feedback on the latest implementation. I might be able to detect if the connection between hass.io and home-assistant is broken but I’ve not prioritized it as it is more an admin issue (afak the hass.io is only used to manage homeassistant so if the connection is broken it won’t really affect the user experience for normal use).
When it comes to support from the developers, I have close discussions with the lead developers of hass.io and as the package is currently implemented it will support further updates.
The current issue with Docker 18, is due the the fact that Synology skrewed up Docker compose. There will no further attempt to fix hass.io but instead are hopeful that Synology will release a fix soon.
There is a pr for synocommunity but there have not been much activity from the reviewers.
No, I don’t think it is broken but you probably have other services running on the default ports. What does the logs say?
Strange, have you tried adding Google Assistant from scratch. It could be some old config or cached info.
Perhaps the nabu-casa configuration option will work better.
Few days ago my RPi hassio died… I had hard time to reanimate, no success… most likely SD card failed. Since I had to do somethng quickly I jumped into Synology package and after few hours only I have everything up and running, with full configuration restored from old installation snapshot. I started instantly with Docker 17 and latest hassio package and over process have absolutely no issues (well, a bit of digging how to configure zwave stick 
) !
GRAT WORK @FREDERIK!!! Thanks so much for your effort!
1 Like
I have been excited to try this and today was the day. Sadly I can’t install docker on my diskstation because is has an arm processor. Tried to search and see if there was any way around this, but haven’t been able to find anything. Anyone know of anything I can do?
I’m very new to all this (NAS / HA / Hassio). Little experience coding - but taking a stab.
Managed to install this package and run HA - The hassio menu appeared, but when I click on it I get a blank screen. Few minutes later an error message “Unable to load the Panel Source: /Api/hassio/app/entrypoint.js”
What I’m missing? What has not worked? What do I need to do?
Help!
Read the discussions on this thread.
I could give a try to test with my usb device (zigbee2mqtt). I am still using your first version of the package. Could you reshare the link to the version potentially solving usb problems and i will try it this week-end and keep you updated.
Thanks again
Thanks Fredrik, end solution was to restart it…
1 Like
Hi,
I’ve migrated from a VM with Debian 9 / hass.io to this package (with docker 17) last weekend.
I’ve tested it this week and it works fine so far.
Also i am using zigbee2mqtt, which works flawlessly.
I faced some problems:
- (known bug) sometimes i have to restart the DSM hass.io package because of the entrypoint.js bug.
- (bug) some USB2Serial Connectors like FTDI, arduino, esp8266 etc. are not working (esphomeyaml) (Containers wont start)
- (faq) To run zigbee2mqtt and get a serial device I’ve had to install this package: http://www.jadahl.com/drivers_6.2/ to enable the kernel modules.
@fredrike Thank you again, now i can delete the VM
@fredrike I have space to share for hyperbackup, PM me
How to handle SMB sharing?
Basically the package works for me flawlesly from hassio perspective, though I found one confusing issue… I have SMB file sharing enabled on my Synology - it is feeding my movies library on Apple TV/Infuse. Then I have SMB add-on enabled within hassio in docker… That means 2 SMB servers running on the same IP. Now I see different behavior depending on system that connects to… Some systems (OS X) have no issues with this setup and do see hassio configuration folder just like another folder shared on Synology. Windows system, contrary, only see folder shared via add-on from inside hassio container, no access whatsoever to folders shared by Synology. Same result when tested with Kodi on Android TV. How do you guys handle this? Any option to have this working like from OSX, so all folders are visible to all systems?
i’m using the DSM built-in samba server
anyone got the WireGuard Addon running? it’s not starting on my system
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”)
You have to update HASSOS.
In the hassio tab, system and then click at update/upgrade at the part of Host system.
After a reboot you can run Wireguard.
1 Like
It’s really long days (leaving home 5.50 and coming back at 19.40 or so) so sorry for my late replies and low activities lately.
Just above #112, I do have some ideas of improving it further but AFIK the 20190813-6dd0666c version works quite well…
Is that with the 20190813-6dd0666c version?
Thanks! I’ll add that to the info page.