-
Notifications
You must be signed in to change notification settings - Fork 0
Advanced
Settings most people never need to change. Each has a sensible default, and each exists because somebody's system is not most systems.
When a device develops a problem, the integration waits before telling anyone, so a device that hiccups and recovers within moments never rings your phone. A fixed delay cannot serve a fleet where one device reports every ten seconds and another every four hours, so the delay scales: it is a percentage of each device's own grace, the patience the freeze engine has already computed for it.
At the default of 30 percent, a device that reports every ten seconds settles in about a minute, and a device with a three-hour rhythm settles in about half an hour. Raise it and fewer transient problems reach you, at the cost of hearing about real ones later. Lower it and notifications become prompter and noisier. Detection is not affected; problems are recorded and listed the moment they are found, and this delays only the message.
The silence_episodes.md report records devices that went unusually quiet, for later study: it is how the integration learns whether a silent device was stuck or simply resting. A row opens when a device has been silent for this share of the distance between its normal rhythm and its freeze line.
At the default of 50 percent, a row opens halfway to the freeze line. Lower it and the file records more, including mild wobbles that recover on their own, which is useful when investigating a flaky device. Raise it and the file records only silences that came close to judgment. This affects one forensic file and nothing else: no detection, no notification, no learning.
The integration tracks activity for every device, which changes constantly. Writing every change to disk would mean a write every minute or two forever, which wears SD cards and adds up on any system. Instead, routine activity is held in memory and written on this interval. Anything important, a new problem, a recovery, an acknowledgment, a checked box, is always written immediately regardless.
The default is 15 minutes. On an SD card, longer is kinder. On an SSD, shorter narrows the window of activity data that a power cut could lose, which at worst costs the affected devices a few minutes of clock and heals with their next report. The range is 1 to 60 minutes.
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