Skip to content

Fix Tesla Fleet charge current scope handling#166919

Open
Bre77 wants to merge 1 commit intohome-assistant:devfrom
Bre77:conductor/teslafleet-cmdscope
Open

Fix Tesla Fleet charge current scope handling#166919
Bre77 wants to merge 1 commit intohome-assistant:devfrom
Bre77:conductor/teslafleet-cmdscope

Conversation

@Bre77
Copy link
Copy Markdown
Contributor

@Bre77 Bre77 commented Mar 30, 2026

Proposed change

Correct the Tesla Fleet charge_state_charge_current_request number entity to use either vehicle_charging_cmds or vehicle_cmds.
https://developer.tesla.com/docs/fleet-api/endpoints/vehicle-commands#set-charging-amps

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

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:

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request fixes the Tesla Fleet charge_state_charge_current_request number entity to accept either VEHICLE_CHARGING_CMDS or VEHICLE_CMDS scopes, matching the behavior of the set_charging_amps API command and preventing the entity from being incorrectly treated as read-only when an application has the broader VEHICLE_CMDS scope.

Changes:

  • Updated the charge_state_charge_current_request entity scopes to include both VEHICLE_CHARGING_CMDS and VEHICLE_CMDS, making it consistent with the charge_state_charge_limit_soc entity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants