Update waterfurnace library to 0.7, add reconnect logic

[sdague]

One of the features of the waterfurnace 0.7 is timingout out stuck
connections on the websocket (which tends to happen after 48 - 96
hours of operation). This requires the homeassistant component to
catch and reconnect under these circumstances. This has turned out to
be pretty robust in preventing stuck sockets over the last month.

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

• New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
• New dependencies are only imported inside functions that use them ([example][ex-import]).
• New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[balloob]

Do you think that this kind of logic should be moved into the waterfurnace lib as it might be useful for other users of the lib too?

[sdague]

It's possible. I get a little concerned when libraries put all their own retry logic under the cover as they may not understand a larger symptom of what is going on that they should stop.

If you want I can move it down to the lower layer.

[balloob]

Well if the lib would expose both, a raw connection and a managed connection, it could work.

I'm fine either way. You pick.

[sdague]

Oh, apparently I never hit submit on my comments. For now I'd like to merge this and get back into the mix.