HyreSolar

Problems

Monitoring shows zero: check this before you call

Three different failures produce an identical display, and the most likely one is not your panels.

Updated September 2026 · Data as of Manufacturer installation documentation read on 3 September 2026

Written by HyreSolar Research team Research and analysis

Audited by HyreSolar Research team Data audit and fact check

3 different failures, one identical display By design
2 of the three are communication, not generation And they are the likelier two
1st explanation the manual gives is nighttime Worth ruling out first

The short answer

A zero on the app does not mean your system is not generating. It means the app is not being told that it is. Those are different failures and the hardware itself distinguishes them: the manufacturer's installation guide documents separate indicators for network communications, device communications and power production. So a zero can mean the gateway cannot reach the internet, or that it cannot reach the microinverters, or that the microinverters genuinely are not producing. Only the third is a solar problem, and it is the least common of the three. The guide's own first explanation for a production indicator being off is the one worth ruling out before anything else: "low-light or nighttime".

Why a zero is ambiguous, and why that is deliberate

The monitoring app is not watching your panels. It is displaying data that had to travel a chain: from the microinverters, to a gateway in your house, over your home network, to the manufacturer's platform, and then to your phone.

A break anywhere in that chain produces a zero, and the app cannot tell you where the break is. From its point of view, "the system produced nothing" and "nobody told me what the system produced" look identical.

The hardware, unlike the app, does distinguish them. The manufacturer's installation guide documents separate indicators, and reading them is the fastest diagnosis available to a homeowner.

A network communications indicator reports whether the gateway can reach the manufacturer's platform. Its documented states include solid red for "local network connection only" and off for "no network connection".

A device communications indicator reports whether the gateway can reach the microinverters. Solid red means "at least one device is not communicating".

And a power production indicator reports whether generation is actually happening. Solid green means "all communicating microinverters are producing"; solid red means "at least one microinverter is not producing".

Those are three separate questions and the app collapses them into one number. Walking to the gateway and looking at it answers in ten seconds what an app cannot answer at all.

The manual’s own first explanation is nighttime

Before anything else, note what the documentation offers as the explanation for two of its indicators being off: "low-light or nighttime".

It appears against both the power production indicator and the device communications one. That second placement is the useful and non-obvious part: microinverters draw their operating power from the panels they are attached to, so when the sun goes down they stop communicating as well as stop producing. An overnight loss of contact with your microinverters is the system working correctly.

This sounds too obvious to state, and it is the single most common reason a homeowner concludes something is wrong. A late-evening check, an overcast dawn, or a snow-covered array all reproduce exactly the display a fault would produce.

Check in the middle of a clear day before concluding anything. It costs nothing and it eliminates the most likely explanation.

The parts of the chain, and which one fails

Microinverter or optimizer
The electronics at each panel. They both convert or condition power and report what they are doing, which is why losing contact with them and losing generation look the same from a distance.
Gateway
The box in your house that collects data from the panel electronics and sends it onward. Most monitoring failures are here or downstream of it, and it carries a shorter warranty than the equipment it serves.
Powerline communication
On many systems the panel electronics talk to the gateway over the building’s own electrical wiring rather than over Wi-Fi. This is why a newly plugged-in appliance can interfere with monitoring without affecting generation at all.
Backfill
Recovery of data recorded locally during an outage once the connection returns. Many systems do this, so a gap in the app is not necessarily lost data.
Anti-islanding
The safety behaviour that shuts a grid-tied system down during a grid outage, so it cannot energise lines crews are working on. It means a neighbourhood power cut produces zero production, correctly, and not as a fault.
Consumption monitoring
An optional separate measurement of what the house uses, distinct from what the system generates. Where it is fitted, a fault in it can make production look wrong when production is fine.

What each indicator is actually telling you

IndicatorStateWhat it means
Network communicationsSolid greenCommunicating with the manufacturer’s platform
Network communicationsSolid redLocal network connection only. The gateway works; the internet path does not
Network communicationsOffNo network connection. Your router, not your roof
Device communicationsSolid greenAll devices are communicating
Device communicationsSolid redAt least one device is not communicating
Device communicationsOffDevices are not communicating, low-light or nighttime
Power productionSolid greenAll communicating microinverters are producing
Power productionSolid redAt least one microinverter is not producing. This is the genuine production fault
Power productionOffNot producing or communicating, low-light or nighttime
All indicatorsFlashing red togetherThe gateway is booting up
All indicatorsFlashing green in sequenceSoftware upgrade in progress

From the manufacturer’s Quick Install Guide troubleshooting table for its gateway models. Read 3 September 2026.

The two boot and upgrade rows matter more than they look. A gateway restarting after a power cut, or updating itself, produces alarming displays and resolves without intervention. Give it time before escalating.

Working out which of the three you have

If network communications is off or red but production is green, your system is generating and the data is not reaching the platform. Nothing is wrong with your solar. This is a home networking problem: a router replaced, a Wi-Fi password changed, a channel moved, a gateway too far from the access point. Your production is being recorded locally and typically backfills once the connection returns.

If device communications is red or off in daylight but the network is fine, the gateway cannot hear the microinverters. On systems that communicate over the electrical wiring, this can be caused by something newly plugged in generating interference, or by a breaker. The panels may well be producing while nothing can report it.

If power production is red in good daylight, you have a genuine generation fault, and the pattern narrows it. Everything dead points at the grid connection or the main wiring rather than at panels. One branch or string dead points at that circuit and its breaker. Scattered individual units point at connectors or at individual failures.

And if everything is green but the app still shows zero, the problem is between the platform and your phone: an app account issue, a site that has been mis-configured, or a display glitch. It is worth checking the platform in a browser before assuming anything about the hardware.

And there is a case where zero is correct and nothing is wrong at all. A grid-tied system without battery backup shuts down during a power cut, deliberately, so that it cannot energise lines that utility crews may be working on. If the neighbourhood is dark, your system producing nothing is the safety behaviour operating exactly as designed. Homeowners frequently discover this during the first outage after installation and reasonably conclude they were mis-sold, which is a conversation better had before the outage than after it.

What to do, in order, before you call anyone

  1. 1
    Check in the middle of a clear day

    The documentation gives low light and nighttime as the explanation for two indicators being off. Ruling that out costs nothing and eliminates the most common cause of a false alarm.

  2. 2
    Go and look at the gateway

    The indicators answer in seconds what the app cannot answer at all: whether this is a network problem, a device communication problem or a production problem. Photograph them, since the states change and you will want the record.

  3. 3
    If the network indicator is the problem, fix your network

    Router replaced, password changed, band or channel moved, or the gateway simply too far from the access point. This is not a solar fault and calling your installer about it will produce a visit you pay for.

  4. 4
    Check whether a breaker has tripped

    There is normally more than one relevant breaker: the array or inverter circuit and, on some systems, a separate one for the monitoring equipment. A tripped breaker produces a convincing impression of catastrophic failure.

  5. 5
    Give a booting or updating gateway time

    All indicators flashing red together means it is starting up; flashing green in sequence means a software upgrade. Both resolve on their own, and both look alarming.

  6. 6
    Note the pattern before you report it

    Everything dead, one string dead, or scattered units dead are three different diagnoses. Whoever you call will ask, and having the answer shortens the visit and sometimes removes the need for one.

  7. 7
    Then call, and say what you have already ruled out

    Report the indicator states, the time of day you checked, whether the network was up and whether the pattern was uniform. That turns a vague fault report into a diagnosis someone can act on.

What monitoring is actually for, and how to use it

Most homeowners check monitoring for reassurance, look at a daily total, and stop. That is the least valuable thing it does, and treating it that way is why a zero causes alarm out of proportion to what it means.

Its real value is comparison. A single day's number tells you almost nothing, because weather varies and a cloudy Tuesday is not a fault. The same month against the same month last year tells you a great deal, because it holds the season roughly constant and isolates change in the system or in its surroundings.

The second thing it does well is localise. Where a system reports at panel or string level, a fault that would otherwise require someone on the roof with a meter is visible from a sofa. One unit consistently below its neighbours in the same conditions is a diagnosis, and it is the single most useful thing to bring to a service call.

The third is documenting a trend you would not otherwise notice. Shading from a growing tree, or the sustained soiling that some regions experience, both appear as a slow decline that no single day reveals. They are also both things you can act on if you see them early and cannot if you do not.

And there is one thing it is not. It is not evidence of what your system was promised. That lives in the proposal, and comparing the two is a separate exercise with its own tolerances, which we cover on our page about underproduction.

One more habit is worth the effort once a year: export the data. Most platforms allow it, and a local copy of your own production history is the only version that survives a change of provider, a decommissioned platform or an account you can no longer access. It costs a few minutes and it is the difference between having a record of what your system did and having a memory of it.

The practical habit worth forming: look monthly rather than daily, compare to the same month a year earlier rather than to yesterday, and note anything that stays different for more than a few days. That is roughly two minutes a month and it catches almost everything worth catching.

Monitoring going dark is not usually a warranty event

One thing worth knowing before you make the call, because it changes what you are asking for.

Across the manufacturer documents we have read in this work, monitoring is generally a service rather than a warranted product feature, and the supporting hardware carries a shorter warranty than the microinverters it serves. On one manufacturer's terms, the microinverters carry twenty-five years while the gateway carries ten.

So a gateway that fails in year twelve on a twenty-five-year system is out of warranty while the system it monitors is not. Losing visibility is not the same as losing generation, and the remedy is usually a replacement you pay for rather than a claim.

That is a reason to check the indicators before assuming a fault, and a reason to keep the loss in proportion. Your system very probably kept working the entire time it was not reporting.

It also raises a question worth asking at purchase rather than in year twelve: what happens to monitoring if the company that provides the platform stops operating it. The panels and the electronics are yours; the service that displays their output is somebody else's, delivered from their servers under their terms. We cover what that means when a company fails on a separate page, and the short version is that visibility is the part of a solar system most exposed to a business decision you have no say in.

Method and limitations

What was read

The manufacturer's own Quick Install Guide for its gateway models, specifically the troubleshooting section and its indicator table. Every state and meaning quoted on this page is verbatim from that document, which is a manufacturer installation document rather than a support article, and therefore the authoritative statement of what its own hardware is signalling.

One manufacturer, and we are not generalising

The indicator scheme described here belongs to one manufacturer's gateway. Other systems use different hardware, different indicators and different conventions, and nothing on this page should be applied to them.

We attempted to obtain equivalent documentation from a second major manufacturer and could not: its site refused every request from our environment, and an archive sweep found no equivalent article. So this page describes one system in detail rather than all systems vaguely, which we think is the more useful of the two, provided it says which.

What does generalise is the structure of the problem. Every monitoring arrangement puts communication between your panels and your phone, so every one of them can show a zero for reasons that have nothing to do with generation. Whatever your hardware, the first question is whether the data path is intact.

Safety

Nothing on this page involves opening equipment, working on the roof, or touching wiring. Reading indicator lights and checking a breaker is the whole of it. Anything beyond that is qualified work, and a photovoltaic array is energised whenever the sun is on it regardless of what any breaker is doing.

Questions

