Home Assistant · Energy
Energy dashboard with the Shelly Pro 3EM
Which sensors belong in the dashboard and why a home energy meter counts differently from the electricity meter.
Read the article →Article · Home Assistant · Photovoltaics
Anyone who wants to see the data of their Fronius system usually ends up at the Solar.web login. It works without it: Home Assistant ships an integration that queries the inverter directly on the home network, without an account and without the cloud. On the Gen24 you first have to switch on an interface, and the battery needs an extra step in the energy dashboard. Since autumn 2026 the integration can also set limits via Modbus TCP.
The integration is simply called Fronius and has been part of the Home Assistant core since version 0.96. The documentation classifies it as “Local Polling”: Home Assistant queries the device on the home network at regular intervals, without going through a server. On the project's quality scale it is at the highest level, Platinum. So you do not need a HACS solution for Fronius.
Every inverter with a built-in Datamanager or an external “Datalogger Web” that offers the Solar API in version 0 or 1 is supported. The documentation lists, among others, Agilo, Eco, Galvo, Gen24, IG Plus, Primo, Symo, Symo Hybrid, Tauro and Verto (Plus). Whatever is connected to the inverter comes along: the Fronius Smart Meter or an S0 meter, the Ohmpilot and the battery.
The Solar API itself is a simple HTTP interface that Fronius documents openly. It returns JSON and only knows queries. According to Fronius it can run alongside Solar.web, the web interface and data logging; if you want to keep the app for the family, you lose nothing.
This is the most common reason why setup fails. Fronius describes the behaviour precisely in the Solar API documentation:
It is switched on in the inverter's web interface under Communication › Solar API. While it is off, the inverter answers every query with HTTP error 404 and the message “Solar API disabled by customer config”. The older devices with a Datamanager do not have this switch; according to the Home Assistant documentation the Solar API is active on them anyway.
Take care of this at the same time: give the inverter a static IP address in the router or create a static DHCP lease. The integration requires this as a prerequisite, or alternatively a local DNS name if your home network resolves one.
Setup runs through the user interface under Settings › Devices & services. The integration can also discover Fronius devices on the network by their DHCP request and offer them. Three things are asked for:
| Field | Meaning |
|---|---|
| Host | IP address or host name of the inverter or datalogger. Required. |
| Modbus port | Only relevant if Modbus TCP is switched on at the device. Default 502. |
| Revert the AC power limit if Home Assistant stops | Whether the inverter drops an AC power limit set by Home Assistant once it hears nothing more. Default: off. More on this below. |
A system with several inverters is a special case on the Gen24: Fronius does not support a query there that returns all devices on the network at once, and requires each Gen24 to be addressed individually. On Fronius systems with a Datamanager, by contrast, one device provides the data for the whole system.
The integration creates separate entities for each device and polls them at different intervals:
| Device | Content | Interval |
|---|---|---|
| SolarNet, power flow | PV power, grid consumption and feed-in, household consumption, battery charge and discharge power, self-consumption and autonomy rate, yield; on the Gen24 with a battery, whether it is in standby; on Gen24, Tauro and Verto, whether backup power is running | 10 s |
| Inverter | Total yield (day and year not on the Gen24), power, current, voltage, frequency, status | 1 min |
| Meter | Power, current and voltage, per phase where supported, counter readings | 1 min |
| Battery | Current, voltage, state, cycle count, capacity | 1 min |
| Ohmpilot | Energy, power, temperature | 1 min |
| Logger (not on the Gen24) | Serial number, software version, configured electricity price and CO₂ factor | 1 h |
If an error occurs, the integration extends the interval to 10 minutes, or 3 minutes for the power flow, until valid data arrives again. Many detail values, such as the voltages and currents per phase, are disabled after setup and can be switched on in the entity settings.
One quirk of the Gen24 concerns the yield: according to Fronius it updates the total yield in the power flow only every five minutes, and since firmware 1.14 it only provides the total counter, no daily or yearly values. The total counter is enough for the energy dashboard; Home Assistant builds daily values itself.
This is where most people get stuck. The Home Assistant documentation gives a recommendation for each area:
| Area | Recommended source |
|---|---|
| Solar production without a battery | Energy total of each inverter |
| Solar production with a battery | Riemann sum over SolarNet Power photovoltaics |
| Battery | Riemann sum over SolarNet Power battery charge and
SolarNet Power battery discharge |
| Grid, meter at the feed-in point | Energy real consumed and
Energy real produced of the meter |
| Grid, meter in the consumption path | Riemann sum over SolarNet Power grid import and
SolarNet Power grid export |
| Devices | Energy consumed of the Ohmpilot |
For the battery, the Solar API provides currents, voltages, capacity and cycles, but no energy counters. The
energy dashboard, however, needs counter readings in kWh, not power values. The Riemann sum closes the gap: it
adds up a power over time into an energy. In Home Assistant the helper is called Integral
and is created under Settings › Devices & services › Helpers, one each for charging and
discharging, with the metric prefix k and the time unit hours.
The integration makes this easier because it already splits the signed battery power into two entities, one for charging and one for discharging, both always positive. The same applies to grid consumption and feed-in. A template sensor that separates the sign is not needed.
On the method, the helper's documentation is worth a look: the default is the trapezoidal rule, which is the most accurate when the source updates frequently. It recommends the “left” method for values that stay stable for a long time and then change abruptly. With a power flow at 10-second intervals, the default setting fits.
If Modbus TCP is switched on, the integration additionally creates Battery charging energy total and
Battery discharging energy total on hybrid inverters that manage their battery as a separate MPP
tracker, such as the Gen24 with a battery. These are counter readings from the device, not integrated values;
according to the documentation they do not drift and survive a restart of Home Assistant. They are measured
on the DC side at the battery, though, and therefore do not exactly match a Riemann sum over the power flow
values. If you run both side by side, do not be surprised by a difference.
The same goes for the yield: Modbus provides PV energy total and values per MPP tracker. That is the
energy the modules delivered before conversion losses; on some devices it is a few percent higher. For the energy
dashboard the documentation recommends the inverter's Energy total, the AC energy you can actually
use or sell.
The Fronius Smart Meter can sit in two places: at the grid connection point or in the consumption path. What its counter readings mean depends on that. Fronius has a table of its own for this: at the feed-in point, one counter records consumption from the grid and the other the feed-in; in the consumption path, the same values record production and consumption. The Solar API reports the installation position in the power flow, as “grid” or “load”. If you are unsure whether the values are right, put them next to the reading on the grid operator's electricity meter for a week. How to approach such a comparison and where a home energy meter deviates from the electricity meter is covered in the article The Home Assistant Energy dashboard with the Shelly Pro 3EM.
The Solar API is read-only. Everything the integration changes on the device goes via Modbus TCP. This option is new: with Home Assistant 2026.9, Modbus TCP via the SunSpec models came to the Fronius integration, initially for values per MPP tracker. As of the check date, the integration also documents control entities.
If the permission was only granted after setup, reload the integration. If the values per MPP tracker are missing, check the port setting and, if necessary, bring the inverter out of power-saving mode.
| Entity | Type | Effect |
|---|---|---|
AC power limit / AC power limiting | Number and switch | limits the inverter's output power |
Battery charge power limit / … limiting | Number and switch | limits the battery's charging power |
Battery discharge power limit / … limiting | Number and switch | limits the discharging power |
Battery minimum reserve | Number | minimum state of charge that stays in the battery |
Battery grid charging | Switch | allows the battery to charge from the grid |
All setpoints are percentages. A limit in watts or a maximum state of charge cannot be set this way. If you want, for example, to charge the battery from the grid at night when electricity is cheap, you build that from these building blocks in an automation. Which strategy is behind it and whether it pays off is covered in the article Controlling a home battery with Home Assistant.
For the AC power limit there is a fallback, which is switched off by default in the integration. If it is on, the inverter drops the limit one hour after it last received it and follows its own settings again. Home Assistant resends the limit every 15 minutes, so the hour only runs out if Home Assistant has really stopped. Fronius describes this behaviour as a revert time: if no new Modbus message arrives within that time, the setpoint ends and the operating mode with the next higher priority takes over.
For the battery setpoints, Fronius documents no such fallback. A charge or discharge limit, a minimum reserve and grid charging therefore stay in place, whatever happens to Home Assistant. If you build an automation that blocks discharging during the day, think about what happens if the command to lift it never comes.
The Home Assistant documentation explicitly warns against confusing the two. An export limit agreed with the
grid operator is implemented on the Fronius by Dynamic power reduction, because it measures at the grid
connection point. The AC power limit only knows the inverter's output power. If Modbus is above
Dynamic power reduction in the priority list, an AC power limit permanently set to 100 % overrides
that limit, and the system may no longer comply with what the grid operator allows. This affects, for example,
systems with the 60 % limit under Germany's solar peak law. If you want to
regulate feed-in yourself with Home Assistant, the limits of such a control loop are covered in the article
Zero export with Home Assistant.
If you run a Fronius Wattpilot alongside the inverter: the Fronius integration does not query it; its device list names inverters, meters, Ohmpilot and battery. What the Wattpilot offers for control under section 14a EnWG is covered in the article Fronius Wattpilot and section 14a EnWG; what “section 14a compliant” means for a wallbox at all, in the article Wallbox “section 14a compliant”.
No. The Fronius integration queries the inverter directly on the home network via the Solar API, without an account and without the cloud. Solar.web keeps running independently; Fronius states that data logging, the Solar.web connection, the web interface and the Solar API can be used independently of each other.
Usually the Solar API is switched off. On new Gen24, Tauro and Verto devices with firmware 1.14.1 or later it is disabled from the factory, and likewise after a factory reset on that firmware. It is switched on in the inverter's web interface under Communication, Solar API. While it is off, the inverter answers with a 404 error and the message Solar API disabled by customer config.
Not via the Solar API, which is read-only. Since Home Assistant 2026.9 the integration can also use Modbus TCP. If control via Modbus is allowed on the inverter, it creates entities for the AC power limit, the battery charge and discharge limits, the minimum reserve and charging from the grid. All setpoints are percentages.
The Solar API only provides power values for the battery, no energy counters. The Home Assistant documentation therefore recommends converting the entities SolarNet Power battery charge and SolarNet Power battery discharge into kWh with the Integral helper (Riemann sum). With Modbus TCP, hybrid inverters such as the Gen24 with a battery also provide counter readings from the device, which do not drift; they are, however, DC values at the battery.
No. According to Fronius, the Solar API is always accessible without authentication, regardless of the web interface passwords. Any device on the same network can read the values. Nobody can write via the Solar API; the write path is Modbus TCP, and the Gen24 lets you restrict it to specific IP addresses.
The inverter only provides some values, such as PV power, when they are non-zero, and an inverter in power-saving mode does not answer at all. If you set up the integration at night, you will therefore see fewer entities. According to the documentation, waiting for sunrise helps.
The information on the integration comes from the Home Assistant documentation and source code, that on the Solar API and Modbus from Fronius's operating instructions. I have no hands-on experience with a Fronius inverter myself; this page is a sourced overview, not a field report. The integration is developing quickly at the moment, especially the Modbus part. What is written here applies to the state of 13 October 2026.
Haag Automation has no business relationship with Fronius. Writing via Modbus changes the behaviour of the system; responsibility for settings specified by the grid operator remains with the operator.
Want to bring your Fronius system into Home Assistant properly, with the battery in the energy dashboard? I can set it up with you – the first conversation is free.