FAQ and Troubleshooting

FAQ and Troubleshooting

Why is Devices Watched lower than my device count? Devices with no hardware behind them (service entries, cloud connections, integration containers) are classified out automatically; they are the Service Devices Ignored count. The rest of the difference is your own exclusions. The classification report names where every device landed; see The Reports.

Why is Devices Learned zero, or low? Each device needs enough completed days to establish a rhythm, seven by default. A fresh install reads zero for its first week; that is the system working, not stalling. Some devices never arm at all: buttons and remotes have no heartbeat to learn, by design.

Why does Status say Learning? No device has established its rhythm yet. It flips to Watching at the first one and stays there.

I excluded something, will it have to re-learn when I un-exclude it? No. Excluded items are still watched and learned; only reporting is suppressed. Undoing an exclusion is instant and complete.

A device shows as "not reported". What does that mean? It has produced nothing at all since Device Sentinel first saw it, for at least 48 hours. This catches the case that would otherwise slip through: a device with no learned rhythm and often no live entity, a registry ghost, a device dead before install, a monitor whose target is gone. It is yours to sort out: fix it, delete it if it is a stale registry entry, or send it to the Freeze Detection exclude list if it is meant to be quiet for now.

A dead device is not showing in the Device: Frozen count. Check whether it is globally excluded. A globally excluded device is judged by nothing, so it is never counted as down, by design. The reports STATUS column shows it as global. If you want it watched for freezes, remove it from Global Exclusions; if you want it watched for battery and signal but not called down, the freeze exclude list is the narrower tool.

Why does nothing reach my phone? Two possibilities. Targets are not set: see Notifications. Or you are on a release before the notification engine ships; the settings are stored and honored the moment it arrives.

Why did my entity IDs change? Release 0.3.12 renamed entities so their IDs say what they count (devices_watched, devices_learned, and so on). Existing installations were migrated automatically, one logged rename each. Dashboards and automations referencing the old IDs need pointing at the new ones once; the table is in the 0.3.12 release notes.

A battery is one percent above my threshold and still flagged. A flagged battery clears at 2 points above the threshold, not 1. The margin exists because battery readings rebound under load; without it, a cell at the line would flap in and out of the report.

Something looks wrong. What do you need from me? Download Diagnostics: Settings, Devices and Services, Device Sentinel, three-dot menu, Download Diagnostics. Attach it to an issue at the issue tracker. It carries the learned state, the settings in effect, and the classification, and answers most questions without screenshots. Notification targets are redacted automatically.