Inconsitent UI behavior when adding KOSTAL Battery

[ram-proconsult]

Describe the bug

This is a UI problem.
Adding a Battery for KOSTAL is problematic because of required field maxchargepower.
This field is only available and forced to be filled in when the advanced options are opened.
Problem: You can bypass this field by not opening the advanced options and get an error.
Please see the attached pics.

Steps to reproduce

1. click "add battery"
2. choose KOSTAL with battery
3. provide necessary fields (ip, etc.)
4. click check -> it will fail (missing maxchargepower)
5. open advanced options
6. click check -> it will complain about missing field
7. set a value to this field
8. click check -> it will pass
   ...

Configuration details

not necessary

Log details

not necessary

What type of operating system or environment does evcc run on?

Linux

External automation

• I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.

Nightly build

• I have verified that the issue is reproducible with the latest nightly build

Version

300.2

[ram-proconsult]

[andig]

Thank you, this needs be improved.

@naltatis to prevent such mistakes (and since overriding a default advanced to „not advanced“ per template is not possible), would you mind if we simply made required fields non-advanced by default? I can do the PR.

[naltatis]

and since overriding a default advanced

Why isn't this possible? Would be good if we could make this possible. advanced as pointer?

[andig]

Sure. But ATM I‘d prefer to get the fix at hand working.