How Settings is organized
Settings uses a left section navigator inside the page. It is separate from the main site menu and lets you jump to Mode, Device, Credentials, Network, Time, Uplink, Modbus Lines, Modbus TCP, Integration, Recovery, MQTT, Wi-Fi, Firmware, Maintenance, and service blocks.
Runtime state
Maintenance actions
Device and runtime truth
Settings shows more than saved fields. It also exposes machine state: Uplink, Cloud, Gateway, and Automation can have separate configured and runtime values. This matters for support: configured describes intent, runtime shows what is actually active right now.
| State | How to read it | What to do |
|---|---|---|
configured |
The saved setting that should apply according to the section rules. | Check apply semantics: now, after reconnect, or after reboot. |
runtime |
The actual service or channel state in the current boot. | Use it as the primary signal for current troubleshooting. |
| Error/counters | Runtime error and counters show what the service attempted and where it failed. | Keep this context before reboot or service action. |
Operating mode
| Mode | Use when | Interface effect |
|---|---|---|
| UMEC Space | The site should work with UMEC Space IoT Cloud Platform and use platform dashboards, mobile access, alerts, notifications, and remote control. | UMEC fields and BLE/provisioning context are shown. Generic MQTT is hidden. This is the primary mode for gateway-to-platform operation. Registration and gateway verification happen in UMEC Space Dashboard. |
| MQTT Generic | Data must be sent to a third-party MQTT broker. | Host, port, transport, auth, TLS, topic preview, session, and LWT settings become visible. |
| MQTT Disabled | The gateway should remain local with no external MQTT. | The MQTT section stays visible, but external editing controls are locked. |
Apply semantics
Not all settings apply the same way. The interface should show whether a change is applied now, after reconnect, or only after reboot.
| Semantics | Meaning | Operator action |
|---|---|---|
| Applied now | The change becomes active immediately. | Check section status and observe runtime state. |
| Applied after reconnect | New parameters take effect after the relevant service reconnects. | Wait for reconnect or perform a controlled reconnect. |
| Requires reboot | A reboot is required. | Save evidence, warn users, and perform a controlled reboot. |
Network and Uplink
Network defines Wi-Fi and Ethernet profiles: DHCP/static IP, DNS, and site addresses. Uplink selects which channel is used as the active outward path: manual Wi-Fi, manual Ethernet, or failover/failback policy. In status, read active uplink and ip acquired because a saved profile does not guarantee working connectivity.
- Wi-Fi fits sites without wired networking or as a backup path.
- Ethernet is usually preferred for cabinets and fixed installations.
- With manual uplink selection, outside integrations use the selected channel while it is available.
Modbus Lines
Lines are split into physical RS-485 lines and the network TCP channel. These are materially different, so do not explain TCP using RTU transparent-mode language.
| Line | Modes | What the operator sees |
|---|---|---|
| RTU 1 / RTU 2 | Polling, Transparent, Disabled | Polling provides local Control values. Transparent reserves the line for passthrough. Disabled turns the line off. |
| TCP | Polling, Not polling, Disabled | Polling updates bus3. Not polling keeps configuration visible but stops background freshness. Disabled turns the channel off. |
Generic MQTT
Generic MQTT is used when the site connects to a third-party broker. Host, transport, auth mode, TLS verification, and topic preview are especially important. Passwords should not be shown back in plain text.
Generic MQTT
Modbus TCP and NAT
Listeners, tunnels, and NAT rules have structured simple editors. They still edit JSON arrays, but give the operator a form instead of a raw text-only workflow.
| Object | Purpose | Watch for |
|---|---|---|
| Listener | Accepts incoming Modbus TCP connections. | strict_map requires a route table, otherwise addresses may not resolve. |
| Tunnel | Defines a remote Modbus TCP endpoint. | If several tunnels are enabled, TCP devices need explicit binding. |
| NAT rule | Maps addresses between source and target domains. | priority is lower-value-first. |
Validation and errors
A save error does not necessarily mean the interface is broken. Often it is a guard against conflicting configuration. Read blocking/warning, field path, and recommendation first, then correct the specific field.
Maintenance
| Action | Purpose | Before using it |
|---|---|---|
| Reboot | Controlled restart after configuration or a service issue. | Save changes and warn the operator. |
| Soft recovery | Non-destructive access recovery. | Confirm that recovery is needed instead of a normal reboot. |
| Factory reset | Full configuration reset. | Download configuration and logs. Use only after an explicit decision. |
| Firmware update | Upload a new `.bin` image. | Check the file, power stability, maintenance window, and rollback plan. |
Recovery and Developer mode
Recovery is a separate area for access recovery and controlled service actions. It is not a replacement for ordinary line or MQTT diagnostics. Before recovery, keep configuration, logs, and visible runtime context.
Developer mode and the web terminal are service support surfaces. A normal operator should not enable them for commissioning, device checks, or daily operation. Use them only under a support procedure and after recording current state.
| Surface | How to enter | Safety boundary |
|---|---|---|
| Recovery | Available after a local recovery event or through the supported service flow when access already exists. | Use it for access recovery or platform reconnection. For connectivity issues, start with Diagnostics. |
| Developer mode | Enabled from the Settings service area after authenticated login and only under support instructions. | Do not use it for normal operation. Save runtime state, logs, and current configuration before enabling it. |
| Web terminal | Use only when Developer mode is allowed and support explicitly requests terminal access. | Do not type secrets into commands and do not run operations with unknown effects. Disable service access after the session. |
If the web password is lost, use soft recovery through the button hold. Keep full factory reset as the last option because it clears all settings and formats storage.