HEART performance.too-hot H-05005
Too hot. The device is overheating and may slow itself down.
| Code | HEART performance.too-hot; inside a message "code": "performance.too-hot" |
|---|---|
| H-number | H-05005: area 05, code 005 |
| Area | performance: Speed, load, heat |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Every product with electronics, motors, heaters or batteries |
Likely causes
- A fan stopped or a vent is blocked by dust.
- The product is in the sun, in a closed box, or in a parked car.
- A motor, pump or connector working harder than it should, or a loose high-current connection.
- A heatsink that came loose.
How to fix or prevent it
- Check fans and vents; clean the dust.
- Move the product out of the sun, or shade its box.
- Check connectors for discoloured or loose contacts.
- Let it cool before using it hard again.
- To prevent it: keep air flowing, and keep filters clean.
What the HEART does by itself
It raises a warning before the product's own protection cuts in, with the temperature and the limit. The product itself may already slow down or derate (an EV charger dropping to 16 A, a processor slowing). A HEART never overrides that protection. It resolves when the temperature falls back.
When to call service
If anything smells hot or looks scorched, if a motor or connector is hot, or it keeps coming back with fans and vents clean.
Related codes
system.main-function-degradedH-01002: Main function degradedactuators.overcurrentH-09005: Overcurrentpower.battery-failingH-02004: Battery failing
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)