Monitoring data gaps are treated as cosmetic and are frequently the most informative thing on the screen. A missing interval means the platform did not receive data, which tells you nothing by itself about whether the array was producing. Depending on how the software fills or ignores the hole, a gap can hide a fault, invent production that never happened, or quietly corrupt the baseline you plan to use for a warranty claim.
Why data goes missing
The usual cause is communication rather than generation. A router was replaced and the gateway never reconnected, a network password changed, a cellular modem lost coverage, a power cycle left a device unconfigured, a firmware update failed, or a cable in the equipment area was disturbed. The array in all those cases was producing normally and exporting normally, and the meter recorded it. Less often the gap reflects something real: the inverter was off, a string was disconnected, or the whole system was down. The two cases look identical in a chart with a hole in it, which is why a gap should prompt a question rather than a shrug.
How platforms fill holes and why it matters
Software has to decide what to do with missing intervals when it computes daily and monthly totals. Some platforms leave them empty, so totals are understated. Some interpolate between known points, which produces plausible numbers that were never measured. Some back-fill from a device’s internal cumulative counter when it reconnects, dumping a large value into the interval where communication returned and creating a spike that looks like a data error. Each behavior is defensible and each distorts the record differently. If you are going to rely on this data for anything important, find out which convention your platform uses, because the same underlying reality produces different monthly totals under each.
The faults a gap can conceal
Alerting usually depends on data arriving. A system that has stopped reporting often stops generating alerts too, so the silence that should be the loudest signal becomes the quietest. A string that failed during a communication outage will not raise an alarm, and when data resumes the platform may show normal-looking output from the remaining strings. Module-level monitoring has the same problem at a finer grain: a device that stops reporting may have failed, or may just have lost its communication link, and the platform often cannot distinguish them. This is why comparing monitored production against the utility meter periodically is worth the few minutes it takes.
What gaps do to a long-term baseline
Degradation analysis and warranty claims rest on a consistent, weather-corrected record. Gaps break that consistency in ways that are hard to correct after the fact, especially if you cannot tell whether a missing month was zero production or missing data. The defensive practice is simple: export raw data periodically rather than relying on the vendor’s retention, note the dates of any outage in a plain text log alongside it, and record the cause once you know it. A gap with an explanation attached remains usable evidence. A gap with no note becomes a hole in the argument years later.
Keeping the link alive
Most gaps are preventable with small habits. Put the monitoring gateway on a network segment that does not change when household equipment is replaced, and write the credentials in the system documentation. Check the platform monthly, which is enough to catch an outage before it becomes a season. Set up whatever notification the platform offers for loss of communication, not only for production faults. After any electrical work, network change or power outage, confirm the system reconnected. And make sure the account is registered to you, so you can do all of this without depending on an installer who may no longer be in business. If the system uses a cellular link rather than the home network, find out who pays for that connection and when it expires. Subscriptions bundled into the original installation sometimes lapse after a few years, and the first sign is a monitoring system that simply stops reporting with no fault anywhere in the hardware.
What to check before you act
- Find out how your platform treats missing intervals in totals.
- Enable alerts for loss of communication, not only for faults.
- Export raw production data periodically and keep a log of outages.
- Reconfirm connectivity after electrical work or a network change.
Common questions
My app shows nothing for three days. Did I lose that production?
Probably not. Compare against your utility meter for the same period. A communication outage leaves the array producing normally while the platform records nothing.
Can missing data be recovered?
Sometimes. Many devices buffer readings locally and upload them when the link returns, so the history fills in. Whether that happens depends on the product and how long the outage lasted.
The practical takeaway
Treat a gap as an unanswered question rather than a blank space. Learn how your platform handles missing intervals, enable communication alerts, export your data periodically and annotate every outage so the record stays usable years from now.
References and further reading
- NREL PVWatts: modeled production for comparison against a recorded history
- NREL: photovoltaics research including system performance monitoring
- NREL: a technical report from the laboratory’s photovoltaics publication library
Numerical scenarios are illustrative unless identified otherwise. Follow the exact product instructions; component ratings and local installation requirements can differ.
