Entities cards
Lists latest readings for many entities as a scrollable grid of compact cards — one card per entity, with server-side pagination for long lists.
Who it’s for
Anyone managing many similar entities — devices, assets, rooms, vehicles — asks “how do I see each one’s latest numbers at a glance without one giant table?” A facility manager scans a card per room instead of scrolling a wide table sideways. A fleet dispatcher wants one tap on a vehicle’s card to jump straight to its own dashboard, without hunting for a row in a data grid first.
What it does
A fleet of 40 trucks, paginated 10 per page, each renders as its own card listing Speed, Fuel level, and Engine temp with their own units and decimals — page through the rest without loading all 40 up front.
- One card per entity, built automatically from whatever the datasource or entity alias resolves; each card’s title uses that entity’s own Label, falling back to its Name
- Every configured key becomes its own row on every card, formatted with that key’s own Units and Decimals
- Server-side pagination fetches only the current page’s entities, so a list of hundreds doesn’t load all at once
- A row of icon-button actions on every card, configured once and applied to every entity
- Independent styling for the entity name, metric labels, and metric values — color, font family, size, weight, and style each on their own
- Lists whatever keys are bound; a key that has never reported for an entity is left off that card rather than shown as a blank row
How to set up
Data keys
| Key | Role | Type | Description |
|---|---|---|---|
| Data keys (any number, user-configured) | One metric row per key, per card | Timeseries or Attribute | Formatted with that key’s own Units and Decimals; the key’s own Label (or name) becomes the row’s label |
Add keys the same way as any latest-value widget — there are no per-key settings specific to this card. Every bound entity gets its own card listing every key that has reported at least once for it; a key that has never reported for a given entity is left off that entity’s card entirely, while a key that has reported but whose latest value is null or blank shows as “No info” instead of a number.
Pagination
| Setting | Default | Effect |
|---|---|---|
| Show pagination | On | On: fetches only the current page’s entities through a dedicated paginated subscription. Off: fetches every bound entity at once and hides the paginator |
| Page size options | 10, 20, 30 | The choices offered in the paginator; the first value doubles as the page size the widget opens with — there is no separate default-page-size setting |
How to customize
- To restyle the entity name (card title) — set Color and the font settings under Entity name styles.
- To restyle metric labels — set Color and the font settings under Metric label styles.
- To restyle metric values — set Color and the font settings under Metric value styles.
Tips
- Card actions are configured once, under the widget’s Actions tab, action source Card action — every action added there renders as its own icon button on every card; there is no per-entity action list.
- The card action icon’s color isn’t exposed in the settings panel — every action button currently renders in the same fixed dark color regardless of your other style choices.
- With Show pagination off, keep the bound entity count reasonable — every entity loads in one request instead of a page at a time.
Share Your Widget with the Community
Built a custom widget? Export it as a JSON from ThingsBoard and publish it to the IoT Hub through a simple 4-step wizard (Upload, Listing, Readme, Review & Submit). Share it with thousands of ThingsBoard developers worldwide and get featured in the catalog.