How OwlWatt measures your solar system — in plain English

Every solar homeowner reaches the same point eventually: is my system producing what it is supposed to? Your Enphase app shows one number. Your installer's original proposal showed another. Weather is always a factor. How does independent solar monitoring actually separate a genuinely cloudy year from a system that is quietly underdelivering?

This page explains how OwlWatt works — what it reads, how it computes the expected-output number, and why independent measurement produces a different result than watching your own app.

Step 1: Reading your actual production

OwlWatt connects to your existing Enphase inverter monitoring — not to a separate sensor or a third-party estimator. There are two read paths:

• Local collection via the Enphase IQ Gateway: The OwlWatt Iris reads directly from the gateway over your home network, with per-microinverter detail. Every panel, updated every five seconds. The data does not leave your network unless you explicitly share it.
• Enphase Enlighten cloud API: For homes where local access is not available, OwlWatt reads from the Enphase cloud on a slower cadence — 15-minute updates with vendor-managed aggregation, per the Enphase API specification.

Local collection is the preferred path because it is higher resolution, does not depend on Enphase's cloud staying online, and reads the inverter hardware directly rather than a cloud-processed summary. The OwlWatt Iris ships preconfigured; plug it in and it starts reading.

Either way, OwlWatt never estimates your production. The actual-production number in your report reflects what your panels generated, measured from the inverter hardware — not a modeled approximation of what they should have generated.

Step 2: Calculating what your system should produce

This step distinguishes independent solar monitoring from watching your installer's app. For every hour of every day, OwlWatt computes an expected production number specific to your system and location, using the open-source model published by the National Renewable Energy Laboratory — the same model behind PVWatts, which is the standard tool installers use to produce the estimated annual production figure in your original proposal. The calculation chain runs like this:

1. Solar geometry: The model calculates the exact position of the sun — its angle above the horizon and its compass direction — for every hour of the day at your latitude and longitude. This determines how much sunlight could reach your panels from a purely geometric standpoint.
2. Available sunlight: Using a peer-reviewed clear-sky model (Ineichen & Perez, 2002), the calculation determines the maximum sunlight available at your location under a cloudless sky, accounting for atmospheric absorption and scattering even on clear days.
3. Panel orientation and angle: The model converts that available sunlight to what actually reaches your panels given their tilt and compass direction. A south-facing panel at 30° tilt captures a different fraction of daylight than a flat panel or a panel facing east or west.
4. Temperature correction: Panels produce less power as they heat up. Crystalline silicon panels lose approximately 0.4% of output for every degree Celsius above their rated test temperature, per international standard IEC 60904-1. The model applies this correction hour by hour, estimated from sunlight intensity and ambient conditions.
5. System losses: A flat 14% derating accounts for unavoidable losses: wiring resistance, panel mismatch, soiling, and the gap between rated and real-world output. This matches the default loss assumption in the NREL model.
6. Inverter conversion: Standard DC-to-AC conversion efficiency is applied to produce a final AC output estimate — the kilowatt-hours that actually flow to your home or to the grid.
7. Aging: Systems lose a small fraction of capacity each year as panels degrade. OwlWatt applies a 0.5% annual degradation factor from your installation date, consistent with the industry-standard silicon degradation rate.

The result is an expected AC kilowatt-hour figure for every hour. Integrated over a month or a year, that is the baseline OwlWatt compares your actual production against.

The calculation runs on pvlib, an open-source Python library originally developed at Sandia National Laboratories in 2013 and now maintained by over 100 researchers internationally. The code is public. If an installer disputes an OwlWatt report, they can run the same model with the same input parameters and arrive at the same number. That reproducibility is what makes OwlWatt's documentation credible in a warranty or guarantee dispute — the expected-output figure is not a proprietary estimate from a black box.

For the complete parameter reference — DC nameplate capacity, tilt, azimuth, system losses, and the full pvlib pipeline — see How OwlWatt Calculates Your System's Expected Production.

Step 3: Adjusting for the actual weather

