Solar Panel Low Power: Microinverter Communication Loss or Shading?

Use only checks that match the exact appliance or system and its official guide.

1. Check 1

   Open the solar monitoring app or portal and compare the affected panel or microinverter's production graph with a nearby reporting device on the same clear-day time window. Check whether the low output is visible only during daylight and whether the system is showing an explicit no-communication state.

   Expected result: The device reports no data but nearby devices produce, the device reports low watts while still communicating, or the whole site has no current data.

   Next step: Save a screenshot and the time window. For one device, continue with the shade and pattern checks; for whole-site missing data, check only the portal's gateway or network status and contact the installer if it remains offline.

   Why this matters

   Why: No data is a communication-path symptom and does not by itself prove that the panel is not producing. Low watts with current data is a production symptom. Whole-site missing data keeps the gateway, network, or site-level state in focus rather than one panel.

2. Check 2

   From the ground or a safe window, observe the array's surroundings at the times shown in the graph. Look for shadows from trees, chimneys, antennas, nearby structures, snow, or debris without climbing, touching a module, or moving an obstruction.

   Expected result: A shadow reaches the affected panel at roughly the same time each day, the shade moves with the sun, or no visible obstruction corresponds to the low-power period.

   Next step: Record the panel location and shade timing for the installer. Do not trim trees, walk on the roof, clean the modules, or alter wiring as a diagnostic experiment.

   Why this matters

   Why: A repeatable time-of-day match supports environmental shading rather than a random communication failure. No visible shade does not clear the equipment, because a panel, microinverter, connector, or monitoring path can still require installer testing.

3. Check 3

   Check the monitoring portal during a clearly lit daytime period for the gateway heartbeat, last-report time, and the count or list of microinverters marked not communicating. Use only the portal or app; do not press equipment buttons or cycle a solar breaker.

   Expected result: The gateway has a current heartbeat but one or a few microinverters are not reporting, or the gateway itself has not reported for the current period.

   Next step: Document the affected device labels and last-report times, then ask the installer to diagnose the communication path and production data.

   Stop if: If the gateway is current and all devices report but one remains low, treat it as a panel or microinverter production issue and request professional testing rather than a roof inspection.

   Why this matters

   Why: A current gateway connection with isolated missing devices points toward the device-to-gateway communication path or a panel-level issue. A stale gateway heartbeat points toward gateway, network, or site-level reporting and can make every panel appear abnormal in the app.

4. Check 4

   Compare the affected device's output with nearby devices across several similar daylight periods, noting whether the same panel is always low, several adjacent panels change together, or the difference appears only under a moving shadow.

   Expected result: The same panel remains low without a shade pattern, several devices on one branch change together, or output differences follow the moving shade.

   Next step: Send the comparison and screenshots to a qualified solar installer. Only trained personnel should perform any device swap, connector inspection, AC/DC measurement, or inverter diagnostic.

   Why this matters

   Why: A persistent single-device difference keeps that panel or microinverter in focus. A group change can point to a branch, grid, or communication issue. A moving, repeatable difference is consistent with shade or another environmental condition, not enough evidence for a component replacement.

5. Check 5

   From a safe distance, look for emergency signs around the array, inverter, and visible conduit: smoke, flame, arcing, a hot or discolored enclosure, broken module glass, exposed wiring, or a burning odor. Do not approach the roof or touch any solar equipment to verify a suspected sign.

   Expected result: Any emergency sign is present, or the system is near a fire, storm damage, flooding, or a fallen overhead line.

   Next step: Move away, keep others away, call emergency responders for fire or immediate danger, and notify the solar installer or utility from a safe location. Do not spray water, disconnect cables, or attempt a shutdown sequence unless directed by trained responders following the system's site-specific procedure.

   Why this matters

   Why: PV components can remain electrically hazardous in daylight and can create shock or arc hazards during fire or damage response. A normal app status cannot make damaged roof equipment safe.