Tescmd

Tesla Vehicle Control (tescmd)

Control and monitor Tesla vehicles through the OpenClaw Gateway. This skill covers runtime usage — for installation and setup, see the tescmd_install skill.

Prerequisites

• tescmd node running and connected to the Gateway (preferred), OR
• tescmd CLI installed locally (fallback mode)
• Vehicle paired and authenticated

Version Note: The plugin and tescmd node versions are independent — they do not need to match. The plugin provides agent tools that invoke commands on whatever node version is connected.

Verify connection:

openclaw nodes status

Or use the agent tool: tescmd_node_status

CLI Fallback: If no node is connected but the tescmd CLI is installed, basic commands (lock, unlock, climate, charge, honk, flash) and data queries (battery, temperature, location) will fall back to CLI execution. Response includes { fallback: true } when CLI is used.

Quick Commands

Vehicle Status

Climate Control

Security

Charging

Trunk/Frunk

Navigation

Supercharger Discovery

Find Tesla Superchargers anywhere, powered by supercharge.info:

Example Workflows

Road trip planning:

"Road trip to Asheville — find Superchargers along the way"
→ Get Asheville coords with goplaces
→ tescmd_superchargers_route with start/end coords
→ Returns Superchargers with distance, stall count, power level

Find charging near destination:

"Is there a Supercharger near the restaurant?"
→ Get restaurant coords
→ tescmd_superchargers_near
→ Returns closest Superchargers with distance

Telemetry Triggers

Set up alerts when telemetry values cross thresholds. Triggers are push-based — when a trigger fires, the tescmd node automatically notifies the agent. You don't need to poll; just create the trigger and respond when notified.

Note: Use domain-specific trigger tools for type safety and correct units. The generic trigger tool has been removed to prevent unit/format errors.

How Triggers Work

1. Create a trigger with a condition (e.g., battery < 20%, location enters geofence)
2. The node monitors telemetry in real-time
3. When the condition fires, the node pushes a notification to the agent
4. The agent responds by taking the requested action

This enables automation like:

• "When I arrive at the gym, post on X that I'm working out"
• "When battery drops below 20%, text me"
• "When cabin temp exceeds 100°F, turn on climate"

Manage Triggers

Note: Triggers are push-based. When a trigger fires, the agent receives a system event automatically — no polling required.

Trigger Tools

Always use these domain-specific tools:

Trigger Operators

• lt, gt, lte, gte — less/greater than
• eq, neq — equals / not equals
• changed — any value change
• enter, leave — geofence (location triggers)

Example: Low Battery Alert

Create a trigger to alert me when battery drops below 20%
→ tescmd_battery_trigger with operator="lt", value=20
→ When fired, the node notifies the agent automatically

Example: Geofence Automation

"When I park at the gym, post on X that I'm working out"
→ Use goplaces to get gym coordinates
→ tescmd_location_trigger with operator="enter", lat=39.109, lon=-77.550, radius=100
→ When vehicle enters the geofence, node notifies agent
→ Agent generates image and posts to X

Common Workflows

Pre-conditioning Before a Trip

1. Check current temperature: tescmd_get_temperature
2. Turn on climate: tescmd_climate_on
3. Optionally set temp: tescmd_set_climate_temp with desired °F
4. Check battery: tescmd_get_battery

Send a Route to the Car

1. Use tescmd_nav_send with the destination address
2. Or use tescmd_nav_gps for exact coordinates
3. For multi-stop routes, see "Multi-Stop Routes with Waypoints" below

Multi-Stop Routes with Waypoints

The tescmd_nav_waypoints tool requires Google Place IDs. If the goplaces skill is installed (requires GOOGLE_PLACES_API_KEY), the agent should automatically resolve addresses to Place IDs.

Agent behavior for multi-stop routes:

1. User requests a multi-stop route (e.g., "send my beach route to the car")
2. Check if goplaces is available (look for the skill in available_skills)
3. For each stop address, run: goplaces resolve "<address>" --json
4. Extract the place_id from each result (it's in the JSON array: [0].place_id)
5. Combine Place IDs into a comma-separated string
6. Call tescmd_nav_waypoints with the combined waypoints

Example:

User: "Load my beach route: coffee at Hornes Port Royal, Supercharger in Tappahannock, then OBX"

Agent:
1. goplaces resolve "Hornes, Port Royal, VA" --json → ChIJn7WjLIHYtokRCOgQWXQZ5l8
2. goplaces resolve "Tesla Supercharger Tappahannock, VA" --json → ChIJwSd9CKXLsIkR4QPmAJuAO1I
3. goplaces resolve "Outer Banks, NC" --json → ChIJcWxzpzxbpIkRszbSdWERdxs
4. tescmd_nav_waypoints with waypoints="ChIJn7...,ChIJwS...,ChIJcW..."

Note: If goplaces is not configured, inform the user that multi-stop routes require the Google Places API.

Plan a Road Trip with Charging

1. Get start/end coordinates
2. Call tescmd_superchargers_route to find Superchargers along the way
3. Review options (stall count, power level, distance)
4. Send destination with tescmd_nav_send

Monitor Charging

1. Check state: tescmd_get_charge_state
2. Check level: tescmd_get_battery
3. Set limit if needed: tescmd_set_charge_limit
4. Start/stop: tescmd_start_charge / tescmd_stop_charge

Error Handling

Slash Commands

Quick commands available from chat (14 total):

Tips

• Wake time: If the car is asleep, commands may take 10-30 seconds as it wakes
• Signed commands: Door lock/unlock use signed Vehicle Command Protocol for security
• Telemetry: Real-time data (location, temp, battery) comes from Fleet Telemetry stream — instant when available, falls back to API polling
• Triggers: Require telemetry streaming enabled (default). Use --fields all when starting the node for full coverage.
• Superchargers: Data from supercharge.info, cached for 1 hour. Community-maintained, 10,000+ locations worldwide.

Full Reference

Call tescmd_help for the complete tool reference with all parameters and detailed descriptions.