> 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.
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.
OWxHealthMeaning
3The temperature value shown in OWxValue is valid
2The value shown in OWxValue may be valid depending on the previous value (2 -> 1: not valid value, 1 -> 2: valid value)
1The value shown in OWxValue may be valid depending on the previous value (2 -> 1: not valid value, 0 -> 1: valid value)
0The value shown in OWxValue is invalid and is an old reading
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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.boomerang3.com/win-gateway-installation-manual/node-information/nwin003-owxvalue-and-owxhealth.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.