Wide-area coverage
Covers rural areas, neighborhoods, industrial sites and remote assets with proper gateway and antenna planning.
LoRaWAN network and IoT platform
LoRaWAN IoT for connecting sensors, assets and operations across wide areas.
Design long-range, low-power networks, connect gateways and devices, and turn telemetry into dashboards, alerts, work orders, commands and operational automations.
Technical guidance, Dashify operations and practical deployment scenarios
Long rangewide coverage with fewer gateways
Low powerreduced sensor maintenance
AU915widely used regional plan in Brazil
What is LoRaWAN
An LPWAN for distributed telemetry, not a replacement for high-speed internet.
LoRaWAN is a networking protocol for sensors and actuators that exchange small data packets over long distances. It prioritizes battery life, coverage, security and scale for periodic readings, states, events and controlled commands.
LPWAN
Low Power Wide Area Network: a network category designed for broad coverage, low data rates and devices that must operate for long periods with limited energy.
Operational autonomy
Supports efficient transmission cycles for battery-powered or small solar-powered sensors.
Many devices
A managed architecture registers devices, deduplicates messages and routes data to authorized applications.
Flexible infrastructure
Gateways can use Ethernet, fiber, Wi-Fi or cellular connectivity as backhaul to the network server.
LoRaWAN at the center of the decision
LoRa, LoRaWAN, mesh and P2P solve different problems.
Radio modulation is not the same as a managed IoT network. Compare purpose, topology and operational capabilities before selecting a technology.
LoRa
The long-range radio modulation technology. It provides the physical link but does not define registration, security, routing, management or network integration.
Best suited forRadio foundation for custom solutionsLoRaWAN
Adds protocol, authentication, device classes, gateways, a network server and application integration to operate IoT at scale.
Best suited forManaged sensors and actuatorsMeshtastic
An open LoRa mesh messaging system for communication among users and devices beyond conventional coverage.
Best suited forOff-grid messaging between peopleMeshCore
Lightweight firmware for decentralized routing among LoRa nodes. It is a communication mesh rather than a gateway-and-server IoT network.
Best suited forSimple distributed mesh networksLoRa P2P
Direct communication between two devices without gateways or a network server. It is simple for specific links but limited in governance and scale.
Best suited forDirect controlled linksHow a LoRaWAN network works
From field sensor to business process in four layers.
Devices transmit by radio, one or more gateways forward packets, the network server validates and organizes traffic, and the platform turns data into operations.
Field devices
Sensors and actuators measure variables, detect events or execute commands according to their class and power policy.
Uplinks, downlinks, OTAA and Classes A/B/CLoRaWAN gateways
Receive packets from every in-range node and forward them without binding each sensor to a single gateway.
Outdoor, indoor, Ethernet, fiber or cellularNetwork server
Authenticates devices, removes duplicate messages, manages ADR, selects gateways and routes valid data.
Join Server, Network Server and AES securityDashify and applications
Decodes payloads, organizes assets, displays maps and metrics, and triggers flows, alerts, integrations and work orders.
MQTT, HTTP, APIs, dashboards and automationsStar-of-stars topology
The same uplink may reach several gateways. The server deduplicates copies and keeps the best available path for the application and possible downlinks.
Hardware selection
Assemble the right stack to prototype, cover and maintain the operation.
The regional frequency is only the beginning. Environment, power, protection, antenna, connectors, firmware and maintenance determine real-world performance.
Development kits
Boards and bundles for validating sensors, payloads, joins, coverage and integrations before purchasing at scale.
Selection criteriaBand, MCU, power, interfaces and documentation
Sensors and nodes
Ready devices for temperature, humidity, level, pressure, energy, presence, soil, air quality and digital states.
Selection criteriaClass, IP rating, battery, accuracy and send interval
Trackers
Mobile nodes with GNSS, BLE or motion sensing for assets, people, livestock, loads and checkpoints.
Selection criteriaPosition interval, autonomy and environment
Gateways and infrastructure
Indoor or outdoor concentrators connecting the radio layer to the network server through reliable IP backhaul.
Selection criteriaChannels, mounting, antenna, backhaul and redundancy
Embedded modules
Radios and modules for manufacturers adding LoRaWAN to meters, controllers, equipment and proprietary products.
Selection criteriaCertification, firmware, interface and product lifecycle
Antennas and accessories
Antennas, cables, connectors, surge protection, power supplies and enclosures determine loss, safety and availability.
Selection criteriaGain, impedance, cable loss, height and grounding
LoRaWAN device classes
Power and latency change with the device class.
Every device implements Class A. Classes B and C add receive windows for applications needing more predictable or faster downlinks.
The class must reflect the power source, command frequency and acceptable latency.
Class A
Opens two short receive windows after each uplink. It maximizes battery life and works well when the device initiates communication.
Lowest powerEnvironmental, soil, leak, waste, parking and asset tracking applications.Class B
Adds beacon-synchronized periodic receive windows, reducing downlink wait without continuous reception.
Intermediate powerScheduled commands, device groups and operations requiring predictable latency.Class C
Keeps reception open almost continuously, providing the lowest downlink latency with higher power demand.
Highest powerStreet lighting, alarms, meters and usually mains-powered actuators.LoRaWAN applicability
An IoT layer for cities, farms, industry and remote infrastructure.
Use LoRaWAN when many points must send readings, states or events with low power and without Wi-Fi or a cellular subscription per device.
Smart public lighting
Monitor luminaires, faults, consumption and controller status and apply commands according to device class and operational policies.
Faults, energy, availability and commands
Urban infrastructure
Connect parking, waste, air quality, flooding, noise and roadside cabinets across the city.
Level, presence, environment and critical events
Soil and microclimate
Compare moisture, temperature, conductivity, rainfall and environmental conditions across fields, greenhouses and crop zones.
Soil, climate, rainfall, CO2 and humidity
Irrigation and water
Monitor reservoirs, flow, pressure, pumps and valves to detect anomalies and guide irrigation routines.
Level, flow, pressure and pump status
Livestock and remote areas
Record motion, checkpoints, fences, water troughs and field conditions with low-maintenance devices.
Periodic location, motion and supply
Water, energy and utilities
Monitor meters, tanks, stations, pressure, leaks and electrical states across dispersed or unattended infrastructure.
Metering, pressure, level, losses and alarms
Industry and facilities
Add lightweight telemetry to equipment, warehouses, cold rooms, panels and outdoor areas without replacing critical industrial controls.
Temperature, vibration, status and environment
Assets and logistics
Track tools, crates, slow vehicles, equipment and checkpoints when periodic visibility matters more than continuous streaming.
Motion, checkpoints, location and inventory
Environmental monitoring
Deploy stations for climate, rivers, soil, air, wildfire risk and other environmental conditions across wide territories.
Climate, air, water, risk and trendsLoRaWAN operations
LiveActive devices2.486+42
Processed uplinks98,7%24h
Open alerts07-18%
Automation executedCritical level created an alert, owner and inspection order.
IoT operations in Dashify
Telemetry creates value only when it becomes a decision, task or automation.
Centralize the LoRaWAN application layer with asset, user, map, metric and business-process context.
Registry and asset twin
Link DevEUI, sensor, location, owner, model, firmware and history.
Maps and coverage
View gateways, devices, areas, states, incidents and signal quality.
Dashboards and BI
Turn payloads into series, KPIs, trends, comparisons and reports.
Alerts and SLA
Detect limits, missing communication, low battery, faults and abnormal patterns.
Flows and automations
Create tasks, messages, escalations, commands and actions from events or rules.
Integrations
Connect MQTT, HTTP, APIs, databases, CRM, ERP and field services.
Field maintenance
Open work orders with location, asset, diagnosis, deadline, evidence and history.
AI and analysis
Summarize incidents, identify deviations and support prioritization and diagnosis.
Professional deployment
Move from proof of concept to production without skipping radio planning.
Quality comes from combining a measurable goal, correct regional plan, coverage survey, suitable hardware, security and observability.
Define the outcome
Specify the variable, frequency, acceptable delay, retention, alerts, commands and process that will consume the data.
Confirm band and compliance
Align the device, gateway, antenna, channel, sub-band, local limits and certification before purchasing.
Plan coverage
Assess terrain, buildings, height, shadow zones, interference, redundancy, gateway backhaul and power.
Validate devices
Test power, payload, accuracy, join, ADR, RX windows, enclosure, antenna and field behavior.
Integrate the platform
Configure the network server, decoders, identities, maps, dashboards, alerts, flows and data retention.
Pilot and scale
Measure coverage and availability, document installation, monitor battery and firmware, then expand in controlled waves.
Security from provisioning onward
Protect identities, keys, integrations and operational actions throughout the device lifecycle.
- Prefer OTAA for new projects
- Use unique keys and protected storage
- Separate scopes, users and applications
- Audit joins, downlinks and changes
Regional plans
All hardware must operate on the same frequency plan.
The nominal band is not enough: gateway, node, channels, antenna and server configuration must match the region and project sub-band.
Brazil: AU915 requires consistent configuration
Brazilian projects commonly use AU915-928. Confirm the sub-band, channels and applicable certification for every device and installation site.
Regulations, limits, certifications and plans may change. Always verify current local authority, manufacturer and LoRa Alliance documentation.
| Band | Formal plan | Typical market | Range |
|---|---|---|---|
| AU915 | AU915-928 | Brazil | 915-928 MHz |
| EU868 | EU863-870 | Europe | 863-870 MHz |
| US915 | US902-928 | United States and North America | 902-928 MHz |
| AS923 | AS923-1/2/3/4 | Asia-Pacific markets | 915-928 MHz |
| AU915 | AU915-928 | Australia and New Zealand | 915-928 MHz |
| CN470 | CN470-510 | China | 470-510 MHz |
| IN865 | IN865-867 | India | 865-867 MHz |
| KR920 | KR920-923 | South Korea | 920.9-923.3 MHz |
Technical roadmap
Learn, select and validate before scaling.
Organize team learning in the same sequence used to reduce project risk: fundamentals, hardware selection and field validation.
01
Learn the fundamentals
Understand architecture decisions before comparing products or estimating coverage.
- Differences among LoRa, LoRaWAN, mesh and P2P
- Gateway and network server roles
- Regional plans, channels and duty cycle
- Classes A, B and C, ADR, uplink and downlink
02
Choose hardware
Compare the complete installed stack, not only the radio or the advertised range.
- Sensor, accuracy, payload and send interval
- Indoor/outdoor gateway, channels and backhaul
- Antenna, cable, connector, height and protection
- Battery, power supply, enclosure and maintenance
03
Build and test
Take the prototype to its final environment to measure coverage, power and operational behavior.
- Build and provision the first node using OTAA
- Test RSSI, SNR, antenna height and shadow zones
- Plan multiple nodes, redundancy and capacity
- Troubleshoot join, decoder, uplink and downlink
LoRaWAN questions and troubleshooting
Most problems come from inconsistency between radio, network and application.
Use these answers to guide a proof of concept and separate coverage, provisioning, channel, decoding and integration failures.
Layered diagnosisCheck frequency and radio first, join and network server second, decoder and application last.
Verify that device, gateway and server use the same region, channels and version; confirm DevEUI, JoinEUI, AppKey/NwkKey, OTAA, join counters and radio coverage. Band or credential mismatches are common causes.
End-to-end LoRaWAN project
Plan radio, devices, platform and automations as one IoT operation.
Start with a measurable use case, validate coverage and energy in the field, and connect the network to Dashify maps, dashboards, alerts, flows, teams and integrations.
Discuss the project