[aniceberg]

What

Parents can now choose where a bus's position comes from: a Traccar server (as before) or a Bouncie OBD-II tracker. To use both, add Bus Monitor once per account; each bus profile follows one vehicle from its own entry.

• Config flow opens with a provider menu (Traccar / Bouncie). The Traccar step is unchanged.
• Bouncie signs in with OAuth through HA Application Credentials. Each parent registers their own free app at bouncie.dev with the redirect URI https://my.home-assistant.io/redirect/oauth. Positions are polled from GET /v1/vehicles: every 30 s by default, 15 s minimum. Reauth reruns the OAuth flow and rejects a different Bouncie account.
• Provider layer in providers/: base.py holds the shared Device type, errors and Provider protocol, traccar.py is the moved client, and bouncie.py is new. traccar_client.py stays as a re-export so scripts/probe.py still works.
• Device ids are now strings everywhere. A v1 → v2 config entry migration adds provider: traccar and turns stored ids into strings. Entity unique_ids ({entry}_{id}_…) don't change, so existing installs keep their entities, profiles and settings.
• Docs and tools: docs/bouncie.md covers setup, the README is updated, and scripts/bouncie_probe.py measures how often Bouncie positions refresh during a drive.

Why

The goal is to support one or more tracking providers as inputs. Bouncie is the first addition after Traccar.

Reviewer notes

• Not yet tried against a real Bouncie account. Bouncie doesn't document how often stats.location refreshes mid-trip, the units of REST speed (mph assumed, matching the webhook docs), or any rate limits. Run scripts/bouncie_probe.py on a drive before relying on the alerts. If positions refresh slowly, tripData webhooks (on the roadmap) become the priority.
• Token request override. Bouncie's token endpoint wants a JSON body, so BouncieOAuth2Implementation._token_request overrides HA's form post. It reuses HA's private config_entry_oauth2_flow._raise_mapped_token_error so error handling matches HA's (4xx → reauth, 429/5xx → retry). A future HA release could rename or remove that function.
• Device identifiers stay (DOMAIN, id): HA 2026.10 (our minimum) already scopes them per config entry, and a test confirms a Traccar and a Bouncie vehicle with the same raw id stay separate.
• Rebased onto the rewritten main (v0.4.0). Upstream's new street and time checkpoint code needed only the str id change.

Tests

ruff check . is clean and pytest passes (92 tests). The new tests:

• tests/test_bouncie.py: parsing, mph → m/s, name fallbacks, paging, HTTP and refresh error mapping, and a check that the token request is JSON.
• tests/test_bouncie_ha.py: the full OAuth config flow, a Bouncie entry tracking and alerting, Traccar and Bouncie entries side by side, and the v1 → v2 migration keeping entities.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-29T04:19:59.319005Z	d2cd552	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d2cd552fa0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".