Load Management

Returns a status string from the internal load-management daemon.

• When internal LM is disabled, the literal string "internal lm not activated" is returned.
• When enabled, the daemon publishes a pipe-delimited status string describing cluster state, connected sockets, and current allocation. The exact format is considered an internal debugging aid; treat the payload as opaque and do not parse it in clients — the layout changes between firmware versions.

To determine whether internal LM is active, a string-equality check against "internal lm not activated" is the most stable approach.

Enables, disables, or reconfigures the Internal Load Management feature (current sharing between sockets on this station and optionally one slave station).

The body value is a pipe-delimited command string, not JSON. The accepted forms are:

Side effects of enabling

• Updates the persisted LM configuration with active: true, internal.active: true, internal.role, internal.pole_max_amp: 32, and (for master) internal.sockets[].
• Introduces the LMD lane in the current-limit composer (see Current limit composition). Offered current is now bounded by lmd_limit in addition to the three standard lanes.
• Until LM/internal/max_amp is written, the LMD lane value is whatever the daemon last allocated, which may be lower than the station's configured max_amp. Integrators enabling LM should typically follow up with an LM/internal/max_amp write to establish a known starting point.
• Does not restart the daemon; changes take effect on the next regulation cycle (typically ≤ 1 s).

Side effects of disabling

• Sets active: false in the persisted LM configuration. The LMD lane is no longer consulted; the effective current limit reverts to the three standard lanes.

Writes the LMD lane of the current-limit composer in Amperes, and simultaneously updates the station's configured max_amp cap that the internal regulator sees.

This write is special-cased by the REST handler and fans out to three MQTT topics:

• port0/salia/LM/internal/ts = current Unix timestamp (server-side).
• port0/salia/max_amp = the clamped value (updates the station's configured max).
• ci/global/dyn_current_limit/lmd_limit = the clamped value (updates the LMD lane directly).

The value is clamped on the server to the station's configured min_current / max_current, same as grid_current_limit.

Only meaningful when internal LM is active. If LM is disabled, writing this still publishes the three topics above, but the lmd_limit is ignored by the charge controller. The side effect on port0/salia/max_amp will still apply.

Integer Amperes, as a string (e.g. "16").

Changes the station's cluster role relative to other Salia stations on the network. Persisted across reboots.

Side effects

• sync_rfidtags and sync_protection intervals (in seconds) are rewritten from scratch on every role change. Custom values are lost.
• After switching to slave, RFID tag list and protection settings will be overwritten on the next sync tick from the master. Local edits made in between are lost.
• Switching from slave back to master or standalone does not restore any previously overwritten RFID list — the last synced state from the master is what remains.
• Role change does not restart the station; the new role takes effect immediately for sync behavior.

Returns whether time control (Zeitsteuerung) is currently active:

• "1" — Enabled: a schedule is configured and in effect.
• "0" — Disabled: no schedule is restricting charging.

Time control lets the operator configure time-of-day charging windows via the web UI. While a restrictive window is active, the internal regulator lowers the current to limit_tc (see below). This is not an API-writable endpoint; use the web UI (Configuration → Time Control) to configure schedules.

Current limit applied by time control in Amperes.

• When a time-control window is actively restricting charging, this is the per-window limit (e.g. a reduced overnight cap).
• When no window is restricting, this equals the configured max_amp — time control does not reduce the current below that default.

Time control's effect is enforced through the station's internal regulator lane (salia/intctrl_limit). Reading limit_tc shows the setpoint time control currently wants; reading intctrl_limit shows what the regulator has actually published (which may differ briefly during transitions).