Phase Switching

Triggers a phase switch between 1-phase and 3-phase charging.

Prerequisite: Phase switching must be available on the device. Detect this by checking for the presence of the secc.port0.salia.phase_switching subtree in the snapshot — see the detection pattern under the Phase Switching tag description. If the subtree is absent, the REST layer still accepts this write and returns {"result":"ok"}, but the station discards it and the phase configuration is unchanged.

Valid Values

Phase Switching Workflow

Phase switching is an asynchronous operation with timing constraints. After triggering, poll phase_switching/status to track progress.

Observable status

phase_switching/status only ever returns "idle" or "progress":

Code
┌──────┐   setphase accepted    ┌──────────┐
│ idle │ ────────────────────> │ progress │
└──────┘                        └──────────┘
    ▲                               │
    │      success / timeout /      │
    └─────── abort ─────────────────┘

• idle — No switch in flight. Ready for a new request and for subsequent calls such as grid_current_limit.
• progress — A switch is in flight. Internally the station passes through delay/duration checks, triggers the relay, and waits for feedback (up to 60 s); externally all of that is collapsed into this one state.

Internal timing constraints that affect how long progress can last:

• Delay (30 s): blocks switching for that long after charging starts (see phase_switching/delay).
• Duration: minimum interval between consecutive switches, taken from the phase-switching delay configured in the web interface (see phase_switching/duration). The same configured value also sets the pause during the switch itself, but there the charging firmware accepts only 10-300 s and falls back to 20 s — a configured 6 s gives a 6 s interval and a 20 s pause.
• Feedback timeout (60 s): if the vendor firmware does not confirm the switch within 60 s, the previous phase is restored and status returns to idle. Check ci/evse/phase/actual to see whether the switch actually took effect.

Integration Pattern

Code
1. PUT  {"salia/phase_switching/setphase": "3"}
2. Poll GET /api/?path=secc/port0/salia/phase_switching/status every 2s
3. Wait until status == "idle" (up to ~60s worst case). On its own
   this is not proof that the switch happened — the status returns to
   "idle" after any accepted request.
4. Verify with GET /api/?path=secc/port0/ci/evse/phase/actual
5. NOW safe to set grid_current_limit

Step 4 reads ci/evse/phase/actual deliberately. That value is the phase the vehicle actually charges on; phase_switching/actual is the station's stored selection. Under normal operation the two agree — see the note under the Phase Switching tag description for what it means when they do not.

Constraints

• During charging (CP state C/D): Full switching process executes. This is the only state in which a switch should be requested.
• During CP state A/B/E/F (not charging): the request updates the stored selection and the web interface display, but is not reliably carried through to the power stage; whether it is applied at the next charging start is not guaranteed. Do not pre-select a phase outside a session and assume the session starts on it. In particular, do not drop the charging current to zero or pause the vehicle immediately before requesting a switch — that takes the station out of the charging state.
• Power mode auto-switch: Setting chargemode to "power" automatically triggers a switch to 3-phase if not already in 3-phase.
• Sequencing: Never set grid_current_limit until phase switch completes. Calling out of sequence will block charging.

Returns the station's stored phase selection: "1" or "3". This is the value the web interface displays, and it is what the last accepted setphase request set. During a switch it updates only after the operation completes.

This is not a reading of the relay state. To find out how many phases the vehicle is actually charging on, read GET /api/?path=secc/port0/ci/evse/phase/actual. Under normal operation the two agree; see the Phase Switching tag description for what it means when they do not.

Note: This endpoint (and all phase_switching/* endpoints) only returns data when phase switching is available on the device. If it is not, the entire phase_switching subtree is absent from the snapshot — see the detection pattern under the Phase Switching tag description.

Returns the current state of the phase switching state machine. Poll this endpoint after triggering a phase switch to know when it completes.

See the setphase endpoint documentation for the full state machine description.

Minimum time (in seconds) between consecutive phase switches. This prevents rapid toggling that could damage relays. Default: "10" seconds.

Time (in seconds) after charging starts during which phase switching is blocked. This allows the charging session to stabilize. Default: "30" seconds.

Returns the configured number of phases for the charging station. This is the hardware capability, not the current switching state.

Returns the actual phase reported by the EVSE controller. "0" indicates no active phase (not charging).