Add new integration here_weather

[eifinger]

Proposed change

Add a new integration using the HERE Destination Weather API to provide weather and sensor entities.

The integration provides the following four modes:

• Astronomy: Sunrise, Sunset and Moonphase
• Hourly: Weather forecast in an hourly format
• Daily: Weather forecast in a dailyformat
• Daily Simple: Like Daily but with high/low temp, UV-index and pressure
• Observation: Detailed precipitation for the next 24h

All sensors and all weather entities but the Daily Simple are disabled by default.
The information is refreshed every 300s or less if the number of active integrations is too high. This way it is automatically made sure that the free limit of 250k request per month ist not exceeded.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Add integration here_weather home-assistant.io#11261

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

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

• Documentation added/updated for www.home-assistant.io

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

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[arsaboo]

@eifinger Does this also obtain the moon data (moonrise and set times)? Here is one of the few providers that provide this information. I think the herepy library provides that information.

[eifinger]

@arsaboo with the following config:

sensor:
- platform: here_weather
  name: Home
  app_id: "<APP_ID>"
  app_code: "<APP_CODE>"
  mode: forecast_astronomy

you will get the following sensors:

"sunrise": {"name": "Sunrise", "unit_of_measurement": None},
 "sunset": {"name": "Sunset", "unit_of_measurement": None},
"moonrise": {"name": "Moonrise", "unit_of_measurement": None},
"moonset": {"name": "Moonset", "unit_of_measurement": None},
"moonPhase": {"name": "Moon Phase", "unit_of_measurement": "%"},
"moonPhaseDesc": {"name": "Moon Phase Description", "unit_of_measurement": None},
"city": {"name": "City", "unit_of_measurement": None},
"latitude": {"name": "Latitude", "unit_of_measurement": None},
"longitude": {"name": "Longitude", "unit_of_measurement": None},
"utcTime": {"name": "Sunrise", "unit_of_measurement": "timestamp"}

[arsaboo]

Does it include the forecast information as well? We can have today's value as the value of the sensor and forecast as attributes.

[eifinger]

The current implementation (which I am not all too happy with) creates a sensor for each information (e.g. moonrise). If you want to have the information for a specific point in the future you can also define offset: <DAYS> to get the information up to 7 days in the future.

Currently this means if you want to have the information for today and the information for 7 days in the future you would have to have the following config:

sensor:
- platform: here_weather
  name: Home
  app_id: "<APP_ID>"
  app_code: "<APP_CODE>"
  mode: forecast_astronomy
- platform: here_weather
  name: Home in 7 days
  app_id: "<APP_ID>"
  app_code: "<APP_CODE>"
  mode: forecast_astronomy
  offset: 7

I as I have said I am gladly taking ideas on how to to this differently.

[arsaboo]

I created a custom sensor just for the moon data. It creates one sensor with the state as the current moon phase and all the forecast information in attributes.

I don't want to pollute this PR with all the feature request discussion. I am discord (arsaboo) if you want to discuss it there.

[eifinger]

Still open

[eifinger]

...

[MartinHjelmare]

Will this integration use the same api key as here_travel_time? If that's the case, I still think it's a really bad idea to add a new integration that uses the same connection credentials and api limits etc as an existing integration.

[eifinger]

Yes, it uses same API keys and request limits. The HERE API does not differentiate between them

[eifinger]

As this PR is now open for nearly 2 years (I think the all time record 😅) and a lot of people spent a lot of time and effort on it I am currently debating whether it would be best for all if I close the PR and publish this integration as a custom component. This way we avoid spending even more time.

@MartinHjelmare you spent the most time with me on this PR what do you think?

[MartinHjelmare]

The main problem is that this new integration would share api key and api limits with another integration. I don't think we should do that.

A custom integration is a good alternative until we have a solution for the above problem, I think.

Thanks for your work and contributions! 👍