Connection Problem

Hello. I thank you in advance for your help.
I am using HA from 4 month on a synology NAS in a docker container.
The installation work fine until yesterday.
After trying to set up te HomeKit lines in my configuration yalm and trying to remove the HomeKit bridge following the advice on that page ( https://www.home-assistant.io/integrations/homekit/#supported-components) from now i can not acces to the HA home page anymore.
The error is unable to access to the server.
My usual url is 192.168.2.200:8123.
I already delete the container and create a new with the old config yalm.
Regarding the log file, the container is running (see screenshots)
i also restart the NAS itself.
Any ideas to resolve this problem.

!

I thank you in advance.

Next time please post the logs directly in here and press the button “</>” on the top to format it correclty, instead of posting a picture. Is it correct that you are able to login via ssh to get this logs but you are not able to acccess the frontend anymore?

I am accessing to the log via File station in the DSM of the synology.
For security reason, the ssh is not open but if for problem solving, it is needed, i can reopen the ssh on the NAS.

So you don’t trust your internal LAN?

Yes my lan is supposed to be safe. I am just following the Synology security recommandations :slight_smile:

Are there more errors before the first line you posted? For me it looks like your NAS can’t connect to other devices on your network, because you get errors from connecting to different hubs. Do you have a backup you can use? Just deleting the container and reloading the old configuration, will still leave the db and everything if you configured a persisten volume.

@Burningstone
here is the complete log

2019-11-18 09:02:41 ERROR (MainThread) [homeassistant.components.hue] Error connecting to the Hue bridge at 192.168.2.29
2019-11-18 09:02:42 WARNING (MainThread) [homeassistant.config_entries] Config entry for hue not ready yet. Retrying in 5 seconds.
2019-11-18 09:02:48 WARNING (MainThread) [homeassistant.setup] Setup of person is taking over 10 seconds.
2019-11-18 09:02:54 WARNING (MainThread) [homeassistant.components.weather] Setup of platform met is taking over 10 seconds.
2019-11-18 09:02:58 WARNING (MainThread) [homeassistant.components.media_player] Setup of platform yamaha is taking over 10 seconds.
2019-11-18 09:03:11 ERROR (MainThread) [homeassistant.components.plex] Plex server could not be reached: http://192.168.2.200:32400
2019-11-18 09:03:11 ERROR (MainThread) [homeassistant.components.plex] Plex server (http://192.168.2.200:32400) could not be reached: [HTTPConnectionPool(host='192.168.2.200', port=32400): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f88bbeadad0>, 'Connection to 192.168.2.200 timed out. (connect timeout=30)'))]
2019-11-18 09:03:48 ERROR (MainThread) [homeassistant.components.media_player] Setup of platform yamaha is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2019-11-18 09:03:51 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 09:04:22 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 09:04:52 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 09:04:55 ERROR (SyncWorker_18) [rxv] Failed to fetch http://192.168.2.168:80/YamahaRemoteControl/desc.xml
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 157, in _new_conn
    (self._dns_host, self.port), self.timeout, **extra_kw
  File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 84, in create_connection
    raise err
  File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 74, in create_connection
    sock.connect(sa)
TimeoutError: [Errno 110] Operation timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen
    chunked=chunked,
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 387, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/local/lib/python3.7/http/client.py", line 1244, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/local/lib/python3.7/http/client.py", line 1290, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.7/http/client.py", line 1239, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.7/http/client.py", line 1026, in _send_output
    self.send(msg)
  File "/usr/local/lib/python3.7/http/client.py", line 966, in send
    self.connect()
  File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 184, in connect
    conn = self._new_conn()
  File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 169, in _new_conn
    self, "Failed to establish a new connection: %s" % e
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f88bb597f90>: Failed to establish a new connection: [Errno 110] Operation timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 720, in urlopen
    method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
  File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 436, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.168.2.168', port=80): Max retries exceeded with url: /YamahaRemoteControl/desc.xml (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f88bb597f90>: Failed to establish a new connection: [Errno 110] Operation timed out'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/rxv/rxv.py", line 108, in _discover_features
    desc_xml = self._session.get(self.unit_desc_url).content
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 546, in get
    return self.request('GET', url, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 646, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 516, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='192.168.2.168', port=80): Max retries exceeded with url: /YamahaRemoteControl/desc.xml (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f88bb597f90>: Failed to establish a new connection: [Errno 110] Operation timed out'))
2019-11-18 09:04:55 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 157, in _new_conn
    (self._dns_host, self.port), self.timeout, **extra_kw
  File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 84, in create_connection
    raise err
  File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 74, in create_connection
    sock.connect(sa)
TimeoutError: [Errno 110] Operation timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen
    chunked=chunked,
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 387, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/local/lib/python3.7/http/client.py", line 1244, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/local/lib/python3.7/http/client.py", line 1290, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.7/http/client.py", line 1239, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.7/http/client.py", line 1026, in _send_output
    self.send(msg)
  File "/usr/local/lib/python3.7/http/client.py", line 966, in send
    self.connect()
  File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 184, in connect
    conn = self._new_conn()
  File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 169, in _new_conn
    self, "Failed to establish a new connection: %s" % e
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f88bb597f90>: Failed to establish a new connection: [Errno 110] Operation timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 720, in urlopen
    method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
  File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 436, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.168.2.168', port=80): Max retries exceeded with url: /YamahaRemoteControl/desc.xml (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f88bb597f90>: Failed to establish a new connection: [Errno 110] Operation timed out'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/yamaha/media_player.py", line 118, in setup_platform
    receivers = rxv.RXV(ctrl_url, name).zone_controllers()
  File "/usr/local/lib/python3.7/site-packages/rxv/rxv.py", line 103, in __init__
    self._discover_features()
  File "/usr/local/lib/python3.7/site-packages/rxv/rxv.py", line 108, in _discover_features
    desc_xml = self._session.get(self.unit_desc_url).content
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 546, in get
    return self.request('GET', url, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 646, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 516, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='192.168.2.168', port=80): Max retries exceeded with url: /YamahaRemoteControl/desc.xml (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f88bb597f90>: Failed to establish a new connection: [Errno 110] Operation timed out'))
2019-11-18 09:05:23 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 09:08:28 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 09:23:54 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 09:54:50 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 10:25:44 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 10:56:41 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 11:27:32 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 11:58:28 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 12:29:22 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 13:00:13 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 13:31:06 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}
2019-11-18 14:02:03 ERROR (MainThread) [pysma] Could not start session, Could not connect to SMA at http://192.168.2.44 (timeout), got {'err': 'Could not connect to SMA at http://192.168.2.44 (timeout)'}

Concerning the sma and the yamaha receiver. This is normal, there are not online for the moment.
as i mentioned, i already tried to remplace the old container with a new one.

The last thing i did before it cease working was the introduction of these line in my configuration.yalm.
`logger:
  default: warning
  logs:
    homeassistant.components.homekit: debug
    pyhap: debug

homekit:
  filter:
    include_entities:
      - demo.demo`
I already remove these lines from my config file but still autistic. :slight_smile: 

Are you able to ping the hue bridge and the other devices from your home assistant instance?

What do you call an instance?
The hue bridge is well connected and before this garbage, all the hue devices where well recognised.

Can you ping the hue bridge from the home assistant docker container?

How can i do that.
I am really not useful with ssh commands.
The rare times i was using it was as sudo user.
I don’t know how to ping FROM the container.

Start from scratch.
Well, start with default config and make that run.

Once default is running, you may add back groups of integration configs to that.

The presumption is you either have extra [Space], incorrect spacing or other wrong. It is best to remove all others issues and get back to good state before move forward.

I not have synlogy in a while but there are many network settings outside docker to allow outside connect on LAN to application. Must verify you not mess these up. If running, I believe the docker monitor for Synology show some cpu use for HA docker container. This can help determine running vs network not allowed

1 Like

I already tried with a single config file as that # Configure a default setup of Home Assistant (frontend, api, etc) default_config:
and the problem remains the same.

Then your NAS or your Docker containers cannot talk to the network properly.

Ssh into your NAS, then enter
ping xxx.xxx.xxx.xxx

Well that won’t get anywhere. :smiley:

ping 192.168.2.200
If that works,
ping 192.168.2.1
If that works,
ping 1.1.1.1
If that works, the NAS can see itself at the LAN IP, the gateway (assuming your gateway is 192.168.2.1), and it can see the internet.

I am actually wondering if the problem is just a bad configuration yaml, and what you are seeing is actually not the problem.

i made a ping
but the command continue endlessly
here is the resultNasadmin@NAS:~$ sudo -i Password: root@NAS:~# ping 192.168.2.29 PING 192.168.2.29 (192.168.2.29) 56(84) bytes of data. 64 bytes from 192.168.2.29: icmp_seq=1 ttl=64 time=0.327 ms 64 bytes from 192.168.2.29: icmp_seq=2 ttl=64 time=0.273 ms 64 bytes from 192.168.2.29: icmp_seq=3 ttl=64 time=0.266 ms 64 bytes from 192.168.2.29: icmp_seq=4 ttl=64 time=0.268 ms 64 bytes from 192.168.2.29: icmp_seq=5 ttl=64 time=0.252 ms 64 bytes from 192.168.2.29: icmp_seq=6 ttl=64 time=0.268 ms

Ctrl+C will kill the continuous ping.

Press CTRL + C to abort the command.

I’m not really an expert in networking (as you may have realised already from my posts). Why doesn’t this get anywhere? Do you mean because I wrote xxx.xxx.xxx.xxx or because this will not help with the problem?