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.
The prose at the top, and the part most people will read. Up to four parts, each present only when it has something to say.
First, what happened to the house itself: restarts, a bridge or broker outage, an integration reloading. It sits above the device lines because it is the context for them; a reader who has it will not read fifty consequences as fifty faults.
Second, 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. A device that went and came back several times is one sentence with a count and a total, not one sentence per trip. And a device that stayed dead through restarts is one sentence with its true span: each restart closes its open silence as bookkeeping, because a reboot can revive a stuck radio, but when the device never speaks between the interruptions the brief reads its own record and says so plainly, "silent since Aug 18, 2.5d so far, across 6 restarts", rather than reporting a recovery for every reboot.
Third, beginning "Right now:", the standing problems at the moment of writing, worst first.
Fourth, when a pattern has earned it, "Keeps failing on its own:" names any device whose interruptions keep having no explanation, with the count, the days it spread over, and the worst day. No restart, outage, reload, or pairing window accounts for these, which is what makes them worth a line of their own: it is the shape of a television that reads unavailable when somebody turns it off, or of a device genuinely dying. How many unexplained interruptions in a week earn the line is the Repeat Offender Threshold on the Advanced screen.
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. The rows behind a dead device's restart bookkeeping are left out, because the sentence above already tells the one outage they fragment, and the event counts at the head of the table count what the table shows.
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.
Muted devices. This is a report, and muting 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 muting 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.