Gateways overview

A gateway is field hardware that reads local sensors (RS485/Modbus, GPIO, I²C, SPI, UART, CAN, M-Bus) and forwards their readings to Synacl over MQTT.

Supported types: esp32 and raspi (self-service flash + OTA), plus other (generic).

Lifecycle:

  1. Flash firmware onto the board (flash an ESP32).
  2. Provision it with Wi-Fi so it registers itself (provision Wi-Fi).
  3. Add devices under it and pick sensors/pins (sensor pick & pin validation).
  4. Maintain it — OTA updates, restart, reset config, or view its console log over USB.

Each gateway reports online, signal strength (rssi), and its last local IP.

Its status dot reflects only the gateway's own connection — two states: green (online) and red/grey (offline). An unreachable device does not turn the gateway amber: the gateway stays green and the unreachable device is flagged at the device level — an amber device-count on the gateway card, a "N device(s) unreachable" badge on the gateway page, and an amber dot on the device itself. This keeps a down gateway and a misbehaving device clearly distinct. See device & gateway status.

More in Gateways
Flash an ESP32 from your browser
Use Web Serial to load gateway firmware — no toolchain needed.
Provision a gateway's Wi-Fi
Give a freshly flashed gateway network credentials so it comes online.
Update gateway firmware (OTA)
Push a new firmware version over the air from the gateway page.
Restart or reset a gateway
Reboot a gateway or clear its configuration remotely.
Picking sensors & pin validation
Add sensors to a gateway with automatic pin-conflict checking.
Gateway uplinks & network configuration
Wi-Fi, Ethernet, and cellular uplinks; parent/child chaining; and configuring a gateway's Ethernet port.