I am experiencing errors and a sluggish/strange HA behaviour. This is showing up in my log about twice a day:
2017-09-29 07:08:10 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
File “/usr/lib/python3.4/asyncio/selector_events.py”, line 582, in _read_ready
data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host
and sometimes:
2017-09-29 14:53:37 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
File “/usr/lib/python3.4/asyncio/selector_events.py”, line 582, in _read_ready
data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out
My setup: RPI connected with wifi to my Fritzbox (which prefers to assign a specific IP to the RPI). My etc/network/interfaces:
Hi there, i was just wondering if you figured it out?
I have exactly the same errors in my log, and can’t find any solutions to this. Searched all over the forums and googled the whole net, without any luck till so far .
No - unfortunately I still have no clue at all. I plan to reinstall my whole RPi & HA in the near future. Since then: Power-cycling the system every 2-3 days…
Error/log messages being not self-explaining / specific enough (for normal users) ist still an issue with HA. But I am still a HA fan after all.
I’m having same issue too. HA continues to run but logs this error 2 or 3 times a day. Doesn’t seem to be a pattern. Also have updated to most current software.
ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
File “/usr/lib/python3.5/asyncio/selector_events.py”, line 723, in _read_ready
data = self._sock.recv(self.max_size)