10000 Added navigation commands to tesla_fleet by alexw23 · Pull Request #145854 · home-assistant/core · GitHub
[go: up one dir, main page]

Skip to content

Added navigation commands to tesla_fleet #145854

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.

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

Closed

Conversation

alexw23
Copy link
@alexw23 alexw23 commented May 29, 2025

Proposed change

This adds services to send navigation requests to a Tesla. If the car is in standby it will appear once you hop in. If the car is active it will override the current route.

The services that have been added are:

  • tesla_fleet.navigate_to_supercharger_request - sends a request to navigate to a specified supercharger. The car will also initiate preconditioning (if required).
  • tesla_fleet.navigation_gps_request - sends a navigation request in lat/long format
  • tesla_fleet.navigation_request - sends a navigation request in the form of free text (i.e. Ally's Bakery, or 123 Smith St NY, or https://maps.app.goo.gl/bvFT69n4rq6Jcfau9)
  • tesla_fleet.share_to_vehicle - can be used to either send a maps URL or a YouTube URL (i.e `https://www.youtube.com/watch?v=dQw4w9WgXcQ). When sharing YouTube it will popup on the screen.

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

  • 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 r 8000 ecommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

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 link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

Copy link
@home-assistant home-assistant bot left a comment

Choose a reason for hiding this comment

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

Hi @alexw23

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

@home-assistant
Copy link

Hey there @Bre77, mind taking a look at this pull request as it has been labeled with an integration (tesla_fleet) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tesla_fleet can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign tesla_fleet Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@Bre77
Copy link
Contributor
Bre77 commented May 29, 2025

The project usually likes library bumps done separately, so I'll make a PR and push 1.1.1 shortly.

@Bre77
Copy link
Contributor
Bre77 commented May 29, 2025

Rebase after #145869 is merged.

@alexw23
Copy link
Author
alexw23 commented May 30, 2025

Thanks @Bre77 will rebase and push up once merged.

@alexw23
Copy link
Author
alexw23 commented May 31, 2025

@Bre77, this has been merged with the 1.1.1 bump. Free to approve.

Copy link
Author
@alexw23 alexw23 left a comment

Choose a reason for hiding this comment

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

Ready for merge

@alexw23
Copy link
Author
alexw23 commented Jun 18, 2025

@Bre77 any idea if there's anything outstanding on this or is it usual to take a few weeks to be approved?

@alexw23 alexw23 closed this Jun 23, 2025
@alexw23
Copy link
Author
alexw23 commented Jun 23, 2025

Closing as this isn't going anywhere.

@github-actions github-actions bot locked and limited conversation to collaborators Jun 24, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0