Update Neato Library And Reduce Cloud Calls

[dshokouhi]

Description:

This PR updates the pybotvac library to the latest version and also reduces the amount of calls being sent to Neato's servers. Previously the robot would update every second, the robot map every 10 and the vacuum/switch entities were set to the default. Now everything is set to update once a minute.

I have tested these changes locally and can confirm a significant drop in the amount of calls being made. Previously there would be more than 50,000 calls a day being made. With these changes that number drops drastically, well below 10,000 a day. This cuts down on most if not all time out and gateway errors that user are experiencing. The only side effect to the change is that the vacuum toggle may be a bit slower to update than before but it will update.

Pi-Hole long term stats to show that the calls were reduced immediately:

Related issue (if applicable): fixes #

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>

Example entry for configuration.yaml (if applicable):

neato:
  username: user
  password: pass

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).
• New dependencies are only imported inside functions that use them (example).
• 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.

[homeassistant]

Hi @dshokouhi,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[Kane610]

Looks good!

[balloob]

That's a crazy amount of calls . Even 10k is a lot. Can we reduce it even more ?

[dshokouhi]

@balloob I will look into that, the camera and switch could probably cut down more on the scanning since the vacuum is probably the most important part :) . I'll do some testing locally and cut down the calls to be more reasonable.

[balloob]

We haven't done it before in Home Assistant, but I wonder if we should explore increasing polling frequency when the vacuum is in use versus when not.

[dshokouhi]

That would be ideal because then we can also update the map only when it needs to be, just after it was in use. There is no need to update the map if there has been no activity on the vacuum. The image is not going to change.