> For the complete documentation index, see [llms.txt](https://docs.mclimate.eu/mclimate-lorawan-devices/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mclimate.eu/mclimate-lorawan-devices/devices/mclimate-ht-+-pir-lite/decoding-and-bacnet-object-mapping.md). # Decoding and BACnet object mapping This section contains 3 sub-sections: * Uplink Decoder * Downlink Encoder * BACnet definition The first two are used to decode/encode the raw HEX data coming from the device, once it is decrypted by the LNS. The provided decoder are capable of decoding data in the most common LNS providers/platforms -> The Things Industries/Network (Multitech Built-in LNS), ChirpStack, Milesight Built-in LNS, DataCake Using the decoders/encoders you should be able to interred the HEX payload into human readable parameters and their values, specific to the particular device. The BACnet definition sub-section provides JSON format data to be use for mapping of BACnet objects, when utilizing the built-in LNS of the most popular Gateways in the BMS space, namely Multitech and Milesight. There is a third possibility, which is Wattsense, however due to the nature of their solution, one does not need a BACnet mapping file, rather this functionality is done via their GUI (in a browser) without the need of any code. --- # 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://docs.mclimate.eu/mclimate-lorawan-devices/devices/mclimate-ht-+-pir-lite/decoding-and-bacnet-object-mapping.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.