v1.4.0b2

The first release with the 1.x code, which replaces 0.3.x. It is a beta: HACS offers it only with Show beta versions switched on for this repository.

The Modbus layer is rewritten. The integration no longer opens its own Modbus connection: it uses Home Assistant's built-in modbus integration and the modbus-connection library, and discovers the inverter's register map at runtime through SunSpec. It can run beside other integrations on the same inverter, and a slow web interface no longer holds up the Modbus values.

The web login is optional. With Without the web API the integration runs on Modbus and the web endpoints that need no login. This works but is not the recommended way: you have to set up the inverter's Modbus by hand, and the battery settings of the web interface (such as the SoC window and backup reserve) and the export soft limit are missing.

Coming from 0.3.x, read this first. Take a Home Assistant backup: going back to 0.3.x afterwards needs it. Entries, entity IDs, history and statistics are kept, but:

• Home Assistant 2026.9.0 or newer is required.
• Enum states are translation keys now, such as auto instead of Auto. Automations and templates that compare against the old texts need updating.
• The checkbox "Restrict Modbus to this IP" became the option Modbus IP restriction. An unchecked box no longer lifts the inverter's restriction: it now keeps the inverter's setting. Allowing Home Assistant adds its address instead of replacing the allowed hosts while the restriction is on.
• The battery's SoC window now follows the inverter's own switch: SoC Maximum and the new SoC Minimum (Web API) can only be changed while the new Web API SoC mode is Manual. In 0.3.x they followed Self-consumption optimisation, so automations that set them may need to switch this mode first.
• Grid charge power and Grid discharge power now do what they say. 0.3.x converted the watts with the maximum of the opposite direction, so with a charge maximum of 10 kW and a discharge maximum of 5 kW, 2 kW charged at 4 kW. If the two maximums differ, check the values your automations set.
• PV charge limit and Discharge limit convert watts with WChaMax, the reference Fronius documents, instead of the battery's nameplate rating. If the two differ, check the values your automations set.
• Values from the web interface update on their own interval, 60 seconds by default. In 0.3.x they came with every Modbus poll, every 10 seconds by default.
• A missing or rejected web login is asked for through Home Assistant's reauthentication on the integration, not in Repairs.

Some entities show a new name; their entity IDs stay, so automations keep working:

0.3.3	Now
Battery API mode	Self-consumption optimisation
Core storage control mode (inverter)	Control mode
Events	Event severity
Max charging power	Charge/discharge reference power
SoC Minimum	Modbus storage reserve
Temperature	Internal temperature
AC Module Temperature	AC module 1 temperature
DC Module Temperature	DC module temperature (3)
Battery Module Temperature	DC or battery module temperature

The full list is in the README, the Migration page and the changelog under 1.0.0b1.

Coming from redpomodoro 0.1.9: update straight to this version and do not remove the integration first. Entities keep their entity ids and history, and devices keep their area and name. The four MPPT sensors get new entity ids; storage_power has no successor. Home Assistant asks for a web login after the update; some entities appear only after that. Going through 0.3.x removes most of the old entities, and that cannot be repaired.

Do not uninstall the old repository. The Marketplace removes the integration's configuration with it, and the update then has nothing to carry over. Instead, take a backup, replace the folder config/custom_components/fronius_modbus with the one from this release by hand, and restart. The Marketplace has no way yet to switch repositories, so it will not offer updates for this one (discussion). If you still run HACS, removing the repository there keeps the entry.

New since 0.3.x

• Why the inverter throttles (Throttle reason, #112), and the inverter's event log as entities and events.
• Module temperatures, fans, per-phase power and battery health from the web interface, without a login.
• An optional fast read of the grid meter's power, as often as every second, for battery controls that follow feed-in.
• Discovery over mDNS; an entry set up by IP address follows the inverter to a new address.
• A diagnostics download with the raw register map.

Changed

• Load can be negative, as in the 0.3.4 pre-releases. With other generation behind the grid meter that the inverter does not see, such as a balcony inverter or an AC-coupled battery, it is the household's consumption minus that generation. Up to 0.3.3 it stopped at 0 W, so automations and energy calculations that expect 0 W or more need a look.

Fixed

• Updates from redpomodoro 0.1.9, from 0.3.3 and later, and from the 0.3.4-rc2 pre-release keep their entities and history (#155, #134).
• A load step between the inverter and meter reads no longer shows in Load as a spike.
• Export soft limit is read and written where inverter firmware 1.42 keeps it (#154).
• Charge from Grid followed by Block Charging no longer fails with an inverter error (#126).
• The storage mode select shows what the inverter does, not what was requested (#127).

Added

• A brand icon.
• tools/inverter_dump.bat reads every Modbus unit with -AllUnits.

The full documentation moved to the wiki. Everything else is in the changelog.