Skip to content

A Home Assistant Battery Check for Low and Missing Readings

Example battery check: Hall sensor 18 percent low, kitchen 72 percent OK, office has no reading.

A sensor battery can run low quietly. A dead battery may leave the sensor unavailable altogether, so a dashboard that only shows low percentages can miss the device you need to check most.

Here is a small Home Assistant dashboard card for the battery sensors you choose. It lists readings at or below 25%, flags missing or invalid readings, and shows a reassuring message only when every selected sensor has a valid reading above the threshold. The example uses fictional sensor names.

What you need

Home Assistant with an editable dashboard and numeric battery percentage sensor entities. This guide uses the built-in Markdown card and follows the Home Assistant 2026.11 documentation; it needs no custom card or HACS. Sensors that expose only a low-battery on/off flag need a different approach. You will need to choose the entities yourself, so the card does not silently include a phone or an unrelated battery.

1. Find your battery entities

Go to Developer tools → States and search for your devices. Find each battery percentage entity and copy its entity ID, such as sensor.hall_battery. Confirm that the state is a percentage from 0 to 100. Names and IDs in the example are placeholders; yours will be different.

2. Add the card

  1. Open the dashboard where you want the check, select the edit button, and choose Add card → Markdown. For a dashboard managed automatically by Home Assistant, taking control means it will no longer update itself automatically; use an existing editable dashboard if you want to avoid that change.
  2. Open the card’s code editor and replace its configuration with the complete YAML below.
  3. Replace each of the three example entity IDs inside batteries with your own, keeping the quotes and commas. Add or remove list entries as needed, but keep at least one. Change threshold = 25 if you want a different cutoff.
  4. Save the card, then save or exit dashboard editing. The card updates as its selected entity states change.

Why an explicit list? It keeps the check focused on devices you care about, and makes a typo visible as a missing reading instead of quietly dropping it. The list is a maintenance task: add a new battery entity when you add a device.

3. Check that it works

  1. Compare each selected entity with Developer tools → States. A reading at or below the threshold should appear as low; one above it should not.
  2. Temporarily change the threshold in the card to a number above one known reading. Save and confirm that sensor appears, then restore your preferred threshold.
  3. To check the missing-data path safely, temporarily add a fictional ID such as sensor.example_battery_missing. It should show “no valid reading”; remove the fictional entry afterward.
  4. If all selected readings are valid and above the threshold, the card says so. Reload the dashboard and confirm the list still matches the entity states.

If something looks wrong

  • Missing or invalid reading: check the entity ID and its state in Developer tools. Unknown, unavailable, nonnumeric and out-of-range states are flagged; an unavailable entity is not proof that its battery is empty.
  • Device is missing from the card: add its battery entity to the list. A device without a numeric percentage entity cannot be evaluated by this card.
  • Nothing changes: check the ID and save the card again. If automatic dependency tracking misses an entity, the Markdown card documentation describes the optional entity_id update list.

Battery percentages are estimates and may be old even when they look valid. This card does not detect stale normal values, send notifications, or work while Home Assistant is down. Use the device’s own warnings for critical equipment. To remove the check, edit the dashboard and delete the card; no sensor or automation is changed.

I checked the YAML and template with fictional readings, including low, normal, missing, and unavailable values. I have not loaded this exact card into a Home Assistant runtime; verify it with your own entities as described above.

For a different problem—an important sensor becoming unavailable—see the sensor availability guide.

References: Home Assistant Markdown card, working with states, and template debugging.

Free Relay. Home Assistant, wherever you are. 5 entities free. No port forwarding. Try free.

Leave a Reply