Device Detail

Everything DSM knows about one device lives on its detail page. Reach it with View from the
device list, from a group's device list, from an alert or event row, or from search.
The header
The Device info card sits above the tabs and stays there whichever tab you are on.
It gives the device's name, its Android serial, its Kuori serial, and two status badges. Green
badges read Device online and SMB connected. Red badges read Device offline and SMB disconnected.
Check these first. Half the tabs below show stale data when the device is offline, and the badges
are what tells you.
Moving between tabs
The tab strip runs under the header and wraps onto a second row on narrow screens. The tab you are
on is part of the page address, so you can bookmark a device's Management tab or paste a link to
exactly the view you mean.
The Backlight tab only appears if you are an administrator on this customer.
Overview
The landing tab, and a summary of the device's recent health.
Two cards give downtime over the last 24 hours and the last 30 days, in minutes. Below them are
this device's active alerts and its events from the last 24 hours.
Information
Every field DSM holds about the device, as a table.
Hardware model, panel, board model, build time, software versions, SMB UUID, Android ID, network
gateway, and when it was first seen. Nothing here is editable, and Edit at the bottom takes you
to the fields that are.
This is the tab to open when someone asks what is actually installed at a site.
Settings
The editable side of the same information.
Device Name is the one field worth caring about. Name devices after where they are.
Ignore alerts from this device stops it raising alerts, and also drops it out of reports. Use it
for a unit that is knowingly out of service. It hides real problems, so it is not a way to quiet a
device you still depend on.
Retire device takes the device out of the fleet. Retired devices leave the counters, the lists,
and the reports.
Timezone matters more than it looks. Scheduled commands run on the device's local time, so a
wrong timezone runs your overnight reset in the middle of the afternoon. Changing it here sends the
new timezone to the device.
Below those is Device Location, which is what puts the device on the Dashboard map. Search for
an address, drag the pin, or type coordinates. Remove Location clears it and takes the device
off the map.
Nothing saves until you click Save Settings.
Sensors and Controllers
Sensors is a live table of what the device measures, temperature and humidity among them, with
a history drill-down on each reading and a CSV export.
Controllers is the same for the controlled outputs: fans, backlight, modem, host, media player.
Live state, with history. This is where you confirm whether a display was actually powered when
someone says the screen was dark.
Report history
The raw check-ins. Pick a date range and the sensors and controllers you care about, and DSM builds
a report from the reports the device actually sent, with a CSV export. Useful when you need to
prove exactly what a device said and when.
Events and Alerts
Events is this device's full event log, filterable by date, exportable as CSV.
Alerts is its full alert history, including alerts somebody has already ignored, which the
Dashboard hides. Also exportable. An alert with no end time is still open.
If you are chasing a recurring fault, this pair is where the pattern shows up.
Notes
Free text tied to the device, with who wrote it and when. Add, edit, and remove them freely. Notes
are for the things DSM cannot know. Which door the key is behind, that the site closes for July,
that the panel was replaced in March.
Groups
Every group this device belongs to. You can add it to an existing group or a new one from here, and
remove it from any of them.
Management
Reset commands, scheduled resets, and modem tools.
More about resets can be found from here
This is the tab that acts on hardware. The
Device Reset Guide covers it in full.
Display health
On-time percentage, the screen-off events behind it, and a timeline bar showing when they happened.
Use it to spot a screen that keeps failing rather than one that failed once.
Backlight
For administrators. Minimum and maximum brightness limits, and schedules for switching the displays
on and off per day and per time. A screen that is off on schedule still counts as downtime in the
backlight reports, which is why those reports carry a warning.
When the device is offline
Anything that sends a command to the device is disabled, and DSM says why rather than failing
silently.
Reading tabs still work. History does not need the device to be reachable. Scheduled commands can
still be saved, and they start running once the device reconnects.