HEART sensors.disagree H-08006
Sensors disagree. Two sensors that should agree do not.
| Code | HEART sensors.disagree; inside a message "code": "sensors.disagree" |
|---|---|
| H-number | H-08006: area 08, code 006 |
| Area | sensors: Readings and calibration |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Products with redundant or related sensors |
Likely causes
- One of the two sensors has drifted or failed.
- They are in places with really different conditions.
- Different units or calibrations.
How to fix or prevent it
- Check both against a reference.
- Check their places and settings.
- Calibrate or replace the one that is wrong.
What the HEART does by itself
It raises a warning, and stops relying on either value for decisions that matter until it can tell which is right. It resolves when they agree.
When to call service
If the sensors are safety sensors.
Related codes
sensors.driftH-08005: Sensor driftsensors.stuckH-08003: Reading stuckai.disagreementH-07010: Brain disagrees with the system's checks
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)