{"id":18790,"date":"2026-05-22T15:57:18","date_gmt":"2026-05-22T07:57:18","guid":{"rendered":"https:\/\/www.lansitec.com\/?p=18790"},"modified":"2026-05-22T15:57:20","modified_gmt":"2026-05-22T07:57:20","slug":"lorawan-duty-cycle","status":"publish","type":"post","link":"https:\/\/www.lansitec.com\/fr\/blogs\/lorawan-duty-cycle\/","title":{"rendered":"Cycle de service LoRaWAN\u00a0: la limite silencieuse qui d\u00e9termine l\u2019\u00e9volutivit\u00e9 de votre r\u00e9seau de suivi IoT"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">What is LoRaWAN Duty Cycle?<\/h2>\n\n\n\n<p><a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> is beautifully frugal. That\u2019s why we use it for long-range tracking, warehouse visibility, vehicle yards, worker safety, cold-chain monitoring, and all those awkward places where Wi-Fi cabling would be a project in itself.<\/p>\n\n\n\n<p><a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> usually operates in shared, unlicensed ISM spectrum. In Europe, that means the EU863-870 MHz band. Because many devices share the same air, regulators and network operators limit how long each device may transmit. That limit is called the duty cycle.<\/p>\n\n\n\n<p>In simple terms, duty cycle is the percentage of time a radio is allowed to occupy a channel or frequency band. If the limit is 1%, a device can transmit for 1 second, then it must stay silent long enough to keep its total transmit time within that 1% window. The Things Network explains the same principle as \u201cthe fraction of time a resource is busy.\u201d <sup><a href=\"#references\">(1)<\/a><\/sup><\/p>\n\n\n\n<p>For asset tracking, that matters a lot.<\/p>\n\n\n\n<p>A temperature sensor sending one small reading every 15 minutes is easy. A gateway forwarding hundreds of Bluetooth beacon messages? Different story. A worker badge reporting location every few seconds from a busy industrial site? Now we need to plan.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why Duty Cycle Matters in Lansitec Tracking Projects<\/h2>\n\n\n\n<p>We\u2019ve seen this in real deployments: the problem is rarely one tracker. It\u2019s the fleet.<\/p>\n\n\n\n<p>One Badge Tracker reporting every minute is harmless. Five hundred badges, a few <a href=\"https:\/\/www.lansitec.com\/gateways\/\">Bluetooth gateways<\/a>, confirmed uplinks, poor spreading factor selection, and oversized payloads? That can become noisy fast.<\/p>\n\n\n\n<p>Duty cycle affects three things that customers actually feel:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>What it affects<\/strong><\/th><th><strong>What happens in practice<\/strong><\/th><\/tr><\/thead><tbody><tr><td><strong>Latency<\/strong><\/td><td>A message may wait before it can be legally transmitted.<\/td><\/tr><tr><td><strong>Battery life<\/strong><\/td><td>Longer airtime keeps the radio active longer.<\/td><\/tr><tr><td><strong>Network capacity<\/strong><\/td><td>Excess uplinks and downlinks reduce room for other devices.<\/td><\/tr><tr><td><strong>Reliability<\/strong><\/td><td>Congestion increases missed packets and retry pressure.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>This is why a \u201c5-second report interval\u201d should not be read as \u201cuse 5 seconds everywhere.\u201d Many Lansitec <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> devices allow very short configurable report intervals, for example, adjustable position report intervals based on 5 s x n and heartbeat intervals based on 30 s x n, but the right value depends on the use case, region, spreading factor, payload size, gateway density, and network policy.<\/p>\n\n\n\n<p>That sounds like a lot. It is. But the design logic is simple: send what matters, only when it matters.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How LoRaWAN Duty Cycle Works Across Channels and Sub-Bands<\/h2>\n\n\n\n<p>This is the part many people miss.<\/p>\n\n\n\n<p>Duty cycle can apply at different levels: device, channel, and sub-band. Actility\u2019s article makes this distinction clearly, and it is worth keeping because it explains why a device may be able to transmit on one channel but not another. <sup><a href=\"#references\">(2)<\/a><\/sup><\/p>\n\n\n\n<p>In the European EU863-870 MHz band, The Things Network lists ETSI sub-band limits such as 0.1%, 1%, and 10%, depending on the exact frequency range. For example, 865-868 MHz and 868-868.6 MHz are listed at 1%, while 869.4-869.65 MHz is listed at 10%. <sup><a href=\"#references\">(3)<\/a><\/sup><\/p>\n\n\n\n<p>So, when someone asks, \u201cCan we send every 10 seconds?\u201d, the honest answer is: maybe.<\/p>\n\n\n\n<p>Which band? Which data rate? How many bytes? Which spreading factor? How many devices? Public network or private network?<\/p>\n\n\n\n<p>You need all those answers to engineer the correct solution.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Airtime: The Real Currency of LoRaWAN<\/h2>\n\n\n\n<p>Duty cycle is the rule. Airtime is what you spend.<\/p>\n\n\n\n<p>Every uplink occupies the air for a certain time. That time depends mainly on payload size, bandwidth, coding rate, and spreading factor. Higher spreading factors increase range and receiver sensitivity, but they also increase time-on-air. The Things Network notes that a fixed payload sent with a higher spreading factor needs a longer time-on-air, and higher spreading factors also shorten battery life because the radio stays active longer. <sup><a href=\"#references\">(4)<\/a><\/sup><\/p>\n\n\n\n<p>Here\u2019s the practical version:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Design choice<\/th><th>Airtime impact<\/th><th>Tracking impact<\/th><\/tr><\/thead><tbody><tr><td>Smaller payload<\/td><td>Lower<\/td><td>Better for dense beacon forwarding<\/td><\/tr><tr><td>Lower spreading factor, such as SF7<\/td><td>Lower<\/td><td>Better for capacity and battery<\/td><\/tr><tr><td>Higher spreading factor, such as SF12<\/td><td>Higher<\/td><td>Better range, worse capacity<\/td><\/tr><tr><td>Confirmed uplinks<\/td><td>Higher network burden<\/td><td>Use only when truly needed<\/td><\/tr><tr><td>Frequent downlinks<\/td><td>Higher gateway duty-cycle pressure<\/td><td>Avoid routine downlink control<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>This is why payload filtering matters. Several Lansitec <a href=\"https:\/\/www.lansitec.com\/gateways\/\">Bluetooth gateways<\/a> can filter Bluetooth payload bytes and report only the useful data through <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a>. The Solar, Macro, Micro, and <a href=\"https:\/\/www.lansitec.com\/products\/compact-bluetooth-gateway\/\">Compact Bluetooth Gateways<\/a> also support Bluetooth data compression and can pack up to 15 beacon messages into a single <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> package at SF9, with a maximum of 105 beacon messages supported, as noted in the product catalog.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why Small LoRaWAN Messages Still Consume Network Capacity<\/h3>\n\n\n\n<p>Let\u2019s say a gateway forwards BLE beacon IDs, <a href=\"https:\/\/www.lansitec.com\/blogs\/rssi-indoor-positioning\/\">RSSI<\/a> values, and a small sensor field. One message is small. No drama.<\/p>\n\n\n\n<p>Now put that in a parking lot, a hospital, a warehouse, or a construction site.<\/p>\n\n\n\n<p>A B-Mobile setup may include <a href=\"https:\/\/www.lansitec.com\/bluetooth-beacons\/\">Bluetooth beacons<\/a> on assets or people, <a href=\"https:\/\/www.lansitec.com\/gateways\/\">Bluetooth gateways<\/a> fixed at known locations, and a <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> gateway that forwards data to the network server and application.<\/p>\n\n\n\n<p>Lansitec\u2019s LoRa solution describes this flow clearly: <a href=\"https:\/\/www.lansitec.com\/bluetooth-beacons\/\">beacons<\/a> periodically advertise data, <a href=\"https:\/\/www.lansitec.com\/gateways\/\">Bluetooth gateways<\/a> receive and reformat it, then forward it via <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> to the network server and app.<\/p>\n\n\n\n<p>At low density, you can report often. At high density, the design should become smarter:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use gateway-side filtering.<\/li>\n\n\n\n<li>Batch beacon messages.<\/li>\n\n\n\n<li>Report change events instead of repeating stable states.<\/li>\n\n\n\n<li>Let static assets be quiet.<\/li>\n<\/ul>\n\n\n\n<p>Short and boring? Good. Boring networks scale.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">EU868 Example: 1% Sounds Generous, Until You Calculate It<\/h3>\n\n\n\n<p>A 1% duty cycle gives 864 seconds of airtime per day. A 0.1% duty cycle gives only 86 seconds per day. A 10% duty cycle gives 8,640 seconds per day. These are daily airtime budgets, not message counts. <sup><a href=\"#references\">(3)<\/a><\/sup><\/p>\n\n\n\n<p>That distinction matters.<\/p>\n\n\n\n<p>A device sending short SF7 packets may fit comfortably. The same device at SF12, with larger payloads and retries, may burn through airtime much faster. Public networks may be stricter too. The Things Network\u2019s Sandbox Fair Use Policy limits uplink airtime to 30 seconds per day per node and downlink messages to 10 per day per node, while private networks must still comply with regulatory and <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> limits. <sup><a href=\"#references\">(1)<\/a><\/sup><\/p>\n\n\n\n<p>For Lansitec customers using private <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> infrastructure, this is good news and bad news.<\/p>\n\n\n\n<p>Good: You can design around your own application requirements.<\/p>\n\n\n\n<p>Bad: You own the capacity planning.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How Lansitec Deployments Should Think About Report Intervals<\/h2>\n\n\n\n<p>The easiest mistake is to start with the fastest possible interval. Can the tracker report every 5 seconds?<\/p>\n\n\n\n<p>Technically, some devices support that minimum interval. Operationally, you probably don\u2019t want that for every device, all day.<\/p>\n\n\n\n<p>A better question is: what decision will this message trigger?<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Use case<\/th><th>Sensible reporting logic<\/th><\/tr><\/thead><tbody><tr><td>Emergency SOS<\/td><td>Immediate uplink, high priority<\/td><\/tr><tr><td>Worker safety zone breach<\/td><td>Event-driven uplink plus short burst updates<\/td><\/tr><tr><td>Vehicle yard tracking<\/td><td>More frequent while moving, slower when parked<\/td><\/tr><tr><td>Warehouse asset tracking<\/td><td>Presence and location changes, not constant chatter<\/td><\/tr><tr><td>Temperature monitoring<\/td><td>Periodic reporting unless the threshold is crossed<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Lansitec\u2019s B-Fixed solution provides a useful real-world benchmark: a Badge Tracker reporting every minute at SF7 is described as supporting a single gateway accessing 500 devices, with a note to use a network capacity evaluation tool for accurate estimation. It also lists a 5-second minimum location-report interval, but that should be treated as a configuration option rather than a default for large fleets.<\/p>\n\n\n\n<p>We like fast data when it helps. We don\u2019t like fast data when it only proves the device is still where it was 10 seconds ago.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">ADR Helps, But Only When The Device Behaviour Fits<\/h2>\n\n\n\n<p>Adaptive Data Rate, or ADR, helps optimize data rate, airtime, and power consumption. It can adjust the spreading factor, bandwidth, and transmit power. The Things Network recommends ADR when RF conditions are stable, generally for static devices, while mobile devices should use ADR only when they can detect that they are stationary for longer periods. <sup><a href=\"#references\">(5)<\/a><\/sup><\/p>\n\n\n\n<p>That maps neatly to tracking.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A fixed indoor gateway? ADR can be useful.<\/li>\n\n\n\n<li>A tracker moving between a warehouse, yard, and truck? Be careful.<\/li>\n\n\n\n<li>A vehicle tracker parked overnight, then moves during the day? A hybrid strategy makes more sense.<\/li>\n<\/ul>\n\n\n\n<p>For tracking systems, the device may move through very different RF conditions. Behind metal racks. Near forklifts. Inside a container. Outdoors. Under a roof. That instability can make ADR less predictable unless the application logic understands motion states.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why Downlinks Can Break LoRaWAN Network Capacity<\/h2>\n\n\n\n<p>Uplinks get most of the attention, but downlinks can hurt a network faster.<\/p>\n\n\n\n<p>Why? Because a gateway transmitting a downlink is not listening at that moment. It also must respect regional duty-cycle limits. In dense tracking systems, too many confirmed uplinks or routine downlink commands can create self-inflicted congestion.<\/p>\n\n\n\n<p>Use downlinks for things that matter:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Configuration changes<\/li>\n\n\n\n<li>Alarm acknowledgment when required<\/li>\n\n\n\n<li>Firmware or operational control workflows<\/li>\n\n\n\n<li>Carefully planned maintenance windows<\/li>\n<\/ul>\n\n\n\n<p>Avoid using downlinks as a polling habit. <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> is not a chatty protocol. It rewards restraint.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Practical Design Rules for Lansitec LoRaWAN Tracking<\/h2>\n\n\n\n<p>Here is the field version we\u2019d use in a project review.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Rule<\/strong><\/th><th><strong>Why it matters<\/strong><\/th><\/tr><\/thead><tbody><tr><td><strong>Start with the business event<\/strong><\/td><td>\u201cMoved,\u201d \u201centered zone,\u201d \u201cSOS,\u201d and \u201ctemperature exceeded threshold\u201d are better triggers than blind repetition.<\/td><\/tr><tr><td><strong>Keep payloads lean<\/strong><\/td><td>IDs, <a href=\"https:\/\/www.lansitec.com\/blogs\/rssi-indoor-positioning\/\">RSSI<\/a>, battery, and the one sensor value you need will scale better than verbose payloads.<\/td><\/tr><tr><td><strong>Use SF7 where coverage allows<\/strong><\/td><td>Lower spreading factors reduce airtime and improve battery life.<\/td><\/tr><tr><td><strong>Batch BLE data at <a href=\"https:\/\/www.lansitec.com\/gateways\/\">gateways<\/a><\/strong><\/td><td><a href=\"https:\/\/www.lansitec.com\/gateways\/\">Lansitec gateways<\/a> can package multiple beacon messages, which helps reduce the uplink count.<\/td><\/tr><tr><td><strong>Limit confirmed uplinks<\/strong><\/td><td>Confirmation creates downlink pressure and should not be the default for routine tracking.<\/td><\/tr><tr><td><strong>Model busy hours, not averages<\/strong><\/td><td>Shift changes, truck loading, emergency drills, and event entrances create traffic spikes.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>In our experience, the \u201cbusy hour\u201d is where designs reveal themselves. A site may look fine at 2 PM, then collapse at 7 AM when 400 badges wake up, 30 forklifts move, and <a href=\"https:\/\/www.lansitec.com\/gateways\/\">gateways<\/a> start forwarding fresh beacon observations.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How this applies to B-Mobile and B-Fixed<\/h2>\n\n\n\n<p>In <strong><a href=\"https:\/\/www.lansitec.com\/solutions\/bluetooth-beacon-mobile-tracking-solution\/\" data-type=\"page\" data-id=\"9372\">B-Mobile<\/a><\/strong>, <a href=\"https:\/\/www.lansitec.com\/bluetooth-beacons\/\">beacons<\/a> are mobile, and <a href=\"https:\/\/www.lansitec.com\/gateways\/\">Bluetooth gateways<\/a> are fixed. The gateway hears nearby BLE advertisements, restructures the data, and forwards it through <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a>. This is efficient when <a href=\"https:\/\/www.lansitec.com\/gateways\/\">gateways<\/a> filter and batch intelligently. It is also where payload compression and reporting-interval tuning do the real work.<\/p>\n\n\n\n<p>In <strong><a href=\"https:\/\/www.lansitec.com\/solutions\/bluetooth-beacon-fixed-tracking-solution\/\" data-type=\"page\" data-id=\"9516\">B-Fixed<\/a><\/strong>, the <a href=\"https:\/\/www.lansitec.com\/bluetooth-beacons\/\">beacons<\/a> are fixed, and the tracker reports what it hears. That can be excellent for worker tracking and indoor-outdoor movement, but the tracker\u2019s reporting strategy becomes critical. Lansitec\u2019s B-Fixed documentation notes a three-second <a href=\"https:\/\/www.lansitec.com\/blogs\/the-essential-guide-to-bluetooth-scan-vs-bluetooth-receiving-unlocking-bluetooth-tracking-and-iot-beacon-performance\/\">Bluetooth receiving<\/a> window and recommends beacon advertisement intervals such as 800 ms, 500 ms, or less, while also warning that shorter intervals improve positioning but consume more beacon power.<\/p>\n\n\n\n<p>Different architecture but the same principle, without flooding the air.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A Sensible Starting Configuration<\/h2>\n\n\n\n<p>Every site needs its own survey, but this is a practical starting point for many Lansitec tracking projects:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Parameter<\/strong><\/th><th><strong>Conservative starting point<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Routine asset heartbeat<\/td><td>5-30 minutes<\/td><\/tr><tr><td>Moving asset update<\/td><td>30-120 seconds<\/td><\/tr><tr><td>Worker badge routine update<\/td><td>60 seconds, then tune<\/td><\/tr><tr><td>SOS or safety alarm<\/td><td>Immediate event uplink<\/td><\/tr><tr><td>BLE beacon advertising<\/td><td>500-800 ms for personnel, slower for static assets<\/td><\/tr><tr><td>Confirmed uplink<\/td><td>Off by default, on only for critical events<\/td><\/tr><tr><td>Payload strategy<\/td><td>Filter, batch, compress<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Then test.<\/p>\n\n\n\n<p>Not in a lab with three devices. Test with real density, real walls, real metal, real movement, and the actual network server. A parking lot full of cars is not the same as an empty parking lot. A hospital corridor at night is not a hospital corridor during shift change.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common LoRaWAN Duty Cycle Mistakes to Avoid<\/h2>\n\n\n\n<p>The most common duty-cycle problems are not exotic. They\u2019re boring, which is why they slip through.<\/p>\n\n\n\n<p>First, teams overspecify reporting frequency because \u201creal time\u201d sounds good in a sales meeting. Then they discover that the business process only needs location every minute, except during alarms.<\/p>\n\n\n\n<p>Second, teams forget payload size. A few unnecessary bytes may not matter once. Across thousands of packets per day, they matter.<\/p>\n\n\n\n<p>Third, teams use confirmed uplinks too casually. Confirmation feels safe, but it increases downlink demand. In a dense <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> deployment, that safety can become a bottleneck.<\/p>\n\n\n\n<p>Finally, teams treat gateway count as the only scaling lever. More <a href=\"https:\/\/www.lansitec.com\/gateways\/\">gateways<\/a> improve coverage and link quality, but they do not override duty-cycle rules. Airtime is still airtime.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p><a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> duty cycle is not an annoying technical footnote. It is one of the reasons <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> works so well when properly designed.<\/p>\n\n\n\n<p>For Lansitec tracking deployments, the goal is not to transmit as often as possible. The goal is to transmit <strong>useful, compact, timely information<\/strong> while keeping the network quiet enough to scale.<\/p>\n\n\n\n<p>That is where <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> shines.<\/p>\n\n\n\n<p>A Badge Tracker does not need to shout every few seconds if nothing has changed. A <a href=\"https:\/\/www.lansitec.com\/blogs\/what-is-a-bluetooth-gateway-how-it-works\/\">Bluetooth gateway<\/a> does not need to forward every byte it hears. A private network does not need to behave like a public sandbox, but it still needs discipline.<\/p>\n\n\n\n<p>The best tracking network is the one that tells you what changed, when it matters, and leaves the air free for the next important message.<\/p>\n\n\n<div\n\tclass=\"betterdocs-faq-wrapper layout-modern icon-after betterdocs-faq-layout-1 betterdocs-faq-93gz47i betterdocs-shortcode\">\n\t<h2 class=\"betterdocs-faq-layout-1 betterdocs-faq-93gz47i betterdocs-faq-section-title\">Frequently Asked Questions<\/h2>\n\t<div class=\"betterdocs-faq-inner-wrapper\">\n\t\t<div class=\"betterdocs-faq-title\">\n\t<h3 class=\"betterdocs-faq-title-tag\">About LoRaWAN Duty Cycle<\/h3><\/div>\n<ul class=\"betterdocs-faq-list\"><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tIs the duty cycle the same across all <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> regions?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\" >\n\t<p><span style=\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\">No. <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> uses regional parameters, and these vary by region. The LoRa Alliance\u2019s RP002-1.0.5 Regional Parameters document, published on October 8, 2025, describes regional differences worldwide. (6)<\/span><\/p>\n<\/div>\n<\/div><\/li><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tDoes a private <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> network remove duty-cycle limits?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\" >\n\t<p><span style=\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\">No. A private network gives you more control over architecture and policies, but radio regulations still apply. Public network fair-use policies may not apply, but government and <a href=\"https:\/\/www.lansitec.com\/lorawan\/\">LoRaWAN<\/a> limits still do. (1)<\/span><\/p>\n<\/div>\n<\/div><\/li><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tShould Lansitec <a href=\"https:\/\/www.lansitec.com\/trackers\/\">trackers<\/a> use confirmed uplinks?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\" >\n\t<p><span style=\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\">Use confirmed uplinks only when the application truly needs acknowledgment, such as critical alarms or configuration workflows. For routine position or heartbeat messages, unconfirmed uplinks usually scale better.<\/span><\/p>\n<\/div>\n<\/div><\/li><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tDoes a smaller payload really improve capacity?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\" >\n\t<p><span style=\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\">Yes. Airtime depends partly on payload size and data rate. Smaller payloads reduce time-on-air, especially when combined with lower spreading factors. This is why Lansitec gateway-side filtering and Bluetooth data compression are useful in dense deployments.<\/span><\/p>\n<\/div>\n<\/div><\/li><li><div class=\"betterdocs-faq-group\"><div class=\"betterdocs-faq-post\">\n\t\t<p class=\"betterdocs-faq-post-name\">\n\t\tWhat is the safest way to scale to hundreds of devices?\t<\/p>\n\t<svg class=\"betterdocs-faq-iconminus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"stroke-width=\"2\"><g fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"round\" stroke-miterlimit=\"10\" stroke-linejoin=\"round\"><path d=\"M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><svg class=\"betterdocs-faq-iconplus\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 24 24\"><g stroke-width=\"2\" fill=\"none\" stroke=\"#528ffe\" stroke-linecap=\"square\" stroke-miterlimit=\"10\"><path d=\"M12 7v10M17 12H7\"><\/path><circle cx=\"12\" cy=\"12\" r=\"11\"><\/circle><\/g><\/svg><\/div>\n<div class=\"betterdocs-faq-main-content\" >\n\t<p><span style=\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\">Start with event-driven reporting, use sensible heartbeat intervals, avoid unnecessary confirmed uplinks, keep payloads compact, and test during the busiest expected traffic period. For B-Fixed, Lansitec\u2019s documentation provides an example of 500 devices per gateway when Badge <a href=\"https:\/\/www.lansitec.com\/trackers\/\">Trackers<\/a> report every minute at SF7, but the actual capacity should always be estimated for the site.<\/span><\/p>\n<\/div>\n<\/div><\/li><\/ul><script type=\"application\/ld+json\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"Is the duty cycle the same across all LoRaWAN regions?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\\\">No. LoRaWAN uses regional parameters, and these vary by region. The LoRa Alliance\\u2019s RP002-1.0.5 Regional Parameters document, published on October 8, 2025, describes regional differences worldwide. (6)<\\\/span><\\\/p>\\n\"}},{\"@type\":\"Question\",\"name\":\"Does a private LoRaWAN network remove duty-cycle limits?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\\\">No. A private network gives you more control over architecture and policies, but radio regulations still apply. Public network fair-use policies may not apply, but government and LoRaWAN limits still do. (1)<\\\/span><\\\/p>\\n\"}},{\"@type\":\"Question\",\"name\":\"Should Lansitec trackers use confirmed uplinks?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\\\">Use confirmed uplinks only when the application truly needs acknowledgment, such as critical alarms or configuration workflows. For routine position or heartbeat messages, unconfirmed uplinks usually scale better.<\\\/span><\\\/p>\\n\"}},{\"@type\":\"Question\",\"name\":\"Does a smaller payload really improve capacity?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\\\">Yes. Airtime depends partly on payload size and data rate. Smaller payloads reduce time-on-air, especially when combined with lower spreading factors. This is why Lansitec gateway-side filtering and Bluetooth data compression are useful in dense deployments.<\\\/span><\\\/p>\\n\"}},{\"@type\":\"Question\",\"name\":\"What is the safest way to scale to hundreds of devices?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"<p><span style=\\\"color: rgb(0,0,0);background-color: transparent;font-size: 11pt;font-family: Calibri, sans-serif;\\\">Start with event-driven reporting, use sensible heartbeat intervals, avoid unnecessary confirmed uplinks, keep payloads compact, and test during the busiest expected traffic period. For B-Fixed, Lansitec\\u2019s documentation provides an example of 500 devices per gateway when Badge Trackers report every minute at SF7, but the actual capacity should always be estimated for the site.<\\\/span><\\\/p>\\n\"}}]}<\/script>\t<\/div>\n<\/div>\n\n\n\n<p id=\"references\"><\/p>\n\n\n\n<p data-wp-context---core-fit-text=\"core\/fit-text::{&quot;fontSize&quot;:&quot;&quot;}\" data-wp-init---core-fit-text=\"core\/fit-text::callbacks.init\" data-wp-interactive data-wp-style--font-size=\"core\/fit-text::context.fontSize\" class=\"has-fit-text\">Resources and Further Reading:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.thethingsnetwork.org\/docs\/lorawan\/duty-cycle\/\" target=\"_blank\" rel=\"noopener\">TTN docs: Duty cycle<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.actility.com\/understanding-duty-cycle-lorawan\/\" target=\"_blank\" rel=\"noopener\">Actility: Understanding Duty Cycle in LoRaWAN<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.thethingsnetwork.org\/docs\/lorawan\/regional-parameters\/eu868\/\" target=\"_blank\" rel=\"noopener\">TTN docs: Regional parameters<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.thethingsnetwork.org\/docs\/lorawan\/spreading-factors\/\" target=\"_blank\" rel=\"noopener\">TTN docs: Spreading factor<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.thethingsnetwork.org\/docs\/lorawan\/adaptive-data-rate\/\" target=\"_blank\" rel=\"noopener\">TTN docs: ADR<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/resources.lora-alliance.org\/technical-specifications\/rp002-1-0-5-lorawan-regional-parameters\" target=\"_blank\" rel=\"noopener\">RP002-1.0.5 LoRaWAN Regional Parameters<\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>What is LoRaWAN Duty Cycle? LoRaWAN is beautifully frugal. That\u2019s why we use it for long-range tracking, warehouse visibility, vehicle yards, worker safety, cold-chain monitoring, and all those awkward places where Wi-Fi cabling would be a project in itself. LoRaWAN usually operates in shared, unlicensed ISM spectrum. In Europe, that means the EU863-870 MHz band.&hellip;&nbsp;<a href=\"https:\/\/www.lansitec.com\/fr\/blogs\/lorawan-duty-cycle\/\" rel=\"bookmark\">Lire la suite \u00bb<span class=\"screen-reader-text\">Cycle de service LoRaWAN\u00a0: la limite silencieuse qui d\u00e9termine l\u2019\u00e9volutivit\u00e9 de votre r\u00e9seau de suivi IoT<\/span><\/a><\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","footnotes":""},"categories":[50],"tags":[15,16],"class_list":["post-18790","post","type-post","status-publish","format-standard","hentry","category-lorawan","tag-lorawan","tag-technology"],"_links":{"self":[{"href":"https:\/\/www.lansitec.com\/fr\/wp-json\/wp\/v2\/posts\/18790","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.lansitec.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.lansitec.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.lansitec.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.lansitec.com\/fr\/wp-json\/wp\/v2\/comments?post=18790"}],"version-history":[{"count":7,"href":"https:\/\/www.lansitec.com\/fr\/wp-json\/wp\/v2\/posts\/18790\/revisions"}],"predecessor-version":[{"id":18797,"href":"https:\/\/www.lansitec.com\/fr\/wp-json\/wp\/v2\/posts\/18790\/revisions\/18797"}],"wp:attachment":[{"href":"https:\/\/www.lansitec.com\/fr\/wp-json\/wp\/v2\/media?parent=18790"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.lansitec.com\/fr\/wp-json\/wp\/v2\/categories?post=18790"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.lansitec.com\/fr\/wp-json\/wp\/v2\/tags?post=18790"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}