Alplakes smart home integration, free and open source

Water temperature of Alpine lakes (Léman, Annecy, Bourget…) and its forecast, by Eawag.
Brings the water temperature of Alpine lakes into Gladys: Lake Geneva, Lake Annecy, Lake Bourget, Lake Constance, Lake Zurich, Lake Lucerne, Lake Maggiore, Lake Garda, Lake Como and more than a hundred Swiss, French, Italian, German, Austrian and Slovenian lakes, with a forecast for the next two days. The values come from Alplakes, the lake platform of Eawag, the Swiss Federal Institute of Aquatic Science and Technology. No account, no key.
Simulations calibrated on measurements, not direct measurements. Alplakes runs hydrodynamic models of each lake, driven by the weather forecast and checked against measurements: the value can be a degree or more away from what a thermometer reads at your beach. This integration is not affiliated with Eawag.
What you get
- One device per lake you follow, from the 1D model of the whole lake (Simstrat): the water temperature now, the maximum of the next 24 hours and of the next 48 hours, and the change expected in 24 hours (for instance +0.6 °C).
- One device per precise point (a beach, a harbour, a jetty) on the lakes that have a 3D model (Lake Geneva, Annecy, Bourget, Zurich, Lucerne, Lugano, Garda, Biel, Neuchâtel, Zug, Murten…): the same four values, at the grid cell of the model nearest to the point.
- The temperature at the surface (for swimming) or at 1, 2, 5 or 10 m deep.
- A scene trigger: the water reaches a temperature (10 to 28 °C), now or in the forecast of the next 48 hours, or falls back below it.
- A dashboard widget: your lakes, their temperature, the maximum of the next 48 hours and the trend.
- A "Find lakes" button that lists the lakes by name, with their key.
Requirements
- Gladys Assistant 5.3.0 or later.
- Internet access from Gladys (the integration asks the public Alplakes API).
Configuration
Install the integration from Integrations → Install from GitHub with the address
https://github.com/guim31/gladys-alplakes, then open its Configuration tab.
Settings
- Lakes: names or keys, separated by commas, 10 at most. A name works in English, French,
German or Italian, with or without its article:
Léman,Lake Geneva,Genfersee,Annecy,Lac du Bourget,Thunersee. Some lakes are split into basins (Zurich, Constance, Lugano, Lucerne): give the key of the basin (upperzurich,lowerconstance…). - Precise points (optional):
lake: latitude, longitude name, separated by semicolons, 10 at most, for instanceLéman: 46.2107, 6.1613 Bains des Pâquis. The name is optional. The coordinates are in decimal degrees with a dot (copy them from a map); four decimals are kept. - Depth: surface (default), 1, 2, 5 or 10 m. It applies to every lake and point.
- Language of the names: the language of the device and feature names, set when the devices are created in Gladys.
Save, then create the devices in the Discover tab. The connection status of the Configuration tab tells you what cannot be followed: an unknown lake, a name matching several lakes, a point that cannot be read, a lake without a 3D model, a point too far from the lake (more than 1.5 km from the nearest cell of the model).
Finding your lakes
The Find lakes button lists the lakes matching a name, with their key, and says which ones have a 3D model (precise points possible). Left empty, it lists the lakes with a 3D model. Copy a name or a key into Lakes, then save.
Devices
Each lake or point is a device with four read-only features, in °C:
| Feature | Content |
|---|---|
| Water temperature | The temperature now, between the two model steps around the hour. |
| Max. next 24 h | The warmest value of the next 24 hours (the current one at least) |
| Max. next 48 h | The warmest value of the next 48 hours |
| Change in 24 h | The temperature in 24 hours minus the current one (signed) |
The temperature and the change are published as "probe" temperatures: a lake placed in a room of Gladys does not change the temperature of that room. Values are computed every hour from the series of the model, and Alplakes is asked again every 3 hours.
Dashboard widget
Add the Alplakes → Lakes widget to a dashboard.
- Without a lake chosen: one line per lake or point (10 at most) with the temperature now, the maximum of the next 48 hours and the trend icon (warming, steady, cooling).
- With a lake chosen: its four values, live.
Settings hide the forecast and the link to the Alplakes website. The widget ends with the attribution "Data: Alplakes, Eawag (CC BY 4.0)" and the time of the last data.
Scene trigger
Water temperature threshold crossed fires when the water of a followed lake or point
reaches a temperature, or falls back 0.3 °C below it (so that a value hovering around a
threshold fires only once). Filters: the lake or point, the value (the temperature now, or the
maximum of the next 48 hours), the temperatures (10 to 28 °C) and the direction (reached,
falling back below). The scene can use the lake name, the water temperature, the threshold,
the value code (current, forecast_48h) and the direction code (rising, falling).
For any other condition (above 21.5 °C, between two values…), use the usual device trigger of Gladys on the features of the device.
Scene examples
- Swimming season: when Lake Annecy reaches 20 °C (temperature now, reached), send "The lake is at {temperature} °C, swimming time!".
- Plan the weekend: when the maximum of the next 48 hours of your beach reaches 22 °C, send a message on Thursday evening.
- End of the season: when the lake falls back below 16 °C, remind you to bring the paddle board in.
Data sources, licence and quotas
- Alplakes (Eawag, https://www.alplakes.eawag.ch): API
https://alplakes-api.eawag.ch, models Simstrat (1D, one per lake or basin), Delft3D-FLOW and MITgcm (3D), driven by the MeteoSwiss forecast. Lake names: the static list of the Alplakes website. - Licence: CC BY 4.0. Attribution: "Data: Alplakes, Eawag (CC BY 4.0)", shown in the widget and in the Configuration tab.
- Fair use: the API is rate-limited per client. The integration asks one series per lake or point every 3 hours (the pace of the models), spaced by one second, with an identifying User-Agent, and the lake list once a day. A failed request keeps the last series: the forecast stays usable for about two days.
- Nothing is sent to Alplakes but the lake keys, the depth and the coordinates of your points.
Troubleshooting
- "Unknown lake": use Find lakes; the small lakes have their own key (
rotsee,oeschinensee). - "Several lakes match": the lake is split into basins: give the key of the basin.
- "No 3D model": precise points are only possible on the lakes with a 3D model; follow the whole lake instead.
- "Point too far from the lake": the coordinates are probably swapped (latitude first) or on land.
- "Alplakes does not answer": the values continue from the last forecast; they come back with the service.
- Logs:
LOG_LEVEL=debugshows every tick.
Limits
- Simulations, not measurements: the models are good on average, less so near a river mouth, in a shallow bay or after a storm.
- The 1D model gives one value for the whole lake; for a beach, use a precise point.
- A depth change asks every series again; a crossing during a restart fires no trigger.
- Spanish lake names exist for the big lakes only; the others keep their English name.
- Not affiliated with Eawag. Data: Alplakes, Eawag (CC BY 4.0).
Configuration settings
These are the settings Alplakes asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| Your lakes | section | No | Follow the water temperature of Alpine lakes, simulated by Alplakes (Eawag) and refreshed every 3 hours. "Find lakes" below lists their names. Save, then create the devices in the Discover tab. |
| Lakes | string | No | Names or keys, separated by commas (10 at most). One device per lake, from its 1D model. |
| Precise points (optional) | string | No | A beach or a harbour: "lake: latitude, longitude name", separated by semicolons (10 at most). Only for the lakes with a 3D model. |
| Depth | select | No | Depth of the temperature: the surface for swimming, deeper for fishing or diving. |
| Language of the names | select | No | Language of the lake and feature names, set when the devices are created. |
| About the data | section | No | Simulations of the Alplakes models (Eawag), calibrated on measurements: not direct measurements. Data: Alplakes, Eawag (CC BY 4.0). |
How to install Alplakes in Gladys
- In Gladys, open Integrations: Alplakes appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/guim31/gladys-alplakes:1.0.0), 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/guim31/gladys-alplakes.
Alplakes requires Gladys >=5.3.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
Alplakes 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 guim31, not by the Gladys core team.
- Browse all integrations, native and community
- Build and publish your own external integration
- Source code on GitHub — source of this documentation