Refactor Waze Travel Time & Update Requirements

[Petro31]

Refactored Waze Travel Time to contain a data object.

Changed error retrieving data to a warning.
Added distance conversion depending on region.
Removed dependency on TRACKABLE_DOMAINS list.
Update to use WazeRouteCalculator 0.10

3rd time's a charm. Deleted fork, caused last PR to screw up. So here we are.

Breaking Change:

Description:

Related issue (if applicable): fixes #

Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#8825

Example entry for configuration.yaml (if applicable):

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.

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

• Documentation added/updated in home-assistant.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.

[Petro31]

Deleted fork because of unrelated issues. Unable to update #22226 because of the missing fork. Created this PR instead.

[MartVisser]

Any idea when this is going to be merged? This is a breaking fix right, I can't get travel times now with the waze_travel_time component.

[Petro31]

No clue. You can add it as a custom component and it will overwrite what you have.

[dennusb]

No clue. You can add it as a custom component and it will overwrite what you have.

How should i add it? custom_components/waze/sensor.py?

[Petro31]

custom_components/waze_travel_time/sensor.py

[radinsky]

any estimate to merge?

[edif30]

If all checks passed, why are there conflicts?

[Petro31]

Because this sat here for 3 months. I'm going to create a new PR sometime in the near future. At that point, I'm going to add a few new functions and I'm going to ping the devs to take a look at it. As for this PR, it looks like it has been ignored.

[balloob]

Changes look good. Thanks! 🐬