Reference · built on requestConnectorEnergy, EV & distributed resources

Fronius Solar API

Local JSON readings from Fronius inverters and Datamanager 2.0: power flow, inverter output, smart meter, storage, Ohmpilot, and archives.

Request accessPricing ↗

About

Fronius builds string inverters, hybrid inverters, and the GEN24, Tauro, and Verto lines, and each inverter or Datamanager 2.0 answers HTTP requests on the local network under /solar_api/v1/. The Solar API is read-only and returns JSON for the inverter itself and for connected Fronius Smart Meters, batteries, Ohmpilots, and string controls. Cloud history for the same systems lives in Solar.web, which Fronius exposes through the separate, chargeable Solar.web Query API.

Through Fibric, an operator polls each inverter's power flow and meter readings from a gateway on your network, spots a site that stopped feeding in or a battery that never charges, and drafts the notice or service request for your approval.

This is a reference listing. It documents what Fibric would read from Fronius Solar API and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Inverter output through GetInverterRealtimeData.cgi with Scope Device or System and the CumulationInverterData, CommonInverterData, 3PInverterData, and MinMaxInverterData collections
  • Grid, load, generation, and battery power for the whole site through GetPowerFlowRealtimeData.fcgi, including Ohmpilot smart loads
  • Fronius Smart Meter channels through GetMeterRealtimeData.cgi, and battery state through GetStorageRealtimeData.cgi
  • Ohmpilot state through GetOhmPilotRealtimeData.cgi, and string currents and sensor cards through GetStringRealtimeData.cgi and GetSensorRealtimeData.cgi
  • Logged history on Datamanager and Hybridmanager through GetArchiveData.cgi, with channels such as EnergyReal_WAC_Sum_Produced, InverterErrors, and InverterEvents in 5 to 30 minute intervals
  • Device inventory and logger identity through GetActiveDeviceInfo.cgi, GetInverterInfo.cgi, GetLoggerInfo.cgi, and the highest supported version through GetAPIVersion.cgi

Proposed actions

Read-only. Actions need a separate connector.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Spot the inverter that stopped feeding in

    The operator polls GetPowerFlowRealtimeData on each site during daylight. When generation stays at zero while neighbors produce, it drafts a service request with the inverter's error and event channels.

    With Array Yield, Alarm Triage

  • Watch export against a feed-in limit

    Reading grid power from the Smart Meter alongside the inverter output, the operator flags sites exporting near their limit and proposes a curtailment change on the system that owns control.

    With Export Limit, Peak Demand

  • Notice a battery that never charges

    Daily storage readings show state of charge and charge power. The operator proposes a check when a battery stays flat for several days while PV production is normal.

    With Battery Dispatch, Sensor Health

Requirements

  • Network reach from a Fibric gateway to each inverter or Datamanager 2.0, on the LAN or over your VPN
  • On GEN24, Tauro, and Verto, the Solar API enabled in the WebUI under Communication, Solar API; off by default on bundle 1.14.1 and later
  • One request per GEN24, Tauro, or Verto inverter, since system-wide requests across inverters are not supported on those devices
  • A Datamanager or Hybridmanager for archive requests; GEN24, Tauro, and Verto do not provide history
Authentication
No credentials. Requests are unauthenticated HTTP GETs to the inverter or Datamanager on the local network, so access control is the network itself.

Limits

  • At most 2 realtime requests in parallel, with 4 seconds between consecutive calls; archive requests run one at a time with 120 seconds between calls
  • Archive access is restricted to 4 clients system-wide, and the Datalogger keeps only as many days as its memory allows
  • Realtime requests need the device awake; a device in standby or offline returns no data
  • Numeric types are not fixed: a value such as UAC can be an integer on older inverters and a float on newer ones

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Fronius Solar API ↗

Questions and answers

Why does a GEN24 answer 404 to Solar API requests?
The Solar API is disabled. On GEN24 devices shipped with bundle 1.14.1 or later it is off by default, and a request returns a 404 with the message Solar API disabled by customer config. Turn it on in the WebUI under Communication, Solar API.
Can Fibric read history from a GEN24, Tauro, or Verto?
Not through the Solar API. GetArchiveData is available on Datamanager and Hybridmanager platforms only; Fronius lists GEN24, Tauro, and Verto as never supported for archive requests. History for those inverters comes from Solar.web through the Solar.web Query API.
How often can the connector poll?
Fronius allows up to 2 realtime requests in parallel with a 4 second gap between consecutive calls. Archive requests may not run in parallel and need 120 seconds between calls. The connector paces itself to those figures per device.
Ask about Fronius Solar API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Fronius Solar API through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy