External integration - Vigicrues (flood vigilance and river levels)

Hi everyone! :waving_hand:

When you live near a river, you all have the reflex to check Vigicrues as soon as it rains for three days in a row :sweat_smile:. Might as well have Gladys do it for us. Here’s Vigicrues: the official flood vigilance and the river height near you, based on public data, without an account or key.

What it does

  • A device per measurement station you follow, with:
    • the water height (m);
    • the flow rate (mÂł/s) when the station measures it;
    • the vigilance of the river section: green, yellow, orange, or red;
    • the date of the last measurement. A station that has been silent for more than 3 hours clearly states this, instead of reposting an old value as if it were fresh.
  • Stations can be chosen by code, by municipality, or automatically around your home. A “Find stations” button lists those nearby, with their watercourse.
  • Two scene triggers: vigilance increases (yellow, orange, red) and vigilance decreases, filterable by station and color.
  • A “Vigicrues” widget: your stations, their height, the trend (rising, stable, falling), and the vigilance color.
  • In French, English, German, and Spanish.

The cool thing

The section turns orange → notification to the whole family and reminder to bring up what’s lying around in the basement
The Garonne exceeds 3 m → we keep an eye on the living room widget

Installation

:warning: Gladys 5.1 minimum.

It will be available in the store at the next indexer run. In the meantime: Integrations → Install from GitHub, with GitHub - guim31/gladys-vigicrues: Vigicrues flood vigilance and river levels (France) for Gladys Assistant, from official open data · GitHub

  1. Choose your stations: a station code, a municipality code (the INSEE code, not the postal code: 31555 for Toulouse), or “around my house”.
  2. Discovery tab: add the stations.

Measurements are read every 15 to 30 minutes, vigilance every 30 minutes.

Honest small reservations

  • Tested on real data: I ran the integration against real public services, on the Garonne in Toulouse (0.50 m this evening, the whole country in green, phew). The behavior during a real flood, however, could not be seen live.
  • It’s a complement, not a security alert system: in case of flooding, official instructions and authorities count.
  • Public data from Vigicrues and Hub’Eau. Independent project, not affiliated with SCHAPI or Vigicrues.

Like the previous ones, developed with Claude Code.

Repository: GitHub - guim31/gladys-vigicrues: Vigicrues flood vigilance and river levels (France) for Gladys Assistant, from official open data · GitHub

Thanks @guim31. It works well

Two small feedback points:

  • the configuration doesn’t ask which house you want to apply station detection to
  • in the devices widget display, there’s no unit for the flow rate

Thanks @StephaneB for this first feedback, and glad that it works on the Doubs :grinning_face_with_smiling_eyes:

Both points are fixed in 1.1.0, which has just been released:

  • House selection: a new « House » setting in the configuration, just before « Around my house ». Until now, the integration took the first Gladys house that had a position, without saying anything. Left empty, it remains as before.
  • Flow rate unit: Gladys doesn’t have a mÂł/s unit, hence the « 10.1 » alone. By default, the flow rate is now converted to mÂł/h, with the unit displayed. Your Doubs will therefore go to approximately 36,000 mÂł/h: it’s correct, but not very meaningful for a river :sweat_smile: If you prefer to keep the official mÂł/s from Vigicrues, there is a « Flow rate unit » setting, but the unit will not then be displayed.

Changing the unit changes the device structure: Gladys will offer « Update » in the Discovery tab.

A small constraint in passing: the house selection only exists since Gladys 5.2, so the integration now requires Gladys 5.2 minimum.

For « Depth » instead of « Water height » on your screenshot: it’s the Gladys dashboard that displays the generic label when the device has only one measurement of this type. I can’t change it from the integration.