Diagnostic build only. The maintenance counter does not reset on done-click for some users (both km- and date-based items). Code analysis alone cannot determine whether the backend is updating in-memory state, whether list_maintenance reads fresh values, or whether the frontend renders stale data. This release adds INFO-level logging at every component boundary so the failing layer becomes obvious.
How to use
- Update via HACS, then restart Home Assistant (Python backend changes require a restart - this is the most likely cause of the original report).
- Hard-reload the browser (Ctrl+Shift+R).
- On the dashboard card, click the green ✓ on a maintenance item.
- Share:
- HA log lines starting with
DIAG(Settings → System → Logs) - Browser console line starting with
[Bosch eBike DIAG](F12 → Console)
- HA log lines starting with
What is logged
Backend (HA log):
DIAG ws_complete_maintenance ENTRYwith bike_id, item_idDIAG ws_complete_maintenance: current_odo=...DIAG ws_complete_maintenance: pre-state=...DIAG ws_complete_maintenance: post-state=...— confirms what was actually written to the in-memory item dictDIAG ws_list_maintenance: item=... -> remaining_km=... remaining_days=...— the values returned to the frontend
Frontend (browser console):
[Bosch eBike DIAG] After done-click, backend says: { ... }with the full item state includingremaining_kmandremaining_days
No behavioural change vs v1.16.8 - only logging added. Will be reverted once the root cause is fixed.