v1.7.1 — Fix POI overlay

Bugfix

The 📍 POI overlay (added in v1.6.0) showed no markers for many users. Several causes were addressed:

• Empty-result cache poisoning — if the very first Overpass query for a ride failed transiently (timeout, CORS hiccup, network error), an empty array was cached in localStorage and every subsequent toggle just read the empty cache without retrying. Now empty results stay in-memory only; only non-empty results are persisted.
• Silent error swallowing — HTTP errors and fetch exceptions are now logged to the browser console with status code and response snippet. Overpass error "remark" fields (returned as HTTP 200) are also logged.
• Loading indicator — the 📍 button now pulses while the Overpass request is in flight and is disabled during that time, so users get feedback during the 5–30 s wait.
• Coverage gaps in the proximity filter — sampling tightened from every 500 m to every 250 m and the bbox padding raised from 200 m to 500 m, so all POIs within 500 m of the route are now reliably caught.

Action required after update

If you toggled POI on a ride before this update and saw nothing, your browser still has the empty cache. Either:

• Open DevTools → Application → Local Storage → delete the `eb-poi-*` entries, or
• Clear site data for your HA dashboard once

The fix prevents future poisoning automatically.

Installation

Update via HACS, restart Home Assistant, hard-refresh the browser (Ctrl+Shift+R / ⌘⇧R).