Navigate to waypoints

The Navigate to waypoints action sends an ordered list of places to your Tesla vehicle’s navigation. The last place is the final destination. All earlier places are intermediate stops.

Use Google Place IDs to identify the places. You can find an ID with Google’s Place ID Finder.

Using this action from the user interface

If you prefer building automations and scripts visually, Home Assistant walks you through this action step by step. You pick what to target, tweak a few options, and save. No YAML knowledge required.

To send a trip from an automation or a script:

1. Go to Settings > Automations & scenes.
2. Open an existing automation or script, or select Create automation > Create new automation.
3. If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
4. In the Then do section, select Add action.
5. From the search box, search for and select Tesla Fleet: Navigate to waypoints.
6. Select the Vehicle to send the trip to.
7. Enter each Place ID in travel order. Put the final destination last.
8. Select Save.

Options in the UI

Using this action in YAML

If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required. For how an automation or a script is built in YAML, refer to Automations in YAML and Scripts.

In YAML, refer to this action as tesla_fleet.navigate_to_waypoints. A basic example looks like this:

action: tesla_fleet.navigate_to_waypoints
data:
  device_id: 0d462c0c4c0b064b1a91cdbd1ffcbd31
  place_ids:
    - ChIJVTPokywQkFQRmtVEaUZlJRA
    - ChIJQWCmo89rkFQRZQfQ6oJUz7o

Options in YAML

Good to know

• Supply the complete trip, including the final destination, in this action.
• The vehicle is woken up if needed, and the Vehicle Commands scope is required.
• The action sends the IDs you supply. It does not look up addresses or coordinates, or check the IDs with Google.
• Place IDs can change. Google recommends refreshing stored IDs older than 12 months. Update your saved IDs if a place moves or an ID stops working.
• Repeated IDs are forwarded unchanged.

Try it yourself

Ready to test this? Open Settings > Tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] without writing a line of YAML.

More examples

Real scenarios where this action shows up in automations and scripts. Copy any example and adapt it to your setup. In the visual editor, select the UI options listed in the example or paste the YAML code.

Automation: send the school run on weekday mornings

Every weekday morning at 7:30, send the school drop-off plus office route to the car so navigation is ready before you get in.

• Trigger: Time: 7:30 in the morning
• Condition: Monday to Friday
• Action: Navigate to waypoints, with the school stop and the office destination

alias: "Send school run on weekday mornings"
triggers:
  - trigger: time
    at: "07:30:00"
conditions:
  - condition: time
    weekday:
      - mon
      - tue
      - wed
      - thu
      - fri
actions:
  - action: tesla_fleet.navigate_to_waypoints
    data:
      device_id: 0d462c0c4c0b064b1a91cdbd1ffcbd31
      place_ids:
        - ChIJVTPokywQkFQRmtVEaUZlJRA
        - ChIJQWCmo89rkFQRZQfQ6oJUz7o

Automation: start a saved trip from your dashboard

Add a button to your dashboard that sends a saved multi-stop trip to the car. The button is an input button helperA helper is a virtual entity you create inside Home Assistant. It is not backed by a physical device. Helpers store values, track state, or do calculations that your automations and dashboards need. [Learn more] that you create separately.

• Trigger: Input button: pressed
• Action: Navigate to waypoints, with the saved stops

alias: "Start saved trip from dashboard"
triggers:
  - trigger: state
    entity_id: input_button.car_trip
actions:
  - action: tesla_fleet.navigate_to_waypoints
    data:
      device_id: 0d462c0c4c0b064b1a91cdbd1ffcbd31
      place_ids:
        - ChIJVTPokywQkFQRmtVEaUZlJRA
        - ChIJQWCmo89rkFQRZQfQ6oJUz7o

Still stuck?

To test the action on its own, run it in the automation editor with Run action, and check the message that it shows. To see what the action did when the automation ran, open the trace of that run. For details, refer to Testing automations. For common problems and their solutions, refer to Troubleshooting automations.

If that doesn’t help, the Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.

Related actions

Explore related actions:

• Navigate to destination: Sets the vehicle’s navigation to an address, place name, or map link.

• Navigate to coordinates: Sets the vehicle’s navigation to a specific latitude and longitude.