Are you saying that I should include that script snippet in the installation part of the package?
Hi @fredrike,
thanks for your Synology hass.io package. Running great on my DS420+ for some weeks now with ever growing integrations/automations.
Since I haven’t found any notice of DSM7 in the thread so far (correct me if I’m wrong), I was wondering whether you are aware of the changes that are planned for third-party packages - notably that they will not run as root anymore? Just thought I’d let you know to possibly adapt in advance when DSM7 goes public.
Best wishes,
io
PS: I’d love to help testing on that side. Sadly, I’m only registered for the preview with my old DS414 which doesn’t support Docker.
1 Like
Trying to get my zwave stick to work on my ds415+
Looking on hass’s website I found this command
sudo docker run --restart always -d --name="homeassistant" -v /volume1/Data/hass.io/homeassistant:/config --device=/dev/ttyACM0 -e TZ=US/Pacific --net=host homeassistant/home-assistant:stable
However it seems to be trying to reinstall the docker images and complains they already exist. How do I edit the docker image for this Hass package to include the ttyACM0 device?
(also I’m just getting into testing and will be testing with some light switches, since it’s just light switched do I need to worry about the zwave network password?)
Just a warning . there is a difference in hass.io package (so called supervised version) and homeassistant Docker.
What works with one (in terms of tinkering with docker container) will probably mess-up other one.
One of the things you could try is to remove hass.io package , plug in stick in USB and then reinstall. in /coker/hass.io folder, there should be usb_devices.txt file that includes USB; if it was found successfully during this installation.
BTW - can’t help you with ZWave as I don’t have it, and Zigbee stick worked without me touching anything (even txt file is empty and it still works).
What you can do is first test if the stick is working in Synology by using terminal to ssh to Synology and check if ttyACM0 exists in /dev folder (ls -la ttyA* from terminal).
I can confirm the stick exists on synology, but it looks like it is still not appearing in usb_devices even after reinstalling the package.
Where do I find the file that controls the docker flags? My assumption is docker is not properly mounting the USB device, since it would need to be specifically specified in the configuration for docker.
What do you plan to use with the stick? Add-on or directly in HA?
I use them in Addons and this is where I add them to configuration files. Dockers are managed by system (supervisor) - if you change how they are called by hand, you risk any changes you make be deleted in future version due to new system auto-healing functionality. You can check beta version release notes.
You can use portainer to access inside container (homeassistant) - there you can also try to issue ls command from above.
Honestly, not sure of the difference :). Just starting to play with Hass now.
Was able to get it to work by adding it in as an integration, it sees it now. W00t
2 Likes
Hi @Paladin732,
it is working now for you? If the z-Wave stick is showing in synology it should normally be found inside of home assistant under supervisor/system/host System press the three dots and select hardware.
There you should find the listing either as by-id or e.g. ttyxxx
I read that by-id is then better to use because the tty’s could change…
Hope this helps if you haven’t already sorted it out yourself!
Hi,
I do not have any plans on supporting DSM7 at this moment. Have too many other projects. We’ll see what happens when DSM7 goes public and people start upgrading.
1 Like
I have the same problem as #2 mentioned in URL (in this threads) below.
https://community.home-assistant.io/t/hass-io-on-synology-dsm-native-package/125559/721
Regardless of the SMB of hass io, the domain of DMS by SMB protocol, seems to be not recognized in other devices due to the DNS of hass io
If you have a good idea about how to modify the DNS to recognize the original domain, please leave a comment.
docker version is 18.09.8-0513, the latest in Synology package Center
home assistant : 0.116.4
hass io : 20200910-2
And by that you talk about those listed errors/critical errors? They are normal - and you can ignore them. hassio package is not officially supported by Synology (and will probably never be) or Home Assistant devs.
Haven’t played with SMB but did you try addon as suggested by fredrike in post below the one you linked to?
Found the resolution to binding Node Red to port 80 on the Synology Native HA install, thanks to Avinash1919.
nginx runs on port 80 to redirect your Synology traffic to whatever port you decide in the setup… This simple change will resolve:
Edit server.mustache, DSM.mustache, WWWService.mustache located in /usr/syno/share/nginx.
String to look for:
server {
listen 80 default_server{{#reuseport}} reuseport{{/reuseport}};
listen [::]:80 default_server{{#reuseport}} reuseport{{/reuseport}};
I just moved it to port 81.
I’ve installed but I can’t access HA page.
My logs:
20-10-29 16:54:33 INFO (MainThread) [supervisor.hassos] No Home Assistant Operating System found stderr 16:54:33 20-10-29 16:54:33 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/a0d7b954 repository stderr 16:54:33 20-10-29 16:54:33 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/core repository stderr 16:54:34 20-10-29 16:54:34 INFO (MainThread) [supervisor.store] Loading add-ons from store: 66 all - 66 new - 0 remove stderr 16:54:34 20-10-29 16:54:34 INFO (MainThread) [supervisor.addons] Found 0 installed add-ons stderr 16:54:34 20-10-29 16:54:34 INFO (MainThread) [supervisor.snapshots] Found 0 snapshot files stderr 16:54:34 20-10-29 16:54:34 INFO (MainThread) [supervisor.discovery] Loaded 0 messages stderr 16:54:34 20-10-29 16:54:34 INFO (MainThread) [supervisor.ingress] Loaded 0 ingress sessions stderr 16:54:34 20-10-29 16:54:34 ERROR (MainThread) [supervisor.core] Detected unsupported OS: None stderr 16:54:34 20-10-29 16:54:34 ERROR (MainThread) [supervisor.core] NetworkManager is not correctly configured stderr 16:54:34 20-10-29 16:54:34 ERROR (MainThread) [supervisor.core] Systemd is not correctly working stderr 16:54:34 20-10-29 16:54:34 INFO (MainThread) [__main__] Running Supervisor stderr 16:54:34 20-10-29 16:54:34 WARNING (MainThread) [supervisor.core] System running in a unsupported environment! stderr 16:54:34 20-10-29 16:54:34 CRITICAL (MainThread) [supervisor.core] System running in a unhealthy state and need manual intervention! stderr 16:54:35 20-10-29 16:54:35 WARNING (MainThread) [supervisor.core] Ignoring Supervisor updates! stderr 16:54:35 20-10-29 16:54:35 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' starting 0 add-ons stderr 16:54:35 20-10-29 16:54:35 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled
@fredrike I had the system working for over a month and at one point I decided to put the fresh system, once again. After uninstalling the application and reinstalling it, the hassio_dns container starts and stops. Manual switching to “on” does not help. Do you have any idea?
I’m not sure if it’s related to this, but in the logs I see only :
Start container homeassistant failed: {"message":"Bind mount failed: '/volume1/home-assistant/hass.io/tmp/homeassistant_pulse' does not exists"}.
I just installed Hass.io on my Synology. It runs, but the hassio_dns container keeps restarting. As a result the other containers can’t resolve dns queries.
2020-10-29T23:28:15+01:00 Fuji kernel: [830950.048592] aufs au_opts_verify:1571:dockerd[11129]: dirperm1 breaks the protection by the permission bits on the lower branch
2020-10-29T23:28:15+01:00 Fuji kernel: [830950.223168] aufs au_opts_verify:1571:dockerd[11132]: dirperm1 breaks the protection by the permission bits on the lower branch
2020-10-29T23:28:21+01:00 Fuji synoscgi_SYNO.Docker.Container_1_list[24426]: container.cpp:435 success regen profile for container [hassio_dns]
2020-10-29T23:28:46+01:00 Fuji kernel: [830981.485269] aufs au_opts_verify:1571:dockerd[15691]: dirperm1 breaks the protection by the permission bits on the lower branch
2020-10-29T23:28:46+01:00 Fuji kernel: [830981.530860] aufs au_opts_verify:1571:dockerd[15691]: dirperm1 breaks the protection by the permission bits on the lower branch
2020-10-29T23:28:47+01:00 Fuji kernel: [830981.695734] aufs au_opts_verify:1571:dockerd[15691]: dirperm1 breaks the protection by the permission bits on the lower branch
2020-10-29T23:28:49+01:00 Fuji ntpd[8701]: bind(35) AF_INET6 fe80::c847:87ff:fe5f:fcf8%256#123 flags 0x11 failed: Cannot assign requested address
2020-10-29T23:28:49+01:00 Fuji ntpd[8701]: unable to create socket on dockerc4a913f (201) for fe80::c847:87ff:fe5f:fcf8%256#123
2020-10-29T23:28:49+01:00 Fuji synoscgi_SYNO.Docker.Container_1_list[25625]: container.cpp:505 Remove dummy container profile hassio_dns
2020-10-29T23:28:54+01:00 Fuji synoscgi_SYNO.Docker.Container_1_list[25725]: container.cpp:435 success regen profile for container [hassio_dns]
2020-10-29T23:29:02+01:00 Fuji SystemInfo.cgi: SystemInfo.cpp:270 get network error.
Try creating the file that is missing in the log.
This is logged in the DNS container:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
loading Caddyfile via flag: open /config/corefile: no such file or directory
[cmd] coredns exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
I would suggest you deinstall package and reinstall it. IF you have any configuration, it will be saved in homeassistant folder, so you are safe on that side.
Second option would be to stop package (hassio) and remove from Docker hassio_dns - it should recreate it when you restart (if I remember correctly).
Can you please in future paste/format log so it’s readable - this one was VERY hard to read due to bad formatting.
My suggestion would be to remove package and install it from scratch. You could try restarting it too, but not sure that it would work.
Out of curiosity, what Synology machine are you running this one?
It was fresh install. I already have installed Home Assistant on docker - can it make any problems?
DS418+