Skip to main content
NestGrid logoNestGrid

The 2026 solar eclipse cut my home output. Was it a fault?

Solar production dipped during Aug. 12, 2026 eclipse and recovered; no inverter fault

Last updated

If your smart-home energy dashboard shows solar production falling in the evening on Aug. 12, 2026, then recovering without an inverter fault, the first suspect is not a broken panel. The clean signature is a smooth U-shaped production dip during the local eclipse window, usually with export falling, import rising, and no matching error code. ENTSO-E had already warned European transmission operators to expect a clear-sky photovoltaic reduction between 19:15 and 21:30 CEST that evening, with up to 9.7 GW of PV reduction possible across Europe under clear skies [1].

That does not mean every home lost the same percentage, or that a grid-scale number can be pasted onto your roof. A home system saw whatever its own sky saw: local obscuration, local weather, panel orientation, battery behavior, and the normal evening decline in sun angle. But if the dip in your Home Assistant Energy dashboard, Enphase or Tesla app, inverter portal, or CT-clamp monitor lines up with the eclipse timing and then returns smoothly, the working status is: expected irradiance event.

Schematic U-shaped solar production dip with grid import rising during the eclipse window

Read the curve before you touch the inverter

The fastest way to waste an evening after an eclipse is to start rebooting devices before looking at the shape of the data. A real solar fault often leaves a sharper fingerprint: a hard drop to zero, a persistent missing string, a trip event, an arc-fault or ground-fault warning, a communications gap, or a failure to recover after the sky event has passed. The Aug. 12 eclipse signature should look more like someone temporarily dimmed the sun.

Dashboard evidenceWhat it points to
Smooth production reduction and smooth recovery during the local eclipse windowExpected irradiance event
Export falls and import rises while house load stays ordinaryExpected grid-tied behavior during lower PV output
Battery discharges more than usual during the dip, then resumes normal behaviorExpected battery response to reduced solar input
No inverter fault, trip, or panel-level alarm at the same timeMore support for expected event status
Hard drop to zero, fault code, tripped inverter, missing string, or no recoveryLeave the eclipse explanation and troubleshoot the solar stack

This is the same attribution problem smart-home owners already know from cloud services and hubs: decide whether the event is outside your system before taking your own stack apart. The same habit used in event-versus-device troubleshooting applies here. The dashboard is the first witness; vendor alarms are the second.

What the expected eclipse curve looks like

A photovoltaic array does not need to “know” there is an eclipse. It responds to irradiance. Less sunlight reaches the modules, DC production falls, the inverter converts less power, and a grid-tied home either exports less surplus or imports more to meet the same loads. SEIA’s plain-language comparison, quoted by Arcadia, treated an eclipse as “no different than a passing thunderstorm” for solar output behavior [2].

On a dashboard, that usually means the eclipse day does not look like a normal clear evening. It looks like the normal evening solar curve with an extra, smooth bite taken out of it. The clean version is rounded on both sides: production eases down as obscuration increases, bottoms out near maximum local obscuration, then climbs back toward the output the system would otherwise have had at that late-day sun angle.

Schematic comparison of a clear-day solar curve and an eclipse-day curve with a smooth dip

Do not expect a perfect textbook U. Late-day solar geometry matters. A west-facing array may show a different shoulder than a south-facing array. Local cloud can add roughness. A battery can hide the dip from whole-home import for a while. Panel-level monitoring can show slightly different module behavior if parts of the array have different orientations or shading. The point is not mathematical symmetry; it is a continuous irradiance-shaped reduction rather than a device-shaped failure.

The astronomy matters only enough to anchor your local timing. The Aug. 12, 2026 total eclipse crossed Greenland, Iceland, and Spain, with NASA identifying it as the total solar eclipse of that date; public event summaries placed totality in Spain around 20:27–20:33 local time and Reykjavik around 17:48, with totality lasting roughly 1–2 minutes in the Spanish path [3][4]. A home outside the totality path still could see a production dip if partial obscuration was meaningful at that location.

Verify it from your own dashboard

Use your monitoring history, not a headline number. A European PV reduction projection cannot tell you whether your inverter behaved correctly. Your own curve can.

Compare Aug. 12 with a nearby clear day

Open the same solar-production view for Aug. 12 and for a nearby clear day. Keep the comparison inside the same tool if possible: Home Assistant to Home Assistant, inverter portal to inverter portal, CT clamp to CT clamp. Mixed tools can disagree because of sampling intervals, rounding, delayed cloud uploads, or whether the chart shows DC production, AC output, site export, or net grid flow.

