Skip to content

Switching phases 3 to 1 or 1 to 3 fails #449

Open

Description

@karansinghlala

Zaptec Go 2 + SenseP1
HA 2026.x
Zaptec HACS integration v0.8.7

Reading works:
three_to_one_phase_switch_current updates correctly from portal.

Writing fails:
number.set_value

Entity:
number.terugschakelen_van_drie_naar_een_fase

Examples:
6 -> failed
8 -> failed
16 -> failed
32 -> failed

Error:
Setting three to one phase switch current to X.X failed

Also in the Zaptec App there is a toggle button 'Use only 1 phase'. This swich/toggle button cannot be set, it does not change through the integration.

Activity

  1. karansinghlala commented on Oct 30, 2026

    @karansinghlala
    Author
    Image

    I want to set 0 or 32 to switch to 1 or 3 phases.

  2. karansinghlala commented on Oct 30, 2026

    @karansinghlala
    Author

    This is the other way in the Zaptec App to force 1 phase (unable to set):

    Image
  3. rhammen commented on Nov 1, 2026

    @rhammen
    Contributor

    Thanks for the screenshots. The most likely cause is that your installation uses Automatic charging (Automatisch laden) with the Sense P1. In that mode Zaptec's power management controls the installation. Zaptec's API then rejects every change to installation settings, including the 3‑to‑1 phase switch current (Terugschakelen van drie naar één fase). That's why every value fails while reading still works. #309 is about the same problem.

    To confirm:

    • Temporarily switch the charging mode to Default charging (Standaard Laden) in the Zaptec app and set the value again. It should work then.
    • Or enable debug logging for custom_components.zaptec and share the failing request. We expect an HTTP 500 with Cannot update installation when using APM.

    This limit is set by Zaptec, not by the integration, so the integration can't get around it. #427 will at least show this reason in Home Assistant instead of the generic "failed" message.

  4. karansinghlala commented on Nov 3, 2026

    @karansinghlala
    Author
  5. rhammen commented on Nov 3, 2026

    @rhammen
    Contributor

    Okay, so when Automatic charging (Automatisch laden) with the Sense P1 is enabled the phase switching will not work. Only when the charging mode is set to Default charging (Standaard Laden) the phase switch will work. So how to overcome this issue? I want to switch phases when the cable is not connected, so not during the loading session. Because the Renault Zoe cannot handle this. So I was thinking, is it possible to automate this as follows: select charging mode Default Charging, switch the phase, select charging mode Automatic. Will this work you think? Is this possible? Maybe with pauses in between? What is the entity called to select the charging mode? Kind regards, Karansingh Lala

    You can try, but if I recall correctly this will NOT work.
    As stated in the Zaptec App:
    Automatisch laden: de beschikbare stroom wordt beheerd door Zaptect Sense
    (Automatic charging: the available current is controlled by Zaptec Sense).
    So in Automatic mode, I expect the Sense to override any charging current limit/3-to-1-phase switching current you have set while in Default mode (Standaard laden).
    Why would they otherwise disable this 3-to-1-phase switching current setting while in Automatic Charging mode?

    If you want manual control over the charging current/3-to-1-phase switching current, I expect you cannot use the Automatic Charging mode. You then must use either the Standaard Laden or Gepland Laden options.
    But give it a try...

    NOTE
    The Zaptec API does not offer the possibility to set the charging mode.
    So you need to set the charging mode in the official Zaptec App, you cannot do that using this integration.

  6. karansinghlala commented on Nov 3, 2026

    @karansinghlala
    Author
  7. rhammen commented on Nov 3, 2026

    @rhammen
    Contributor

    My previous response was about the 3-to-1-phase switching current (0A vs 32A).
    As I explained, I expect this will not work because in Automatic mode the current is controlled by the Sense P1.

    The "Gebruik alleen 1 fase" (use 1 phase only) setting in the app is not currently available in this integration.
    I checked and it is available in the Zaptec API. I tested, and reading the setting works fine, but writing the settings via the API does not seem to work: I get a 200 (=OK) HTTP code response, which suggests the write was accepted, but the switch does not actually change.
    That means adding such switch to the integration would not bring anything.

    I think there are 2 options for you:

    1. you use the Sense P1, so "Automatic charging", and you use the "Gebruik alleen 1 fase" (use 1 phase only) switch in the Zaptec App.
      You can use this integration to read all kind of values but you cannot control the phases used from within this integration.

    2. you use "Default charging", so basically do not use the Sense P1. You can control the phases used and the max. current per phase from within this integration and with HA automations. If you have a P1 meter (NOT Sense P1) connected directly to HA, you can build some automation(s) that set the current used by Zaptec based on the values of the currents/powers of the P1 meter.

    This 2nd option is what I personally have chosen to do: I also have a Sense P1, and like you I also found out that with it enabled (mode: "Automatic charging") I have too little control over what I want. So I decided to use the Standard charging mode instead.
    But Note: I am not using the maximum power with my Zaptec (I have a Hybrid car, so charging it even at lower power goes fast enough), so max. current per phase protection is not at the top of my list.

    This integration is not directly affiliated to Zaptec. If you need any support or have feature requests regarding you Zaptec charger, contact your installer and/or Zaptec directly.
    In #192 we do collect Zaptec API features we would like to have for this integration, and Zaptec people occasionally have forwarded our feedback back to Zaptec. But so far actual changes to the Zaptec API as a result of this are (close to?) None, so I would not count on that.

  8. karansinghlala commented on Nov 15, 2026

    @karansinghlala
    Author
  9. rhammen commented on Nov 15, 2026

    @rhammen
    Contributor

    Thanks for testing, that's useful information.

    The integration uses exactly the endpoint that Zaptec documents for this setting:

    POST https://api.zaptec.com/api/installation/{id}/update with body {"threeToOnePhaseSwitchCurrent": <value>}

    You also confirmed that it works in Standard charging, so the call itself is correct.

    Why do you believe this endpoint is deprecated, and which endpoint do you think is the correct one? Please share a link to Zaptec documentation if you have one. I can't find any replacement endpoint.

    In fact, Zaptec's own developer FAQ says this is expected:
    https://docs.zaptec.com/docs/zaptec-load-balancing-telemetry-developer-faq#q52-when-a-nondefault-mode-is-active-can-an-external-system-still-perform-load-balancing-via-post-apiinstallationidupdate

    Q5.2 says that when Eco Mode, Schedule or APM (Automatic charging / Sense) is active, updates through POST /api/installation/{id}/update should be treated as not supported, and may be rejected with error 527. In my own tests in Automatic charging, the API returns HTTP 500 with Cannot update installation when using APM.

    Can you check whether that's what happens for you?

    1. Go to Settings → Devices & services → Zaptec → Enable debug logging.
    2. Make sure the installation is in Automatic charging, then set the 3-to-1 phase switch current to 0 or 32 in HA.
    3. Turn debug logging off again; HA then offers the log as a download. Look for failed with status 500 and the PAYLOAD line right after it.

    If you see that error, please send it to Zaptec together with the FAQ link and ask them:

    • Why do they say it should work in Automatic charging, when their own FAQ says it's not supported and their API rejects it?
    • Why does changing the same value in the Zaptec Portal work in Automatic charging, but not through the public API?

    The integration can only use the public API, so if Zaptec blocks the change there, we can't work around it.

  10. rhammen commented on Nov 15, 2026

    @rhammen
    Contributor

    A small addition: Q7.1 of the same Zaptec FAQ lists the checks to run before calling POST /api/installation/{id}/update:
    https://docs.zaptec.com/docs/zaptec-load-balancing-telemetry-developer-faq#q71-what-prechecks-are-recommended-before-calling-post-apiinstallationidupdate-for-load-balancing

    The first check is that the installation is in Default mode, with no Eco, APM or Schedule active. Otherwise the installation should be treated as "not externally controllable". You can see the mode in GET /api/installation/{id}, which the integration already polls:

    • availableCurrentMode: 0 = Manual, 1 = Schedule, 2 = Auto
    • enabledFeatures: bitmask with 4 = APM, 8 = Eco Mode, 16 = Schedule

    #427 is a related open PR. It turns Zaptec's error response, including this 527 rejection, into a clear message in HA instead of a generic error. It doesn't block the change up front: the request is still sent and Zaptec still rejects it. A pre-check like Q7.1 could be a follow-up.

    Either way, according to the FAQ, the setting can't be changed through the API in Automatic charging. @karansinghlala, please ask Zaptec why they told you it should work when their own FAQ says otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions