Leave a useful solar-system monitoring handover

Put the essentials on the first page

Start with the property name, monitor location, host model, software version and date verified. Include the normal local dashboard address and where to find the current address if it changes. Identify the owner account by email, but never include its password.

Add a simple connection sketch: equipment to host, host to network, network to viewing screens. Label whether an equipment connection is USB, a supported Bluetooth link or another documented interface. A diagram with five accurately named boxes beats a photograph of an unlabeled cable bundle.

Keep an equipment and measurement register

For each inverter, BMS or controller, record the exact model, firmware when available and observed identity. State which fields are expected and which are unavailable. Keep private identifiers in the private handover copy.

Write a short dictionary for ambiguous values. “Battery percentage comes from the BMS” is different from “battery percentage is reported by the inverter.” Identify configured capacities and calculated values so they are not mistaken for independently measured equipment specifications.

Record a known-good state

Attach a small set of dated screenshots rather than dozens of unlabeled images. Include a view that makes data freshness and equipment count visible.

Explain access and recovery boundaries

List account ownership, invited viewers and local administrator screens. Explain who may revoke access. Store backup and recovery instructions alongside the software release information, with credentials in an appropriate private credential store.

For a Raspberry Pi host, keep the official setup documentation available for reference. The Sunstead image instructions take precedence for its specific installation. A generic OS guide does not establish compatibility with a particular application image.

Do not say “reinstall if broken” without explaining what data would be lost and what has actually been backed up. A spare blank card is not a backup of the existing host.

Finish with open questions and ownership

• Outstanding compatibility or data questions.
• The evidence already collected for each question.
• Who owns the next action.
• The last successful local and remote test.
• Where release notes and equipment manuals are stored.

Walk through the handover with another person. Ask them to locate the current reading timestamp, identify the host and explain who to contact. Their hesitation will expose missing information more effectively than adding another page of general advice.

Review the document after replacing hardware, changing network settings or moving ownership. A dated short record that matches the installation is more useful than an exhaustive one that describes last year’s equipment.