Use the Tesla Fleet API to read and control a Powerwall site's Storm Watch (storm mode) participation as a backup-power automation signal
domain: developer.tesla.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm Tesla's official Fleet API (developer.tesla.com/docs/fleet-api) publishes documented Energy Endpoints for Powerwall/energy sites, including live_status (GET, returns power, state of energy, grid status, and storm mode) and storm_mode (POST, updates storm watch participation)
Register a developer account and set up authentication per Tesla's Partner Tokens/Third-Party Tokens flow described in the Fleet API auth docs before calling any energy_site endpoints
Use site_info to confirm a given energy site is storm_mode_capable before attempting to read/write storm-mode state, since not all sites support the feature
Cross-reference Tesla's consumer-facing Storm Watch support article (tesla.com/support/energy/powerwall/mobile-app/storm-watch) for the feature's intended behavior (automatic charge-to-max ahead of severe weather) versus the raw API fields
Known gotchas
This is a solar+battery storm-preparedness feature, not a generator-specific API — Powerwall's 'storm mode' maximizes battery charge ahead of a forecast outage, it does not control or coordinate with a separate standby generator
Tesla Fleet API access requires a Tesla developer account and is subject to Tesla's billing/rate limits (see developer.tesla.com/docs/fleet-api/billing-and-limits) — don't assume unlimited/free access for a commercial integration
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?