Fronius Primo Inverter Troubleshooting (Homeowner Guide)

The Fronius Primo is the single-phase member of the SnapINverter family — the unit on the wall of countless homes in the 3 to 8 kW range. It shares Fronius STATE codes with its three-phase siblings, but its single-phase design, integrated WLAN, and residential feature set give it its own quirks. This guide focuses on Primo-specific behaviour and faults.

Quick Answer

Primo troubleshooting follows the same core logic as all Fronius inverters — LEDs, STATE code, externals, one safe restart — with Primo-specific notes. A dark display at night is normal sleep, not a fault. Many Primo communication issues trace to home Wi-Fi changes, since models with integrated WLAN join your network directly. For persistent STATE codes, note the code and contact a Fronius service partner; the SnapINverter design allows on-site board replacement, and you should never open the unit yourself.

Normal Primo Behaviour (Not Faults)

• Dark display at night — with no DC from the array, the Primo sleeps; LEDs and display go dark until morning.
• Fan noise under load — the cooling fan ramps with output on warm days. Constant loud grinding is different and worth reporting.
• Clicks at startup and shutdown — relays engaging during the morning self-test and evening wind-down are normal.
• Brief dips on cloudy days — the Dynamic Peak Manager re-scans for the true maximum power point when shading changes; short output dips are by design.

Primo-Specific Checks

LED bar and display

The Primo’s LED section mirrors the SnapINverter language: flashing green means feeding, yellow means a warning, and red means a fault with a STATE code on the display. Record the exact code before doing anything else — it determines everything that follows.

Wi-Fi and Solar.web connection

Primos with integrated WLAN or the Datamanager 2.0 card connect directly to home Wi-Fi, so router replacements, password changes, and mesh-network upgrades are the top cause of “the app shows nothing” complaints. Re-run the Wi-Fi setup via the inverter’s access-point method described in the manual. If the display shows normal production while the portal is silent, the inverter is fine — it is purely a communications issue.

SuperFlex string configuration

The Primo’s two MPP trackers (SuperFlex design) tolerate different string lengths and orientations. After any panel work, mismatched strings across the two trackers can produce confusing yield patterns — check that both trackers show plausible voltage in Solar.web.

Smart Meter and Ohmpilot integration

If your Primo pairs with a Fronius Smart Meter or Ohmpilot, export limiting or hot-water diversion settings can make output look “wrong” — for example, production capped at a grid export limit. Review these settings before suspecting a hardware fault.

Common Primo STATE Codes

Primo units report the standard Fronius STATE family. The most encountered in residential service are STATE 307 (DC-side fault — see our Fronius STATE 307 code page), STATE 475 (insulation fault, often moisture-related — see Fronius STATE 475), grid-window codes in the 401–419 range after network events, and temperature codes on heatwave afternoons. Arc-fault equipped models can also report arc events — treat repeated arc faults seriously and call a professional promptly.

Primo Night-Time Behaviour and Standby Consumption

A common source of confusion: the Primo draws a tiny amount of power overnight to run its monitoring and stay reachable on the network. If your consumption monitoring shows a small overnight draw attributed to the solar circuit, that is usually this standby load — not a fault. What is not normal is the inverter attempting to start repeatedly after dark, showing brief LED activity in a loop. That pattern suggests a control or sensing issue and deserves a service call, with a note of exactly what the LEDs do and when.

When to Call a Professional

Call a Fronius service partner if a STATE code survives a safe restart, if arc-fault or insulation codes recur, if the unit is silent in full sun with isolators on, or if you notice heat damage, water ingress, or persistent fan failure. Provide the STATE code, LED state, photos, and serial number — it dramatically shortens the visit.

Frequently Asked Questions

Why is my Primo display blank every night?

Normal behaviour — with no DC input from the array, the inverter enters sleep mode and wakes with the sun. Only a daytime blank display with isolators on is a concern.

My Primo works but Solar.web shows no data — is it broken?

Almost certainly a Wi-Fi or communications issue rather than a hardware fault. Check the display’s production totals, then re-run the network setup.

Can I reset my Primo from the app?

No — restarts are done with the physical isolators in the correct sequence. The app and Solar.web are for monitoring, not control.

How does Primo troubleshooting differ from the three-phase Symo?

The STATE codes and LED language are shared across the SnapINverter family. The Primo’s differences are its single-phase design and residential features — integrated WLAN, Dynamic Peak Manager behaviour, and Smart Meter or Ohmpilot integration — which is where most Primo-specific confusion arises.

Related Error Codes

• Fronius STATE 307 — DC-side protection trip
• Fronius STATE 475 — insulation resistance fault

Sources: manufacturer installation and operation manuals (Fronius, SolarEdge, SMA, Enphase, Growatt), Clean Energy Council consumer guidance, and U.S. Department of Energy homeowner solar resources.