You are looking for the same broad evening shape with one extra depression. A clear-day comparison is more useful than comparing against a monthly average, because averages blur weather and load behavior. If the day before was cloudy, use the nearest clear day and treat the result as a comparison, not a laboratory measurement.

Align the dip with local obscuration, not just with totality headlines

The household question is not “Was there totality somewhere in Europe?” It is “Did my dip line up with the eclipse as seen from my roof?” ENTSO-E’s Europe-wide preparation window of 19:15–21:30 CEST gives the broad grid-management interval [1]. Your local maximum obscuration may sit inside that broader window, and your production minimum should sit close to it after accounting for dashboard resolution.

If your chart resolution is 5, 10, or 15 minutes, do not over-read the exact minute. A dashboard bucket can make the bottom look slightly early or late. The stronger evidence is that the whole production sag begins, bottoms, and recovers in the same part of the evening as the local eclipse.

Check export, import, and battery behavior

A grid-tied home with ordinary loads should show the energy balance shifting during the dip. If PV production falls below the house load, grid import rises. If the home was exporting before the dip, export shrinks or stops. If a battery is configured to cover loads, it may discharge through part of the eclipse window and reduce visible grid import.

That battery behavior is not an outage. It is closer to the way a battery smooths any short production shortfall. If the event made you realize you do not know which devices your battery or UPS actually supports, the same inventory discipline used for smart-home outage planning and UPS runtime sizing is useful. For the eclipse diagnosis itself, though, a normal battery discharge during lower PV input is supporting evidence, not a fault.

Cross-check inverter and CT records

If your inverter app shows the same production shape as a CT clamp or whole-home monitor, the eclipse explanation gets stronger. If the inverter shows continuous production but your smart-home dashboard has a blank gap, that points toward telemetry or integration trouble. If the app shows a fault at the same time the CT monitor shows a hard production stop, that is no longer just an eclipse curve.

The order matters. First confirm the physical-looking energy pattern. Then check vendor alarms. Then decide whether to troubleshoot. Starting with resets can erase temporary states or create new ones, which makes the post-event record less useful.

Why the same dip showed up at grid scale

The grid reports are useful because they confirm the event was expected and managed. They are not useful as a direct calculator for your roof. ENTSO-E’s pre-event statement projected up to 9.7 GW of European PV reduction under clear skies between 19:15 and 21:30 CEST, and noted that solar represented about 13% of EU generation in 2025 [1]. That is a system-planning number, not a homeowner diagnostic result.

National estimates varied because each system had different installed solar capacity, eclipse geometry, timing, weather assumptions, and demand conditions. Portugal’s REN estimated a 450 MW reduction, equal to about 45% of that hour’s forecast solar output and about 7% of consumption [5]. A Germany estimate put the possible solar reduction around 2 GW [6]. Those numbers explain why operators prepared; they do not say what happened on a single garage roof.

The UK figures need especially careful labeling because public estimates were not identical. Solar Energy UK expected a 0.5–0.8 GW reduction at the eclipse height against a 14.5 GW daily peak [7]. Vattenfall described a broader 0.7–1.3 GW range [8]. NESO’s eclipse-day estimate, as recapped after the event by OpenWeather, narrowed the range to roughly 300–1,100 MW [9]. Treat those as individually attributed estimates, not one blended “UK number.”

Source or systemAttributed estimateHow to use it
ENTSO-E, EuropeUp to 9.7 GW PV reduction under clear skies, 19:15–21:30 CESTConfirms the broad grid-scale irradiance event
REN, Portugal−450 MW, about 45% of that hour’s forecast solar output and about 7% of consumptionShows local grid significance where obscuration and solar share aligned
Germany estimateAround 2 GWShows expected national-scale reduction
Solar Energy UK0.5–0.8 GW at eclipse height versus a 14.5 GW daily peakOne UK estimate; do not merge with others
Vattenfall0.7–1.3 GW for the UKAnother UK estimate with its own range
NESO recap via OpenWeatherRoughly 300–1,100 MWEclipse-day UK estimate as reported after the event

The grid story is reassuring in a narrow way: operators expected a temporary solar dip and planned around it. Vattenfall and Solar Energy UK both framed household supply as unaffected, which matches what a grid-tied homeowner should have seen if the home simply imported more during the PV shortfall [7][8]. It does not prove every inverter app, smart meter integration, CT clamp, or Home Assistant database behaved perfectly that evening.

When the eclipse explanation is not enough

