Save a traceable record before the monitoring context changes
Before solar service or an account change, export the monitoring history currently available through your authorized owner access and preserve its actual date range, site identity, units and channel definitions. Keep the original file unchanged and label missing data honestly. An export is evidence of what the platform recorded, not a guarantee of complete production, system health, billing accuracy or access after a transfer. Do not wait until a change removes your present opportunity to retain a record.
This guide addresses the record-preparation task, not repairing connectivity or diagnosing low production. Tesla’s current Energy Data and solar-monitoring support pages provide a named platform example. Other manufacturers, equipment arrangements and app versions may offer different channels or export options. Use the actual owner documentation and support response. This article does not request access to your account, recommend a paid tool or authorize installer controls, credentials sharing or electrical work.
Name the question the record needs to answer
Write the purpose before downloading: documenting a service complaint, retaining the pre-change history, comparing observations around an appointment, or supplying an authorized provider with requested information. A bounded question helps select useful dates rather than collecting an unlabeled file that nobody can interpret. Ask the recipient which available channels and period they need and whether a screenshot or native export is appropriate for that specific request.
Identify the actual site and equipment from existing records: solar inverter arrangement, any battery and gateway, and whether the platform monitors solar alone or additional household flows. Tesla distinguishes its Solar Inverter and third-party-inverter monitoring arrangements. Do not assume every chart represents every circuit or asset. A solar-production channel is not interchangeable with household consumption, grid flow or battery charging; the presence or absence of a chart needs to be recorded as part of the scope.
Use the native export without inventing its resolution
Tesla’s Energy Data page describes Download My Data in the app and a CSV based on the selected period and timescale. Follow the current instructions available for your authorized system. The page’s specific interval description for Powerwall charge should not be generalized to every exported channel. Record the actual column names and timestamps in the file you receive. If an option is unavailable, ask support rather than fabricating a download or using somebody else’s access.
Keep a short export note: date obtained, platform and app context, selected window, site identifier appropriate for the recipient, visible units and whether the file covers the requested period. Preserve the downloaded original before opening a working copy. Do not overwrite it with a spreadsheet that converted timestamps, rounded values or removed rows. A readable working copy can help analysis, but it should remain clearly separate from what the platform originally supplied.
A usable export states its boundaries
This is a documentation framework rather than a performance test. An unexplained header or time convention should become a support question, not a guessed conversion. Keep each uncertainty visible in the handoff. The provider can then tell you whether the available record addresses the case or whether other evidence is needed without mistaking your edited interpretation for the native data.
| Check | What to retain | What not to assume |
|---|---|---|
| Date coverage | Actual beginning, end and gaps | The whole requested period exists |
| Channel identity | Original headers and meanings | Battery or grid flow equals solar production |
| Units and timestamps | Actual labels and time convention | Every column uses the same interval or unit |
| Source file | Unchanged native download | A reformatted sheet is the original |
| Complaint context | Known service or connectivity events | A missing interval means zero generation |
Check readability and completeness without changing the evidence
Open a copy using a tool you already have permission to use and confirm that columns and rows are readable. Check whether the beginning and end match the intended selection and whether the apparent time convention is understood. If it is unclear, ask the platform or recipient. Do not silently shift timestamps to make an event line up or delete inconvenient gaps. Record what the file shows and what you cannot yet interpret.
Look for coverage limitations rather than declaring the data complete because the download succeeded. A selected window can still contain unavailable intervals or channels your installation does not monitor. Do not replace blanks with zeros or reconstruct values from a chart unless the provider explicitly requests a separately labeled estimate. A chart screenshot can preserve display context, but it does not expand the native file’s coverage or certify the accuracy of a calculation you make later.
Attach event context that is known, not a cause you inferred
Create a brief chronology of known service appointments, documented equipment changes, connectivity interruptions and account-access changes relevant to the selected period. State the source of each entry, such as an appointment confirmation or your observation of unavailable monitoring. Keep a technician’s diagnosis separate from your observation. An interval missing from the app is not, by itself, proof that the inverter stopped producing or that a repair caused a fault.
If physical damage, water near equipment, smoke or another safety concern is present, the urgent response takes priority over exporting history. Do not approach damaged equipment for labels, climb onto a roof or open an enclosure to improve the record. The file-preparation workflow involves ordinary authorized app access and existing documents only. A useful monitoring packet must not require the owner to put themselves in danger merely to provide a more complete support submission.
Protect access and share only the needed record
Confirm the recipient through the service provider’s established communication route before sending monitoring files. Review whether the export includes information about household activity or other details beyond the case’s need. Use the authorized secure handoff the provider specifies and limit unnecessary disclosure. Never include account passwords, recovery codes or an installer login. Exporting a record is not a reason to broaden another person’s privileges or change the system’s control settings.
If ownership or account access will change, ask the actual platform about the required authorized process and any history limitations. Do not promise that a saved export will be imported into a new account, that old history will transfer, or that the provider retains every past interval. Our monitoring-transfer guide covers the separate access task. Ask what should be preserved before the change and which access remains legitimate afterward; continued possession of a password does not itself establish continuing authority.
Illustrative scenario: service is planned and the history has a gap
Imagine an owner preparing for inverter service sees a missing span in the monitoring app. This is an illustrative scenario, not a production measurement or diagnosed fault. The owner exports the available requested period, keeps the original file and records the gap with a known connectivity interruption. The handoff does not turn unavailable information into zero output or claim the service provider has already proven the cause.
The provider confirms receipt and explains whether the supplied channels and dates are sufficient for the case. Any further request is documented rather than satisfied with guessed values. After service, a later export can be retained with its own actual range and context, without overwriting the earlier evidence. The example demonstrates a comparison-ready record, not proof of repaired output, expected savings or continuous historical availability.
Complete the packet and confirm the handoff
Keep the untouched export, working copy if any, export note, actual equipment and channel description, dated event chronology, relevant screenshots and support case reference together. Mark unsupported periods and interpretations explicitly. Ask the recipient to confirm that the file opens, which period and channels they accepted, and which questions remain. Receipt of an attachment and completion of the underlying service investigation should be different checklist entries.
For a later follow-up, retain a new file and note rather than replacing earlier history. Use consistent filenames that describe the actual period without including unnecessary sensitive information. Maintain a distinction between measured platform values, missing data, your notes and professional findings. That structure lets you discuss a specific evidence gap or requested comparison without making universal claims about solar output, battery runtime, tariffs, warranty coverage or the platform’s retention policy.
Frequently asked questions
Does missing monitoring mean no generation? Not automatically. Preserve the gap and seek the appropriate interpretation.
Do all Tesla channels use the same export interval? Do not generalize a Powerwall-charge interval to every channel; inspect the actual file and documentation.
Will history follow a new owner or account? Ask the platform about the actual process. This guide gives no transfer or retention guarantee.
Should I send my password with the file? No. Use an authorized record handoff, not credential sharing.