HEART sensors.no-reading H-08001
No reading. A sensor gives no value.
| Code | HEART sensors.no-reading; inside a message "code": "sensors.no-reading" |
|---|---|
| H-number | H-08001: area 08, code 001 |
| Area | sensors: Readings and calibration |
| Typical severity | warning. 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 unplugged, or its wire broken.
- A sensor that has failed.
- No signal for a radio sensor: GNSS indoors or in thick woods, a wireless probe out of range.
- A flat battery in a wireless sensor.
How to fix or prevent it
- Check the sensor's plug and wiring.
- For radio sensors: move to open sky, or closer to the receiver.
- Replace the battery of a wireless sensor.
- Replace the sensor if it still gives nothing.
What the HEART does by itself
It raises a warning after a number of missed readings (such as 3 failed fixes and 150 s with no position), and stops trusting that value. It resolves when readings return.
When to call service
If wiring and batteries are fine and still nothing is read.
Related codes
sensors.stuckH-08003: Reading stucksensors.out-of-rangeH-08002: Reading out of rangedata.missingH-10002: Data missing
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)