The Device Page

The Device Page

Settings, Devices and Services, Device Sentinel. What every row means.

Controls

Enable Signals, Enable Last Seen, Enable Battery. Three buttons, one per diagnostic kind. Each scans the entity registry for entities of its kind that an integration shipped turned off, and turns them on so Device Sentinel can learn from them, on watched devices only. Entities you disabled yourself are left alone. They are split so you can enable exactly what you want: last-seen entities are protocol truth, the most reliable clock a device can offer, so Enable Last Seen strengthens freeze detection; Enable Battery turns on the battery-percentage sensors the discharge history records; Enable Signals turns on the link-quality entities the signal floor learns from.

Regenerate Reports. Judges every device and rewrites both nightly report files at once. Press it when you have just fixed a device and want the report to reflect it now rather than at the next check: the fresh timestamp at the top of the down-devices section confirms the run.

Problem List. Device Sentinel's own todo list, one row per current finding. Checking a row acknowledges it; a finding that recovers removes its own row. Items you add yourself are left untouched. Empty until the detection families that populate it arrive.

Sensors

Status. Watching, Learning, or Problem. Learning shows until the first device establishes its rhythm; Watching from then on; Problem if Device Sentinel's own storage is unhealthy. The setup count and install date ride as attributes.

Devices Watched. How many devices are being observed and learned. The split behind it (total, set aside, deviceless entities) rides as attributes.

Devices Learned. How many devices have an established rhythm, meaning enough learned days to be judged for freeze. Not expected to reach Devices Watched: devices with no heartbeat, like buttons and remotes, never establish a rhythm and are never judged frozen, by design.

The sensors come in two families of three, named so they group in the entity list: every Signal, Battery, and Device entity sorts together. The Tracked family counts what Device Sentinel watches in each domain, after that domain's excludes, and is always on. The Problems family counts what currently has a fault, and ships off by default: the todo list is where a person reads trouble devices, so these three counts are yours to enable for a dashboard or an automation if you want them. Each carries its devices in attributes.

Signal: Tracked. How many devices have a learned signal floor and so a live danger line, minus the signal-excluded. The scale split (LQI, RSSI) and the still-learning count ride as attributes.

Battery: Tracked. How many devices have an elected battery entity, minus the battery-excluded. The devices ride as attributes.

Device: Tracked. How many devices have a learned rhythm and so are eligible for freeze detection, minus the global device excludes. The devices ride as attributes.

Signal: Problems. How many devices have a signal fault right now, each tagged by kind: a rail (stuck at the 255 or -128 fill value for three days) or a low (dwelling below the danger line, quiet until that line is ruled). The devices ride as attributes, rail first.

Battery: Low. How many batteries are low right now, with one row per device in its attributes: name, entity, area, level, low-since, plus the thresholds in effect. The row shape matches the Battery Sentinel blueprint. This is one sensor: the count is the state, the rows are attributes.

Device: Frozen. How many devices are frozen, unavailable, or unknown right now. Each carries its category and how long it has been down in the attributes. Off by default like the other problem counts; the todo list is where trouble devices are read.

Configuration

Battery: Threshold. The percentage at or below which a battery is flagged. The same setting as the slider on the Low Battery screen, surfaced here so the knob lives where the counts are seen.

Diagnostic

Service Devices Ignored. Devices with no hardware to watch: service entries, cloud connections, integration containers. Device Sentinel classifies these out itself. This is not the exclude list; you did not choose these and they need nothing from you.

Entity IDs

Since 0.3.12, in the form the names suggest: sensor.device_sentinel_devices_watched, sensor.device_sentinel_devices_learned, and so on. Installations from before 0.3.12 were migrated automatically, one logged rename per entity.