Skip to content

fix(tesla_vehicle): recover missing SoC with bounded telemetry wakes #167

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
frahlg merged 2 commits into from
Oct 6, 2026
Merged

fix(tesla_vehicle): recover missing SoC with bounded telemetry wakes #167

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
83b73ce
fix(tesla_vehicle): recover SoC with bounded telemetry wakes
frahlg Oct 6, 2026
fdad907
test(tesla_vehicle): reject unsuccessful nested wake responses
frahlg Oct 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# Changelog

## tesla_vehicle 0.2.5

- Recover missing, partial and old SoC with a telemetry-only wake and read.
- Keep the BMS timestamp; cached successful responses do not renew SoC age.
- Use Core's saved wake budget across restarts: at least 90 seconds between attempts, at most three in 30 minutes. Keep 408/503 backoff.
- Hosts without the new wake budget and wall-clock functions do not run recovery. Physical Tesla BLE acceptance remains untested.

## heishamon 0.8.0

Read `hp_power_w` from `main/Heat_Power_Consumption` (TOP16), with a
Expand Down
4 changes: 2 additions & 2 deletions SUPPORT_STATUS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,8 +160,8 @@ Catalog source is not proof that a target can install or run a driver.
| sungrow | 1.5.10 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
| tesla_cloud | 0.1.1 | ftw-core | not_assessed | — | not_recorded | not_assessed |
| tesla_cloud | 0.1.1 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
| tesla_vehicle | 0.2.4 | ftw-core | not_assessed | — | not_recorded | not_assessed |
| tesla_vehicle | 0.2.4 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
| tesla_vehicle | 0.2.5 | ftw-core | not_assessed | — | not_recorded | not_assessed |
| tesla_vehicle | 0.2.5 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
| tesla_wall_connector | 0.1.1 | ftw-core | not_assessed | — | not_recorded | not_assessed |
| tesla_wall_connector | 0.1.1 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
| teslamate_vehicle | 0.1.1 | ftw-core | not_assessed | — | not_recorded | not_assessed |
Expand Down
4 changes: 2 additions & 2 deletions devices.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1806,11 +1806,11 @@ manufacturers:
protocols:
- protocol: http
driver: "tesla_vehicle"
version: "0.2.4"
version: "0.2.5"
ders: [vehicle]
control: true
firmware_versions: ""
notes: "Read-only vehicle SoC + charge limit via Tesla API-compatible HTTP endpoint (e.g. TeslaBLEProxy)."
notes: "Vehicle SoC and charge limit via a local BLE proxy. Telemetry recovery needs a host with unix_ms and reserve_vehicle_wake. No hardware recovery test yet."
- name: "Tesla Vehicle (Fleet API)"
variants: [Model 3, Model Y]
regions: [CN, EU, NA]
Expand Down
Loading
Loading