> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/win-gateway-installation-manual/node-information/nwin003-owxvalue-and-owxhealth.md).

# NWIN003 OWxValue & OWxHealth

The **OWxValue** fields are the latest temperature values read for each of the 3 digital temperature sensors that can be connected to the NWIN003 node. x is the sensor number ranging from 1 to 3.

<figure><img src="/files/ZBjgvPthRiSwnf91xE0H" alt=""><figcaption></figcaption></figure>

The health status indicator of the sensor can be checked to determine if a reading is valid.

The **OWxHealth** fields are the health status indicators of the 3 external temperature sensors. Each time the node successfully reads the sensor it increments this health indicator until it reaches 3 and then it stops incrementing it. If the node fails to read the sensor it decrements this value until it reached 0 and then it stops decrementing it.

&#x20;&#x20;

<table><thead><tr><th width="138">OWxHealth</th><th>Meaning</th></tr></thead><tbody><tr><td>3</td><td>The temperature value shown in OWxValue is valid</td></tr><tr><td>2</td><td>The value shown in OWxValue may be valid depending on the previous value (2 -> 1: not valid value, 1 -> 2: valid value)</td></tr><tr><td>1</td><td>The value shown in OWxValue may be valid depending on the previous value (2 -> 1: not valid value, 0 -> 1: valid value)</td></tr><tr><td>0</td><td>The value shown in OWxValue is invalid and is an old reading</td></tr></tbody></table>

&#x20;In normal operations the OWxHealth for a connected sensor should always be 3, but if a new sensor is connected a moment ago or a sensor is defective other values may be present.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.boomerang3.com/win-gateway-installation-manual/node-information/nwin003-owxvalue-and-owxhealth.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.