Paired Powerwall FAQ
Pairing gives Grid Getter its own key on your Powerwall’s gateway. With it, your Powerwall can hold a DemandGuard target itself, run Powerwall limits and charge rates, show Tesla app changes in your Activity Log, and fill in Powerwall Batteries.
Pairing
Section titled “Pairing”How do I pair my Powerwall?
Section titled “How do I pair my Powerwall?”Open Settings → Integrations, find Powerwall Pairing and choose Pair my Powerwall. You need a Scheduled plan or higher. Then take your phone, with the page still open, to your Powerwall. The gateway only accepts a new key while its switch is cycled:
- Find the On/Off switch on your Powerwall (on a Powerwall 3, it’s on the side).
- Turn it off, wait about 15 seconds, then turn it back on.
- Wait a few minutes while your Powerwall confirms.
You have 10 minutes from the start. Only the site’s owner can pair. Members and viewers see the button disabled, with the reason.
Pairing says “Not confirmed”
Section titled “Pairing says “Not confirmed””The 10 minutes ran out before the gateway confirmed the key. Usually the switch wasn’t cycled in time. Start again with the same steps and you get a new 10-minute window.
Pairing says “Couldn’t start”
Section titled “Pairing says “Couldn’t start””Tesla didn’t accept the request or couldn’t be reached. Nothing was added to your gateway, and the problem is usually temporary, so try again in a few minutes. If it keeps failing, check your Tesla connection (see Troubleshooting).
How do I remove pairing?
Section titled “How do I remove pairing?”In Settings → Integrations, choose Remove pairing. Grid Getter’s key comes off your gateway and the hourly check-ins stop. Your Tesla connection isn’t affected. You can also remove the key in the Tesla app. To pair again later, choose Pair again and cycle the switch again.
How Grid Getter makes sure paired DemandGuard works
Section titled “How Grid Getter makes sure paired DemandGuard works”This applies to accounts where paired DemandGuard is turned on, which is a small group for now while it rolls out. When your Powerwall holds the target itself, Grid Getter is relying on the gateway to keep your grid draw at that number. So it checks each firmware version, both before it trusts it and after.
Every firmware version is watched
Section titled “Every firmware version is watched”Tesla updates gateway firmware on its own schedule. Grid Getter records each new version the first time any paired Powerwall reports it.
After every paired DemandGuard window, Grid Getter checks what actually happened: whether the Powerwall held the target when it had the battery to do so, and whether it accepted the change back at the end. A window that passes counts toward trusting that version.
- A version Grid Getter hasn’t measured itself is trusted after 3 clean windows on 2 different sites.
- A bigger version jump needs 5 clean windows on 3 sites.
Hardware gets the same treatment. A single Powerwall 3 has been measured and is trusted. Powerwall 2 and systems with more than one Powerwall 3 are watched the same way as a new firmware. Mixed systems don’t run paired DemandGuard.
What happens when a check fails
Section titled “What happens when a check fails”- Your site is held for 7 days. The first time a window fails on your Powerwall, your site goes back to classic DemandGuard on that firmware for 7 days. Your rule keeps running the classic way, with Grid Getter managing the battery minute by minute instead of handing the target to your Powerwall. Meanwhile, Grid Getter looks into the failure.
- A second site blocks the version for everyone. If the same firmware fails on a second, different site, every paired Powerwall on that firmware moves to classic DemandGuard until Grid Getter has checked it and cleared it.
One site failing never blocks a version for everyone. A single bad window can have nothing to do with the firmware. A utility program or a change made in the Tesla app can cause it too.
What you’ll see
Section titled “What you’ll see”Nothing changes in your rules. The DemandGuard editor shows “Grid Getter is using classic DemandGuard on this firmware for now,” with the version number. When the hold ends or the version is cleared, your Powerwall goes back to holding the target on its own. You don’t need to do anything.
Paired DemandGuard
Section titled “Paired DemandGuard”Paired DemandGuard is rolling out and is off for most accounts. Until it’s on for yours, every DemandGuard rule runs classic, even on a paired Powerwall. The editor shows no engine choice and no message about it, and nothing in this section applies yet.
Why is my rule using classic DemandGuard?
Section titled “Why is my rule using classic DemandGuard?”Where paired DemandGuard is on for your account, the DemandGuard editor tells you why a rule is running classic:
| Message | What it means |
|---|---|
| Grid Getter is using classic DemandGuard on this firmware for now | Your firmware is on hold for your site or blocked for everyone. See What happens when a check fails. |
| Can’t read your Powerwall’s firmware | Grid Getter couldn’t read the version from your gateway, so it can’t tell whether the version is trusted. |
| Not yet verified on your Powerwall hardware | Your system’s hardware hasn’t passed enough clean windows yet. |
| Can’t reach your Powerwall’s gateway | Check-ins have failed for over a day and the pairing shows Needs attention. See below. |
| Can’t reach your Powerwall’s paired connection | Recent check-ins with your gateway failed. See below. |
| Available on Adaptive plans or higher | Paired DemandGuard is part of the Adaptive plan. |
Either way, your rule still runs as classic DemandGuard.
”Can’t reach your Powerwall’s gateway”
Section titled “”Can’t reach your Powerwall’s gateway””If every check-in fails for 24 hours in a row, the pairing shows Needs attention in Settings → Integrations and on the Batteries page. Your pairing stays in place. Your automations use Tesla’s cloud and classic DemandGuard for now, and Grid Getter stops checking hourly and tries again every 6 hours. One successful check-in clears the warning and paired DemandGuard comes back on its own.
The owner can press Check connection now to try right away. If it keeps failing, check that your Powerwall is online in the Tesla app, or remove the pairing and pair again. Members and viewers see a note naming the owner, who can check the connection.
”Can’t reach your Powerwall’s paired connection”
Section titled “”Can’t reach your Powerwall’s paired connection””Grid Getter checks in with your gateway every hour. If check-ins keep failing, it uses classic DemandGuard until they work again. Usually the gateway is offline or has dropped off your home network.
First check that the Tesla app shows your Powerwall online. Then open Settings → Integrations, where the pairing shows Test again after a failed check-in. Once a check-in works, paired DemandGuard comes back on its own. The next hourly check-in will also try again without you doing anything.
My battery did something Grid Getter didn’t tell it to
Section titled “My battery did something Grid Getter didn’t tell it to”A paired Powerwall still answers to Tesla. A utility or virtual power plant (VPP) program, Storm Watch, or a change made in the Tesla app can override what Grid Getter set.
On a paired site, changes made in the Tesla app show up in the Activity Log Changes tab, so you can see who changed what. If you’re enrolled in a utility battery program, its events can stop your battery from covering your home for a while.
My battery reached its floor during the window
Section titled “My battery reached its floor during the window”With Lower my demand, your battery covers spikes above your target. When it has enough charge to last to the end of the window, it runs your home down to your floor. If it hits the floor, the Last window card on the rule says so and shows the time. A higher floor keeps more in reserve for spikes. A lower one saves more but leaves less for a late spike. If your floor leaves little room, the editor shows roughly how much energy you have to work with.
Still stuck?
Section titled “Still stuck?”Contact support with your site name and roughly when it happened. The Gateway details section under your pairing in Settings → Integrations lists your gateway’s firmware and key state, which helps us find the problem faster.