Get minute forecast

Use this action to get a minute-by-minute precipitation forecast for the next hour, for example to decide whether to start the garden sprinklers or to send yourself a heads-up before rain arrives. It returns the forecasted rain or snow for each of the next 60 minutes as response data.

Using this action from the user interface

If you prefer building automations and scripts visually, Home Assistant walks you through this action step by step. You pick what to target, tweak a few options, and save. No YAML knowledge required.

To get a minute forecast from an automation or a script:

1. Go to Settings > Automations & scenes.
2. Open an existing automation or script, or select Create automation > Create new automation.
3. If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
4. In the Then do section, select Add action.
5. From the search box, search for and select OpenWeatherMap: Get minute forecast.
6. Select the OpenWeatherMap weather entity you want the forecast for.
7. In the Response variable field, enter a name to store the data in, such as weather_forecast.
8. Select Save.

Options in the UI

This action has no options beyond the target.

Using this action in YAML

If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required.

In YAML, refer to this action as openweathermap.get_minute_forecast. Because it returns data, you store the result in a response variable. A basic example looks like this:

action: openweathermap.get_minute_forecast
target:
  entity_id: weather.openweathermap
response_variable: weather_forecast

Options in YAML

This action has no options beyond the target.

Targets of the action

This action requires a target. The target is the object of the action. You can point the action at a single entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more], a device, an area, a floor, or a label, and Home Assistant will run the action on every matching weather entity behind that target.

• Entity: one specific weather entity, such as weather.living_room.
• Device: every weather entity that belongs to a device.
• Area: every weather entity in a room or area.
• Floor: every weather entity on a floor.
• Label: every weather entity that shares a label.

You can also select different target types in one action. For example, you can add a specific entity and an area as targets in the same action to run the action on both of them at once.

Response data

The action returns the forecast for each targeted weather entity, keyed by its entity ID. For each entity, the response contains a forecast field with a list of 60 entries, one for each minute of the next hour. Each entry has the following fields:

• datetime: the time of the forecasted conditions.
• precipitation: the forecasted precipitation amount, in millimeters per hour.

A trimmed example response looks like this:

weather.openweathermap:
  forecast:
    - datetime: "2024-10-19T18:59:00+00:00"
      precipitation: 5.46
    - datetime: "2024-10-19T19:00:00+00:00"
      precipitation: 5.62
    - datetime: "2024-10-19T19:01:00+00:00"
      precipitation: 5.62

Good to know

• The forecast covers the next 60 minutes, with one entry per minute.
• A precipitation value of 0 means no rain or snow is expected for that minute.
• The forecast is only as accurate as the data OpenWeatherMap provides for your location.

Try it yourself

Ready to test this? Open Developer tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] without writing a line of YAML.

Still stuck?

The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.