-
Notifications
You must be signed in to change notification settings - Fork 0
The Daily Brief
This report outlines the health of your system and its devices and sensors. Where the diagnostic files explain the machinery, this brief answers two questions in plain language: what is wrong now, and what happened since yesterday.
It is an HTML page located in the configuration folder at www/device_sentinel/, one file per day, named daily_brief_YYYY-MM-DD.html. Beside the dated files sits daily_brief.html, a copy of the newest write, so a dashboard Webpage card pointed at /local/device_sentinel/daily_brief.html shows the current brief.
Two paragraphs at the top, and the part most people will read.
The first tells the window's history in the order it happened. A device stopped reporting at 1:02 AM, recovered at 3:03 AM after two hours when the Zigbee bridge reconnected, a battery fell to 14% at 3:02 PM. The second is a summary report of the state of the system when the report was generated, worst first.
What needs attention, as a table: the device, the problem, when it started, and how long it has been going. Sorted worst first.
This section is always current. It is read at the moment the file is written, not bounded by the window, so a brief written at 7 AM tells you where things stand at 7 AM whatever period its history covers.
The events, newest first, with their exact times. The prose above is for reading; this is for scanning and for looking up when something happened.
Between one brief and the next, the file is rewritten as an in-progress version whenever reports are generated: by the Regenerate Reports button, at startup, and at midnight. Each version replaces the last and is marked in progress.
That working copy always covers the last twenty-four hours, wherever in the day you open it, so a dashboard card shows a full day rather than the handful of hours since your brief time. The dated file for each day is a separate thing and does not move: it stays bounded by your brief time, as described above.
Excluded devices. This is a report, and exclusion suppresses reporting.
Acknowledged problems. Acknowledging something is the statement that you know about it and do not want to be reminded.
The integration's own machinery. No learned rhythms, no freeze windows, no lag values, no exclusion reasoning. Those belong in the diagnostic files and would only get in the way here.
The brief is emailed on its schedule to whoever is listed under Send the Full Brief To on the Notifications and Daily Brief screen, most often an email address through SMTP. What arrives is the page itself, tables and styling included, so the brief in your inbox is the same document as the one on your dashboard. If a signal anomaly line is present, it links to the chart so it opens from a phone or browser.
It uses your external Home Assistant address where one is set, and your internal address otherwise. Both are set under Settings, System, Network.
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