A calculation based purely on clear-sky geometry overestimates production on cloudy days. A system that produces less on an overcast morning is not failing — it is responding to physics.

OwlWatt separates weather effects from system problems. For each day where ground-level weather data is available from NOAA stations, airport weather instruments, or regional solar monitoring networks, OwlWatt scales the expected output proportionally to actual sky conditions. The hourly shape of the production curve stays intact — more output at midday, less at sunrise and sunset — but the magnitude adjusts to what the sky actually permitted that day.

The result is a weather-adjusted expected output: what your system should have produced given the specific sky it experienced, not what a long-term historical average assumes. Why weather adjustment changes the analysis is worth understanding — comparing production to an unadjusted model is one of the most common ways homeowners and installers alike miss real underperformance.

On days where local weather data is not available, OwlWatt falls back to the clear-sky estimate and marks those entries in the report, so you can see which days used which approach.

Step 4: Reporting the gap

Once OwlWatt has both numbers — actual production from your inverter and expected production from the weather-adjusted model — the shortfall calculation is direct:

• Shortfall in kWh: Expected minus actual, floored at zero. If you produced more than expected on a particularly sunny day, that is recorded as positive variance — it does not cancel out a shortfall from another period.
• Shortfall as a percentage: The kWh gap divided by expected output, expressed as a percentage. A 10% shortfall on a system expecting 1,000 kWh for the month means you generated 900 kWh.
• Shortfall in dollars: The kWh gap multiplied by your electricity rate. OwlWatt defaults to the average residential electricity price for your state from the EIA Electric Power Monthly (Table 5.6.A). You can override this with your actual rate if you are on a time-of-use tariff or your bill rate differs from the state average.

To make the scale concrete: a 10 kW system in New England might have an expected output of around 900 kWh in March. A 10% shortfall — 90 kWh — translates directly to electricity you paid your utility for instead of generating yourself. At current New England residential rates (EIA, 2025), that is roughly $28 for the month. Sustained across 12 months, a persistent 10% gap on a 12,000 kWh/year system adds up to approximately 1,200 kWh annually. The financial impact depends on your rate, but the production gap is a fact regardless of what electricity costs.

All three figures — kWh, percentage, and dollars — accumulate over your chosen window: today, this month, year-to-date, or since installation. If your installer gave you a production guarantee, OwlWatt tracks your cumulative production against the guarantee threshold and shows you where you stand months before the annual reconciliation date.

Every data point carries a timestamp. The report records the methodology version, the input parameters, and the weather data source for each period — an audit trail that is useful if you need to file a production shortfall claim.

Why the measurement being independent matters

Your Enphase app displays your production accurately. The production number itself is not the gap — the gap is the absence of a comparison. Enphase's app is designed to display inverter data; it does not compute what your system should have produced and show you the difference.

OwlWatt's expected-output calculation runs independent of your installer, your inverter manufacturer, and anyone else in the supply chain with a financial stake in the result. The model is open source. The inputs are your own system parameters. When actual and expected diverge by more than normal variation — a sustained gap above 5% after weather adjustment is the alert threshold OwlWatt uses — OwlWatt flags it, and the documentation exists before you need to make a claim.

The recurring pattern: a microinverter fails silently, a tree grows into the shading clearance, or panel connections degrade from weather cycling. Each issue alone causes a production drop. Two or three occurring together over two or three years can push the total meaningfully below expected output — precisely the range at which solar underperformance crosses from "normal variation" into territory worth a warranty or guarantee claim.

The full technical picture

This page covers how OwlWatt works at the level a solar owner needs to understand the measurement. If you want the complete parameter set — the exact pvlib version, how degradation is calculated month by month, how the model handles snow-loss days, and how shortfall interacts with contract guarantee clauses — the OwlWatt methodology page documents all of it. That page is written for engineers, attorneys, and installers who need to audit or reproduce the calculation.

For context on what a production guarantee actually promises and how OwlWatt's measurement fits into a warranty dispute, the production guarantee explainer covers the contract side of the equation.