Météo France integration for Gladys Assistant
French weather forecasts and official vigilance alerts from Météo France.
Published by William-De71
- Devices
- Version 1.0.1
- Requires Gladys >=4.85.0
- ★ 0
This integration provides Gladys with weather forecasts and the official vigilance alerts from Météo France, the French national weather service. It feeds the dashboard weather widget, the voice assistant and the weather-alert scene triggers.
Ready to use
No configuration is required. Forecasts and vigilance alerts go through the Météo France public service: install the integration and it works right away.
An optional API key additionally unlocks the national vigilance map (see below).
What it provides
- Hourly forecast for the next 24 hours: temperature, feels-like, humidity, pressure, wind (speed, gusts, direction), rainfall and precipitation probability.
- Daily forecast for up to 8 days: min/max temperatures, conditions, total rainfall, UV index, sunrise and sunset.
- Official vigilance alerts: the nine Météo France phenomena (violent wind, rain-flooding, thunderstorms, floods, snow-ice, heatwave, extreme cold, avalanches, coastal flooding), with the department name and the full official bulletin.
- Vigilance map for today and tomorrow (requires the API key).
Scenes triggered by vigilance alerts
You can create a scene that runs when a vigilance alert is issued — for example, to receive an SMS on an orange-level alert.
In the scene editor, add a "Weather alert raised" or "Weather alert ended" trigger, then pick the house and, optionally, the phenomenon type and the minimum severity.
Gladys checks for alerts every 30 minutes. This integration additionally watches the vigilance every 15 minutes and notifies Gladys as soon as it changes, so your scene runs within seconds instead of waiting for the next scheduled check.
Vigilance map (optional)
Displaying the national vigilance map requires a personal API key, free of charge:
- Create an account on the Météo France API portal.
- Subscribe to the "Données Publiques de Vigilance" API (free). It also appears as "Bulletin Vigilance", and as
DPVigilancein technical URLs — all three are the same API. - On the API configuration screen, pick the API Key token type (not OAuth2), enter a long validity duration, then generate the key — see the two points below, this is where it usually goes wrong.
- In Gladys, open the Météo France integration's Configuration screen, paste the key and save.
An API key, not an OAuth2 token
On the "Configurer l'API Bulletin Vigilance" screen, the portal asks for a token type:
| Works here | Lifetime | |
|---|---|---|
| API Key | ✅ yes | the duration you enter |
| OAuth2 (the Generate Token button) | ❌ no | about 1 hour, not renewed here |
So tick API Key. An OAuth2 token appears to work at first, then stops working after roughly an hour: the map silently disappears. If your map used to show and no longer does, this is almost always why.
Key validity duration
Once API Key is ticked, the portal shows a mandatory "Durée" (duration) field, empty by default, to be filled in seconds. That is when the key stops working — and the vigilance map with it.
Since the integration uses this key permanently, enter the longest duration you can, otherwise you will have to regenerate and re-paste it regularly.
Enter
94672800(about 3 years). That is the maximum the portal accepts — anything higher is rejected.
For reference, should you prefer a shorter duration:
| Duration | Value to enter |
|---|---|
| 1 month | 2592000 |
| 6 months | 15552000 |
| 1 year | 31536000 |
| ~3 years | 94672800 — maximum |
Write the expiry date down somewhere: on that day the map will stop with no warning, exactly like an OAuth2 token. Generating a new key and re-pasting it in Gladys is then all it takes.
Without this key, everything else keeps working normally — only the map is unavailable.
Cache duration
The dashboard and the chat assistant both ask for the weather, and every request costs two calls to Météo France. The integration therefore reuses a recent answer for the cache duration, adjustable in the Configuration screen (600 seconds by default, between 0 and 3600).
You normally never need to change it: the 600-second default suits the vast majority of setups.
Which value to pick
The setting is in seconds, between 0 and 3600 (1 hour).
| Value | Effect |
|---|---|
| 0 | no cache, every request calls Météo France |
| 300 (5 min) | fresher data, more calls |
| 600 (10 min) — default | good balance, recommended |
| 1800 (30 min) | fewer calls, very responsive dashboard |
| 3600 (1 h) | maximum, forecasts may be up to an hour old |
Raising the value is not risky: Météo France only refreshes its forecasts a few times an hour, so a 10 to 30 minute cache costs you almost nothing in freshness while making the dashboard faster.
Two things worth knowing:
- a change in the vigilance level is detected independently of the cache: the integration clears the cache and asks Gladys to re-pull immediately, so your alert scenes fire without waiting for the cache to expire, even with the cache set to 1 hour;
- setting it to 0 disables the cache and calls Météo France on every request. Since the forecast endpoint can take up to 20 seconds on a cold cache, the dashboard may then feel much slower. Keep it for one-off troubleshooting rather than permanent use.
Coverage
Météo France covers mainland France and its overseas departments. For a house outside that area, the integration returns no data and Gladys automatically falls back to another weather service if you have one configured.
Precedence over OpenWeather
If you already had OpenWeather configured, installing Météo France automatically takes over with no setting to change. If you stop or uninstall the integration, Gladys falls back to OpenWeather just as automatically.
Configuration settings
These are the settings Météo France asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| Ready to use | section | No | Forecasts and vigilance alerts work with no configuration at all. The optional API key below only unlocks the national vigilance map image. |
| Météo France API key (optional) | secret | No | Only needed to display the national vigilance map. Create a free account on the Météo France API portal and subscribe to the "Données Publiques de Vigilance" API. Pick the "API Key" token type, NOT OAuth2 (which expires after about an hour), and set the mandatory "Durée" field to 94672800 seconds — about 3 years, the maximum the portal accepts. The map stops loading once that duration runs out. |
| Cache duration (s) | number | No | In seconds, between 0 and 3600. How long a weather answer is reused before calling Météo France again. The forecast endpoint can take up to 20 seconds on a cold cache, so reusing a recent answer keeps the dashboard responsive. The default of 600 (10 min) suits most setups; raising it to 1800 costs almost no freshness, as Météo France only refreshes a few times an hour. Set to 0 to always call the API (slower dashboard). A vigilance change always refreshes immediately, whatever this value. |
How to install Météo France in Gladys
- In Gladys, open Integrations: Météo France appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/william-de71/gladys-meteo-france:1.0.1), starts it in a sandbox isolated from the core, and generates the integration's interface (devices, discovery and configuration). - Open the Configuration screen of the integration, fill in the settings, and save.
- You can also install it directly from its repository URL: https://github.com/William-De71/gladys-meteo-france.
Météo France requires Gladys >=4.85.0. The catalog inside Gladys refreshes every hour, so a new version becomes available at most one hour after its release.
Not running Gladys yet? It is free and open source: follow the installation guide to get started.
About external integrations
Météo France is an external integration: a community integration packaged as a Docker container and published on GitHub, that Gladys installs in one click and runs in a sandbox isolated from its core. It is published and maintained by William-De71, not by the Gladys core team.
- Browse all external integrations
- Discover the native integrations built into Gladys
- Build and publish your own external integration
- Source code on GitHub — source of this documentation