This integration is no longer developed. Its successor is TomTom: blitzer.de’s reports built in, plus TomTom’s own jams, closures, roadworks, accidents and road weather in more than 70 countries, Lufop speed cameras, a route planner on the card and 30 languages. Blitzer.de keeps working as it is, but gets no new features. How to switch is in the v4.1.1 announcement further down this thread.
Hi all,
I’d like to share a custom integration that brings Blitzer.de traffic data into Home Assistant — speed controls and traffic hazards, with a dashboard card of its own: github.com/somansch/blitzer
Unofficial: not affiliated with, endorsed by or supported by Blitzer.de.
The card
“What is on my way right now”: controls and hazards in one list, nearest first, with a map above them that either mirrors the list or drives it. Three formats — portrait (map over list), landscape (side by side), and minimal, a single line with three numbers and the reports behind it in a pop-up.
Two of those numbers are also filters. NEW narrows the card to what has just been reported; the red one adds up what the jams cost — +10 min, +1 h 35 min — and narrows it to exactly those. The map follows either way, and on a route entry it draws the route itself.

The map can also show the traffic flow, coloured the way Blitzer.de’s own map colours it — fetched only for the part of the map on screen, and only while someone is looking at it; on a route only the route itself, in its direction of travel. Official road closures are drawn as a red band along the closed stretch, with Since / Until chips on the entry. And when nothing is reported the map stays, showing the route or the circle it watches instead of a blank card.
Pick the area on the card or pin it to one, switch between controls and hazards, sort by distance, newest or oldest, measure distances from a person or a zone instead of the area’s centre, group nearby reports or draw every one, fold a long list, refresh on demand.
It comes with the integration — nothing to download, no file in www, no resource to register.
Yours to style
Around 220 settings in the editor, each with an “i” explaining it: colour, typeface, size, background and symbol, element by element. No YAML, no card-mod, no CSS.
Same card, same data as above. For dressing a whole dashboard at once there are 159 CSS variables, one per layout setting, documented in the README.
What it reports
For any area or route you configure — a centre point + radius, a radius that follows a device tracker, a hand-drawn route along waypoints, or a route openrouteservice works out from a start and a destination — everything Blitzer.de knows about that stretch arrives as geo_location entities:
- Controls / Kontrollen — not just speed cameras. Red light cameras, section controls, tunnel cameras, distance, weight, height and lane checks, entrance and access controls, overtaking bans, police checks and dummies. Seventeen kinds, each tickable on its own.
- Hazards / Gefahren — tailbacks with the length of the queue and the delay it costs, plus accidents, roadworks, obstacles, broken-down vehicles, road blocks and official police bulletins. Ten types, all off until you switch them on. Official closures from the Mobilithek come with the closed stretch of road, the period and the origin.
Features
Config flow — add as many areas or routes as you like (“Munich”, “Berlin”, “Commute”), each with its own entities and its own device
Route (start/destination) — a start, a destination and optional via points; openrouteservice works out the route along real roads and Blitzer.de is searched along it. Where there is more than one way it offers up to three, and one switch creates the way back as a second entry. Reports are measured along the route, so a marker reads “at km 23” rather than “3 km from a waypoint”. Needs a free openrouteservice API key, used only while a route is set up
Route (waypoints) — draw a corridor along waypoints instead of a radius, no external routing engine needed, and edit the waypoints later without redrawing
Device tracker (radius) — the same circle, around wherever a phone or a car currently is rather than around a fixed point
Traffic flow on the card’s map — on demand, never polled; needs Home Assistant 2026.10
Request count and delivered reports per area — two diagnostic sensors with a reset button, so you can see what a poll costs before you shorten an interval. A new entry polls once an hour; a route asks for cameras and hazards in one request per point
“Counts as new for” / “Als neu zählen für” — how long a report counts as new, per area and separately for each half, also as a number entity on the device page. One answer that the card, an automation and a template all read
A ready-made summary on every entity — Stauende · 2.3 km · 34 km/h · +3 min · A100, Berlin— so a card or a notification uses one field instead of six
Controls and hazards poll independently, each with its own interval, count limit, city whitelist, ID blacklist and on-demand refresh actions — one of them, blitzer.refresh, fetches both halves in a single pass
blitzer_new_controlandblitzer_new_hazardevents — fired only for something genuinely new, never for one already known and never right after a restart. Each carries the report’s own distance, so an automation can say “at km 23” without a reference point of its own
Blueprint “Report Alerts” — live alerts for anything new plus a digest of everything currently reported. Push, notification bell, dashboard helper, text-to-speech, your own actions. No YAML, and it installs itself along with the integration
It says when it stops working — three failed polls in a row raise a repair under Settings → System → Repairs, naming the entry and the reason, and it clears with the next poll that succeeds
German and English throughout — config flow, actions, card and count sensors follow your Home Assistant language
Installation
Available as a HACS default repository:
- Open HACS in Home Assistant
- Search for “Blitzer.de”
- Click the “Download” button
- Restart HA
That is everything: the card and the blueprint come along. Needs Home Assistant 2024.7 or newer; the traffic flow and the map’s grouping options need 2026.10. Manual installation instructions are in the README as well.
Also on the standard map card
Every report is a plain geo_location entity, and each entry publishes two sources of its own — blitzer_<name>_controls and blitzer_<name>_hazards — so the built-in map card can show one area, one half, or any combination, with Blitzer.de’s own symbols rather than generic markers.
A note on the data source
There is no official, documented Blitzer.de API — this integration reads the same data Blitzer.de’s own map application reads (since v4.0.0 from Blitzer.de’s own site), the same way several long-standing community projects (Home Assistant, ioBroker, FHEM) do. Blitzer.de’s terms of use don’t really cover this kind of use, so please be aware this sits in a legal gray area — use it at your own risk, same as the projects it’s based on. The integration keeps its requests few: a new entry polls once an hour, and each area tells you what a poll costs.
Feedback, issues, and PRs are all welcome on GitHub. Hope it’s useful to some of you! A
on the repo helps others find it — and if you insist on the coffee after all, I won’t say no ![]()






