Add Teslemetry sensors for FSD/regen firmware-2025.44 telemetry fields - #177608
Open
Bre77 wants to merge 1 commit into
Open
Add Teslemetry sensors for FSD/regen firmware-2025.44 telemetry fields#177608Bre77 wants to merge 1 commit into
Bre77 wants to merge 1 commit into
Conversation
Add three new sensor entities surfacing streaming fields not yet exposed: lifetime energy gained from regenerative braking (kWh, total_increasing), and the two firmware-2025.44+ self-driving statistics mileage counters (miles since reset, self-driving miles since reset), both distance sensors gated behind streaming_firmware and disabled-by-default diagnostics since the pull-side FSD totals don't share documented reset semantics.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds three diagnostic, disabled-by-default Teslemetry streaming sensors for regenerative energy and self-driving mileage counters.
Changes:
- Adds regenerative energy and mileage sensors.
- Firmware-gates mileage sensors to 2025.44.25.5.
- Adds translations, state assertions, and registry snapshots.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
homeassistant/components/teslemetry/sensor.py |
Defines the three streaming sensors. |
homeassistant/components/teslemetry/strings.json |
Adds sensor names. |
tests/components/teslemetry/test_sensor.py |
Tests states and registry properties. |
tests/components/teslemetry/snapshots/test_sensor.ambr |
Records entity registry metadata. |
| ) -> None: | ||
| """Test the new firmware-2025.44 streaming sensors are disabled-by-default diagnostics.""" | ||
|
|
||
| await setup_platform(hass, [Platform.SENSOR]) |
This was referenced Jul 30, 2026
Bre77
marked this pull request as ready for review
July 31, 2026 05:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed change
Adds three new streaming-only Teslemetry sensors surfacing telemetry fields introduced with vehicle firmware 2025.44:
lifetime_energy_gained_regen: lifetime energy recovered via regenerative braking.miles_since_reset: total miles since the vehicle's self-driving statistics were last reset.self_driving_miles_since_reset: FSD-specific miles since that same reset.All three are diagnostic, disabled by default, and streaming-only, matching the existing
lifetime_energy_usedsensor. The two mileage sensors are additionally gated behindstreaming_firmware="2025.44.25.5"since Tesla only started sending those fields on that firmware or later, and are diagnostic/disabled-by-default because they're firmware-gated, low general relevance, and only useful for diagnosing FSD-related counters rather than everyday use.This is one of a 3-PR split; binary_sensor and cover changes for the same firmware fields are in separate PRs.
Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: