microinverter-failed-to-report on an Enphase Energy Enphase IQ8 microinverters: Microinverter cannot communicate with the Envoy/IQ Gateway over the AC power lines (power-line communication)
Short answer
On an Enphase Energy inverter, microinverter-failed-to-report means: Microinverter cannot communicate with the Envoy/IQ Gateway over the AC power lines (power-line communication). The inverter keeps running. An engineer is needed to fix the cause.
Reviewed 24 September 2026 · 1 source
What it means
The manual says: Microinverter cannot communicate with the Envoy/IQ Gateway over the AC power lines (power-line communication).
Part involved: power-line communication.
When it shows: Microinverter cannot communicate with the Envoy/IQ Gateway over the AC power lines (power-line communication).
Likely causes:
- Tripped solar breaker; gateway plugged too far from panel or sharing socket with noisy devices; relocated gateway; new appliances adding line noise.
Is it safe?
| Does the inverter stop? | No |
|---|---|
| Severity | Warning |
| Engineer needed? | Yes |
The inverter keeps running.
Resetting itself: yes.
Manual reset: Recovers automatically on a later polling cycle (gateway polls every 5 min).
What you can check
- Open the Enphase App (or Enlighten) and note the event name, affected microinverter serial number(s) and date/time for your installer.
- Occasional instances can be ignored.
- Check the solar breaker(s) are on.
- If the gateway is plug-in, make sure it is plugged directly into a socket (not a surge-protected extension) and remove other devices sharing that socket.
What the engineer will check
- Check PLC signal level; relocate gateway nearer the consumer unit; check branch breakers; add communications filtering.
Who to ask for: Enphase-certified installer / MCS PV installer.
Certification: Qualified electrician (BS 7671; MCS-certified PV installer for work on the PV array/DC side).
What you might notice
Sources
- Installer's Guide to Troubleshooting an Enphase System ↗ · August 2014 · page 43 · Reviewed 24 September 2026
A code explains what the controller detected, not a confirmed root cause.
Reviewed: 24 September 2026