Fronius Modbus Integration

farmio · March 12, 2025, 8:48am

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.

mgrn0 · March 13, 2025, 7:35am

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?

farmio · March 13, 2025, 7:50am

I don’t know, as I don’t have a Gen24 device. As this thread is about Modbus, maybe continue here:

github.com/home-assistant/core

Fronius Gen24 firmware 1.35.4-1 not responding

opened 07:21PM - 19 Feb 25 UTC

darkomani

integration: fronius

### The problem I just looked at 5pm on Homeassistant and no updates or anythin…g done and suddenly no connection to Fronius, Fronius ist still working with the API checked that via browser like https://142.206.xxxxxxsolar_api/v1/GetMeterRealtimeData.cgi?Scope=System ### What version of Home Assistant Core has the issue? core-2025.2.3 and now upgraded to core-2025.2.4 thought it would help ### What was the last working version of Home Assistant Core? core-2025.2.3 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Fronius Integration can not connect any more ### Link to integration documentation on our website https://www.home-assistant.io/integrations/fronius ### Diagnostics information 2025-02-19 19:52:13.008 DEBUG (MainThread) [homeassistant.components.fronius] Finished fetching fronius_logger_http://142.206.XXX data in 3.083 seconds (success: False) 2025-02-19 19:52:36.432 DEBUG (MainThread) [homeassistant.components.fronius] Finished fetching fronius_logger_http://142.206.XXX data in 3.056 seconds (success: False) 2025-02-19 19:53:19.632 DEBUG (MainThread) [homeassistant.components.fronius] Finished fetching fronius_logger_http://142.206.XXX data in 3.049 seconds (success: False) 2025-02-19 19:54:43.152 DEBUG (MainThread) [homeassistant.components.fronius] Finished fetching fronius_logger_http://142.206.XXX data in 3.105 seconds (success: False) 2025-02-19 19:56:06.480 DEBUG (MainThread) [homeassistant.components.fronius] Finished fetching fronius_logger_http://142.206.XXX data in 3.075 seconds (success: False) ### Example YAML snippet ```yaml YAML did not change at all so I guess there is no problem... the entity itself does not have a connection ``` ### Anything in the logs that might be useful for us? ```txt I do not know if this problem comes from the integration or home assistant itself ``` ### Additional information _No response_

Flix007 · March 14, 2025, 7:28am

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.

Flix007 · March 16, 2025, 9:05pm

Hi @redpomodoro,
next / same problem here: With core version 2025.3.1, I get this when the modes are switched by an automation:

This happens although the mode is “Auto” since hours and the SOC is > 70%.

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.