Consistency between absolute/relative limit values and homassistant integration

[reinhard-brandstaedter]

What happened?

Via MQTT or the UI we can set the inverter limits higher than the actual limit of the inverter.
E.g. we can set a HMS-2000 absolute limit to 3000/150%.
This is OK as in my experience this allows to get more from 2 channels of a 4 channel inverter as the limit is evenly split across 4 channels. With a limit of 2400W and only 2 channels of the inverter connected I can still get 1200W.

However the homeassistant templates that are pushed for auto-config of HA have different max values than what is allowed in the UI/MQTT commands. This leads to warnings:

15:44:03.421 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.hms_2000_limit_nonpersistent_relative: 140.0 (range 0.0 - 100.0)
15:44:03.421 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.hms_2000_limit_persistent_relative: 140.0 (range 0.0 - 100.0)
15:44:03.426 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.hms_2000_limit_nonpersistent_absolute: 2800.0 (range 0.0 - 2250.0)
15:44:03.427 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.hms_2000_limit_persistent_absolute: 2800.0 (range 0.0 - 2250.0)

In my opionion those max values in the config template should also be adjusted to 150% resp. 3000 (for a 2000W inverter)

To Reproduce Bug

• enable HA integration/auto config
• set the limit to 150% in OpenDTU
• observe HA log for the warning

Expected Behavior

same limit boundaries on MQTT/UI side and HA configuration

Install Method

Pre-Compiled binary from GitHub

What git-hash/version of OpenDTU?

https://github.com/tbnobody/OpenDTU/releases/tag/v24.3.15

Relevant log/trace output

No response

Anything else?

No response