GeoSphere Austria smart home integration, free and open source
Austrian weather from GeoSphere Austria (ex-ZAMG): stations, forecast and official warnings.
Published by guim31
- Devices
- Version 1.0.1
- Requires Gladys >=5.2.0
- ★ 0
The official weather of Austria in Gladys, from GeoSphere Austria (formerly ZAMG), the Austrian national weather service: the readings of the nearest TAWES weather station every 10 minutes, the forecast of its 2.5 km model, and the official weather warnings (storm, rain, snow, black ice, thunderstorm, heat, cold).
Open data: no account, no API key. This integration is not affiliated with GeoSphere Austria.
Developed without access to the live GeoSphere API, from published answers of the services: feedback welcome.
Overview
- Two devices: the nearest station (temperature, humidity, pressure, wind, gusts, rain, sunshine, snow depth) and your place (forecast for the next 24 hours and tomorrow, warning levels).
- A scene trigger, "New GeoSphere warning", as soon as a warning is announced, often hours before it starts.
- A dashboard widget with the readings, the temperature curve of the next 24 hours, the warnings and tomorrow's forecast.
- Read-only: GeoSphere is a data source, nothing is controlled.
Requirements
- Gladys 5.2.0 or later.
- A place in Austria (the forecast also covers the neighbouring areas, the stations and the warnings only Austria).
- Your Gladys house located on the map (Settings → Houses), or coordinates typed in the configuration.
- Gladys must reach the Internet (
dataset.api.hub.geosphere.atandwarnungen.zamg.at).
Configuration
Install the integration from Integrations → Install from GitHub (or from the store), then open its configuration. Every field is optional: by default the integration takes the position of your first located house, the station nearest to it, and refreshes every 10 minutes.
| Field | Use |
|---|---|
| House | The house whose position is used. Empty: the first house that has a position. |
| Latitude, Longitude | Another place than a house, for example 47.07 and 15.44 (a comma works too). Both, or neither. |
| Weather station | The id of a GeoSphere station, for example 11035 (Wien/Hohe Warte). Empty: the nearest one. |
| Refresh interval | 10, 15, 30 or 60 minutes. The stations report every 10 minutes. |
| Language of the feature names | Language of the feature names (set when the devices are created) and of the scene event texts. French by default. |
The house position is read through the Gladys location permission, shown when you install the
integration. It is sent to GeoSphere Austria only, to get the forecast and the warnings of the
place, and never written to the logs.
Then open the Discovery tab of the integration and add the two devices to Gladys.
Devices
Station
The name is "GeoSphere" followed by the station name. Values of the last 10-minute observation:
| Feature | Unit | Note |
|---|---|---|
| Temperature | °C | Air temperature, 2 m |
| Dew point | °C | |
| Humidity | % | |
| Pressure (sea level) | hPa | Pressure reduced to sea level, as in the forecasts |
| Wind speed | km/h | 10-minute mean |
| Wind gusts | km/h | Strongest gust of the last 10 minutes |
| Wind direction | ° | Where the wind comes from: 0 = north, 90 = east |
| Rain intensity | mm/h | Rain of the last 10 minutes, as an hourly rate |
| Sunshine (last 10 min) | min | 0 to 10 |
| Snow depth | cm |
A station that does not measure a value (many have no sunshine or snow sensor) leaves that feature empty. A station silent for more than 3 hours is not re-published as current.
Place
The name is "GeoSphere" followed by the house name (or the coordinates). Forecast of the model at the place, and the warnings of its municipality:
| Feature | Unit | Note |
|---|---|---|
| Weather | text | The weather of the coming hour, e.g. "Partly cloudy" |
| Minimum next 24 h | °C | |
| Maximum next 24 h | °C | |
| Precipitation next 24 h | mm | |
| Strongest gust next 24 h | km/h | |
| Minimum tomorrow | °C | Tomorrow in the time zone of Gladys |
| Maximum tomorrow | °C | |
| Precipitation tomorrow | mm | |
| Warning level | 0 to 3 | Highest level in force: 0 none, 1 yellow, 2 orange, 3 red |
| Storm warning | 0 to 3 | Level in force for this type |
| Rain warning | 0 to 3 | |
| Snow warning | 0 to 3 | |
| Black ice warning | 0 to 3 | |
| Thunderstorm warning | 0 to 3 | |
| Heat warning | 0 to 3 | |
| Cold warning | 0 to 3 | |
| Weather warnings | text | The warnings in force or announced, e.g. "Orange · Storm → 18:00" |
The levels are those in force now: an announced warning raises them when it starts. To act as soon as it is announced, use the scene trigger.
Widget
GeoSphere weather shows, in the language and units of the dashboard:
- the place name, then the temperature, humidity, wind and gusts of the station;
- the temperature curve of the next 24 hours;
- the warnings in force (until when) and announced (from when), or a green "None" line;
- the weather of the coming hour, the next 24 hours and tomorrow (minimum, maximum, rain);
- the source and the time of the observation.
Scene trigger
New GeoSphere warning fires when GeoSphere Austria issues a warning for the place, or raises the level of one: once per warning and per level, as soon as it is announced. A restart does not fire it again. The very first start only takes note of the warnings already issued.
Filters (empty = any): Warning types (storm, rain, snow, black ice, thunderstorm, heat, cold) and Levels (yellow, orange, red).
Information passed to the scene actions: warning type, level, level (1 to 3), start, end, already
in force, level raised, official text (in German, or in English for the other languages) and
municipality. For example, a message: GeoSphere: \{\{triggerEvent.data.level_label\}\} \{\{triggerEvent.data.type_label\}\} warning from \{\{triggerEvent.data.starts_at\}\} to \{\{triggerEvent.data.ends_at\}\}.
Configuration actions
- List the nearest stations: the 8 active stations nearest to the place, with their id, region, altitude and distance. Copy an id into "Weather station" to choose another one (a station in the same valley often fits better than the nearest one across a mountain).
- Check the connection: reads every source now and says what answered: the station temperature and its time, the forecast, the number of warnings.
Scene examples
- Storm coming: trigger "New GeoSphere warning", types "Storm" and "Thunderstorm", levels "Orange" and "Red" → close the shutters, retract the awning, send a message with the start time.
- Heat day: when the "Heat warning" feature becomes greater than or equal to 2 → close the south-facing shutters at 10:00 and send a reminder to drink.
- Frost tonight: every evening at 20:00, if "Minimum next 24 h" is below 0 °C → notify to protect the plants and the windshield.
Troubleshooting
- "No location": no house has a position. Place your house on the map in Settings → Houses, or type coordinates, or choose a station.
- "Outside the GeoSphere Austria area": the place is outside the area of the model (latitude 43 to 51.8, longitude 5.5 to 22.1).
- "GeoSphere Austria does not answer": Gladys cannot reach the service; the values are updated when it is back. The logs say which source fails, once, and when it works again.
- A feature stays empty: the station does not measure it. Choose another station with List the nearest stations.
- More details: set the
LOG_LEVELvariable of the container todebug.
Limits
- Data: open data of GeoSphere Austria, licence CC BY 4.0 ("Data source: GeoSphere Austria", shown by the widget).
- Requests: about 13 an hour at the default pace (observation and warnings every refresh, forecast once an hour, station list once a day), far below the limits published by the GeoSphere Data Hub (5 requests a second, 240 an hour, at the time of writing).
- One place and one station per installation.
- The feature names are set when the devices are created: changing the language later does not rename them.
- The warnings API is the one of the GeoSphere warning website; GeoSphere may change it without notice.
- Developed without access to the live API: the formats come from the answers published by python-zamg and ioBroker.weather-warnings. Feedback welcome.
Configuration settings
These are the settings GeoSphere Austria asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| GeoSphere Austria | section | No | Open data of GeoSphere Austria, the Austrian weather service: no account, no key. By default, the integration uses the position of your first Gladys house: the nearest weather station, the forecast and the warnings of that place. Not affiliated with GeoSphere Austria. |
| House | select | No | The house whose position is used. Empty: the first house with a position. |
| Latitude (optional) | string | No | To use another place than a house. Takes precedence over the house. |
| Longitude (optional) | string | No | |
| Weather station (optional) | string | No | Id of a GeoSphere station. Empty: the nearest one. The action below lists them. |
| Refresh interval | select | No | The stations report every 10 minutes. |
| Language of the feature names | select | No | Used when the devices are created, and for the scene event texts. |
How to install GeoSphere Austria in Gladys
- In Gladys, open Integrations: GeoSphere Austria appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/guim31/gladys-geosphere: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/guim31/gladys-geosphere.
GeoSphere Austria requires Gladys >=5.2.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
GeoSphere Austria 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