Published by Vivian van Zyl in Raspberry PI and LoRaWAN the 04/02/2026 at 02:17 am
If you have been playing with long-range LoRa before, you have probably seen the other path too: decentralized mesh networks like Meshtastic. LoRaWAN takes a different approach. Instead of everyone passing packets through each other, LoRaWAN is a standardized protocol for low-power sensors sending data over long range to dedicated gateways, which then forward that data over the internet to applications.
This guide focuses on building a local LoRaWAN setup using the SenseCAP M2, Lorawan gateway and the built-in ChirpStack server. The goal is simple: receive sensor messages locally, keep your data closer to where it is collected, and be ready to add devices and profiles next.
LoRaWAN is designed for devices that run on batteries for a long time. Typical use cases include smart cities, agriculture, asset tracking, and industrial IoT. In practice, sensors transmit over LoRa to a gateway, and the gateway forwards received packets to a network server, which then makes the data available to applications via APIs.
A key mental model:
Instead of relying on an online cloud platform, the SenseCAP M2 can run a built-in local network server.
The unit used here is the Seeed Studio SenseCAP M2 indoor multi-platform LoRaWAN gateway. It is not weather sealed, so it is meant for indoor setups.
What to notice on the hardware:
Different versions exist depending on which connectivity methods you want (Ethernet, Wi-Fi, 4G/LTE, or combinations). You also choose the correct regional frequency plan. The unit discussed uses US915.
This is the part that makes the SenseCAP M2, Lorawan workflow particularly friendly if you want “local first”. The gateway runs two separate software components:
Why you should care: with the built-in local ChirpStack, you can start building and testing a working LoRaWAN network without immediately sending everything to an external cloud service.
Start by connecting the LoRa antenna. The gateway can be sensitive to startup conditions, so it is a good habit not to power it before the antenna is attached.
To enter hotspot mode:
That blue flashing state indicates the gateway is now acting like a Wi-Fi hotspot so you can configure it right away.
On your computer, connect to the SenseCAP access point (SSID typically appears as SenseCAP Access Point or similar).
The default hotspot Wi-Fi password is shown in the quick start guide. In this setup it was:
12345678
Next, open a browser and go to the gateway’s hotspot IP address:
http://192.168.168.1
Lucy login credentials are printed on a sticker on the bottom of the gateway, including the default username and password.
Hotspot mode is only meant to get you through initial setup. The next goal is to connect the gateway to your home or lab network so you can reach it consistently and so it can forward LoRaWAN packets upstream.
Inside Lucy:
Important gotcha: if you only “save” and forget “save and apply,” rebooting can leave the gateway stuck in the old configuration and it may not reconnect to Wi-Fi.
After applying changes, wait for the gateway to come back online, then find its new IP address on your network (it may change once it joins Wi-Fi).
In the system settings, sync time and set your timezone. Timezone matters for timestamps in logs and for consistent behavior across components.
In the setup described, the timezone was set to America/New_York.
Check the firmware version and update if a newer build is available. The gateway includes an in-place update mechanism.
While updating:
After completion, re-open Lucy and confirm the version is now current.
In the LoRa network settings, the gateway can forward packets to different destinations depending on your architecture.
The useful option here is to choose the local network server running on the gateway itself.
Once enabled, Lucy shows the IP address of the built-in ChirpStack instance. Open that server in a browser.
ChirpStack login is also provided by the gateway defaults (commonly admin/admin in this setup). After logging in, you should be able to access sections like:
At this stage, the gateway is:
The next step is what makes it “real” for sensors: connecting devices, creating device profiles, and verifying that uplink messages show up in ChirpStack as expected.
No. You can also connect via Ethernet using your LAN. Hotspot mode is simply convenient for initial setup when you do not yet know the gateway’s network IP address.
It lets you keep packet processing and sensor data on your local network instead of relying on an external cloud platform. This can simplify early testing and improve privacy and control.
Common options include Ethernet, Wi-Fi, and some versions also include 4G LTE via a nano SIM. The exact mix depends on the specific model you purchased.
Choose the version that matches your region (for example, US915 for many parts of the United States). Using the wrong region will prevent proper LoRaWAN operation.
In this workflow, forgetting to use “Save and Apply” after changing Wi-Fi settings. Without applying changes, the gateway may not reconnect as expected after reboot.