Openweathermap attribute info for irrigation system

Hi all,

Struggling with below quite some time. Hope somebody can really help me with it.

For my irrigation automation I’d like to know for today and tomorrow what;

the “precipitation” is
the “precipitation_probability” is

If I go to the developers tools, I can run

action: weather.get_forecasts
target:
  entity_id: weather.openweathermap
data:
  type: daily

to load all the attribute information from OWM entity. There I can see the needed information is available from OWM weather provider.

However, I cannot calculate with this information in an automation.

How can I create below sensors that only contain what I’m interested in;
1: precipitation_today (in mm)
2: precipitation_probability today (in %)
3: temperature (celsius)
4: precipitation_tomorrow (in mm)
5: precipitation_probability tomorrow (in %)
6: temperature tomorrow (celsius)

This info (sensors?) I want to use in an automation, to define if/how long I should irrigate my lawn/borders.

Thanks!

Please next time post formatted text (also for output) instead of screenshots, because we cannot copy from them. You can for instance create a template sensor like this to put the data in attributes (untested, may have small bugs). You can put this in templates.yaml:

 - trigger:
      - platform: time_pattern
        minutes: /1
    action:
      - service: weather.get_forecasts
        data:
          type: daily
        target:
          entity_id: weather.openweathermap
        response_variable: daily
    sensor:
      - name: Weather Forecast values
        unique_id: weather_forecast_values
        state: "{{ now().isoformat() }}"
        attributes:
          precipitation_0: "{{ daily['weather.openweathermap'].forecast[0].precipitation }}"
          precipitation_1: "{{ daily['weather.openweathermap'].forecast[1].precipitation }}"

from it you can guess the other attributes. I set it to get the info every minute because you have to wayt that long to get the first results. When it works, increase the time because the numbers won’t change this fast.

Or you can use a pre built integration to do the heavy lifting for you: