> 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/integrations/milesight.md). # Milesight ## **Connecting Milesight to MClimate’s LoRaWAN broker** ### **1.** Go to and create your m-token.

Copy the token.

### **2. Go to Network Server-> Applications->{your\_application}->Add new Data transmission with type HTTP**

### **3. Add headers and URL** {% hint style="warning" %} Depending on your device firmware the fields values in this section are different, make sure you follow the instructions that match your firmware version. You can see it in the Status page. {% endhint %}

#### Firmware version ≤ 60.0.0.42-r4 / 56.0.0.3-r1 * **Type - HTTP** * **m-token:** your token from Enterprise *(Step 1)* * **username:** apiuser *(this is not an example it is static for all gateways)* * **password:** password *(this is not an example it is static for all gateways)* * **url:** the public IP address of the gateway ***(ex: 212.39.89.221)*** {% hint style="warning" %} Make sure that the IP is exposed and accessible from outside of your LAN. We need it for sending downlinks, if you are behind a NAT check your router for the public IP (the local one would not work). {% endhint %} A correctly filled out example is shown in the image below.

#### Firmware version ≥ 60.0.0.42-r5 / 56.0.0.4 With these newer Firmware devices you would need an AES-128 bit encrypted password. Using the link below you can easily generate one: {% embed url="" %} AES encryption tool {% endembed %} Fill in the parameters from the table below: | Parameter | Value | | ------------------- | ------------------------------------------------------------------- | | Encryption text | THE LOGIN PASSWORD FOR THE GATEWAY | | Secret Key | 1111111111111111 (static value) | | Encryption Key Size | 128 Bits | | Encryption Mode | CBC | | IV (optional) | 2222222222222222 (static value) | | Output format | Base64 | A correctly filled out form would look as the one in the image below. Press the Encrypt button and you will be given a string to copy from the Encrypted Text field.

AES-128 bit encrypted password in Base64 form

* **Type - HTTP** * **m-token:** your token from Enterprise *(Step 1)* * **username:** your gateway login username * **password:** your gateway login password that we encrypted in the previous step * **url:** the public IP address of the gateway ***(ex: 212.39.89.221)*** {% hint style="warning" %} Make sure that the IP is exposed and accessible from outside of your LAN. We need it for sending downlinks, if you are behind a NAT check your router for the public IP (the local one would not work). {% endhint %} A correctly filled out example is shown in the image below.

### **4.** Add URL The uplink data URL should be:

### **5.** Done --- # 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/integrations/milesight.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.