Dashboards

A Dashboard is a live canvas of widgets that visualize what your devices are reporting right now. Each widget is bound to one or more device Attributes and updates on its own over a live connection. You arrange widgets on a grid, resize them, group them, and the layout saves itself. This page covers how dashboards work, the controls and settings every widget shares, and a complete catalog of every widget type with its configuration options.

Where Dashboards Live

Every dashboard belongs to an application. You open, create, and manage an application’s dashboards from its Dashboards page, which is organized as tabs: you open dashboards into tabs and switch between them in place, rather than scrolling a list. A widget you create inside an application stays in that application’s context.

Create, rename, and delete

• 1
  On the Dashboards page, create a new dashboard. Give it a Dashboard Title (required) and an optional Description.
• 2
  Rename or edit the title and description any time from the dashboard’s gear menu (Edit). You can also double-click the dashboard’s description to edit it in place; the title is renamed from the Edit dialog (or by double-clicking a dashboard’s tab to rename the tab).
• 3
  The gear menu also offers Duplicate (creates a “Copy of …” with all its widgets) and Delete. Delete asks for confirmation, then permanently removes the dashboard and every widget on it. Deleting a dashboard cannot be undone — the Undo toast applies only to deleting an individual widget on a dashboard (see The Grid), not to deleting a whole dashboard.

Tabs: keep several dashboards open at once

• Add a hidden dashboard to the tab bar, or create a brand-new one, from the add-tabs dialog.
• Reorder tabs by dragging, rename a tab (with edit permission), and close a tab to hide it from the bar (closing a tab does not delete the dashboard).

The Grid: Adding, Arranging, and Saving

Widgets live on a responsive 12-column grid. With edit permission you can drag, resize, and group them. Without it, the dashboard is view-only.

Layout behavior

Saving, autosave, and history

• Autosave: layout changes (moves, resizes, spacer edits) persist automatically. A small indicator shows Saving…, then Saved · just now, and warns if a save failed and will retry.
• Auto Align Widgets packs widgets tightly into a clean grid, section by section, in one action.
• Refresh Dashboard re-pulls data for every widget on demand.
• Undo / Redo covers layout commits plus adding and deleting widgets, up to the most recent 20 actions on the current dashboard.
• Full screen expands the dashboard for a wall display. When several dashboards are open as tabs, previous/next arrows flip between those open dashboards.

Widget Controls: Hover to Reveal

Widgets keep their controls hidden so the dashboard stays clean, especially on a wall display. Point at a widget and its controls fade in at the top. Move the pointer away and they disappear again. On a touch screen the controls live behind a ⋮ (More) button instead; tap it to show them, tap elsewhere to dismiss.

The expanded view

• Charts add a date-range picker and a Max points input, so you can look at a different time window or point density without editing the widget, plus a CSV download button. The CSV contains exactly the data drawn on screen.
• XY-Charts let you zoom into the plot with the scroll wheel. The date-range picker is not available here (the window comes from the widget’s own Live or Daily setting), but CSV download is: one file per pair, with Timestamp, X Value, and Y Value columns.
• Gauge and Label widgets let you grow or shrink the value text with the scroll wheel.

Live Data

Widgets update themselves. The dashboard opens an authenticated WebSocket connection and keeps every widget current as new readings arrive.

• Charts and XY-Charts request a time window (Live or Daily) and stream a series of readings.
• Single-status widgets (gauge, label) request the latest reading only.
• Multi-status widgets (table, map, progress, pie, doughnut) request the latest value per bound attribute.
• Data Push widgets display nothing, so they subscribe to nothing. They only send.

Building a Widget: What Every Widget Shares

Every widget is created and edited in the same editor: a config panel on the left and a live preview on the right. This section covers the controls that are the same for every widget type. The per-type options live in the Widget Catalog below, so they are not repeated for each widget.

• 1
  Check the Dashboard field, enter a Widget Title (required), and optionally a Description.
• 2
  Choose a Widget Type: Chart, Single Status, Multi Status, Data Push, or XY-Chart. Then choose a Style (the sub-type) within that type.
• 3
  Set the type-specific options (time range, scale, table cells, and so on), then add one or more Attributes (Data Push widgets have none).
• 4
  Watch the Preview, then save. The widget drops onto the dashboard at the next free spot.

Dashboard

The first field in the editor shows which dashboard the widget belongs to. It is locked by default so you cannot move a widget by accident: the dropdown is greyed out until you click the small pencil next to the “Dashboard” label. Unlock it to create the widget on a different dashboard, or to move an existing widget when you edit it. In the few flows where the destination is fixed, the field is hidden entirely.

Widget Title, with tags

The Widget Title is required, and it can do more than plain text: it can embed one of your tags. Click the braces button (Insert a tag) at the end of the field, search the application’s tags, and pick one. This drops a token like {{tag.room}} into the title, and the widget shows the tag’s current value in its place.

