Skip to content

v4.0.0

Choose a tag to compare

View all tags
@somansch somansch released this 11 Oct 17:06
· 4 commits to main since this release
v4.0.0
5209e9d

The card on a route from Berlin to Munich with the traffic flow on: only the route itself coloured, green where traffic moves and red where it stands, the two tailbacks on it marked, and the NEW and the +13 min badges counting them

This one was not an easy release. Two things broke at once: Blitzer.de rebuilt its map and stopped serving the data from where this integration had read it since the start, and Home Assistant 2026.10 replaced the engine under its map card, which the Blitzer card draws on. Both are dealt with here, and a good deal came along on the way.

⚠️ Every area or route that polled faster than once an hour polls once an hour after this update. Through v3.3.2 a new entry polled once a minute, and that is what Blitzer.de blocks. The update sets such entries to the new hourly default and names each one in the log; 0 (on demand) and anything slower stay as they are. Shorten it again under Configure if you must - the new Request count says what it costs.

🌐 The data comes from Blitzer.de's own site now. The old server blocks an address once it has been polled too often; the site does not appear to, so an installation that had been cut off should work again. Nothing to change in any entry.

🚧 Official road closures, with the road they close and when they end. The card draws the closed stretch as a red band along the road and shows Since … / Until … as chips; the hazard entity carries closure_since, closure_until, closure_polyline and more.

The card on an area in Berlin: two official closures drawn as red bands along the closed streets under their symbols, the list naming each one's road and its text with Since and Until chips, and the traffic flow coloured on the streets around them

🚦 The traffic flow, on demand. Show the traffic flow colours the roads the way Blitzer.de's map does - fetched for the view on screen while the card is visible, never polled. On a route only the route itself, in its direction of travel. A line under the subtitle switches it, says when it was fetched and refreshes it. Home Assistant 2026.10 or newer.

🗺️ The map stays when nothing is reported, showing the circle or the route it watches instead of a blank card (#3).

📊 What a poll costs. Request count and Delivered reports per area, with a Reset counters button.

⏳ Fewer requests. A new entry polls hourly, a route asks for cameras and hazards in one request per point, and blitzer.refresh fetches both halves in one pass.

🧭 A closed side road is no longer "on the route". A line has to run along the route to count, not merely cross it under a bridge.

👥 Grouping nearby reports is a choice, and on 2026.10 so is a group's shape: the new bubble with symbols, or the disc with the count.

🔗 Links open the rebuilt map. 🔢 A new entry keeps 20 reports per half, not 9. 🗄️ Archive data are gone - the rebuilt site no longer delivers them, so the switch went with them.

🐛 Fixed: the card works with Home Assistant 2026.10's new map (route, marker click, viewport, group colours, a badge loop that froze the page); no more getZoom errors in the log on 2026.9 when a map goes away; the pop-up's list follows the pop-up's map; "Change the route" asks openrouteservice only for a changed end.

📖 Full release notes: CHANGELOG

⭐ If Blitzer.de is useful to you, a star on the repo is genuinely appreciated - it is how other people find it. Thank you!

☕ This release took a good many evenings. If it saves you a fine or a jam, a coffee is welcome.

Assets 3
Loading