Fronius Modbus Integration

[redpomodoro]

@nicolaufg

Some comments (with the sole aim to help )
“PV Charge Limit”
It is not the first in the list of controls while it is referred to as the first one everywhere in the documentation and -old- screenshots. Not a big deal.

Keeping documentation updated is always a challenge I’ll review it for the next release.

@nicolaufg

Using % or W/kW
It would be great to have the charge/discharge limits in W or kW rather than a % of the total power. Not sure if this can be done automatically at the time of setting up the device once the maximum capacity has been read, or if it would require the user to provide it beforehand in order to set the limits to the sliders…

Considered this before but have not gotten round to implement it. Added it to list for a future release:

Feature request: Show limits in Watts instead of %

@nicolaufg

“Minimum Reserve”
It is independent of the “SoC Minimum” in the “Battery Management” screen of the inverter site. Is this the expected behaviour? If so, it is good because the original one in the web can be left as a fallback in case something goes wrong in HA.

Minimum Reserve is the same as ‘Reserve Capacity’ in the web interface. And as far as I tell from the documentation it is not possible to set ‘Soc Minimum’ through modbus. Which indeed is good so that a battery can’t be totally discharged by accident.

@nicolaufg

Possible clash
What would happen if I have a charging schedule set through the inverter web and this integration commands something different? I haven’t tried

I haven’t tested this either, but just to be sure I’ll add a caution to the documentation to disable the charging schedule to avoid unexpected behavior.

[redpomodoro]

@nicolaufg

I noticed the settings selected by the user are changed when different Modes are selected… I understand some of these settings are ignored depending on the settings (as per the table provided), but changing the values selected by the user in HA seems a bit confusing. I see it is done through change_settings every time the Mode is changed (set_auto_mode, set_charge_mode, etc).

In my opinion, it would be better to decouple the user choices from the actual values in the inverter, and only internally use the relevant values and ignore/overwrite those not needed in a specific Mode. Otherwise, selecting one Mode and then to another one could lead to unexpected results.

I also noticed a weird behaviour:

1. I set “Grid Charge Power” to 10%
2. I change “Mode” to “Charge from Grid”
3. Unexpectedly, the “Grid Charge Power” changes to 100% and the inverter charges at full throttle.

I believe the logic to check if the setting is below 0 fails:

    def set_grid_charge_mode(self):
        grid_charge_power = self.data.get('grid_charge_power')
        if grid_charge_power is None:
            _LOGGER.error(f'Grid Charge Power not set')
            return
        if grid_charge_power == 0:
            grid_charge_power = 100
        discharge_rate = grid_charge_power * -1
        self.change_settings(mode=2, charge_limit=100, discharge_limit=discharge_rate, grid_charge_power=grid_charge_power)
#        self.set_minimum_reserve(99)
        _LOGGER.info(f"Forced charging at {grid_charge_power}")

Not familiar with the internals of HA, but could it be the value from charge_rate = self.data.get('charge_limit') is not the expected one??

Changing to other Modes also seem to scramble the limits (sorry, no time to look at it now).

From UI perspective it is indeed confusing and have to look at documentation to see which controls are ignored or is not intuitive. I’ll look into if I can disable the controls to make it more user friendly.

Feature request: Disable controls that are ignored in certain modes

As far as the behavior it should only change setting if it is zero. When it is 10% it should work.

Unexpected behavior when changing mode and limit is preset.

[callifo]

With Gen24/BYD batteries, what is the minimum charge rate you can set the battery down to? It’s it 6A like an EV or can you literally crank down to 1W?

[redpomodoro]

You can you down to 0.01% of the maximum charge rate, so indeed 1W for 10KW inverter.

[redpomodoro]

Version 0.1.4 is out!

BREAKING CHANGES:

• The limit and power controls are now in Watts instead of percentages. Feature request: Show limits in Watts instead of % · Issue #13 · redpomodoro/fronius_modbus · GitHub @nicolaufg
• Controls are enabled depending on the active control mode. This should make it more intuitive to use the integration. Note to change the mode first then set controls active in that mode. Feature request: Disable controls that are ignored in certain modes · Issue #14 · redpomodoro/fronius_modbus · GitHub @nicolaufg

Other changes:

• Changed entities names to include device names to make them easier to distinguish. Feature request: add entity prefix · Issue #12 · redpomodoro/fronius_modbus · GitHub @tompat
• Added multiple data points to see the connection status at various points in the system. Feature request: offgrid or mode sensor · Issue #16 · redpomodoro/fronius_modbus · GitHub

[onestyle (Christian)]

Hi! Is there an option to read mpp1 and mpp2 seperately by HA? I have a Fronius Symo 4.5-3-M inverter. I can’t find an entity in the official implementation nor a modbus register in the documentation.

[redpomodoro]

Yes through modbus mpp trackers can be read individually. The integration supports this:

[onestyle (Christian)]

Thank you for your message. You have a GEN24 inverter, whereas mine is an older or more affordable model. It seems that MPP1 and MPP2 are not supported with my inverter and the official integration. That’s why I’m looking for an alternative way to implement them.

[redpomodoro]

The current Symo models do support modbus TCP. Just try if you can enable the modbus interface in the inverter web control.