I am using the external integration Vigicrues (via the Gladys SDK), which retrieves data from the Hub’Eau API. It creates a « Flow (m³/s) » feature for the Montjean-sur-Loire station, but the unit does not display in Gladys.
Cause: the water-valve category currently only accepts cubic-meter-per-hour (m³/h). However, river flows, such as those published by Hub’Eau and Vigicrues, are expressed in m³/s. The integration cannot therefore declare the correct unit.
Request (at the maintainer’s discretion):
Add cubic-meter-per-second (m³/s) to the units of water-valve / type flow, or
Create a dedicated category for rivers (flow, water height), with the units m³/s and m.
Interest: all integrations that follow rivers (floods, hydrometry) could display a correct unit instead of a unitless value.
Thanks in advance!
@guim31: for information, the « Flow (m³/s) » feature of the Vigicrues integration is currently sent with unit: null. Once Gladys accepts m³/s for this category, it may be necessary to declare the unit on the integration side.
Hi @XDECO, thanks for the request, it’s very clear!
Regarding Vigicrues, this is intentional for now: Gladys doesn’t have a m³/s unit, so with the setting Flow rate unit = m³/s, the feature runs without a unit (its name, « Flow rate (m³/s) », gives it away). If you want a unit displayed right now, switch this setting back to m³/h (the default choice): the value is converted (1 m³/s = 3,600 m³/h).
As soon as the core accepts m³/s, I’ll add it to the integration
