Hello,
Following the discussion about the new weather trigger, I think there is another complementary use case: the ability to retrieve weather forecasts from a scene, in order to use the information in subsequent actions.
This is not about triggering a scene based on a weather condition, as this functionality is already addressed in the other request.
Use Case
In my case, I have a wake-up scene that launches various notification scenes:
- today’s birthdays;
- today’s schedule/appointments;
- and I would like to add the day’s weather.
The goal would be, for example, to automatically produce a morning announcement like:
Good morning! Today, the weather will be partly cloudy with temperatures between 14 and 24 °C. Some showers are possible in the afternoon.
Proposal
Add a scene action of the type:
Weather → Retrieve Forecasts
with, for example, the following parameters:
- location/house;
- period:
- now;
- today;
- tomorrow;
- optionally the next X hours;
- optionally the next X days.
The idea would be to have a similar functionality to the new actions that retrieve data and make it available in the scene.
Returned Data
The action could, for example, expose:
- weather condition/description;
- current temperature;
- minimum temperature;
- maximum temperature;
- felt temperature;
- precipitation probability;
- precipitation amount;
- humidity;
- wind speed;
- gusts;
- optionally sunrise and sunset if available.
For example:
weather.description
weather.temperature
weather.temperature_min
weather.temperature_max
weather.feels_like
weather.precipitation_probability
weather.precipitation
weather.humidity
weather.wind_speed
The names are of course given only as examples.
Also Provide a Ready-to-Use Sentence
In addition to the structured data, it would be very practical for the action to directly provide a natural language weather summary, ready to be used in a notification or voice announcement.
For example:
Today, the weather will be partly cloudy with temperatures between 14 and 24 °C. Some showers are possible in the afternoon.
You could thus simply do:
Retrieve weather forecasts
Period: today
↓
Voice announcement:
{{ weather.summary }}
This summary could ideally be built directly from the weather provider’s data, without requiring a call to an AI.
This would allow for a quick, deterministic sentence to generate, suitable for notifications or TTS.
Why Keep the Structured Data as Well?
The summary would not replace the various values returned.
This would allow, for example, to build a custom message from the retrieved information:
Retrieve weather forecasts
Period: today
↓
Message:
"It will be between {{ weather.temperature_min }} and
{{ weather.temperature_max }} °C today."
So you would have two options:
- structured weather data, to freely build the scene content;
- a ready-to-use natural summary, for notifications and voice announcements.
Example with a Wake-Up Scene
This would allow, for example, to have:
Wake up
├─ Birthday notification
├─ Today's schedule notification
├─ Today's weather notification
└─ Continue waking up...
With the weather part:
Retrieve weather forecasts
→ today
↓
Voice announcement
→ {{ weather.summary }}
The idea would really be complementary to the new weather trigger: here, the weather does not serve to trigger the scene, but constitutes information retrieved during its execution, in order to be able to use it in subsequent actions.
What do you think? ![]()