-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
You need a KachelmannWetter Plus subscription. The free tier does not include API access.
The hobby plan supports 2 API locations. You can add the integration multiple times in HA with different coordinates (as long as each is configured on kachelmannwetter.com).
No. The Kachelmann API requires a paid subscription. There is no free tier with API access.
No, this is a custom component maintained by the community. It is not affiliated with Meteologix AG or Kachelmann Gruppe.
Default: every 10 minutes. Configurable between 1 and 60 minutes via integration options.
The daily forecast (from the 6h endpoint) covers ~10 days. The 14-day trend is a separate dataset with less detail (no hourly breakdown) but covers 14 days. Both are available — the trend data is in the sensor.kachelmannwetter_trend_14day sensor attributes.
-
precipitation_probability_today(sensor): Percentage chance of ≥1mm rain today, from the 14-day trend -
rain_expected_3h(binary sensor): Whether any of the next 3 hourly forecasts show precipitation or rain conditions
The integration automatically switches to clear-night when the API reports isDay = false. This gives you proper nighttime icons in the weather card.
Yes! Use the sensor.kachelmannwetter_trend_14day sensor attributes:
{# Today #}
{{ state_attr('sensor.kachelmannwetter_trend_14day', 'days')[0].temp_max }}
{# Day after tomorrow #}
{{ state_attr('sensor.kachelmannwetter_trend_14day', 'days')[2].precipitation_probability_1mm }}
{# Available fields per day: #}
{# temp_max, temp_min, precipitation, precipitation_probability_1mm, #}
{# precipitation_probability_10mm, precipitation_type, wind_gust, #}
{# sun_hours, sun_hours_relative, sun_max_possible, thunderstorm, #}
{# cloud_coverage_eighths, condition, weekday, is_weekend #}Sensors that most users don't need are disabled to keep the UI clean:
- Nautical dawn/dusk
- Astronomical dawn/dusk
- API requests remaining (diagnostic)
You can enable them anytime from the device page.
Yes, like any HA entity: click the entity → gear icon → change name. The entity ID stays the same.
All values use metric units:
- Temperature: °C
- Wind: km/h
- Precipitation: mm
- Pressure: hPa
- Radiation: W/m² (current) or Wh/m² (daily sum)
HA will convert to your preferred unit system automatically.
The integration raises UpdateFailed, entities show as "unavailable", and HA retries at the next update interval. No manual intervention needed.
The integration reads the Retry-After header and schedules an automatic retry. See API & Rate Limits for details.
Yes, it uses Home Assistant's built-in aiohttp session which respects your HA proxy configuration.
Absolutely. You can have multiple weather entities from different providers. Just use the correct entity ID in your automations and cards.
Make sure you added it as a custom repository first:
- HACS → three dots → Custom repositories
- URL:
https://github.com/nodomain/haKachelmannWetter - Category: Integration
HACS shows available updates in its dashboard. Click update, then restart HA.
Only your configured coordinates (latitude/longitude) are sent with each request. The API key is sent as an HTTP header.
Since v2.3.1, coordinates are not written to Home Assistant logs, even at debug level. Only the endpoint type (e.g., "current", "forecast") is logged.