Skip to content

Use VCSEC broadcasts for Teslemetry vehicle lock - #979

Draft
Bre77 wants to merge 6 commits into
fm/ble-d9-2-coverfrom
fm/ble-d9-3-lock
Draft

Use VCSEC broadcasts for Teslemetry vehicle lock#979
Bre77 wants to merge 6 commits into
fm/ble-d9-2-coverfrom
fm/ble-d9-3-lock

Conversation

@Bre77

@Bre77 Bre77 commented Jul 31, 2026

Copy link
Copy Markdown
Owner

Breaking change

Proposed change

Reroute the vehicle lock to its VCSEC lock-state broadcast when the vehicle is
BLE paired, reusing the BLE data manager's connection-generation availability.
Lock/unlock commands still route through the existing command router, and the
charge cable latch stays on the stream. An unrecognized lock enum resolves to
unavailable.

This stacks on #978 (its base branch), part of the series moving cheapest-source
vehicle values onto the local Bluetooth link.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to frontend pull request:

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

Bre77 added 2 commits July 31, 2026 14:43
Reroute the vehicle lock to its VCSEC lock-state broadcast when the
vehicle is BLE paired, reusing the BLE data manager's connection-
generation availability. Lock/unlock commands still route through the
existing command router, and the charge cable latch stays on the stream.
An unrecognized lock enum resolves to unavailable.
# Conflicts:
#	tests/components/teslemetry/test_ble.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant