There is an issue with this firmware version. The SolarApi (the one the core integration uses - and maybe also your charger) didn’t work properly there. Meanwhile there should be a fixed version released by Fronius.
I don’t know if Modbus Communication was also affected, but I wouldn’t think so as afaik it was an HTTPS / certificate issue in the internal Webserver.
That sounds very reasonable.
the changelog (https://firmware-download.fronius.com/releaseGroup/Gen24/common/1.35.8-1/changelog.pdf) does not mention anything, do you know if ‘1.35.8-1’ (march 11th) is the fixed one?
I don’t know, as I don’t have a Gen24 device. As this thread is about Modbus, maybe continue here:
Hi @redpomodoro,
this integration is really helpful and I am using it now since 3 months. From time to time I experience the problem, that the storage charging lifetime energy is jumping back and forth:
The “upper” values are the correct ones. But I have no idea why it is jumping down to this constant value of 429.496 Wh.
This behaviour only happens occasionally. I do not see it in February, in March only yesterday.
But it also happened in January:
It would be really nice, if that could be fixed as it leads to wrong data in the Energy Dashboard.
Hi @redpomodoro,
next / same problem here: With core version 2025.3.1, I get this when the modes are switched by an automation:
I have no clue what’s going on here. After deactivating “Control via Modbus” in the Fronius WebInterface, it constantly works in “Auto” mode - but of course cannot be controlled via HomeAssistant anymore.
After a bit more debugging: These continuous changes of Holding / Discharging seem to be sent by the inverter. They even occur, when control via Modbus is deactivated.
hello.
i discover today this integration and its very interesting.
I dont have a byd battery yet (maybe in some months i will buy one).
I have a, maybe, stupid question.
What is the diference between this integration and the oficial in reading information times?
is modbus more acuracy and less lag that oficial fronius.net ??
thanks a lot
Can I use above stuff to create automations to set my output limit on my snap primo3
Sorry I’m new to all this 
I’m needing to set an output limit on the Primo, around 50 watts above what ever is being produced. For some reason, manually setting the softlimit like this, stops my lights flickering AND stops output Volatge swinging ± 20 volts! which in turn stops a 435 error that pops up otherwise!
I started using the other one a few years back, but as soon as this one became available, I got both running side by side. I believe this one here would probably suffice, but I have a lot of automations based on the other one already.
Now, this one here has way better control over the battery. I use it to change the minimum State of Charge (SoC) at midnight from the common 5% to 20%, and back to 5% at 7am. That time frame has much lower electricity prices, and this way I make sure I have enough battery for the morning activities before the sun hits my panels (neighbor tree shadow during winter, an axe anyone?).
Anyone able to speculate what happens when you use ‘Charge from Grid’ when there is solar available?
Getting a BYD HVM soon, and trying to workout control logic.
On days where there is insufficient solar to fully charge the battery, if I select ‘Charge from Grid’ and then set an amount of say 1000W. Will it:
a) only charge at 1KW, partially from solar + grid, but if solar exceeds 1000W, export the rest?
b) charge at a maximum of 1KW from the grid, plus whatever is coming from solar. Thereby if the is 2000W solar, it will charge at 3000W total?
c) something else?
Any chance this could incorporate Export limitation using this
- service: modbus.write_register
data:
unit: 1
hub: mb_fronius
address: 40236
value: "0"
- service: modbus.write_register
data:
unit: 1
hub: mb_fronius
address: 40232
value: "{{ states.sensor.solar_trim_percent_when_greater_load.state }}"
- service: modbus.write_register
data:
unit: 1
hub: mb_fronius
address: 40236
value: "1
Hi
First of all: thanks for your work!
I got my Fronius Symo Advanced installed this week.
I was hoping that I could use your integration to monitor the two MPP trackers (north/south). The values aren’t really relevant, but they are still interesting for my curiosity 
I can read both values in the Fronius solarweb portal. I would also like to have them in my HA.
Is there a chance that you can also optimize your extension for the Symo? Or does anyone know of another option?
Hi! I noticed you have the same setup as me (Symo24 10 + HVM 13.8), and it looks like everything’s working smoothly on your end 
I’m running into trouble trying to install the Addon — I keep getting the error message {"message":"Invalid handler specified"} and haven’t found any solid answers on GitHub.
Do you happen to have a tip (or three) I could try? Really appreciate any help 
Hello
I updated today to 2025.8.2
And updated pyton scripts pro to de latest version.
And the fronius modbus stop working.
I dont konw if the problem was ha update or python
The error is this:
EDIT:
I think the problem is ha update 2025.8.2 that includes this change:
And Maybe fronius modbus check the pymodus versión as old versión??
hello
this integration is fantastic!!!
but some people in the github want to help.
@redpomodoro
do you see it???
IDEA: adding more maintainers to the repo · Issue #55 · redpomodoro/fronius_modbus
Hi, great Integration !
Question :
I have 2 Fronius inverters, both with a BYD home battery pack attached
This integration works perfect to put 1 inverter + 1 battery pack in this integration (gives me 51 entities)
BUT When I try to add the second inverter, it doesn’t seem to work
(it adds the device, but it doesn’t get add any entities to it)
Help or a workaround would be highly appreciated 
Hello! Anyone tried this integration with the new Reserva battery?
Can this be used to stop photovoltaic export to the grid ? I’ve tried a few options and none seem to stop export to grid but still run all power of the photovoltaic s
see the PR pending of aprove. one of this is for this exact problem
I apply this changes in my integration and now works fine all my fronius:
I’ve been running @redpomodoro original version for some time, and getting my BYD battery soon so I thought I might roll up all the PR’s into a new fork for those that are interested, and push out a new version with them incorporated.
Hope I havent stepped on any toes, but I didnt see mention of an up to date fork, only those incorporating their own changes.
I’m not python savy, so it loads up and works on mine, however I dont have a battery connected yet. If I can work it out, happy to add others to the repo if they wish to assist with PRs.
