Summary: After years of working just fine, yesterday at 21:12 the integration suddenly stopped providing all entities in it's SolarNet device, showing as unavailable now. But all others are fine, and the (local) API endpoint that delivers the data is also fine and has all the data it always has.
Details: The Fronius integration (part of HA Core) brings data from their (solar) inverters and associated devices into HA. It creates multiple (virtual) devices that represent different aspects (inverter, battery, meter), one of them being the SolarNet, which contains all the power flow and usage. All of the data comes from the SolarAPI that is a fully local endpoint, providing the raw values. Basically one for each of the HA devices. All HA entities belonging to other devices work perfectly fine. Looking into the SolarWeb (online portal of Fronius) I cal also see the power flow just fine.
To be clear: there was no update to the firmware of the inverter. The last HA Core update was ~24 hours before this, and afaict it didn't contain any changes related to Fronius. I did restart both HA and (much later) the inverter as well, with no changes.
Hardware: Symo GEN24 8.0 (ROW 1.37.6-1), BYD Battery-Box Premium HV (7.68 kWh), Fronius Powermeter at Grid interconnection point.
Screenshots are attached, showing both the SolarNet (not working) and SmartMeter (working).
Digging for logs was not very successful, since HA doesn't save logs anymore since I think november of last year or so. But I did find one line in the Docker logs of the HomeAssistant container itself:
2026-03-25 21:12:12.367 ERROR (MainThread) [homeassistant.components.fronius] Error fetching fronius_power_flow_Fronius-Gen24.<domainname_censored> data: An error occurred while attempting to fetch data: BadStatusError at GetPowerFlowRealtimeData.fcgi. Code: 255 - UnknownError. Reason: Internal error..
Any way to un-break my SolarNet?