Full control of your Powerwall and Tesla, wherever you automate

A few weeks ago I wrote about being able to force charge and force discharge a Powerwall for the first time. That was one command, in one client. The goal since then has been bigger: whichever home automation platform you use, you should be able to do everything with your Powerwall and your Vehicle that the hardware allows, from your own automations, and over your local network wherever possible.
This week a lot of that landed at once. Here's what "full control" means now, and where to find it in Home Assistant, Homey, Node-RED and n8n.
What full control means
- Every command. Every (safe) vehicle and energy site command is in the Teslemetry API. If the API can do it, your automation can.
- Local first. Powerwall commands go straight to the Powerwall on your local network when your client is paired with it, and fall back to the cloud only when they need to. Vehicle commands can go over Bluetooth in Home Assistant and Homey. Local commands are faster, keep working when the internet doesn't, and don't use command credits.
- Island mode. Take your home off the grid and reconnect it from an automation, the same as the Go Off-Grid button in the Tesla app.
- Battery dispatch. Charge or discharge the Powerwall at a power you choose (up to 10kW) for as long as you choose, then let it go back to normal by itself.
- Charge on Solar. Turn on Tesla's Charge on Solar for your car, so it charges from excess solar and stops when the excess runs out, with a lower limit so it never sits too low.
Keys to the kingdom required
Some energy commands, including island mode and battery dispatch, have to be signed with a key your Powerwall trusts. There are two ways to get that:
- Pair your client with the gateway on your local network. Commands go direct, and this is the fastest option.
- Pair Teslemetry with your Powerwall from Powerwall setup on your energy site in the Console. Teslemetry then signs those commands for you through the cloud, so they work from anywhere, and from clients that can't reach your gateway.
Either way you need physical access to the Powerwall once, to flick its switch off and on to approve the key. With both set up, clients that support local control try the gateway first and use Teslemetry as the fallback.
Home Assistant
Home Assistant already has the most local control of any client. Bluetooth vehicle control and local Powerwall control shipped in 2026.10, and 2026.11 added two more:
- Dispatch battery power and Resume battery operation actions charge or discharge your Powerwall locally, at a set power for a set time.
- A Charge on solar switch and Charge on solar lower limit number for each vehicle, behind a Labs preview. Turn it on under Settings > System > Labs. The upper limit is the car's existing charge limit.
# Charge from excess solar, but never let the car sit below 50%
- action: number.set_value
target:
entity_id: number.YOUR_VEHICLE_charge_on_solar_lower_limit
data:
value: 50
- action: switch.turn_on
target:
entity_id: switch.YOUR_VEHICLE_charge_on_solar
Homey
Homey has caught up fast. Version 1.7.0 brought local control: turn on Connect over the local network in the Powerwall's settings, or Connect over Bluetooth in the car's, and commands go straight to the device. 1.8.0 added Flow cards to charge or discharge the Powerwall at a set power for a set number of minutes, and to resume normal operation early.
Homey 1.9.0 adds:
- Go off-grid and Reconnect to the grid Flow cards on the Gateway device, sent straight to the gateway when the local connection is on, and otherwise through Teslemetry. If the Powerwall refuses, for example because the charge is too low, the card fails with the reason, rather than failing silently.
- Charge on Solar Flow cards to turn it on or off for your car, with a lower limit.
Put them in any Flow you like, and use the existing Island mode activated and Island mode deactivated triggers to know when the change has taken effect.
Homey Flow cardsNode-RED
Node-RED got the biggest change. The Vehicle Command and Energy Command nodes now list every Teslemetry API command, grouped, with the credit cost shown, and a field for each argument. Each field can be a fixed value or come from msg, flow, global, an environment variable or JSONata, and arguments are checked against the API's allowed values before anything is sent. Nodes you've already built keep working unchanged.
The Energy Command node also has a Route setting:
- Automatic sends to your Local gateway first and falls back to the cloud, as before.
- Local only never touches the cloud.
- Cloud only never uses your local network.
Island mode is in there too, local first through your gateway. You can also run any command by name from a Function node:
// Charge the Powerwall at 5 kW for 30 minutes
msg.command = "dispatch_battery_power";
msg.payload = { power_watts: -5000, duration_seconds: 1800 };
return msg;
There's a Charge on Solar example flow to get you started under Import > Examples.
Vehicle commandsEnergy commandsn8n
n8n sends its commands through the cloud. The Energy node now has a Set Island Mode operation to go off-grid or reconnect to the grid. It lists only the sites Teslemetry is paired with, since those are the ones it can sign the command for.
n8n Energy nodeNo platform at all
If you don't run any of these, Teslemetry now has its own automations. They run vehicle and Powerwall commands on a schedule, or when your car's telemetry changes, with nothing running at home. They're in alpha, and you'll find them in the Console under Utilities > Automations.
What's next
The goal is to keep finding and exposing every command surface we can, so that Teslemetry is the best way to take full control of your Tesla products.
As always, let me know what you build with it on Discord.