Understanding fault events

Protocol fault events tell you a device isn't reading cleanly:

Event Usual cause
modbus/timeout Wrong modbusId/baud, wiring, or device offline
i2c/fault Bad address, missing pull-ups, clock too fast
spi/fault Wrong SPI mode/clock or CS wiring
uart/fault Baud or framing mismatch
can/fault Baud mismatch or bus termination
mbus/fault Wrong primary address or baud
http/poll-error Bad URL, auth failure, unexpected JSON
snmp/poll-error Unreachable host, wrong community/version
gpio/fault Pin conflict or out-of-range value
link/weak Degraded Wi-Fi signal on a gateway

A device hitting one of these faults shows an amber status dot — the gateway is up but can't read that device — which is distinct from a red/grey offline dot (the gateway itself is down or the device went silent). See device & gateway status.

Fix the underlying connection setting (see the matching device how-to); the faults stop once clean reads resume, and the dot returns to green.

More in Events
Telemetry, events, and alerts
The three data streams and where each one shows up.
Using the events feed
Where events show up and how to read them.
Event types reference
Every event type Synacl emits, grouped by area.
Sound alerts & notifications
Play a sound when an alert at or above a severity arrives.