The Tesla app isn't bad. For most Powerwall owners, it's where you set Time-Based Control, watch your solar generation, and feel good about your energy independence. That's fine, until you're on a rate plan with demand charges and realize it's costing you $40–$80 a month you didn't need to spend.
The gap isn't about hardware. Your Powerwall can do more than the Tesla app asks of it. The gap is software: what gets monitored, when it reacts, and how precisely it understands your specific utility's billing structure.
What Time-Based Control Actually Does
Time-Based Control lets you set windows for when the Powerwall should charge (cheap off-peak hours) and when it should discharge (expensive peak hours). Self-Powered mode prioritizes consuming your own solar generation before pulling from the grid.
Both modes are passive. They follow a schedule. Neither one watches your real-time grid draw and adjusts battery output to hold you under a specific wattage threshold.
That distinction matters a lot if you're on SRP's E-27, APS's R-3, or any plan that charges you based on your peak demand interval — not just how many kWh you consumed.
Here's what passive scheduling can't prevent: you've got Time-Based Control set to discharge during APS's 4–7 PM peak. The Powerwall starts pushing power. Your home is drawing 7 kW, Powerwall is outputting 5 kW, grid draw is 2 kW. Fine.
Then your AC compressor kicks on during a heat soak at 5:45 PM. Home draw jumps to 10 kW. The Powerwall doesn't know your demand target. It keeps outputting 5 kW. Grid draw just spiked to 5 kW — and if that spike holds for 15 minutes on APS, that's your new demand peak for the billing period. At around $13–$16 per kW on APS R-3 demand tiers, a 3 kW overage you could have prevented just cost you $39–$48.
DemandGuard: Active Capping
DemandGuard works differently. It monitors your real-time grid draw continuously and adjusts Powerwall discharge to keep you under a target kW limit you set.
Same scenario: 10 kW home load, Powerwall currently at 5 kW output. DemandGuard sees grid draw climbing toward 5 kW and ramps Powerwall output up to its rated ceiling if needed, keeping your grid draw at or below your target, say 2 kW.
It's not reacting to a schedule. It's reacting to what's actually happening at your meter right now.
The difference in bill impact compounds over a full billing period. One uncontrolled spike on a demand-charge plan can wipe out weeks of careful overnight charging. DemandGuard's job is to make sure that spike never registers.
Your Rate Plan Is Specific. Tesla's Modes Aren't.
SRP measures your demand in 30-minute intervals. APS uses 15-minute intervals. PG&E's E-TOU-C plan has peak windows that shift seasonally. These aren't details you can paper over with a generic "discharge during peak hours" setting.
On SRP's E-27, your demand charge is based on the highest average kW draw during any single 30-minute window in the on-peak period on weekdays — confirm the exact current hours against your tariff, since SRP has adjusted these seasonally. If you miscalculate and your battery starts discharging 15 minutes late, you've already taken a demand hit for that half-hour window.
Grid Getter lets you build rules tied to your actual rate plan, not the clock. You can set a rule that pre-charges the battery to 100% by 3:30 PM on weekdays so you're fully loaded before APS's 4–7 PM window opens. Or a rule that reserves a specific state-of-charge percentage exclusively for demand management, separate from whatever you've committed to backup reserve.
The Tesla app has a backup reserve slider. It doesn't have "hold 40% for demand management between 4–7 PM on weekdays, then release to self-powered mode after 7 PM." That level of specificity requires custom rules.
kW vs. kWh: The Number That Actually Drives Your Bill
Most homeowners think about electricity costs in terms of kWh — how much energy they used. That's the right metric if you're on a flat-rate or simple TOU plan.
But if you're on a demand-charge rate, your bill is driven by two separate numbers: kWh consumption and peak kW demand. The demand charge often hits harder than the consumption charge. On SRP's E-27 plan, the on-peak demand charge alone can run around $17 per kW. That figure is based on a single 30-minute window, not your average behavior.
Optimizing for kWh reduction (which is what Self-Powered mode does well) doesn't automatically optimize for demand reduction. You can cut your consumption by 30% and still take a demand hit if one bad spike goes unmanaged during a billing interval.
DemandGuard targets the demand number directly. It doesn't try to minimize how much energy comes from the grid; it keeps the rate of that draw under a threshold, measured across the specific interval your utility uses for billing.
The Setup Question
One reason people stick with the Tesla app: it's already there. Setup is minimal. DemandGuard, custom pre-charge rules, anomaly notifications. That sounds like work.
In practice, Grid Getter setup takes about 10 minutes. You select your utility and rate plan, set your demand target, configure your peak window, and turn on DemandGuard. The pre-charge rules use a simple interface — pick a time, pick a target state of charge, pick which days it applies. You don't need to write code or understand your utility's tariff document in detail; Grid Getter knows the billing intervals for SRP, APS, PG&E, SCE, and SDG&E already.
The payoff depends on your rate plan. If you're on a flat residential rate with no demand charges, Time-Based Control is probably enough. But if you're on APS R-3, SRP E-27, or any plan where peak demand shows up as a line item on your bill, the math on active demand management gets favorable quickly.
If you want to see what DemandGuard would do on your specific setup, Grid Getter is free to try at gridgetter.com/free/ — no credit card, no commitment. The first thing worth doing after you connect: pull up your last utility bill and find the demand charge line. That number is what you're optimizing against, and it's usually bigger than people expect.