Secomea

Manages the Secomea SiteManager for remote access.

Module id: secomea.

Configuration

Config type	Component ref	Description
secomea	secomea.secomea.main	SecomeaConfiguration is the singleton secomea.secomea.main remote-access config.

When servers, domain, or name actually change, the SiteManager configuration is rewritten and the process is restarted. A config update is merged over what is already stored: a partial update (for example a bare enable/disable) preserves existing servers / domain / name / agents. Disabling only stops the SiteManager - it does not clear the configuration. An update that changes neither the stored configuration nor the enabled state leaves the SiteManager running, so live remote-access sessions survive the republish the configurer sends on every restart and after each commit.

Changing only agents through Algol configuration does not reach the stored configuration or the running SiteManager: agents are written only together with a servers / domain / name change, since an agent-only edit must not restart it. In practice the GateManager provisions them and Algol reports them back - the effective configuration therefore carries what the device holds, which can be more than the update sent.

After enabling, config status is WAIT while the GateManager connection is established (grace period, default 60 s), then OK or ERROR. That prevents a transient "not connected" from being kept as a permanent error. The stored configuration is re-read every --sme-poll-interval seconds (default 30) and the config status republished only when it changed, so GateManager-side edits become visible on their own.

NATS endpoints

None declared.

Config and status only. Command-runner telemetry on secomea.runner.main - see Telemetry.