Attributes card

Who it’s for

Operators who need the whole picture for a device on one tile — not the headline reading, but the six or eight values that together say what state it is in. Commissioning engineers use the same card to confirm a device is publishing everything it should before the dashboard around it gets built.

What it does

The Attributes card lists several readings as a label-and-value table, and repeats that table for every entity in the datasource. A pump reporting flow, pressure, runHours and mode shows as four rows under the pump’s name; add a second pump to the datasource and a second titled block appears beneath the first.

• One tile covers a whole device — as many keys as you add, each on its own row, rather than one card per reading.
• Several entities on one card — each datasource contributes its own titled block, which makes side-by-side comparison of identical devices straightforward.
• Text and numbers both render — non-numeric values pass through the platform’s translation lookup, so a mode reporting IDLE can display as translated text rather than a raw token.
• Precision is per key — a key’s own units and decimals override the widget’s, so a pressure to two decimals and a run-hour counter to none sit in the same table.
• Font size follows the tile, recalculated on every resize, so the table stays readable as the widget grows and shrinks.
• A key with no data leaves its value cell empty while the label stays, which distinguishes “this device never sent it” from “this device is not configured for it”.
• The Attributes card is a table of current values: no history, no chart, no per-row coloring or thresholds.

How to set up

Data keys

The Attributes card takes any number of datasources and any number of keys per datasource.

Key	Role	Type	Description
Any	One table row each	Timeseries	Attributes work equally well, and the two can be mixed in one card. The row caption comes from the key’s label, so set that to the wording operators should read. Numeric values are formatted with the key’s units and decimals; text values are passed through translation.

Each datasource becomes a block titled with its own name, so name the datasources after the entities they represent rather than leaving the default. Rows appear in the order the keys are listed.

How to customize

• To change a row’s caption — edit that data key’s label; the card prints labels, not key names.
• To set a row’s precision and unit — set Decimals and Units on the key itself, which overrides the widget-level values for that row alone.
• To reorder the table — drag the data keys into the order you want; rows follow the key list.
• To retitle a block — rename the datasource, which is what the card prints above each table.
• To fit more rows — make the widget taller rather than adjusting fonts; the card recalculates text size from its own height on every resize.

Tips

• Put the values an operator checks first at the top of the key list. The card gives every row equal weight, so the only ordering signal available is position, and a table read top-down should open with the reading that decides whether anything else matters.
• Use this card during commissioning even if it will not survive into the final dashboard. Pointing it at a new device with every expected key added shows in one glance which keys arrive and which stay blank — faster than opening the device’s telemetry tab key by key.