A gateway points at one network server, which is why migrations are risky and why joining a community network usually means giving something up. This open source multiplexer removes the constraint: one gateway feeding several servers at once, converting between Semtech UDP, Basics Station and MQTT, with filtering by gateway, device address or JoinEUI.
Running gateways without visibility into what's actually happening on the air is flying blind. This open-source traffic analyzer connects to your LoRaWAN MQTT broker, captures every packet your gateways see, and serves a web dashboard showing operators, devices, spectrum usage, and live traffic, yours and everyone else's.
Every vendor quotes you a per-sensor price. None mention that a managed platform's per-device fees can cost €36,000 over five years for a single deployment, before hardware. Here's where IoT budgets actually go, and why the platform decision makes or breaks ROI over five years.
Every managed LoRaWAN platform charges per device, per month, forever. ChirpStack gives you a production-grade network server you own outright, with no per-device fees, no vendor lock-in, and no data leaving your infrastructure. Running your own LNS is the difference between renting your IoT network and owning it, and it's usually far cheaper too.
The gateway is online, nearby sensors report fine, and the far half of the fleet went quiet. Nothing is broken: the noise floor came up. How out-of-band transmitters and your own power supplies steal range, how to prove it before buying hardware, and what cavity and SAW filters really cost in measured decibels.
The old advice was simple: sensor data is time-series, so use InfluxDB, because Postgres handles it badly. Both halves of that have since changed. TimescaleDB turned Postgres into a real time-series engine, InfluxDB rewrote itself twice and broke its query language both times, and a ten thousand device fleet turns out to generate about eleven rows per second anyway.
Platforms get sold, repriced, or shut down, and one day the network your sensors depend on is somebody else's business decision. Moving a live fleet is not a database export: it is a key custody audit and a re-join campaign. Here is how to do it with both networks running side by side and nothing going dark.
A device that transmits perfectly and never joins is one of three failures, and they have nothing in common. Here is how to tell them apart in a single look at the gateway traffic, and the specific causes behind each: byte order, DevNonce replay, sub-band mismatch, RX2 mismatch, and downlinks that arrive too late.
Every datasheet says thousands of devices per gateway. The honest answer ranges from a few hundred to tens of thousands, and the variable that decides it is not the gateway at all. Here is the arithmetic, the collision limit nobody mentions, and why downlink runs out long before uplink does.
A gateway is the cheapest part of the RF chain to get right, and the antenna system is where deployments quietly lose most of their range. Twenty metres of the wrong coax costs 11 dB. Here is what each decision is worth in decibels, and why most dead gateways died through the Ethernet cable.
A LoRaWAN gateway is a radio bridge, and the link from that bridge to the network server is not part of the LoRaWAN specification at all. Three protocols dominate: Semtech UDP, Basics Station, and MQTT. They differ in security, reliability, and what breaks when the link goes bad.
Hundreds of LoRaWAN sensors exist, and many work flawlessly on the bench then fail in the field. The datasheet won't tell you which. Here are the criteria that actually decide a deployment, from firmware quality and battery chemistry to build materials, lead times and vendor support, and how to validate a device before you order five hundred of the wrong one.
Your 10-sensor pilot works perfectly. Six months later, the 500-device rollout is stalled. Different problems, different budget, different politics. 70% of enterprise IoT projects never escape pilot purgatory. Here's what actually goes wrong and how to architect for scale from day one.
Ship a EU868 sensor to a US site and it won't just underperform. It's illegal to transmit, and it won't talk to your gateway. Region is the first decision in any LoRaWAN deployment and the easiest to get expensively wrong. A global tour of the frequency plans, power limits, and airtime rules that decide where your hardware is allowed to work.
Your sensors reported fine in the pilot. At 500 devices, packets vanish. You haven't hit a range limit. You've hit an airtime limit. Duty cycle, dwell time, and fair-use policies cap how much each device can talk, and the math catches most deployments by surprise. Here's how to budget airtime before it throttles you.
Your IT security team has one question before the rollout gets approved: where do the encryption keys live? LoRaWAN encrypts every payload by default with AES-128, but 'encrypted' and 'secure' aren't the same thing. Here's what the spec actually guarantees, where real deployments go wrong, and the architecture that earns sign-off.
Clients shrug at 240 grams until they carry a 5 kg gateway up a 20 metre mast. Weight decides how high you can mount, and height decides coverage: 2 km at 3 m, 8-10 km at 20 m. What 1.2 W does to solar costs, why the gateway should go where the antenna goes, and where IP65 is not enough.
Clients hesitate at 600 EUR until you price a truck roll. Seven years of deployments later, those units are still running. What the premium actually buys: IP67 from -40 to +60°C, -140 dBm sensitivity, a sealed internal antenna that hands over to an external one automatically, and the cases where a 200 EUR gateway is the better answer.
Manufacturer specs claim 15km range. Your actual deployment gets 3km in one direction and 8km in another. Range testing before you commit gateway locations is the cheapest insurance in any IoT project: walk-testing procedures, what RSSI and SNR values actually mean, and why a gateway at 10 meters beats a high-gain antenna at ground level.
Units I installed in 2016 are still running without failures. The Multitech Conduit costs more than consumer gateways, but when you can't afford a site visit to replace failed hardware, that price difference pays for itself. IP68 rating, -40°C to +70°C operation, and why this remains the benchmark for industrial deployments.
That hillside has no internet and no power. With mesh, a solar relay there forwards packets through 8 hops to your one internet-connected gateway. No cellular SIM at every location. Flash ChirpStack Gateway OS on a SenseCAP M2 and the economics of remote coverage change completely.
Before installing permanent infrastructure, prove the coverage works. This 1W mesh relay fits in a backpack and runs for days on a USB battery. Hike to that hilltop, velcro-strap it to a tree, collect data for a week. Raspberry Pi Zero W build guide included.
Your utility bill shows total consumption, but not where the water actually goes. A leak runs for months before anyone notices. LoRaWAN sub-meters pinpoint consumption by zone and detect leaks within hours: pulse-counter versus ultrasonic options, installation without shutting off supply, and typical payback periods.
The technician checks at 9am and 5pm; the compressor fails at midnight. Continuous LoRaWAN monitoring catches equipment failures within minutes: detect problems before spoiled inventory, generate automatic audit trails for compliance.
I launched a solar-powered GPS tracker on a high-altitude balloon from France. It landed in Turkey 55 hours later, transmitting the entire way. Maximum range to a receiving hotspot: 511km. Total hardware cost: under €100.
InfluxDB is purpose-built for time-series data, so queries stay fast across millions of datapoints without asking you to think about partitioning. Setting up the data pipeline from ChirpStack to InfluxDB to Grafana, the tag and field decisions that determine query speed a year later, and retention policies that keep storage manageable.
A construction foreman spends half a morning calling other sites looking for a generator. GPS/GNSS trackers show where equipment actually is: theft alerts while recovery is possible, utilization data revealing which expensive machinery sits idle.
Most LoRaWAN projects stall at the same place: the data reaches the network server, and then someone spends three to six months writing middleware to get it into the cloud. Native integration removes that step. Device twins, Thing shadows, message routing and serverless processing, with the path from sensor to storage down to two hops.
Which tenant used what? Which EV charger drew how much? Is your solar actually producing what the salesman promised? CT clamp sensors install without shutting off power, so you finally know where the electricity actually goes.
Every other option rents you something: a SIM, a subscription, a carrier's coverage decisions. With LoRaWAN you buy the gateways, run the server and hold the keys, on free spectrum, with devices lasting five to ten years on one cell. Why the range holds up, why the encryption is not optional, and what owning the network is actually worth.
A rain gauge placed near a building undercounts by 30% because wind turbulence throws rain away from the funnel. A temperature sensor without a radiation shield reads 10-20°C too high in direct sunlight. Weather stations produce garbage data when installed wrong.
Most buildings run HVAC on timers, conditioning empty spaces. LoRaWAN occupancy sensors reveal when rooms are actually used, so you can cut energy waste, improve air quality, and catch leaks before they become expensive.
Most irrigation runs on fixed schedules: 4 hours every 3 days regardless of whether it rained yesterday. Soil moisture sensors change that, cutting water use by 30-50% by triggering irrigation only when the soil actually needs it. Sensor placement, valve control, and the logic that ties them together.
Sigfox allows 140 messages a day at twelve bytes each. NB-IoT works only where a carrier chose to deploy it, and bills per device forever. LoRaWAN is the one you can own outright. The architectural decision behind each technology, compared side by side, and the deployments where the other two are still the right call.
A rancher managing hundreds of cattle across thousands of hectares: where are they right now? Riding out to check takes hours. LoRaWAN GPS trackers show herd locations, catch fence breaks, and spot behavioral changes that signal health issues.
Fifty panels showing every possible metric crammed onto one screen. Nobody looks at it. Good dashboards show 6-8 panels that actually drive decisions. Panel types, alerting strategies, and query optimization that keeps dashboards fast.
Onboarding one gateway by hand is fine. Onboarding fifty is a script. And once they're in the field, you need to reach them without a truck roll. This covers automated provisioning, reliable remote access over OpenVPN, and why WireGuard can quietly lose a gateway you can't drive back to.
You need to mount an anemometer on 32mm pipe at a specific angle to clear a solar panel. No commercial bracket exists. Design it in CAD, print overnight in ASA, install the next day. Custom mounts for a fraction of commercial prices, ready when you need them.
That 1995-era water meter still works fine. That €200k CNC machine isn't going anywhere. Instead of replacing legacy equipment, add LoRaWAN connectivity to what you already have: Modbus, RS485, 4-20mA, pulse outputs. Custom firmware bridges the gap between decades-old industrial protocols and modern IoT monitoring.