Field Discovery

When a device sends telemetry data, the platform automatically discovers and registers the data fields. You don't need to define a schema upfront.

Image placeholder: Screenshot of the discovered fields list with types

How It Works

A new telemetry message arrives with payload: {"temp": 25, "hum": 60}
The platform checks the field registry for temp and hum
If a field doesn't exist, it creates a new entry:
- Field Name: temp
- Field Type: number (auto-detected)
- First Seen: Current timestamp
- Sample Value: 25
On subsequent messages, the Last Seen timestamp is updated

Each discovered field has the following metadata:

Property	Description
Field Name	The key from the JSON payload
Field Type	Auto-detected: `number`, `string`, or `boolean`
Unit	Optional unit of measurement (editable)
Display Name	Human-readable name (editable)
Is Hidden	Can hide fields from the UI
First Seen	When the field was first observed
Last Seen	When the field was most recently received

Dashboard widgets use discovered fields for data source selection:

When configuring a widget, you select from available fields in a dropdown
Only fields that have been received at least once appear in the list
Field types help determine appropriate widget types (e.g., numbers for gauges and charts)

If a new field doesn't appear in widget configuration, make sure the device has sent at least one message containing that field.