"No route to host" when hub is lost

[echoromeo]

I get this error message when testing overnight in Home Assistant.
I guess this happens when the hub restarts:
Catch this exception as well?

Log Details (ERROR)
Sun Jun 17 2018 23:19:57 GMT+0200 (Central European Summer Time)

Unhandeled exception: [Errno 113] No route to host
Traceback (most recent call last):
  File "/config/custom_components/climate/nobo_hub.py", line 536, in socket_receive
    resp = self.get_response(True)
  File "/config/custom_components/climate/nobo_hub.py", line 507, in get_response
    response += self.client.recv(bufsize)
OSError: [Errno 113] No route to host

[capelevy]

We need to catch some sort of OSError, maybe handle the network exception here:

pynobo/nobo.py

Line 397 in e6e5786

except Exception as e:

I guess this is a retry'able error :)

[capelevy]

@echoromeo, I have rewritten the reconnect logic a bit, and started catching the OSError you were seeing. I cannot reproduce the "No route to host" by playing with network connections, could you check the dev_better_reconnect_stability branch, and see if that solves the problem?

[echoromeo]

@capelevy nice! will do

[echoromeo]

Unfortunately I still get the same "No route to host". It looks like I will have to set up the dev environment and get some more detailed debug output.