Finding your devices
The device list is where you see every device in your workspace, how each one is doing, and when each was last heard from. From there you can open a device to look at its readings, its history, and (if you have the right role) the commands you can send to it.
Opening the device list
Click Fleet in the sidebar, then the Device list tab. You'll only see devices that belong to your workspace; devices in other workspaces, or devices that haven't been assigned yet, aren't shown.
The columns
By default the list shows:
- DevEUI: the device's unique identifier, a 16-character code that's the same on the device label.
- Serial: the device's serial number from its label, handy for matching a device to physical stock. Blank if not recorded.
- Name: the friendly name your provider gave the device, or its DevEUI if no name has been set.
- Primary and Secondary: the two most-important readings from this device, each with units and the time of the latest reading. You'll see a dash if nothing has been received yet.
- Health: one or more chips telling you the device's current state at a glance. See below.
- Signal: how strong the device's wireless connection was for its latest reading, as a percentage with a simple label (Excellent, Good, Fair, or Poor).
- Battery: the device's latest known battery level, as a percentage with a simple label (Good, Low, or Critical), or Powered for devices that run on external power. See Battery readings for what the values mean and how fresh they are. A dash means the device has not reported battery yet.
- Last seen: how long ago the device last sent a reading.
The list puts online devices first, then orders by the most recently seen, so the devices reporting right now stay near the top. Health and last-seen update on their own as readings arrive, so you don't need to refresh the page.
You can search the list by name, DevEUI, serial number, or tag using the search box above the table. Next to it, the Health quick filter narrows the list to Online, Offline, Alerting, or Warning devices, using the same definitions as the health chips below.
Your search and filters stay put
The list remembers your search, quick filters, and the page you were on while you work. Open a device, come back with the Fleet breadcrumb or your browser's Back button, visit another part of the app and return: the list is exactly as you left it. It also survives a page refresh, and the filters are part of the page address, so you can bookmark a filtered view or send the link to a colleague. The memory is per browser tab; a new tab starts with the full list.
Whenever a search or filter is active, a line above the table reads Showing X of Y devices with a Clear filters link that puts everything back, including the page. The Gateways tab works the same way.
Choosing your columns
The default set isn't fixed. Click the Columns button above the table to choose exactly what you see: tick a column to show it, untick it to hide it, and drag the handle next to a name to change the order. Hidden columns wait below the divider, ready to be re-added; that's where you'll find extras such as Tags (any labels set on the device, handy for grouping or searching), Last gateway (the gateway that relayed the device's most recent reading; blank for devices that connect directly over cellular or that haven't reported yet), and, if your plan includes them, Site and Network. At least one column always stays visible.
Your layout saves to your profile automatically, so the list looks the same next time you sign in, on any computer. Reset to default in the same menu puts everything back. The Gateways tab has its own Columns button that works the same way.
Exporting the list
Click Export above the table to download the Device List as a CSV file that opens in Excel and other spreadsheet apps. The downloaded file matches what you see: it includes only devices that pass your current search and filters, and only the columns you have chosen to show, in the same order.
To export a particular group, apply the filters first, choose the columns you need, then click Export. Hidden columns and devices outside the filtered results are left out.
The health chips
| Chip | What it means |
|---|---|
| Online (green) | The device sent a reading recently, within its expected reporting window. |
| Offline (gray) | The device hasn't been heard from for longer than its offline threshold (typically 30 minutes, but configurable per device). |
| Alert / Warning / Info (colored) | A rule has flagged this device. See Responding to alerts. |
| Quota (yellow) | The device has hit a daily limit on how many readings it can send. New readings will resume tomorrow. |
| Cert expiring or Cert expired | A certification document attached to the device is about to lapse or has lapsed. Your provider handles renewals. |
| Battery (colored) or Powered | The device's latest battery level, color-coded like the Battery column, or Powered for externally powered devices. Only shown once the device has reported battery. See Battery readings. |
Hover any chip for a tooltip with detail (for example, the exact last-seen time).
What "last seen" means
A device's last-seen time is the timestamp of its most recent reading. If a device transmits every hour, "Last seen 47 minutes ago" is normal; if it transmits every five minutes, the same value is a warning sign.
The platform decides a device is offline by comparing the last-seen time to a per-device offline threshold (default 30 minutes). Cross the threshold and the chip flips to Offline.
"Last seen" only counts readings the device sent. The platform doesn't ping devices, so a quiet device may be working fine and simply not have anything to report yet.
Battery readings
Battery-powered devices show their latest known battery level in the Battery column, and as a chip next to the online/offline status on the device detail page. The percentage is color-coded so problems stand out at a glance:
| Label | Level | What to do |
|---|---|---|
| Good (green) | 60% or higher | Nothing; the device is healthy. |
| Low (orange) | 30-59% | Plan a battery change during your next site visit. |
| Critical (red) | Below 30% | Replace the battery soon; the device may stop reporting without warning. |
Devices that run on external power show a Powered tag instead of a percentage. A few devices cannot measure their own battery; those show a dash, as do devices that simply have not reported battery yet.
Battery readings are not live. Depending on the device, the battery level either arrives with its regular readings or is collected by the network a few times a day. Hover the value to see exactly when the reading was taken; a reading a few hours old is completely normal. Battery moves slowly, so this is plenty to act on.
You can also chart battery over time on a dashboard (bind a widget to the Battery field) and get ahead of dead batteries with a workflow: a condition like Battery is less than 30 alerts the right person automatically, and it is checked the moment a new battery reading arrives. See Creating workflows.
Opening a device
Click any row to open the device detail page. You'll see several tabs across the top.
Dashboard
If your provider built a dashboard tied to this device's type, the Dashboard tab shows it filled in with this specific device's readings. Treat it the same way you would any other dashboard. See Reading your dashboards.
Events
The Events tab is a chronological log of what the device has sent and received: every reading, every status change, every command if any have been sent. Use it to confirm something arrived, or to spot a gap.
Each reading also shows a Signal Quality percentage with a simple label (Excellent, Good, Fair, or Poor). It is a quick read on how strong the device's wireless connection was for that message: a steady run of Poor readings usually means the device is too far from a gateway or something is blocking the signal.
Configuration
The Configuration tab shows the device's name, description, location on a map, offline threshold, and downlink expiry. For Operators and Viewers this tab is read-only; only your Workspace Admin or your provider can change these values.
Downlink expiry sets how long a queued command stays valid for this device. If the device can't receive the command within that time, for example because it stays offline, the network discards the command instead of delivering it late. Leave it blank to let commands wait indefinitely. This is useful for devices like valves or switches, where a command that finally arrives hours later could leave the device in the wrong state.
Downlinks (only on some devices)
If your device supports commands, you'll see a Downlinks tab. Everyone who can open the device can see the tab's command history; sending is restricted.
Permission required to send: Workspace Admin, and only if your provider has enabled commands for this device's profile and your plan includes them. Viewers and Operators see the history but not the send controls.
A command waits in a queue until the device next checks in. If a downlink expiry is set on the Configuration tab, a command that can't be delivered within that window is dropped rather than sent late.
Downlink history
The History section lists every command sent to the device in the last 12 months: what was sent, when, who or what sent it (a person, a workflow, a shared dashboard, or an integration), and what happened to it. Filter by status, by source, or by date range, and use Export CSV to download the filtered list.
Each command shows a status:
- Queued: waiting for the device's next check-in.
- Delivered: transmitted to the device.
- Device-acked: the device confirmed it received the command. Only commands set up to request confirmation can show this.
- Nacked: the device received the command but rejected it. Ask your provider to check the command's setup.
- Stuck: the command has waited far longer than the device's usual check-in interval. The device may be offline or out of range.
- Expired: the command could not be delivered within the downlink expiry window and was discarded rather than sent late.
- Flushed: an administrator cleared the queue before the command was sent.
Select Details on any row to see the full payload, delivery timestamps, and whether confirmation was requested.
Showing the commanded state ("from command")
Some commands are set up so that, once the device confirms it received them, a field updates to show what you asked for. For example, sending Open valve can set the valve's state to Open as soon as the device acknowledges the command, without waiting for the device's own status report.
This is useful when a device's status reports are unreliable, for instance on weak network coverage, where the report saying "I am now open" can be lost. The field shows a small from command tag so you know the value reflects a confirmed command rather than an independent reading from the device. As soon as the device does send a real reading for that field, it takes over and the tag clears. Your provider sets this up per command; if you don't see it, it isn't configured for that device.
Fields
The Fields tab lists every reading the device sends, with its units. Workspace Admins can pick which two appear as Primary and Secondary in the list. Viewers and Operators can see the list but not change it.
Certification (only on some devices)
If your provider tracks compliance documents on devices, you'll see a Certification tab with the current documents and their expiry dates.
Locating a device
If you need to find a device on a map, open its Location tab. The map shows the location your provider entered when the device was installed.
Setting a location by address
If you can edit a device (Workspace Admins), you don't need to know the latitude and longitude to place it on the map. On the Location tab, use the Search for an address box: start typing the street address of where the device is installed, pick the matching result, and the map pin and the latitude and longitude fill in automatically. You can still fine-tune the spot by dragging the pin, and dragging it fills in the nearest address for you. Click Save to store it. A gateway has the same Location tab.
For a workspace-wide view, open Fleet in the sidebar, then the Fleet Map tab. It plots every device and gateway that has a location, with street and satellite views. Nearby pins combine into a numbered cluster; the cluster's color reflects the worst state inside it (red and pulsing when a sensor is alerting, gray when something is offline, green when all is well), so a problem anywhere on the map is visible at any zoom level. Click a pin for the device's status and last reading time, then jump straight to its detail page. The Filters button on the map narrows the view to device or gateway pins, or to online, offline, or alerting devices only, and the home button under the zoom controls snaps back to the full-fleet view.
Frequently asked
A device is offline but I know it's working. What's wrong? The device hasn't sent a reading in longer than its offline threshold. It could be a flat battery, a network outage near the device, or the threshold being set too tight for how often the device reports. Ask your provider to investigate.
Why don't I see a device I expect to see? Devices appear once your provider assigns them to your workspace. If your plan lets you claim hardware yourself, a device you hold won't show until you claim it, see Claiming a device or gateway. If something is still missing, ask your provider to check.
Can I rename a device? Workspace Admins can edit the name on the Configuration tab. Operators and Viewers cannot.
Can I delete a device? No. Removing a device is something only your provider does.