Weather

Weather saves locations for the current user and presents current conditions, hourly and daily forecasts, rain radar, and unattended display views. Use it to check one place quickly or keep several locations ready for recurring plans.

Use Weather

• Save a German city once and return to its forecast from the overview.
• Compare current conditions with hourly values for near-term decisions.
• Use the daily forecast for the broader trend across the available days.
• Check rain radar when the timing and movement of precipitation matter.
• Open Display for a shared screen, or add the current-weather widget to a dashboard.

Forecasts describe the saved coordinates rather than every street or local microclimate. Provider data can change as newer observations arrive.

Understand the Weather model

City search allows public Geo endpoints and the shipped geo host by default; the operator can replace this list with GEO_ALLOWED_TARGETS in the Weather container when another internal Geo host is needed.

Location search currently covers German cities. A saved location stays in the user's account until the user removes it. Weather may reuse cached provider data according to the configured cache duration.

How Weather fits Cloud

Weather owns location and forecast behavior. It uses Cloud for user identity, application settings, dashboard widgets, API publication, capability registration, and the shared in-product Help surface.

Find detailed product help

Open Help inside Weather for saved locations, forecast views, displays, and troubleshooting. Developers can read App capabilities, Application settings, and Dashboard widgets for the shared contracts Weather adopts.

Automate Weather from the terminal

Weather does not register a dedicated cld weather module. Use its typed Queries through the generic capabilities interface when a script needs weather data:

cld capabilities query weather location.list \
  --input '{"limit":10}' \
  --json

cld capabilities query weather forecast.get \
  --input '{"source":{"kind":"coordinates","lat":52.52,"lon":13.405}}' \
  --json

City search requires a Geo API URL in Weather settings. If it is empty, weather.city.search returns WEATHER_CITY_SEARCH_NOT_CONFIGURED (500) and asks an administrator to configure it. A Geo service failure returns WEATHER_CITY_SEARCH_UNAVAILABLE (500). In both cases, forecasts still work with known coordinates: call weather.forecast.current or weather.forecast.get with source.kind = "coordinates", as shown above.

Run cld capabilities catalog --json to inspect the live schemas and safety metadata. Run cld capabilities query --help for the current invocation syntax. Capability calls use the current profile and do not bypass application authorization.

Deployment requirements

PUT /api/weather/admin/settings accepts { updates, replaceUnreadable: ["weather.geo_url"] } to explicitly replace unreadable saved settings; every listed key must be a Weather setting included in updates.

See Deployment requirements for this app’s startup prerequisites, optional integrations, configuration and functional checks.