Production Omega devices use MQTT with TLS. Connection settings live in the connection: block of your client YAML (embedded at build time).
Production MQTT
Runtime environment:
Copy broker host, credentials, and topic filters from the console device detail or platform-tui devices mqtt-details.
Topic namespace
Default root: omega/{device_id}
Example for device fleet-unit-42:
Golain-managed devices may use platform-specific topic layouts — follow MQTT details from the console when not using default Omega roots.
Transport modes
Never deploy HTTP polling transport to production. It has no authentication or TLS.
Development mock server
Terminal 1:
Terminal 2:
Self-hosted broker
Point server_url at your operator MQTT endpoint (for example ssl://mqtt.ilyama.golain.io:8883). Ensure TLS trust anchors and client certificates match your vm-edge PKI.
Verification
Successful connection logs include broker handshake and module startup. Confirm in:
- Console device status → connected
platform-tui events watch --device=<uuid>platform-tui events list --source=mqtt
Certificate enrollment
For mTLS without manually copying passwords, use JITR enrollment — Omega obtains device cert and broker URL before MQTT connects. 
