Configure any Modbus sensor

Enter your admin key, then choose a gateway. From here you can update its complete wire and register map, request an immediate reading, and inspect the queue arriving at the API.

`—`Awaiting data

Live control and telemetry for this ESP32 gateway.

Optional and separate from applying a configuration: it asks the gateway for a reading right now instead of waiting for its next sample window. A configuration change lands on its own — it does not need a reading request first.

Desired config

—

Backend version

Applied config

—

Waiting for telemetry

Last seen

—

No telemetry yet

Read request

—

No request sent

…

Configuration awaiting gateway

No device acknowledgement has been received for this version.

Status pending

Gateway configuration

Full device, sensor wiring (Modbus register layout or pulse pin), decoding, and telemetry selection

JSON ready0 bytes

Config reference

Gateway

enabledqueue_depthchannels[]sensors[]

channels[].type: f32i32bytes

Modbus sensor

baud_rateparitystop_bitsslave_addrfunction_codetimeout_ms

read_blocks[]block_gap_mssample_period_msaggregation_interval_s

Modbus values

group_ids[]group_unitfields[]f32i32u32i16u16

Pulse sensor

pinpulledgedebounce_mscounting_interval_s

Pulse output

COUNT_<pin>i32pulses

The backend is the single source of truth for what a configuration must look like -- this reference is a pointer, not a contract. Submit and read the rejection if something is off. Register addresses are wire addresses; read_blocks is a list of {address, count} blocks in register order. A pulse sensor has no fields, group_ids, or read_blocks; it always reports the raw integer channel COUNT_<pin>.

Telemetry queue

Latest values and recent readings received by the backend

No sensor values received yet.

Recorded	Config	Message schema	Device uptime	Fields
The queue is empty.

Telemetry chart

Selected channels plotted against device recording time (backend receipt time before clock sync), one axis per channel