🚨 Blitzer.de 3.0.0 — now with traffic hazards
🚧 Traffic hazards are reported too. Tailbacks, accidents, roadworks, obstacles, broken-down vehicles, road blocks and police bulletins — ten types under Hazards / Gefahren, each tickable on its own and all off until you switch them on. They get their own map source, their own update interval and their own count sensor: a tailback is stale within a minute, a permanent roadwork is still there next week.
🔍 Seventeen control kinds, instead of four categories that hid them. A tunnel camera, both halves of a section control, a weight check, a dummy and a plain speed camera were all "fixed" — 98 of 127 in the test data. How a control is installed and what it measures are now two separate axes, Controls / Kontrollen and Control types / Kontrollarten, so "only section controls" is something you can actually ask for.
📝 Every report prints in one line. summary reads Stauende · 2.3 km · 34 km/h · +3 min · A100, Berlin, so a card or a notification uses one field instead of six. Alongside it: kind, type_name, created, confirmed, info, and a tailback's speed and delay computed the way blitzer.de's own map computes them.
🔔 A blueprint, "Report Alerts". A live alert for every newly reported control or hazard, inside a time window you set — plus a digest of everything currently reported, at a time of day, when you leave a zone, or on demand. One set of filters, one set of channels: mobile push, the notification bell, a dashboard helper, text-to-speech, and your own actions.
🗄️ Archive data / Archivdaten on request. Blitzer.de's own record of enforcement that used to be there. Off by default and labelled archive, so it can never be read as something standing there today.
🧭 The setup form got shorter. The three switch groups are single lists now: seventeen control kinds take 700 px instead of 1300. The count sensors follow your Home Assistant language — Control count / Anzahl Kontrollen — instead of being German for everyone.
🐛 Five fixes. A third of all controls showed the wrong symbol; the map picks by what the control is, not by category and speed limit. A single camera near Sankt Michael im Lungau could take a whole entry down, because its info arrived as an empty list. Also: six cameras wrongly reported as trailers, a duplicate area name slipping through, and an entry with no control type sending a malformed request.
blitzer.refresh → blitzer.refresh_controls and its response key cameras → controls; the event blitzer_new_camera → blitzer_new_control; a map source now names its half (blitzer_berlin_controls). Every entry becomes a device, so entity ids lose the "Blitzer.de" prefix — the count sensors are migrated and keep their history. type no longer reports redlight; read kind instead.