Skip to content

v1.4.0 — Multi-account & multi-bike support

Choose a tag to compare

View all tags
@Xunil99 Xunil99 released this 27 Apr 21:15
· 296 commits to main since this release
v1.4.0
40253ae

Multi-account and multi-bike support

The integration now properly handles users with two or more bikes, regardless of whether each bike has its own SingleKey ID or all bikes share one account.

Multiple Bosch accounts

Add the integration multiple times (one Client-ID per account). Each instance is fully isolated — own tokens, sensors, activities.

Multiple bikes per account

  • Per-bike hardware sensors (drive unit, battery, service) are already created
  • New: Activities are attributed to the correct bike via an odometer heuristic — we walk activities newest-first and match each one to the bike whose current odometer is closest to `startOdometer + distance`, then unwind that bike's odometer for the next-older activity (1.5 km tolerance).

Card filters

The Lovelace card now shows two extra dropdowns above the activity list (auto-hidden when not relevant):

  • Konto / Account — appears when more than one account is configured
  • Bike — appears when more than one bike is known across the configured accounts

Filtering is live and client-side; sorting works as before within the filtered result.

New / changed websocket API

  • `bosch_ebike/list_instances` (new): enumerate accounts and their bikes
  • `bosch_ebike/list_activities`: now returns `accountId`, `accountLabel` and `bikeId` per activity; accepts optional `config_entry_id`
  • `bosch_ebike/get_track`: accepts optional `config_entry_id`

Documentation

README updated (German and English) with a setup walk-through for both scenarios.

Installation

Update via HACS, restart Home Assistant. Hard-refresh the browser (Ctrl+Shift+R / ⌘⇧R) to load the new card JS.

Assets 2
Loading