Skip to content

v1.7.0 — Editable service-due date and km

Choose a tag to compare

View all tags
@Xunil99 Xunil99 released this 28 Apr 05:04
v1.7.0
8bfe0b4

User-editable next service date / odometer per bike

Each configured bike now exposes two new editable entities:

  • `date._service_due_date` — date the next service is due (HA date picker)
  • `number._service_due_odometer` — odometer reading at which the next service is due, in km

On first encounter of each bike, the entities are seeded from the Bosch API's `serviceDue.date` / `serviceDue.odometer` (when present).

Once you change a value, your override takes precedence — the existing service-due sensors (`service_due_in_days`, `service_due_in_km`) and event triggers (`ha_bosch_ebike_service_due_soon` / `_service_overdue`) all read the user value first, falling back to Bosch only when the override is empty.

Resetting: setting the odometer to `0` clears the override and falls back to the Bosch value. The date entity is sticky once set; later Bosch updates do not overwrite it (intentional — that value represents your plan).

Overrides are persisted in the existing Store helper and survive HA restarts.

Installation

Update via HACS, restart Home Assistant.

Assets 2
Loading