• A Resolves to preview under the field shows the finished title. If the tag is missing, a Referenced tag not found warning appears instead.
• Rename once, update everywhere: point several widget titles at the same tag and editing the tag’s value renames them all.
• Only tags whose key uses letters, numbers, hyphens, and underscores can be inserted. Others are shown greyed out in the picker.

Description

An optional Description (up to 250 characters) appears in smaller, muted text under the widget’s title on the dashboard. Long descriptions are truncated; hover to read the full text. Use it for context the title can’t carry, like “3rd floor, north wing” or “resets at midnight”.

Preview, with sample data

The right-hand pane always shows something useful. Before you bind an attribute it is labelled Preview (Sample) and renders your widget with realistic sample data, using the exact type, style, and options you have picked so far. Map and Data Push widgets show a sketch placeholder instead. Once a real attribute is bound the label switches to Preview and the data is live.

Attributes and their options

Every widget except Data Push is built from one or more Attributes (data points). Each attribute row ties a device to one of its measurements, plus display options. Which options appear depends on the widget type:

Calculations

Attribute rows on chart and status widgets carry two calculation buttons, so a widget can plot computed values instead of raw readings:

• The tags toggle switches the row between a single attribute and a simple combination of two attributes (add, subtract, multiply, or divide). Use it for quick sums and differences, like supply minus return temperature.
• The lightning-bolt button (Advanced calculation) opens a formula editor for anything beyond the basics: unit conversions, scaling, and full formulas. Once a formula is set, the row collapses to a Calculation card with Edit and Remove links, and the button turns blue.

On the dashboard a calculated series plots like any other, with a small ⚠ badge if the calculation has a problem. The formula itself is shown in the editor, not on the widget. The Advanced calculation editor and the formula language are covered on their own page.

The Widget Catalog

There are five widget types, most with several styles. The type identifiers are chart, single_status, multi_status, data_push, and correlation (the XY-Chart); each style has its own sub-type identifier shown below.

Chart — Line, Bar, Area, Scatter

What it shows: one or more attributes plotted over time. Use it for trends, comparisons across devices, and history. Charts plot numeric values only.

XY-Chart — Line, Scatter

What it shows: the relationship between two measurements, instead of one measurement over time. Each point pairs an X reading with a Y reading taken in the same time window, so you can see how one attribute moves with another: temperature against humidity, power draw against occupancy, and so on. Scatter draws a cloud of points; Line connects them in time order.

Single Status — Gauge

What it shows: a single device’s latest value as a dial against a min/max range. Use it for “current temperature”, “current CO₂”, and similar at-a-glance KPIs. Exactly one attribute.

Single Status — Label

What it shows: the latest value as plain text with its unit. Use it for compact readouts and for non-numeric attributes (status strings, on/off states) that a gauge cannot show. One attribute.

• Rounding (style and decimal places) for numeric values.
• Color for the value.
• Handles string and boolean values, which is why it pairs well with categorical attributes.

Multi Status — Table

What it shows: a grid of latest values, one attribute per cell. Use it to lay out related readings (for example one row per room, one column per metric).

Multi Status — Map

What it shows: device pins placed on an uploaded floor plan or site image, colored by attribute. Use it for spatial monitoring (a floor of sensors, a site map).

Multi Status — Progress

What it shows: progress bars toward a target, per attribute. Use it for “X of max” style readouts (people counted vs capacity, output vs goal).

Multi Status — Pie and Doughnut

What it shows: a share-of-total breakdown across attributes. Pie is a filled circle; Doughnut is the same with a hole in the middle. Use them for composition (share of devices by state, contribution to a total).

Data Push — Form, Button

What it does: everything above shows data. Data Push is the one widget that sends it. It pushes a payload (a command or setting) from the dashboard to a device endpoint, so an operator can act without leaving the dashboard: reset a counter, switch a mode, send a configuration string.

On the dashboard the two styles behave differently:

• Form shows an editable text box pre-filled with the Default Payload, above the send button. The operator can adjust the payload before sending, or just click.
• Button is a single large button that fills the widget. One click sends the configured commands. There is no text box to edit.

Data Push widgets bind no attributes. Saving one only requires a destination and a button label.

Plan Limits

Each plan card in Billing lists a Dashboards allowance for the workspace, which may appear as a specific number or as Unlimited depending on your plan; there is no separate per-widget cap surfaced in the product. The limits that always apply are structural and are covered with each widget above: up to 16 map widgets per dashboard, up to 32 attributes (pins) per map widget, up to 16 cells per table widget (up to 16 rows and 8 columns, capped at 16 cells total), up to 8 pairs per XY-Chart, and up to 4 commands per Data Push button.