-
Notifications
You must be signed in to change notification settings - Fork 0
The Problem List
The problem list contains the frozen devices and low batteries the integration currently sees and is where its detections become something you can act on. It is a standard Home Assistant to-do entity, todo.device_sentinel_problem_list, visible in the sidebar's To-do panel, in the companion app, and on any dashboard through the ordinary to-do list card.
The moment a device is judged frozen, unavailable, unknown, or never reported, the moment a battery crosses the low threshold or is projected to run down to empty, or the moment a signal problem is confirmed, an item appears.
A device appears once, no matter how many problems it carries. The line leads with the device's name and then lists its problems in a fixed order: the freeze verdict first, then the battery, as a percentage where it is under the threshold and as a forecast where it is running down.
Checking an item means you have seen this problem and decided it can wait.
The item remains on the list, marked as done, and becomes silent. It is ignored and does not appear on the daily brief, it will not appear in the persistent dashboard card, and is absent in your phone notifications. The fault is still recorded in the diagnostic reports and audit trails.
The worked example: you have a vibration sensor in a vehicle that is at the mechanic. Unchecked, every daily brief would mention it. Checked, it moves to the background and becomes silent for as long as the car is gone.
Acknowledgment ends when the problem does:
- If the problem worsens while acknowledged, for example a low-battery device freezing, nothing is sent, because you already said you know it needs attention.
- If the device recovers on its own, the daily brief will say so, and any later fault on that same device is treated as a fresh incident.
Checking never means recovered. Recovery is detected, not declared. When the device recovers, its item is removed whether you checked it or not.
Unchecking an item returns it to the open block, making it an active alert again. Deleting an item by hand while its device is still down is the hard un-acknowledge: on the next sync, the integration will see the device is still down, re-add it as a new incident, and announce it again.
Open items sort alphabetically by device name, so the active list reads like a roster rather than a timeline.
Acknowledged items follow in the order you checked them, oldest first. This makes the checked section a stable history that does not reshuffle as active problems come and go around it.
An acknowledgment silences a current incident. An exclusion is the standing statement that a device should never be judged for that problem again. If you find yourself re-acknowledging the same device every time it fails, the exclusion pages, like Low Battery or Global Exclusions, are the better tool. Once excluded, the device drops off the list at once and stays off.
The standard Home Assistant to-do list card, pointed at todo.device_sentinel_problem_list, gives you the live report and the acknowledgment checkbox in one place.
Two settings on that card are worth knowing:
- Keep the completed section visible: This is where your acknowledged items live.
- Avoid the "Remove completed items" action in the card's menu: This hand-deletes all your acknowledgments. Because the devices are still broken, the next sync will re-add them all and fire fresh notifications for every one.
Device Sentinel is brought to you by James Lander at The Thinking Home. Read the story behind it: Reliable Home Assistant Dead Sensor Detection.
Repository · Report an Issue · Releases · Blueprints
Licensed under GPL-3.0-or-later. Copyright © 2026 James Lander.
Start Here
Configuration
- The Device Page
- Notifications and Daily Brief
- Exclusions and Muting
- Low Battery
- Signal Strength
- Freeze Detection
- Advanced
The Reports
Automations
Understanding
- How Device Sentinel Learns
- Maintenance Mode
- The Bridge and Broker Sensors
- What Is Recorded About Your House
- Built to Be Efficient
Coordinator Stacks
Help