custom-components
Enforce minimum current values for chargers
The Zaptec API lets me set ChargerMinCurrent to 0, however if this value is used and changing another setting in the Zaptec Portal, it returns an error for this field:
Do we need to enforce a minimum value of 6A on ChargerMixCurrent? Does this apply to the other fields: ChargerMaxCurrent, AvailableCurrent* and ThreeToOnePhaseSwitchCurrent?
@ivastokic, @bonfaceOchieng, @thecoldwine
Hello @sveinse your observation is accurate. In the Zaptec API, it is technically possible to set ChargerMinCurrent to 0, but this value is not valid for normal charger operation. Zaptec Portal enforces a minimum of 6A, which is the lowest supported current for EV charging according to IEC standards. If 0 is used, it will cause validation errors when making changes through the Portal or other system interactions, since the field falls outside the accepted operational range.
About enforcing a minimum value on other fields, other than ChargerMinCurrent see recommendation below
-
ChargerMinCurrent: should be enforced with a minimum value of 6A. -
ChargerMaxCurrent: must always be greater than or equal to ChargerMinCurrent, and within the charger’s configured max capacity. -
AvailableCurrent : should reflect the available supply current, and must also stay within the valid range (≥ 6A, and not higher than the physical max).
-
ThreeToOnePhaseSwitchCurrent : must also be at least 6A, as switching thresholds below this are not valid.
I hope this clarifies
@bonfaceOchieng thank you, this helps.
- ThreeToOnePhaseSwitchCurrent : must also be at least 6A, as switching thresholds below this are not valid.
I assume setting it to 0 to force it to charge with 3 phases is valid? This is what's mentioned in your docs: https://docs.zaptec.com/docs/3-to-1-phase-switching-with-zaptec-go-2
Since it seems some values are left for the integrators to validate. E.g. minimum 6A as described in this issue. Don't issue pause command if not charging. As a integrator it would be very helpful with a list of the validation items that is expected to be handled by the integrator or front-end. Without it, we get questions like this issue. I'll add it to the request list in #192