Activity Log
The Activity Log is your full audit trail — every automation that fired, every DemandGuard decision, and every notification you’ve received. It’s the first place to look when you want to understand what Grid Getter has been doing on your behalf.
To get there: click Activity Log in the top navigation, or visit app.gridgetter.com/activity-log.
The Activity Log has four tabs:
Automation Logs
Section titled “Automation Logs”A feed of every time an automation executed, newest first.
Each entry shows:
- Automation type — a color-coded icon and badge (Custom Schedule, Peak Time, DemandGuard, Battery Protection)
- Date and time the action ran, in your local timezone, plus how long ago it happened (e.g. “5m ago”)
- What happened — the action message, with the specific setting it changed (e.g. a mode or reserve percentage) called out as its own highlighted chip
Pre-Peak Charge also logs its battery hold here:
- “Holding the battery at N%”: the forecast needs a grid top-up, so the battery is held until the top-up starts
- “Released the battery hold”: the hold ended, with the reason (for example solar should cover the rest before 5:00 PM., peak period starting. or the reserve was changed to 15% outside Pre-Peak Charge, so it stays there.)
Custom Schedule Powerwall limits (paired Powerwalls, rolling out) log when they’re requested, when one couldn’t be set and why, and when the battery reaching your floor ended one early.
When a paid plan ends and a DemandGuard, Peak Time or Pre-Peak Charge rule finishes its last window, it logs “Turned off because your plan ended.” When DemandGuard puts your reserve back on the way out, the entry adds the level, for example Battery reserve restored to 20%. See When your plan ends.
If you pause your automations during a Peak Time or DemandGuard window, the entry starts “Automations paused, so the Powerwall was put back” and lists what was restored. If it couldn’t be put back, the entry reads “Automations paused, but the Powerwall could not be put back. Check the Tesla app.” A pause also adds its own lines. Each Custom Schedule, Peak Time and DemandGuard rule that’s on logs “Automations paused by Sam Lee through Nov 9.” when the pause is set and “Automations resumed by Sam Lee.” when it ends, with the name of whoever tapped. If a rule reaches its start time during a pause, it logs Automations paused: “Rule name” did not start. Paused by Sam Lee through Nov 9. (and sends a push, see Notifications) Beyond those, rules skipped by a pause log nothing here. DemandGuard still records readings during a paused window, so the DemandGuard Decisions tab keeps filling, but none of those minutes touched the battery.
Filters available:
- Time range — last day, or a custom date and time range
- Automation type — select one or more types, or leave blank to show all
Changes
Section titled “Changes”A record of every change to the site’s settings, newest first, under day headings (Today, Yesterday, then the date). Each entry shows the time, who made the change, and what changed, with the old and new value where Grid Getter knows both. Changes saved together, such as a new operating mode and reserve in one save, appear as one entry. Automation changes name the automation, unless it has since been deleted. Settings covered include battery reserve, operating mode, grid charging, energy exports and Storm Watch.
To see one setting’s history, pick it from the row of filters above the list. The filtered view also shows the setting’s current value. Show more at the bottom loads older changes.
Each change shows who made it:
- A person, by name (never an email address)
- An automation, by its name
- Grid Getter support, when our team made the change for you
- Outside Grid Getter, when the setting changed somewhere else, such as the Tesla app
Everyone who has access to the site can see this tab, whether they own it or were invited. People appear by name only.
A person’s change also shows the device it came from, after their name: “Chrome on macOS” on the web, or “iOS” or “Android” in the apps. Changes made by Grid Getter support show no device.
When an automation is edited, the entry lists each field that changed, for example End 9:00 PM → 10:00 PM. An automation you’ve deleted keeps its name in older entries. Holiday calendar changes get their own line too.
An automation’s change also says why it happened, in a short line such as Held the battery: demand 4.20 kWh under the 5.00 kWh target, Window started, Site paused or Restored after the Powerwall reconnected. A View in log link opens the matching entry in Automation Logs, filtered to that automation an hour either side, or in DemandGuard Decisions.
If an automation couldn’t change a setting, the entry says so in red, for example DemandGuard · Weekday peak couldn’t set backup reserve to 20%: Tesla rate limit. The same failure repeating within an hour shows once with a count, like “×3”. A failed attempt never counts as the setting’s current value. Your own failed changes don’t appear here, because the app already showed you the error.
Changes made in the Tesla app show up only for sites with a paired Powerwall. Grid Getter checks about once an hour, so a Tesla app change can take up to an hour to appear. Storm Watch changes made in the Tesla app don’t appear, because Grid Getter can’t see them. On a site that isn’t paired, the tab shows “Pair your Powerwall to see changes made in the Tesla app.”
Grid Getter keeps about a year of changes. Older ones are archived and no longer shown here.
DemandGuard Decisions
Section titled “DemandGuard Decisions”Switch between two views with the Cards / Table toggle above the log.
Grid Getter groups your DemandGuard readings into runs — continuous stretches while DemandGuard is actively managing your battery — and splits each run into numbered periods based on your DemandGuard automation’s demand interval (30 minutes by default, or whatever interval you’ve set). The header above the log shows how many runs are in view; on a site where DemandGuard runs continuously, you may see just one run with no breaks.
Cards view (the default) shows your current run at the top, labeled Current Run with its active mode (e.g. “Solar Surplus”) and a live end time that reads ”– now”. Older activity is grouped underneath by day under Previous Runs. Each period card shows:
- Its time range and reading count, plus X min left while it’s still active
- A totals strip — Total Grid, Total Battery, and Total Solar (kWh) for the period, your Battery Range, and Period Demand (kWh)
- A Paused badge, with the time range, on any period the site pause covered, even partly. Consecutive fully paused periods fold into one card (for example Periods 3–6) that spans the whole pause.
- Individual readings — the active period’s most recent reading is shown automatically; click Show N earlier measurements, or the period header, to see the rest. Each reading shows whether Grid Getter drew from grid or battery, your battery percentage, Storm Watch status, the Grid + Battery + Solar breakdown that made up your load, and the action taken.
Table view lists the same readings as rows in a sortable table, with a banner above the first row of each run reading Active Run or Completed Run and its time range.
Some entries reflect DemandGuard’s self-checks rather than threshold decisions:
- “Re-asserted” — Tesla hadn’t complied with an earlier command within a few minutes, so it was re-sent. A battery already at its reserve doesn’t get this, because it can’t discharge any lower
- “Re-disabled grid import” — Tesla quietly resumed grid charging mid-window and the pause was re-sent
- “Reserve returned to N%” — a grid hold released and the reserve went back where it belongs
- Backfilled — a missed check’s minutes were filled in automatically, assuming the same reading as the next real measurement
This log is useful for verifying that DemandGuard is working correctly and reviewing how well it protected you during high-demand periods.
The log stays readable after your plan ends or drops below Adaptive, as long as the site still has a DemandGuard automation (on or off). An Adaptive upgrade card sits above it. Without Adaptive and without a DemandGuard automation, the tab shows only the upgrade card.
Notifications
Section titled “Notifications”A history of all in-app notifications — the same items that appear in the notification bell, but with full history and pagination.
You can scroll back through older notifications here even if they’ve been cleared from the notification panel.
Filter the list with the All / Alerts / Automations toggle above it — each button shows a count. Notifications about an automation firing are grouped under Automations; everything else (battery anomalies, threshold alerts, and other system notices) falls under Alerts. Unread notifications show a count next to the header and stay highlighted until you open them.
Loading more history
Section titled “Loading more history”Each tab shows recent entries by default. Click Load More at the bottom of the list to load older records.
Exporting logs
Section titled “Exporting logs”For a full export of your automation logs and energy history, use the Data Export feature in Settings → Data.