State Timeline Widget
Horizontal state bands over a time range. Where the Status widget answers "what is the state right now", the State Timeline answers "how long was each state over this window": motion / no motion across the day, machine running hours derived from a current reading, or a device's online / offline history.
What it shows
One horizontal track for the selected time range, split into colored bands. Each band is one continuous stretch of a state. Hover a band to see the state, when it started and ended, and how long it lasted. Below the track sit an optional time axis, a legend, and an optional summary row with per-state totals ("Running 16h 05m (67%)").
The two sources
Pick the source on the Data tab. Each speaks a different language of states.
Field values
Classifies each reading of one bound field:
- Boolean fields -
true/falsemap straight to two states. Rename them to what they mean (Motion / No motion, Open / Closed). - Text fields - every distinct value is a state. Add one row per expected value on the States tab; readings that match no row fall into the catch-all state.
- Numeric fields - one threshold rule splits readings into two states (for example running when
current > 0.5). Calibration applies before the comparison, so the timeline agrees with a calibrated gauge on the same dashboard. Leave the rule's label blank to auto-caption it from the rule ("Current > 0.5 A").
Mapping and formula fields are not supported yet, and date fields have no time series.
Connectivity
No field needed: online and offline bands are derived from the gaps between uplinks. A device is offline once it has been silent for longer than its offline threshold (set on the device, 30 minutes by default).
Note this deliberately differs from the Status widget's Connectivity variant, which has its own widget-level offline window (default 5 minutes) for tuning how quickly "now" flips. The timeline always reconstructs history with the device's own threshold so every timeline of the same device agrees.
No data is not a state
In field mode, when the field goes silent for longer than the gap sensitivity (Auto = the device's offline threshold), the band turns into a hatched "no data" band instead of stretching the last known state. A motion sensor that died should not show three days of "no motion". You can set a custom gap in minutes, or turn gap detection off entirely.
Connectivity mode has no separate no-data band: offline is what silence means there.
Configuring a State Timeline widget
Basics tab
| Field | What it does |
|---|---|
| Title | Header text (required, max 120 chars). |
| Subtitle | Optional secondary line. |
Data tab
| Field | What it does |
|---|---|
| Source | Field values / Connectivity. Switching resets the States tab to that source's defaults. |
| Device | Bound device. Implicit on device dashboards. |
| Field | Field values source only. Boolean, text, and numeric fields are selectable. |
| Time range | Use the dashboard range, a preset (hour to month), or a custom absolute range. |
States tab
One row per state band: color swatch plus editable label. Boolean and connectivity sources have two fixed rows; text fields let you add and remove value rows (up to 12); numeric fields show the threshold rule row and an "otherwise" row. In field mode the hatched No data row is always last, with its own label and the gap sensitivity control.
Appearance tab
| Field | What it does |
|---|---|
| Bar height | Slim, regular, or fill (the band stretches to the widget height). |
| Show time axis | Tick labels under the band (times for short ranges, dates for long ones). |
| Show legend | Color chips plus labels under the axis. |
| Show summary row | Per-state totals for the visible window, sorted longest first. |
For a single state's total as a big number on its own tile, use a Value widget with the Duration in state aggregation; it computes the same totals the summary row shows. | Show time range tag | Small clock + range tag ("24h") in the corner. |
Data window and limits
- The timeline reads raw uplinks, so the window is limited to your raw telemetry retention (30 days by default). A wider request is clamped and the widget says so.
- Extremely chatty fields can exceed the band limit for one window; the widget shows a hint that the timeline was cut short. Narrow the range if you see it.
Tips
- Pair a State Timeline with a Status widget for the same device: Status for "right now", the timeline for "how did we get here".
- For machine runtime, bind the AC current field, set the rule to
>your idle draw, and turn on the summary row for daily running totals. - On a device-profile dashboard the device is implicit, so one timeline definition gives every device on the profile its own history.
When to use a different widget
- For the current state only -> Status widget.
- For the actual numeric curve -> Chart widget.
- For a row-per-reading log -> History widget.