pipsolar: current_max_ac_charging_current uses wrong MUCHGC format on Axpert MKS IV

[nicolaERTT]

Hi,

I found an issue with current_max_ac_charging_current on a Voltronic Axpert MKS IV using ESPHome pipsolar.

With the stock component, pressing a button that sets AC charging current to 20 A generated:

MUCHGC020

On my inverter this command was rejected (NAK / command not successful).

I tested a local override using ESPHome external_components and changed this line in:

pipsolar/output/init.py

from:

CONF_CURRENT_MAX_AC_CHARGING_CURRENT: ([2, 10, 20], "MUCHGC0%02.0f"),

to:

CONF_CURRENT_MAX_AC_CHARGING_CURRENT: ([2, 10, 20], "MUCHGC%04.0f"),

After that, ESPHome generated:

MUCHGC0020

and the inverter accepted the command (ACK / command successful).

Verification after the command:

• current_max_ac_charging_current was reported correctly as 20 A
• before the fix, the command was rejected
• after the fix, the command succeeded and the value matched

Relevant logs:

Before:
[D][pipsolar.output:015]: Will write: MUCHGC020 out of value 20.000000 / 20
[D][pipsolar:215]: Sending command from queue: MUCHGC020 with length 9
[D][pipsolar:049]: command not successful

Wrong intermediate test (too many zeros):
[D][pipsolar.output:015]: Will write: MUCHGC00020 out of value 20.000000 / 20
[D][pipsolar:215]: Sending command from queue: MUCHGC00020 with length 11
[D][pipsolar:047]: command successful
[D][sensor:124]: 'Axpert_MKS_IV current_max_ac_charging_current' >> 2 A

Working fix:
[D][pipsolar.output:015]: Will write: MUCHGC0020 out of value 20.000000 / 20
[D][pipsolar:215]: Sending command from queue: MUCHGC0020 with length 10
[D][pipsolar:047]: command successful
[D][sensor:124]: 'Axpert_MKS_IV current_max_ac_charging_current' >> 20 A

This may be a protocol variant specific to Axpert MKS IV and possibly similar models.

If useful, I can provide my YAML and full logs.