HEART power.battery-low H-02003

Battery low. The battery needs charging soon.

Likely causes

• Normal use since the last charge.
• Too little sun or wind for a self-charging product, such as a solar camera in winter.
• Cold weather, which lowers a battery's usable charge.
• More use than normal: more reports, more pictures, a longer motor run.
• An implant or long-life device reaching its planned replacement point.

How to fix or prevent it

1. Charge or replace the battery.
2. For solar products: clean the panel and check that it faces the sun.
3. Reduce what drains it, such as how often it reports, if the product allows it.
4. For a medical implant: book the planned replacement with the clinic, as the alert says.
5. To prevent it: charge on a schedule, and replace batteries before winter.

What the HEART does by itself

It raises a warning with the charge left and, where it knows it, the time left. It may save power on its own, such as reporting less often, if a Playbook allows it. It resolves when the battery is charged.

When to call service

Only if the battery does not charge, or empties much faster than before: then see power.battery-failing.

Related codes

• power.battery-failing H-02004: Battery failing
• power.supply-lost H-02001: Main power lost
• system.flatline H-01003: No Pulse (flatline)

Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written HEART storage.full. Things that simply happen, such as system.started, are event types, not faults. The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7. All of it, as data: fault-codes.json.

All fault codes, by area · All fault codes, by H-number · Problem types (API errors)