A solar eclipse can explain a temporary irradiance-shaped production drop. It should not be used to wave away ordinary faults that happened to be noticed on the same evening.

  • A hard drop to zero before the local eclipse window, especially if it does not recover, points away from a smooth irradiance event.
  • An inverter trip, arc-fault warning, ground-fault warning, isolation fault, breaker trip, or shutdown message deserves normal solar troubleshooting.
  • A blank app chart while CT data still shows production suggests a monitoring, cloud, Wi-Fi, gateway, or integration problem rather than lost generation.
  • One string or one panel group falling out while the rest of the array follows the expected curve can indicate string, optimizer, microinverter, connector, shading, or panel-level trouble.
  • A production dip that repeats on later clear days at the same clock time is not the Aug. 12 eclipse. Check recurring shade, inverter derating, export limiting, or equipment faults.
  • A battery that never resumes normal charge or discharge behavior after the event should be checked as a battery or energy-management issue.

This fork protects both sides of the diagnosis. It prevents unnecessary panel panic when the data fits the eclipse, and it prevents the eclipse from becoming a lazy explanation for a real failure. If devices went offline because of an unrelated power event, the recovery path is closer to post-outage smart-home recovery or hub-specific recovery than to solar irradiance analysis.

Did the eclipse damage panels or meaningfully change annual output?

The evidence supports reassurance, with scope. Panels stayed live; they received less sunlight for a short period and then more sunlight again as the moon moved away. That is not a damage mechanism by itself. The University of Toledo put the 2017 eclipse in annual-output context, reporting that the event cost residential production less than 0.1% of annual output in its comparison [10].

A peer-reviewed 2021 residential case study is useful for the shape and scale of one observed home system, not as a universal promise. In that single case, a residential PV system recorded an energy-output drop of about 80% at about 70% peak obscuration during the 2017 eclipse [11]. That case shows how strong a local dip can look without implying hardware damage, but it should not be converted into a prediction for every 2026 roof.

For broader solar ownership questions, the eclipse belongs in the same practical bucket as rated-watt expectations, tariffs, maintenance decisions, and disposal planning: useful to understand, but not a reason to assume the array is failing. If you are comparing this event with normal solar-performance questions, keep it separate from topics like portable panels and rated watts, home solar price pressure, or solar panel disposal. The eclipse dip was a time-stamped sky event.

Status card for the Aug. 12, 2026 dashboard dip

FieldStatus
Verification dateAug. 25, 2026
Event checkedAug. 12, 2026 solar eclipse
Expected home signatureSmooth U-shaped PV production reduction aligned with local obscuration; export drops, import rises or battery covers load; no inverter fault
Status when those signatures matchConfirmed: expected irradiance event
ScopePost-event synthesis from grid statements, eclipse timing, irradiance behavior, and case evidence; not a device-specific lab test of every inverter app, Home Assistant setup, or CT-clamp monitor
Escalate whenThe curve, timing, export/import behavior, or fault logs do not match the eclipse signature

Save the same comparison method for the Aug. 2, 2027 eclipse: nearby clear-day curve, local obscuration timing, export/import behavior, and fault logs before hardware resets.

References

  1. Transmission System Operators prepare for solar eclipse to ensure secure system operation, ENTSO-E, Aug. 7, 2026
  2. Solar Eclipse Energy Grid, Arcadia
  3. Total Solar Eclipse on August 12, 2026, NASA
  4. Solar eclipse of August 12, 2026, Wikipedia
  5. Solar power output set to fall during eclipse, Euronews, Aug. 10, 2026
  6. European transmission system operators prepare for solar eclipse, pv magazine, Aug. 10, 2026
  7. Eclipse’s impact on grid ‘predictable and manageable’, Solar Energy UK
  8. When the sun disappears: Europe prepares for a temporary drop in solar power, Vattenfall, 2026
  9. How Europe's grid rode out August 2026 eclipse, OpenWeather
  10. Physicists Compare Drop in Power Output From UT Solar Panels During Eclipse to Cloudy Day, University of Toledo, Sept. 14, 2017
  11. Residential photovoltaic system performance during the 2017 solar eclipse, ScienceDirect, 2021

Corroborating context

For protocol background on why this failure happens, see Compatibility & Protocols.

Not currently linked to a known regression. Background on the underlying protocol lives in Compatibility & Protocols.

Other fixes for this device

Report / Feedback

If this fix didn't hold on your exact hardware/firmware combination, file a scoped report -- it feeds the re-verification queue instead of an open comment thread.

Blogarama - Blog Directory