HEART sensors.stuck H-08003
Reading stuck. A reading has not changed when it should have.
| Code | HEART sensors.stuck; inside a message "code": "sensors.stuck" |
|---|---|
| H-number | H-08003: area 08, code 003 |
| Area | sensors: Readings and calibration |
| Typical severity | error. A product may set another for its own case. |
| Applies to | Products with sensors: thermostats, chargers, pumps, printers, trackers, medical devices |
Likely causes
- A sensor frozen by a fault, giving the same value again and again.
- A reading copied from a cache when the real sensor stopped.
- A bus or driver error that keeps the last value.
- A probe that came out of what it measures, such as a soil probe pulled from the soil.
How to fix or prevent it
- Compare with a second reading: a hand thermometer, a gauge, another sensor.
- Check that the probe is in place.
- Restart the sensor or its bus.
- Replace it if it freezes again.
What the HEART does by itself
It raises an error alert when the value has not changed while it should have, such as 90 s without change through watering, or no change while the GNSS shows movement. It stops trusting the value. The product's firmware often cannot see this if the frozen value is near the target. It resolves when the value moves again.
When to call service
If the sensor matters for safety, or freezes again after a restart.
Related codes
sensors.no-readingH-08001: No readingsensors.disagreeH-08006: Sensors disagreesensors.driftH-08005: Sensor drift
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)