core: OpenWeatherMap Integration Fails to Add Both OneCall Daily and OneCall Hourly for Same Lat/Long

atm i am using 2 instances of the integration (2nd has long / lat offset by .00000000000001 this allows me add the 2nd, but now we have weather service it would be nice to be able to just 1 integration for both Hourly and Daily.

You can create a new instance with different lat\lon, change just a fraction of a value. It’s probably will be few kms/meters away from original place, but I don’t think forecast will be dramatically different.

This repository holds the yaml files and shell script I use to create the weather data sensors and to acquire the ONE_CALL_BY_CALL data using Openweathermap’s API. https://github.com/kaijk/openweathermap/tree/main

The same API Key should work in multiple calls. Just make sure the total calls between them do not exceed the daily free call limit. You should not get a 404 using the link (with your KEY and your lat/long. I get a JSON returned. You have something wrong in the https call

Note that the REST Call creates just an openweather_report entity. That entity has attributes from the JSON return. I can post the template sensor script I use to create the entities for each weather item. But it will have to be later. Here is a sample: I have a script that builds this for multiple attributes and icons for 12 hours.

template:
  sensor:
# hourlyy Values
#  Hour0 (Note H0 in OPW is last hour. Current hour is H1. So, call shift H1 to H0, etc
    - name: 'Openweather Temp 0h'
      state: >
        {% if state_attr('sensor.openweather_report', 'hourly')[1].temp is defined %}
           {{ ( state_attr('sensor.openweather_report', 'hourly')[1].temp | float(0) ) | round(1) }}
        {% else %}
           0
        {% endif %}
      attributes:
        dt:        "{{ state_attr('sensor.openweather_report', 'hourly')[1].dt }}"
        date_time: "{{ state_attr('sensor.openweather_report', 'hourly')[1].dt | timestamp_custom('%Y-%m-%d %H:%M', true) }}"
      state_class:  measurement
      device_class: temperature
      unit_of_measurement: '°F'

I hope that the integration will be modified to allow selecting BOTH daily and hourly one-call calls, and then provide just one set of current data.

If you have an Openweather “one-call” subscription, you can get current conditions, and daily, and hourly forecasts for free if you stay below a call-frequency threshold (See Scan_Interval below).

However, the problem is that the HA integration does not support getting both one-call daily, and one-call hourly for the same LAT/LON.

As an example, Add one-call daily, and then add one-call hourly with a slightly different LAT/LON. It works. But, BOTH provide Current data so you now have both sensor.* and sensor.*_2 (e.g., two sets of current conditions) for every current condition. That is the second part of the problem I raise in this issue.

As a workaround, I call Openweather’s API using the following REST command, and I have built my own large collection of template sensors for Current, Daily, and Hourly weather data.

sensor:
  - platform: rest
    name: openweather_report
    json_attributes:
      - current
      - daily
      - hourly
      - alerts
    value_template: "{{ value_json['current']['dt'] | timestamp_custom('%Y-%m-%d %H:%M', true) }}"
    resource: https://api.openweathermap.org/data/3.0/onecall?lat=<YOUR_LAT>&lon=<YOUR_LON>&exclude=minutely&appid=<YOUR_APP_ID>&units=imperial&lang=en
    scan_interval: 3600  # This keeps the number of calls below the permitted One-Call Free Call threshold