Hassio Network keeps going down

I have had issues with Hassio since december. About once a day my network disconnects and does not come up until I reboot my pi. At this point I am looking at either dumping hassio and the next thing I am going to try is completely new hardware to rule that out.

My setup and what I have tried:

  • Raspberry PI 3 Model B
  • Static IP set on network
  • Ethernet Connection
  • Wifi/Bluetooth disabled in boot script
  • Latest version of hassio and core
  • Wiped and reinstalled hassio/ha from scratch and from snapshot a few times
  • Replaced SD Card
  • Sometimes my SSH connection goes down (entire host is down) and other times its just core that goes down
  • root login is extremely slow connecting via port 22222 sometimes during this broken state
  • Rebooting the PI ALWAYS fixes the issue

I get errors like the following:

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 472, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/bond/switch.py", line 72, in update
    bondState = self._bond.getDeviceState(self._deviceId)
  File "/usr/local/lib/python3.7/site-packages/bond/bond.py", line 157, in getDeviceState
    r = requests.get(url, headers=headers)
  File "/usr/local/lib/python3.7/site-packages/requests/api.py", line 76, in get
    return request('get', url, params=params, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 530, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 643, 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.0.xx', port=80): Max retries exceeded with url: /v2/devices/3420b633/state (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x6b03c390>: Failed to establish a new connection: [Errno 110] Operation timed out'))
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/urllib/request.py", line 1319, in do_open
    encode_chunked=req.has_header('Transfer-encoding'))
  File "/usr/local/lib/python3.7/http/client.py", line 1252, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/local/lib/python3.7/http/client.py", line 1298, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.7/http/client.py", line 1247, 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/http/client.py", line 938, in connect
    (self.host,self.port), self.timeout, self.source_address)
  File "/usr/local/lib/python3.7/socket.py", line 728, in create_connection
    raise err
  File "/usr/local/lib/python3.7/socket.py", line 716, in create_connection
    sock.connect(sa)
OSError: [Errno 101] Network unreachable

What sort of router are you using?

Edgerouter X

Unlikely to be that then. Do you monitor the pi’s system resources?

I just added system resource monitors to see what the issue is. My memory average is around 75% so maybe upgrading to a pi with 4GB will fix that issue. Next time it crashes I’ll see what the values are

process

It appears my processor went to 60% before it went offline again today, does anyone have any ideas?