My app says zero. Is my solar broken?
Probably not. A zero means the app has not been told about production, which can happen because the gateway cannot reach the internet, because it cannot reach the microinverters, or because generation genuinely stopped. Only the last is a solar fault and it is the least common of the three. The gateway’s own indicators distinguish them in seconds.
Why does my system show nothing at night?
Because it is working correctly. The manufacturer’s documentation gives "low-light or nighttime" as the explanation for both the production and the device communication indicators being off. Microinverters draw operating power from the panels, so when the sun goes down they stop reporting as well as stop producing.
How do I tell a network problem from a solar problem?
Look at the gateway. A network communications indicator that is red or off while the production indicator is green means your system is generating and only the reporting has failed. That is a home networking issue, and calling your installer will produce a visit that finds nothing wrong with the solar.
The lights are all flashing. Is that bad?
Usually not. All indicators flashing red in unison means the gateway is booting up, and flashing green in sequence means a software upgrade is in progress. Both are normal states that resolve without intervention, and both look far more alarming than they are.
One string shows nothing but the rest is fine. What does that mean?
It localises the problem, which is useful. Everything dead points at the grid connection or main wiring; one branch dead points at that circuit and its breaker; scattered individual units point at connectors or individual failures. Note which pattern you have before calling, because it is the first thing you will be asked.
Is the monitoring covered by my warranty?
Often less than you would expect. Across the manufacturer documents we have read, monitoring tends to be a service rather than a warranted feature, and the supporting hardware carries a shorter term than the electronics it serves. On one manufacturer’s terms the microinverters carry twenty-five years and the gateway ten.
Will I lose the production data from while it was offline?
Frequently not. Many systems record locally and backfill once the connection is restored, so a gap in the app can fill in retrospectively. Whether yours does is a question for your specific equipment, and it is worth knowing before you panic about a missing week.
When should I actually call the installer?
When the production indicator is red in good daylight, when a network and device check has ruled out the communication path, or when a pattern points at a specific string or circuit. Report the indicator states, the time you checked and the pattern. That is a diagnosis rather than a complaint, and it gets a faster and cheaper response.

Written and audited by

HyreSolar Research

Primary-source research, data analysis and fact checking

We are a research desk, not a sales floor. We read the statute, the tariff, the code section, the federal filing or the manufacturer data sheet ourselves, and we publish the figure with the document it came from and the date we retrieved it. Where a number cannot be traced to a primary source, we publish the shorter page and say what we could not verify. That rule has cost us whole sections, and it is the reason the rest can be trusted.

160
primary sources read and cited
220
figures with a retrieval date
115
federal and state government sources
66
researched pages published

How this desk works

  • Primary sources only. Statutes from the legislature’s own publishing system, federal data from the agency that collects it, code text from the adopted edition, manufacturer claims from the data sheet. We do not cite an article that cites a source; we go and read the source.
  • Every figure carries its provenance. A named document and the date we retrieved it, so you can check it and so you know how old it is. Retrieval dates are not decoration: an EIA rate from May is a different fact from an EIA rate from August.
  • We publish what we could not verify. Every research page carries a section naming the things we tried to establish and could not, and why. A paywalled standard, a state website that refused the request, a manufacturer that publishes no figure at all.
  • We separate measurement from modelling from our own reasoning, and label which is which on the page. A laboratory measurement, an assumption inside a modelling tool and our own inference are three different kinds of claim and they are never presented as one.
  • We do not sell solar, and we take no payment for placement, ranking or a favourable mention. Nobody buys a position on this site.

Data as of Manufacturer installation documentation read on 3 September 2026. Authorship on this site is organisational: the analysis belongs to the desk rather than to a named individual, and we do not publish credentials we do not hold. Our editorial policy sets out how we source, date and correct what we publish.

Sources & retrieval dates

  1. Enphase, Installing the Enphase IQ Gateway, Quick Install Guide — Models ENV2-IQ-AM1-240 and ENV-IQ-AM1-240. Source for the complete troubleshooting indicator table quoted on this page, including the separation of network communications, device communications and power production onto distinct indicators, the meanings of each state, and the documentation of "low-light or nighttime" as the explanation for the production and device communication indicators being off. Retrieved 3 September 2026.
  2. Enphase Energy Limited Warranty: IQ Microinverters and Balance of System Products — Cited for the point that supporting hardware carries a shorter warranty term than the microinverters it serves, which is why a gateway failure late in a system’s life is generally not a warranty event. Retrieved 2 September 2026.

Zero on the app and nobody answering?

Send us a photograph of the gateway indicators and the time you took it. We will tell you whether this is a network problem, a communication problem or a genuine production fault.

Ask about a fault Open the calculators

HyreSolar is an independent analysis and matching service. We are not an installer, lender or utility. When a reader asks to be introduced, installers may pay us a referral fee. That fee never buys ranking, scores or placement in research. Our editorial policy sets out the rules.