[Bug]: ** `number.charge_rate max attribute uses max_current_hard instead of max_current_soft`

[PascalBBBB]

The problem

Description
The number.charge_rate entity has its max attribute set to max_current_hard (80A)
instead of max_current_soft (32A).

This causes issues with the openevse-card which displays 80A as the maximum
charge rate instead of the configured 32A limit.

OpenEVSE API values (from /config endpoint)

• max_current_soft: 32
• max_current_hard: 80

Home Assistant entity attributes

• number.charge_rate: min=6, max=80 (should be max=32)

Expected behavior
The max attribute of number.charge_rate should use max_current_soft (32)
as this represents the user-configured limit, not the hardware maximum.

Environment

• OpenEVSE Firmware: 8.2.3.CGMI
• WiFi Firmware: v5.1.5
• Service Level: 2 (European)

What version of Home Assistant?

core-2025.12.5

What version of OpenEVSE?

• OpenEVSE Firmware: 8.2.3.CGMI - WiFi Firmware: v5.1.5

Diagnostics information

No response

Anything in the logs that might be useful for us?

Additional information

No response

[PascalBBBB]

Issue Screenshot with a system configured on the openevse with a 32A limit:

[PascalBBBB]

Proposed fix

In custom_components/openevse/number.py, the native_max_value property currently uses max_amps (hardware limit) instead of the user-configured limit.

Current code (line ~85):

@property
def native_max_value(self) -> float:
    """Return the maximum value."""
    max_ = self.coordinator.data["max_amps"]
    return float(self._max if max_ is None else max_)

Proposed fix:

@property
def native_max_value(self) -> float:
    """Return the maximum value."""
    # Use current_capacity (user configured limit) instead of max_amps (hardware limit)
    # Fallback chain: current_capacity -> max_current_soft -> max_amps -> default
    data = self.coordinator.data
    max_ = data.get("current_capacity") or data.get("max_current_soft") or data.get("max_amps")
    return float(self._max if max_ is None else max_)

This ensures European Level 2 installations (and any setup with max_current_soft < max_current_hard) display the correct maximum charge rate.

I've tested this fix on my setup and it works correctly.

[firstof9]

This is working as it should.
Using your logic, I wouldn't be able to change my EVSE from 40A (my current soft limit) to 48A (my unit's hard limit).

[PascalBBBB]

You're right, it's more an issue in the kipK/openevse_card I'm using.
I'm closing this issue and opening one in kipk's github

Thanks