--- title: "Blitzortung" description: "Blitzortung is a Marketplace integration for Home Assistant. It has 6.1k installs sharing analytics, needs the vendor's cloud and was last updated October 24, 2026." canonical: "https://vulpo.app/integrations/marketplace/mrk-its-homeassistant-blitzortung" url: "https://vulpo.app/integrations/marketplace/mrk-its-homeassistant-blitzortung.md" last-updated: "2026-10-25" version: "1.4" --- # Blitzortung > Blitzortung is a Marketplace integration for Home Assistant. It has 6.1k installs sharing analytics, needs the vendor's cloud and was last updated October 24, 2026. Blitzortung is a Home Assistant integration that reports real time lightning strikes near a chosen location using Blitzortung.org data. It adds sensors for the distance and azimuth of nearby strikes and a counter of strikes. It also emits geo location events for strikes, which show on the map. Data reaches Home Assistant through a public MQTT server run for this component, which reduces the data sent to clients compared with a direct connection to Blitzortung servers. The location can be fixed coordinates, which default to the home location, or a device tracker, person or zone entity that the integration follows. Options cover the detection radius, the time window for tracked strikes and the maximum number of tracked strikes, and setting that maximum to zero turns off the strike entities while the sensors keep working. Setup is done in the UI. Automatic summary of the README and code of mrk-its/homeassistant-blitzortung. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact) [Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=mrk-its&repository=homeassistant-blitzortung&category=integration) On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=mrk-its&repository=homeassistant-blitzortung&category=integration) ## Supports - **Uses the vendor's cloud**: Needs an internet connection and an account with the vendor. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services. ### Connect - **Configuration type**: The integration can be configured for static coordinates or follow the location entity. ### Entity - **Location entity**: The device\_tracker, person or zone entity whose location will be used by the integration. ### Coordinates - **Name of the integration instance**: The name the integration will use for this configuration. - **Latitude**: A decimal number representing latitude. - **Longitude**: A decimal number representing longitude. ### Change the connection - **Latitude**: A decimal number representing latitude. - **Longitude**: A decimal number representing longitude. ### After setup - **Lightning detection radius**: Radius of the circle for which lightnings will be detected. - **Time window**: Lifetime of tracked lightnings in minutes. - **Maximum number of lightnings**: Maximum number of tracked lightnings. Set to 0 to create no lightning strike entities (the sensors keep working). Texts from the code of [mrk-its/homeassistant-blitzortung](https://github.com/mrk-its/homeassistant-blitzortung). ## Entities - **Sensors**: Lightning azimuth, Lightning counter, Lightning distance ## Troubleshooting - **Diagnostics**: Downloads a diagnostics file to attach to a bug report. ## From the README > Blitzortung.org is a worldwide, real time, community collaborative lightning location network. This component uses Blitzortung data and provides real time notifications about lightning strikes in a given area (by default within 100km radius of your home). Data is served through a public MQTT server (dedicated to serve requests for this component) - thanks to geohash-based topics and some other optimizations, it greatly reduces amount of data sent to clients comparing to direct websocket connection to Blitzortung servers (it is also required by Blitzortung data usage policy - third party apps must use their own servers to server data for their own clients). > > - distance and azimuth sensors of lightning strikes nearby > - counter of lightning strikes > - emits geo\_location events for lightning strikes (visible on the map) > - data is realtime, with average delay of few seconds From the README of [mrk-its/homeassistant-blitzortung](https://github.com/mrk-its/homeassistant-blitzortung#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Weather and alerts](https://vulpo.app/integrations/category/weather-and-alerts.md), Public warnings - Number: 6.1k installs sharing analytics; 352 GitHub stars - Connection: Needs the vendor's cloud - Upkeep: Updated in the last 6 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: v1.7.4, last updated October 24, 2026 - Domain: `blitzortung` - Source: - Issues: In Vulpo: Chart card, Apple Watch Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-10-25. Source: https://vulpo.app/integrations/marketplace/mrk-its-homeassistant-blitzortung --- - HTML version of this page: https://vulpo.app/integrations/marketplace/mrk-its-homeassistant-blitzortung - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml