Device & Sensor Error Codes

When a sensor reports a problem, the v5 API surfaces an error code describing the condition: a hardware fault, a communication problem, an out-of-range value, or a failed calculation. You are looking for HTTP errors codes, see HTTP Status Codes.

Each reading in the values array carries its own error_code field, alongside value,unit, timestamp, and the other fields. An error_code of 0 means no error and the reading is valid; a non-zero error_code is one of the values listed below.

"values": [
            {
              "port_num": 1,
              "measurement": "Air Temperature",
              "unit": "°F",
              "sensor_name": "TEROS 15",
              "value": 90.32,
              "timestamp": 1705485442,
              "datetime": "2024-01-17T09:57:22-08:00",
              "error_code": 0
            }
          ]

Device & sensor error codes appear inside a successful response body, on the individual reading, and are surfaced by data-returning endpoints such as Get Device Readings.

Code reference

What each code means

The entries below explain the condition behind each code and, where relevant, how to resolve it. Communication and hardware faults usually require servicing the unit in the field; value and calculation errors usually clear on their own once the underlying condition passes.

Hardware and communication

128 — Sensor calibration problem The sensor is reporting a problem with its calibration values. This can result from a damaged sensor or corrupted firmware.

129 — Excitation under-voltage error The excitation voltage is too low to make a reliable measurement. Often a power problem on the logger — install fresh batteries and check the board for corrosion.

131 — Sensor type not supported The connected sensor is not recognized by the data logger, commonly because the logger firmware is out of date. Update the logger to the latest firmware.

132 — Sensor communication error The sensor and logger are communicating, but the data is corrupted — typically a damaged sensor, corrupted sensor firmware, or a damaged cable. Inspect the cable and port; a field visit is usually required.

133 — Sensor is reporting an error No usable communication from the sensor, commonly an unplugged or broken sensor or a damaged cable. A field visit is usually required.

134 — No response from sensor The sensor and logger are not communicating at all — usually an unplugged or broken sensor or damaged cable. Inspect the connection; a field visit is usually required.

235 — Erased flash memory The logger is reporting erased flash memory. Contact METER environment support with your logger serial number.

Value availability and range

130 — Sensor value is temporarily out of range The sensor cannot make the measurement right now; the value will return once conditions return to normal (for example, an ATMOS 41 whose sonic transducers are temporarily covered by water).

136 — Sensor value outside the expected range The reported value is outside the sensor’s valid range. inspect the sensor, check for improper installation or damage.

143 — No data available for the requested time/measurement No measurement exists for the requested time or measurement.

Value and calculation

137 — Invalid value A processed value resolved to NaN (not a number) or infinity.

138 — Alpha value too low The alpha value for the index is below the acceptable threshold (NDVI alpha <0.79 or > 2.0; PRI < 0.02).

139 — Radiance value(s) too low Measured radiance is too low to calculate the index.

140 — Calculation exceeds limits An input to the computation is outside the model’s acceptable limits (for example, an NDVI or PRI result outside −1 to 1, or VPD outside 0 to 10000).

141 — Calculation error An unexpected processing error occurred while computing the value.

142 — Value exceeds limits of the model The value is too extreme to be reasonable, typically from a misconfigured port, corrupted firmware, or a broken sensor.

Notes

• Relationship to v4 codes. These codes are a renumbered version of the v4 metadata codes (v4 65528–65542). The meanings carry over directly; only the numbering and some wording changed. Consumers migrating from v4 should re-map rather than reuse the old numeric values.