I’m trying to move a hass.io install from an Ubuntu with Docker setup over to my Synology. I have the package from this thread, should I be downgrading the Synology Docker package to the 17.x version rather than the 18.x version for the Hass.io package from 20191006 to work correctly?
No, the latest Docker version for Synology works fine.
1 Like
There have been a discussion wlth this earlier in this thread…
It would really be interesting to see what is confusing DSM (but honestly I think they have a bug due to new interfaces caused by the docker instance).
It should be reproducable by just creating a docker network (as that is more or less the only thing I’ve found that hassio-supervisor does). Perhaps you need to set iptables and routing as I’ve shown in the gist (also earlier in this post) too.
Hello all,
I just installed hassio_x64-6.1_20191006-3c5c9bce.spk on my fully updated 1019+, DSM 6.2.2-24922 Update 4 and Docker 18.09.0-0506 and I’m getting several errors in HA on first startup. I’ve read the whole thread and maybe I missed something but I thought I should be fine with this version of Docker.
2019-12-05 15:42:55 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 830, in _resolve_host
self._resolver.resolve(host, port, family=self._family)
File "/usr/local/lib/python3.7/site-packages/aiohttp/resolver.py", line 30, in resolve
host, port, type=socket.SOCK_STREAM, family=family)
File "uvloop/loop.pyx", line 1469, in getaddrinfo
socket.gaierror: [Errno -3] Try again
2019-12-05 15:42:59 WARNING (MainThread) [homeassistant.setup] Setup of hassio is taking over 10 seconds.
2019-12-05 15:43:04 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/ping request
2019-12-05 15:43:04 WARNING (MainThread) [homeassistant.components.hassio] Not connected with Hass.io / system to busy!
2019-12-05 15:43:14 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /homeassistant/options request
2019-12-05 15:43:24 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/options request
2019-12-05 15:43:34 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /homeassistant/info request
2019-12-05 15:43:34 WARNING (MainThread) [homeassistant.components.hassio] Can't read last version:
2019-12-05 15:43:44 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /ingress/panels request
2019-12-05 15:43:44 ERROR (MainThread) [homeassistant.components.hassio.addon_panel] Can't read panel info:
2019-12-05 15:43:54 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /discovery request
2019-12-05 15:43:54 ERROR (MainThread) [homeassistant.components.hassio.discovery] Can't read discover info:
2019-12-05 15:48:49 ERROR (MainThread) [metno] https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/1.9/ returned Cannot connect to host aa015h6buqvih86i1.api.met.no:443 ssl:None [Try again]
Try to restart the package, it looks like network issues that might work better after a restart (of the package).
Ok, I have raised the ticket in Synology. They asked me few things, I’ve provided some logs along with remote support to my NAS. Most recent reply from them is:
Dear Customer,
thank you for your feedback.
At the moment your case is in our development. I will contact you if I have any news.
Lets hope that we will some fix for that issue in a next update 
I will keep you informed.
1 Like
Ended up having to restart the NAS but after that all is working. Thanks.
hello everyone, what version should i use ? Home Assistant from Docker ? Or Hass.io as native package?
It seems like on home assistant i cannot install addons like configurator/editor
Does anyone else have the issue where the hassio_supervisor crashes and restarts every 5 minutes? At this point, it’s becoming more than a nuisance. Any work that I’m doing with Hassio addons breaks every 5 minutes while the supervisor crashes and restarts.
Is there a way that I can configure hassio_supervisor into debug or trace mode to see if its logging any errors when it crashes?
19-12-08 00:24:42 INFO (MainThread) [hassio.core] Hass.io is up and running
19-12-08 00:24:42 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-12-08 00:24:42 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-12-08 00:24:42 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
19-12-08 00:24:42 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request running
19-12-08 00:28:53 INFO (MainThread) [__main__] Stopping Hass.io
19-12-08 00:28:53 INFO (MainThread) [hassio.misc.forwarder] Stop DNS forwarding
19-12-08 00:28:53 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API error: Received message 257:None is not str
19-12-08 00:28:53 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API connection is closed
19-12-08 00:28:53 INFO (MainThread) [hassio.api] Stop API on 172.30.32.2
19-12-08 00:28:53 INFO (MainThread) [hassio.core] Hass.io is down
19-12-08 00:28:53 INFO (MainThread) [__main__] Close Hass.io
Hey Fredrik,
thank you so much for your efforts!
The installation was working flawlessly on my nas!
The only concern I have is about hibernation…
Is it true that this package prevents the synology from switching to hibernation or is it just my configuration?
Hey @fredrike!
Please see what Synology replied to me:
Dear Customer,
thank you for your request.
After consulting with our development department, this is a docker problem.
Here is a forum entry from Docker.
https://github.com/docker/for-linux/issues/123
Actually I was unable to confirm their findings, as the issue solution in mentioned Docker issue is to add a bridge docker network, which we already have in Synology box. Maybe I’m missing something? If you could dig into this and confirm or not their theory, so I could get back to them.
I think you need to raise the issue again. It is not a Docker issue, Docker works fine. It is a Synology DSM issue (everything else works fine).
I’ll try to update this post with the commands that the hassio-supervisor issues when creating the hassio network.
But, I don’t have a box to fully test this myself so I can’t guarantee anything. (My NAS is in “production” running hassio)
Edit
This is the code that creates the docker network. https://github.com/home-assistant/hassio/blob/dev/hassio/docker/network.py#L66
return self.docker.networks.create(
DOCKER_NETWORK,
driver="bridge",
ipam=ipam_config,
enable_ipv6=False,
options={"com.docker.network.bridge.name": DOCKER_NETWORK},
)
Ok, so I’m trying to use z-wave stick with my home assistant but I’m having an issue seeing the z-wave stick but when I go to hass.io–>System–>Hardware I do see the USB “/dev/ttyACM0” but when I add that in the z-wave integration it doesn’t look like it works. On the other hand zigbee stick works perfectly that is connected on /dev/ttyACM1
Nothing shows in Z-Wave nodes.
Z-wave Stick: Zooz Z-Wave Plus S2 USB
Thank you,
Try using the serial/by-id device instead.
Perhaps you need to install the serial USB drivers linked to above.
If you are writing to a disk it will not go to sleep… I’m not sure how you can set up the system to allow it to hibernate.
I tried serial/by-id device the same issue. How can I find a serial USB driver download link
I have to run more tests. I have 2nd Synology Box without hassio package.
And I can tell that creating a Docker network with the same parameters as the hassio network on my 1st box results in no issues with the VPN package at all. So there must be something else what is causing this.
Ok i installed the serial USB driver on the Synology but i still can’t get it working. This is the log in OZW_Log.tx in homeassistant
2019-12-09 14:20:25.348 Always, OpenZwave Version 1.4.3440 Starting Up
2019-12-09 14:20:27.361 Info, Setting Up Provided Network Key for Secure Communications
2019-12-09 14:20:27.361 Info, mgr, Added driver for controller /dev/ttyACM0
2019-12-09 14:20:27.361 Info, Opening controller /dev/ttyACM0
2019-12-09 14:20:27.361 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
2019-12-09 14:20:27.361 Info, Serial port /dev/ttyACM0 opened (attempt 1)
2019-12-09 14:20:27.361 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-12-09 14:20:27.361 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-12-09 14:20:27.361 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-12-09 14:20:27.361 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-12-09 14:20:27.361 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-12-09 14:20:27.361 Detail,
2019-12-09 14:20:27.361 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-12-09 14:20:28.361 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-09 14:20:28.361 Detail, contrlr, Removing current message
2019-12-09 14:20:28.361 Detail, contrlr, Notification: Notification - TimeOut
2019-12-09 14:20:28.361 Detail,
2019-12-09 14:20:28.361 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-12-09 14:20:29.361 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-09 14:20:29.362 Detail, contrlr, Removing current message
2019-12-09 14:20:29.362 Detail, contrlr, Notification: Notification - TimeOut
2019-12-09 14:20:29.362 Detail,
2019-12-09 14:20:29.362 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-12-09 14:20:30.362 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-09 14:20:30.362 Detail, contrlr, Removing current message
2019-12-09 14:20:30.362 Detail, contrlr, Notification: Notification - TimeOut
2019-12-09 14:20:30.362 Detail,
2019-12-09 14:20:30.362 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-12-09 14:20:31.362 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-09 14:20:31.362 Detail, contrlr, Removing current message
2019-12-09 14:20:31.362 Detail, contrlr, Notification: Notification - TimeOut
2019-12-09 14:20:31.362 Detail,
2019-12-09 14:20:31.362 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-12-09 14:20:32.362 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-09 14:20:32.362 Detail, contrlr, Removing current message
2019-12-09 14:20:32.362 Detail, contrlr, Notification: Notification - TimeOut
Ok, so I got it working!
I have noticed that in the network configuration of hassio is a check whenever a Hassio network already exist. https://github.com/home-assistant/hassio/blob/fc5d97562f1abd028295542e602f04f9ce055dce/hassio/docker/network.py#L52
"""Get HassIO network."""
try:
return self.docker.networks.get(DOCKER_NETWORK)
except docker.errors.NotFound:
_LOGGER.info("Can't find Hass.io network, create new network")
I thought that it should be possible to create the network manually first, and then install the package.
So first I have uninstalled the hassio package.
To fully restore the VPN package functionality i had to reboot Synology
Then I have created a Docker network from GUI (with the same parameters which hassio uses):
Network Name: hassio
Subnet: 172.30.32.0/23
IP range: 172.30.32.0/24
Gateway: 172.30.32.1
Enable IPv6: unchecked
Disable IP Masquerade: unchecked
Installed the hassio package and no issues observed!
VPN package working, all network interfaces are displayed correctly.
And If I recall correctly, when I have first installed the hassio some time ago i had some issues with restart-loop of hassio_dns containter and also that DNSes were unable to resolve names in hassio containers (i had to manually adjust the resolv.conf).
And now all these issues are gone.
1 Like
Great find!
It would be interesting to see what the supervisor does differently than the DSM interface then. I think you must raise and ask Synology for this. I don’t have deep insight on what the supervisor does to create the hassio network (the corresponding docker-cli commands) but perhaps @pvizeli can help with that.
I had some issues that the routing to the hassio network didn’t work so the package adds routing manually perhaps that also could be a reason for this issue.
I really need an extra box to test this things on…