> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/connectors/lns-connector/lora-2g4.md). # LoRa 2.4 GHz LoRa 2.4 GHz in Kilo IoT — global license-free deployment, higher throughput, and more channels than sub-GHz LoRa. LoRa is a radio technology for transmitting small messages from low-power devices. **LoRa 2.4 GHz** uses the 2.4 GHz radio band, rather than the sub-GHz bands used in many LoRaWAN deployments. It is a radio option, not a separate IoT Server or software connector. Use this guide to understand where that option fits before selecting equipment. Devices and gateways must support the same radio configuration; a sub-GHz gateway cannot receive 2.4 GHz transmissions. Check equipment compatibility and local radio requirements before planning a deployment, and see the [LNS connector](/connectors/lns-connector.md) for the platform connection. ## Why 2.4 GHz Matters for Deployments ### Global, License-Free Operation The 2.4 GHz ISM band is available worldwide without region-specific regulatory approvals. A single device hardware design can be manufactured and deployed across multiple countries without modifying the radio configuration or going through additional certifications. This significantly simplifies procurement, logistics, and inventory management for organizations operating across borders. ### Higher Data Throughput Compared to sub-GHz LoRa, the 2.4 GHz band supports higher data rates. This makes it well-suited for applications where devices need to transmit larger payloads or communicate more frequently — without compromising battery life. ### Expanded Channel Availability Operating at 2.4 GHz provides more frequency channels than traditional sub-GHz ISM bands. This reduces congestion in crowded radio environments and gives network designers greater flexibility when scaling device density within a site. ### Coexistence with Other Wireless Technologies The 2.4 GHz spectrum is shared with Wi-Fi, Bluetooth, and Zigbee. LoRa 2.4 GHz is engineered to coexist with these technologies, making it practical for environments like industrial facilities, smart buildings, or commercial campuses where multiple wireless systems operate in parallel. ### Adequate Range for Most IoT Use Cases While higher frequencies generally reduce transmission range, LoRa at 2.4 GHz can still achieve several kilometers of line-of-sight coverage — up to 8–10 km under optimal conditions. Indoor performance remains effective, making it suitable for building-level and campus-level deployments. ### Cost-Effective and Battery-Friendly Modules for 2.4 GHz LoRa are similarly priced to their 868 MHz and 915 MHz counterparts, and remain well-suited for low-power, battery-operated devices. ## When to Use LoRa 2.4 GHz LoRa 2.4 GHz is a strong choice for: * **Global or cross-border deployments** — international asset tracking, logistics, or supply chain monitoring where devices move between regulatory regions * **High-data IoT applications** — scenarios requiring increased bandwidth and channel density beyond what sub-GHz bands provide * **Dense wireless environments** — factories, commercial buildings, and campuses where Wi-Fi, Bluetooth, and other 2.4 GHz systems are already operating * **Larger payload transmissions** — low-power image or audio data where slightly higher throughput is required while staying energy-efficient When registering a device on the Kilo IoT Server, select **ISM2400** in the Band field to configure a device for the 2.4 GHz band. For sub-GHz regional frequency bands, see [LoRaWAN Frequencies](/connectors/lns-connector/lorawan-frequencies.md). For an overview of the LoRaWAN protocol, see [What is LoRaWAN?](/connectors/lns-connector/what-is-lorawan.md). --- # 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.kiloiot.io/connectors/lns-connector/lora-2g4.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.