Welcome to the RAKwireless Bulletin.

The past months brought new ways to monitor gateways for LoRaWAN^®, new hardware for industrial networking and Meshtastic, and field projects showing RAKwireless technology at work.

See what’s new with WisDM Metrics, WisGate Connect Router RAK7392, the Verizon-certified RAK7268CV2-V, and WisMesh Repeater Mini V2. We also cover LoRaWAN field testing, smart agriculture, DEF CON, and upcoming RAKwireless appearances in Birmingham, Amsterdam, and Valencia.

TL;DR

• WisDM Metrics and Remote Extension Install add fleet-wide visibility and remote WisGateOS 2 extension management.
• A WisGateOS 2 tutorial covers CSV import and bulk generation for adding multiple devices.
• New hardware includes WisGate Connect Router RAK7392, RAK7268CV2-V, and WisMesh Repeater Mini V2.
• Kevin Cheng shared a lightweight LoRaWAN field-testing workflow using Field Tester Pad and RAK7268.
• Lee Cheng Zhe's project measured LoRaWAN coverage across Sunway City, while TERRA AI chose RAKwireless for its farm network.
• Rokland showcased an exclusive green WisMesh Pocket V3 at DEF CON 34.
• Upcoming events include The Things Conference in Amsterdam and IoT Sparks in Valencia.

More Ways to Manage Gateways for LoRaWAN^®

WisDM Metrics Brings Fleet-Wide Data Into One View

Managing gateways one by one gets harder as a LoRaWAN network grows. WisDM Metrics brings fleet data into customizable, no-code dashboards so teams can review gateway health and network performance from one place.

Track LoRa link quality, CRC errors, uplink and downlink results, CPU and memory use, uptime, and backhaul traffic. Dashboards can also be narrowed by gateway, location, firmware, or metric conditions, making it easier to spot devices that need attention first.

WisDM Metrics is included across all WisDM plans at no additional cost.

See how WisDM Metrics brings gateway health and network performance into fleet-wide dashboards, without checking gateways one at a time.

New WisDM Feature: Remote Extension Install

WisDM Remote Extension Install is a new feature that lets teams install, update, and manage available WisGateOS 2 extensions on eligible gateways through a guided workflow in the WisDM console.

Select the target gateway, choose an extension, start the remote install, and monitor status from the same console. At launch, available extensions include Cellular Failover, WiFi Reboot, Operation & Maintenance (O&M), and Port Management.

Add Multiple Devices Faster in WisGateOS 2

Adding devices one at a time can slow down larger LoRaWAN deployments and increase manual entry errors. WisGateOS 2 provides two ways to handle bulk registration more efficiently.

Use CSV Import when you already have a large device list with assigned settings. Use Bulk Generate when you need sequential device EUIs and JoinEUIs, with consistent IDs that can be saved to CSV for later use.

New Hardware for Edge, Cellular, and Mesh Deployments

WisGate Connect Router RAK7392 Brings Industrial Networking to Raspberry Pi®

WisGate Connect Router RAK7392 combines Raspberry Pi Compute Module 4 with four native Ethernet ports, MiniPCIe expansion, and two WisBlock slots for industrial networking and edge applications.

RAKPiOS adds Docker capabilities for router applications, protocol gateways, VPNs, and other edge workloads. With networking and expansion built into one platform, RAK7392 reduces the need for separate adapters and extra integration work.

See RAK7392

WisGate Edge Lite 2 Adds a Verizon-Certified Variant

Some US deployments require carrier-approved hardware before IT or procurement teams can move forward. The RAK7268CV2-V adds Verizon certification to WisGate Edge Lite 2 for projects that need Verizon LTE connectivity.

The three variants cover different connectivity requirements. RAK7268V2 uses Ethernet and WiFi, RAK7268CV2 adds LTE Cat 4, and RAK7268CV2-V adds Verizon certification. The Verizon variant also includes WisGateOS 2, WisDM, Zero Touch Provisioning, secure MQTT/TLS, PoE, and 9-36 V DC input.

See the Verizon-certified RAK7268CV2-V

WisMesh Repeater Mini V2 Adds a High-Power Option

WisMesh Repeater Mini V2 gives Meshtastic networks a dedicated outdoor relay for extending communication between nodes.

The new version offers a high-power option up to 30 dBm, or 1 W, where regional regulations permit. It also retains solar operation and IP67 protection while adding updated waterproof USB Type-C connectivity and improved battery mounting.

Meshtastic comes pre-flashed, and Bluetooth allows configuration without connecting the repeater to a computer.

Meet WisMesh Repeater Mini V2

LoRaWAN and Meshtastic Outside the Lab

Kevin Cheng Shares a Lightweight Field Test Kit for LoRaWAN

RAKwireless Regional Manager Kevin Cheng shared the portable kit he uses for LoRaWAN field testing: a Field Tester Pad, RAK7268 gateway, tripod, compatible USB-C PD power bank, and a 12 V Type-C-to-DC5521 trigger cable.

The Field Tester Pad handles the measurements while the rest of the kit fits into a backpack for field work. Kevin described this as his own configuration and recommends checking that the power bank and cable provide the required 12 V output before connecting the gateway.

Student Project Establishes a LoRaWAN Coverage Baseline Across Sunway City

A university project put LoRaWAN coverage planning through a real-world test at Sunway City.

Lee Cheng Zhe presented the work during SUNForge at Sunway University. The project used a RAKwireless gateway and tracker to collect location-tagged RSSI, SNR, and data-rate measurements.

Lee and his co-supervisor, Dr Abdikarim Ibrahim, compared the measurements with CloudRF predictions, revealing coverage gaps and weak-signal areas associated with shadowing and non-line-of-sight propagation. The results give the team measured data for future gateway placement and wider IoT planning.

TERRA AI Chooses RAKwireless for Its LoRaWAN Network

TERRA AI chose RAKwireless as it builds its own LoRaWAN network to connect farms. The project brings long-range wireless connectivity into agricultural environments where devices may need to communicate across large areas.

The announcement points to another way LoRaWAN can bring connected devices and data collection to agricultural operations beyond conventional network coverage.

Rokland Showcases an Exclusive WisMesh Pocket V3 at DEF CON 34

Rokland brought an exclusive green WisMesh Pocket V3 to DEF CON 34 in Las Vegas, putting Meshtastic hardware in front of attendees exploring mesh communications and long-range wireless.

RAKwireless VP of Strategic Growth & Design Partner Gavin Brown joined the Rokland team onsite to meet attendees, talk about Meshtastic deployments, and help bring the WisMesh community into the DEFCON conversation.

Upcoming: Meet RAKwireless at Events

The Things Conference 2026 | Amsterdam | September 22–23

RAKwireless returns to The Things Conference as a Gold Sponsor and newly recognized Strategic Contributor to the LoRaWAN ecosystem. Meet the team at Booth L11 at De Kromhouthal in Amsterdam.

On September 23, Xose Pérez will present the keynote Operational Visibility and AI Troubleshooting. Carl Erick Rowan will demonstrate real-world low-power performance with RAK3172-F modules, while Gavin Brown will join a panel on designing and manufacturing reliable LoRaWAN devices.

We will also feature WisGate Soho Lite, RAK3172-F, and the RAK7437/RAK7437C BACnet Gateway at our booth.

IoT Sparks 2026 | Valencia | October 7

Xose Pérez will present Operational Visibility and AI Troubleshooting at IoT Sparks 2026 in Valencia.

As gateway fleets for LoRaWAN grow, finding the cause of an issue can mean sorting through large volumes of metrics, logs, and events. Xose will show how AI can turn that raw operational data into actionable troubleshooting steps and shorten the path from symptom to cause.

Xose and Gavin Brown will also be onsite to discuss LoRaWAN deployments and taking IoT projects from pilot to production.

This Month in One View

The past few months’ developments point to a broader direction for RAKwireless: helping teams move from connecting devices to operating larger deployments with better visibility, field data, and hardware matched to real deployment requirements.

As LoRaWAN and Meshtastic networks expand, the challenge shifts from getting devices online to managing, testing, and troubleshooting them effectively over time.

IoT Made Easy,
The RAKwireless Team

Note: Raspberry Pi is a trademark of Raspberry Pi Ltd.

What happens when LoRaWAN devices can reach a gateway, but connecting that gateway to the wider network is the difficult part?

Long-range radio coverage does not remove the need for backhaul. A gateways for LoRaWAN still requires a route to the network, typically through Ethernet, fiber, WiFi, cellular, or another IP connection. Across a large facility, however, the ideal location for radio reception may be nowhere near existing communications infrastructure.

For Koelus, a subsidiary of Aritium that develops IoT- and AI-based solutions for industrial environments, that challenge became very real during a water-monitoring modernization project in Madrid, Spain.

The approximately 18-hectare industrial plant required water consumption to be measured across 18 points distributed among different areas and process stages. Existing infrastructure provided limited visibility, while obsolete meters lacked communication capabilities. Extending wired connections throughout the site would add cabling costs, installation work, and the possibility of disrupting ongoing production.

The deployment had to account for:

• 18 hectares of industrial space
• Measurement points distributed across multiple zones
• Legacy metering infrastructure with limited connectivity
• Physical distance and complex plant layouts
• The cost of extending cabling to new locations
• Construction work that could interfere with ongoing operations

The issue was therefore bigger than getting a LoRaWAN signal to each meter. Gateway locations also had to connect back to the network without turning the project into a major cabling exercise.

The Solution: A LoRaWAN Network Using Gateway Mesh

Koelus addressed that constraint with a private LoRaWAN architecture built around Gateway Mesh.

Gateway Mesh allows relay gateways to forward LoRaWAN traffic wirelessly toward a border gateway, reducing the need for conventional backhaul at every gateway location.

In this deployment, secondary gateways relayed traffic toward a central master, allowing the radio infrastructure to be placed according to site requirements rather than the availability of wired backhaul.

From the meter to the existing control system

At field level, pulse collectors transmit water-consumption readings wirelessly. The secondary gateways carry that traffic across the plant toward the RAK7391 master, which serves as the central aggregation point for the mesh.

From there, Koelus MSE processes the incoming information, while the Koelus Platform can add visualization, alerts, analytics, and predictive capabilities. Those outputs can then feed established BMS, SCADA, or PLC environments through standard industrial protocols, extending the facility’s existing systems rather than forcing their replacement.

The important architectural shift is simple: the gateway no longer has to be placed only where conventional backhaul is easiest to provide. Gateway Mesh gives the deployment another path between the field and the point where the network connects to the rest of the industrial infrastructure.

The Deployment: Gateway Mesh in a Real Industrial Environment

The architecture became tangible once it was distributed across the plant itself. Instead of concentrating connectivity in one convenient location, Koelus placed each part of the network where it could serve a specific field role across the industrial site.

The deployment included four RAKwireless gateways: one WisGate Connect Smart Building as the master gateway and three WisGate Edge Lite 2 RAK7268 units as secondary gateways. Eighteen pulse collectors captured water-consumption readings from measurement points distributed across the plant.

At the measurement points

New water meters were paired with pulse collectors at the monitored locations. The collectors captured water-consumption data and transmitted it over LoRaWAN, allowing readings from distributed points across the facility to reach the wireless network without new communications cabling to each meter.

Three Secondary Gateways Across the Plant

Three WisGate Edge Lite 2 RAK7268 units served as secondary gateways in different areas of the facility. They received LoRaWAN traffic from field devices within their coverage areas and forwarded it through Gateway Mesh toward the master gateway. This allowed gateway coverage to be placed where it was needed without extending conventional backhaul to every secondary location.

One Master Gateway at the Aggregation Point

One WisGate Connect Smart Building served as the master gateway and central aggregation point. Traffic forwarded from the three secondary gateways converged there before continuing into the digital infrastructure used by the Koelus MSE.

Together, the pulse collectors and four gateways created a wireless path from distributed water-meter locations to the plant’s central monitoring environment. Secondary gateways brought connectivity closer to the measurement areas, while the master gateway brought their traffic together at the network’s central aggregation point.

The Result: Less Infrastructure, More Visibility

The payoff was visible on both sides of the project: less physical infrastructure to add and more operational information available from the plant.

Infrastructure avoided

Water-consumption readings could be collected wirelessly without extending cable routes to each measurement location. That removed the need for trenching and cable trays, reduced associated construction work, and helped avoid production downtime during installation.

Visibility gained

The deployment included 18 pulse collectors across 18 water measurement points in different zones and process stages. This gave operators a more granular view of consumption and more context for identifying anomalies and opportunities for optimization.

Existing workflows retained

The additional IoT data did not have to live in an isolated monitoring system. Readings and insights from the Koelus environment can be incorporated into established management workflows, giving operators a broader view of water use without replacing the control infrastructure already in place.

The result was more than wireless metering. The plant expanded its view of a critical resource without requiring a comparable expansion of wired infrastructure. That is the operational value the content strategy calls for: less cabling and installation complexity, with greater flexibility in how the network reaches the areas that matter.

Beyond Water Monitoring: Building an IoT Infrastructure

Water monitoring was the first operational need, not the limit of the system. With the private LoRaWAN network and Koelus MSE already in place, the site now has a foundation that can accommodate additional industrial applications as priorities change. 

Koelus identifies several possible next steps: energy optimization, environmental monitoring, equipment monitoring, predictive maintenance, and asset tracking.

The bigger value is what comes after the first use case. Rather than remaining a single-purpose water-monitoring installation, the architecture can evolve as new requirements emerge. Each additional application can build on infrastructure that is already established, turning the original project into a broader industrial IoT foundation.

The Gateway Mesh Takeaway

The Koelus deployment points to a broader lesson for industrial LoRaWAN: radio reach and gateway connectivity are two different design problems. A device may be able to communicate over long distances, yet the most effective gateway location can still be far from convenient Ethernet, fiber, cellular, or other IP access. Gateway Mesh becomes especially useful when those two requirements do not line up.

By relaying traffic from secondary gateways toward a master, the Madrid project gave Koelus more freedom to distribute connectivity around a complex industrial property without providing an independent wired backhaul path at every point. The resulting architecture also demonstrates a model that Koelus can adapt to other large facilities facing similar constraints.

Put the gateway where the network needs it, not simply where the nearest cable ends.

One LoRaWAN network. Greater reach. Less infrastructure.

The trail turns, the bars on your phone drop to zero, and the group behind you is out of contact. It is the same silence a family hears when a storm takes out the local tower for three days, and the same one a festival crew hits when twenty thousand phones land on one overloaded cell site at once.

Cell coverage is not a utility. It is a commercial service with gaps, and the gaps show up where the stakes are highest. There is an answer to this that has been quietly maturing for years, and it costs you no subscription and no radio license. So what is Meshtastic? Hikers carry it. So do search and rescue volunteers, festival crews, and a growing number of neighbors who got tired of discovering their phones were useless at exactly the wrong moment.

Meshtastic is a free, open-source project that turns small LoRa® radio devices into a private messaging network. Every device relays for every other, so a group can trade texts and GPS positions across kilometers of dead zone. No cell towers. No internet. No SIM card, and no monthly bill.

How does Meshtastic work?

The radio. Every Meshtastic device carries a LoRa chip. The name is short for Long Range, and Semtech built it around one deliberate trade: give up speed, buy distance. You will not be streaming video over this. Think closer to the pace of a text message. What you get back is a signal with very little power behind it that still covers kilometers, where Wi-Fi and Bluetooth quit after a few tens of meters.

The mesh. Each device is a node, and here is the part that does the heavy lifting. Out of the box, a node relays traffic that is not its own. It listens, then it forwards. Picture you and a friend on opposite sides of a ridge, far outside each other's range, with a third node sitting somewhere between you. Your message travels through that middle node and lands. Nobody configured anything. That relaying is the entire difference between a LoRa mesh network and a pair of walkie-talkies. Coverage grows as nodes are added, and no central tower can fail, because every participant is the infrastructure.

Your phone. The node handles the radio, your phone handles the keyboard and map. They pair over Bluetooth, so you type in the Meshtastic app as you would in any messaging app, with your phone in airplane mode if you like.

For the routing logic in detail, the official Meshtastic project site covers it properly.

Does Meshtastic need the internet or a cell signal?

No. Nodes talk directly to each other over radio, with no SIM, Wi-Fi, account, server or monthly bill. You can optionally bridge a mesh to the internet using MQTT, a lightweight protocol for passing data between systems, but that is an addition you choose, not a dependency you inherit.

Meshtastic range: how far does it actually reach?

Here are figures from a controlled RAKwireless comparison of two versions of the same station. A note on the units first, because the scale is deceptive. dBm means decibel-milliwatts, and it is not linear. Add 3 dBm and you have roughly doubled your output. So the step from 22 dBm to 30 dBm is bigger than those numbers suggest. 30 dBm is a full watt, six times the power.

• The 22 dBm standard station in an urban setting holds usable links of 1 to 3 km, the same output power as most nodes in the Meshtastic ecosystem.
• The 1 W (30 dBm) station, mounted high with reasonable line of sight, reaches much further. RAKwireless field tests recorded stable 12 km links.

Six times the power, and yet the more useful lesson from that test was not about power at all.

Antenna height, placement and repeaters

Antenna height beats wattage. How high your antenna sits will decide your range more than anything else you do. Take one station, move it from 1 m to 3 m, and it comfortably outperforms itself. What stands in the way matters nearly as much. Metal roofs are brutal. Dense foliage drinks signal, and so does any interior wall you were hoping to shoot through. A higher-gain antenna will help you, but not before elevation and line of sight do.

Where terrain blocks a link entirely, the fix is usually another node rather than a bigger radio. A repeater is just a node parked where it can hear both sides, typically on a hill, a roof or a tower.

There is also a trap worth knowing before you buy the largest radio available. Running far more power than the nodes around you creates an asymmetric link. Your station shouts across the valley, the small node hears it perfectly, then replies with its own modest radio and nobody hears it come back. That is not extra range, it is a one-way conversation.

What is Meshtastic used for?

Keeping a group together off grid. Hiking parties and field teams clip on wearable trackers so nobody has to guess where anyone else is. RAKwireless demonstrates this with the WisMesh Tag, a badge-sized unit rated IP66, which is the rating for dust-tight and able to shrug off water jets. No SMS. No calls. Nothing cellular anywhere in the chain. Everyone carrying one shows up as a named marker in the app, and you can check status or watch a location from there.

Emergency communication when networks fail. A mesh that never depended on commercial infrastructure keeps working when that infrastructure goes down, which is why community response groups were among the earliest adopters. Battery and solar-charged nodes keep relaying through outages.

Community networks and work sites. Volunteers seed nodes across a town, campus or festival site so everyone in reach gets a shared layer that costs nothing to run. Farms and construction sites use it where cellular is patchy.

For fixed installations there are Raspberry Pi based stations that arrive with Mosquitto, Node-RED and Grafana already installed. You get an MQTT feed and a local dashboard of node status and signal quality, running on the box in front of you rather than someone else's cloud.

Meshtastic setup: what you need to start

Two things: a node, and a phone you already own. A conversation needs at least two nodes, so most people buy a pair or join an area where a community mesh already exists.

Ready-to-use device or DIY build?

Both start from the same radio. What changes is how much of the work is already done for you.

The real question is whether you want the network or the project. RAKwireless sells both routes in its Meshtastic device collection: assembled units like the WisMesh Board ONE Pocket and the WisMesh Pocket V2, alongside the bare WisMesh Board ONE for people who want to build their own enclosure.

Your first thirty minutes

1. Unbox. Attach the LoRa antenna before powering on.
2. Power on. Slide the side switch. A colored status light reports what the device is doing: solid red charging, solid green running, blue blinking when a message arrives.
3. Pair. Open the Meshtastic app, select the device, confirm the Bluetooth pairing.
4. Set your region. The app will not transmit until you choose it. This keeps you on your local frequency, so it is not optional.
5. Send a message. You are on the mesh.

On the Board ONE Pocket, one press of the left button switches the screen, a double press broadcasts your location, and a triple press toggles GPS. Devices ship with firmware installed, so updating is optional. When you do want it, the official Meshtastic web flasher walks you through the whole thing from a browser tab.

/

GPS or non-GPS?

Choose GPS if you want the node to report its own position for tracking and mapping. The receiver draws meaningfully more power, so plan for shorter runtime rather than multi-day battery life.

Choose non-GPS for messaging, longer battery life, and a free expansion slot for sensors such as environmental or motion modules. Your phone can still supply position when it has a fix.

Meshtastic channels, encryption and privacy

Conversations live on channels, and a shared key locks each one. The encryption is AES-256, the same standard guarding bank transfers and classified files. Hold the key, read the channel. Without it you get nothing, and that holds even for the people whose nodes are physically carrying your messages across the mesh. Nodes forward encrypted packets they cannot open.

One honest limitation: the default public channel ships with a publicly known key, because it exists so strangers can find each other. Create your own channel for anything private. The project documents its encryption model in full if you want the specifics.

Is Meshtastic legal, and do I need a license?

Legal, and no license needed for standard use. Meshtastic runs on the ISM bands. That stands for Industrial, Scientific and Medical, and it means shared public spectrum that anyone can transmit on without asking permission, so long as they stay inside the power limits. Your Wi-Fi router lives in the same neighborhood. So does your garage door remote.

Which frequency you use depends on where you are standing. Much of Europe runs 868 MHz. North America runs 915 MHz. That is precisely why the app refuses to transmit until you pick a region, and it is worth getting right the first time. If you are unsure which band applies where you live, your national spectrum regulator publishes the limits.

There is one exception, and it deserves to be taken seriously. High-power 1 W equipment may require a license, or may not be permitted at all in your region. Check before you mount one. Standard 22 dBm nodes carry no such complication.

Meshtastic vs LoRaWAN®: same radio, different networks

The two names keep turning up in the same threads, and there is a reason. They sit on the same LoRa radio layer. So what is LoRaWAN? Treat it as the other thing you can build once you have that radio. Hundreds of low-power sensors report inward to a LoRaWAN gateway, which passes their data up to a central server. One shape is a web. The other is a wheel with a hub. Sort that out and you have understood LoRa vs LoRaWAN.

A rough rule: humans reading the messages means Meshtastic. Machines producing readings that some database has to swallow at scale means a LoRaWAN network. Projects graduate from the first to the second somewhere around the point where device counts hit the hundreds. Range per gateway is much the same, since the radio underneath has not changed, but you plan coverage around where the gateways go rather than watching it grow wherever users wander. Our LoRaWAN and LoRa primer goes deeper than this page should.

Frequently asked questions

What is Meshtastic and how does it work?

Meshtastic turns low-power LoRa devices into a private mesh network for texts and GPS positions. Each device relays traffic for its neighbors, so messages hop node to node across distances no single device could cover. You type on your phone, paired to the node over Bluetooth.

Does Meshtastic need the internet or a cell signal?

No. Nodes communicate directly over radio, with no cell tower, SIM card, Wi-Fi or subscription. You can optionally bridge a mesh to the internet using MQTT, but nothing requires it.

How far can Meshtastic reach in real conditions?

Height and line of sight decide this more than which device you buy. RAKwireless testing put a 22 dBm station at 1 to 3 km of usable range in a city. Mount a 1 W station high with a clear view and the same testing held stable links at 12 km. Messages hop between nodes as well, so the network as a whole reaches further than any single link.

Is Meshtastic legal, and do I need a radio license?

In most countries, yes, and no license is required, because Meshtastic runs on license-free ISM bands. Set your region in the app so the device transmits on your local frequency. High-power 1 W hardware is the exception and may require a license or be prohibited where you live.

What do I need to buy to start with Meshtastic?

One node and a phone you already own, though a conversation needs at least two nodes. An assembled device such as the WisMesh Board ONE Pocket works out of the box. A bare board costs less up front but needs a battery, an enclosure you print yourself, and some assembly time.

Is Meshtastic encrypted and private?

Yes. Messages use AES-256 and are readable only by devices holding the channel key, including on nodes that relay them. The default public channel uses a widely known key by design, so create a private channel for sensitive conversations.

TL;DR

• What is Meshtastic? LoRa devices forming a private mesh for texts and GPS positions. No cell towers, no internet, no SIM, no monthly fee.
• Every node relays for the others, so coverage grows with the group and no single failure takes the network down.
• Tested range: 1 to 3 km for a 22 dBm station in a city, stable 12 km for a 1 W station mounted high. Height beats wattage, and overpowering one side creates a one-way link.
• License-free on ISM bands for standard use. Set your region in the app. 1 W gear may need a license locally.
• Encrypted by default with AES-256 per channel, though the default public channel is intentionally open.
• To start: one assembled node, a phone, about 30 minutes.
• vs LoRaWAN: peer-to-peer messaging for people, versus gateway-based data collection for sensors.

Ready to try it? Pick up a WisMesh node and send your first mesh message today. Not sure which one fits? Start with our guide to the best Meshtastic devices for beginners.

Meshtastic is a registered trademark of Meshtastic LLC. LoRa® and LoRaWAN® are registered trademarks of Semtech Corporation.

A new way to deploy capabilities across WisGateOS 2

WisDM Remote Extension Install adds a new remote deployment feature to gateway device management for LoRaWAN^®: teams can install, update, and monitor supported WisGateOS 2 extensions on each eligible gateway directly from the WisDM console.

Remote Extension Install handles how supported extensions are deployed and managed, one gateway at a time, from a single console. The extensions themselves provide the gateway functions, such as connectivity recovery, maintenance automation, and network management.

The shift is in how those extensions reach a gateway already in the field. Operators can identify the devices that need a function, choose the appropriate extension, begin the rollout, and follow its status within the same environment. As requirements change across sites or deployments, supported functionality can evolve with them instead of remaining limited to what was configured at installation.

That raises an important question: what exactly is a WisGateOS 2 extension, and where does Remote Extension Install fit within WisDM?

What is WisDM Remote Extension Install?

WisDM Remote Extension Install is the deployment mechanism for supported WisGateOS 2 extensions. Built into WisDM, it gives gateway teams a centralized way to install, update, and monitor extensions on an eligible gateway individually.

It handles the rollout layer: operators select the gateway, choose the supported extension they want to deploy, start the installation, and follow its status from WisDM.

What Are WisGateOS 2 Extensions?

WisGateOS 2 extensions are modular software components that add specific functions to a gateway without changing its core operating system. Depending on the extension, those functions can address connectivity recovery, maintenance, or network management.

Current examples include WiFi recovery, cellular failover, scheduled maintenance, and port management.

Extension vs. firmware: Firmware changes the underlying WisGateOS 2 operating system. An extension adds functionality on top of it. This distinction makes Remote Extension Install more than another OTA firmware mechanism. It is designed specifically for managing the modular software layer of WisGateOS 2.

Remote Extension Install sits within WisDM rather than functioning as a separate product. It brings those modular additions into the same device management environment, giving gateway teams a centralized way to handle extension deployment and maintenance as their requirements change.

Why RAK Built It: Gateway Capabilities Should Not Stop Evolving After Deployment

A LoRaWAN deployment rarely stays exactly as it was on day one. Connectivity conditions shift, maintenance policies mature, and network controls may need to change long after the hardware is installed. 

Remote Extension Install was built around that reality: the software functions available to a WisGateOS 2 device should be able to evolve with the operation.

Manual device-level work creates room for inconsistency. When the same software change has to be carried out separately on individual units, often over SSH, it's easy for versions to drift. WisDM replaces that manual process with a guided, repeatable install for each gateway, making it easier to keep track of what has been applied and where.

Post-deployment changes are part of the lifecycle. A function that was not needed at launch may become relevant later as connectivity, maintenance, or network policies develop.

The next question is how that process works inside WisDM.

How WisDM Remote Extension Install Works

The workflow is intentionally simple: choose where the extension should go, select what you want to add, then follow the rollout in WisDM.

Step 1: Select the Gateway 

Start by choosing the gateway that should receive the extension. Extensions are currently installed one gateway at a time, keeping each change scoped and easy to verify before moving to the next device.

Step 2: Choose the Supported WisGateOS 2 Extension

Next, select the required option from the supported extension catalog. The choice depends on the function the gateway needs, whether that relates to connectivity, maintenance, or network management.

Step 3: Start the Rollout and Monitor Status

Once the target gateway and extension are selected, begin the remote installation. WisDM displays rollout status so you can follow progress on the chosen device and see how the deployment is proceeding.

Think of it as an MDM-style approach for a gateway for LoRaWAN: WisDM brings app-style, no-SSH deployment to WisGateOS 2 extensions from a central platform. No need to open each gateway's own console.

Which WisGateOS 2 Extensions Can You Deploy Remotely?

WisDM Remote Extension Install currently highlights four WisGateOS 2 extensions, each adding a specific function to an eligible gateway. More extensions will be added to WisDM in the coming months.

WiFi Reboot (recover a lost WiFi connection)

Connectivity checks run against configured targets. If all ping/httping tests fail, the WiFi module or the entire gateway can be restarted to restore the link.

Cellular Failover Reboot (respond when every backhaul link goes offline)

This option watches LTE, Ethernet, and WiFi. When none of those connections is available, it can restart the LTE module or reboot the gateway.

Operation and Maintenance (automate recurring upkeep)

Scheduled reboots are paired with cellular-network monitoring and automatic cellular module restart, covering two common maintenance tasks in one package.

RAK Open/Close Port (apply network traffic rules)

Ports can be opened or closed as needed, while source-IP restrictions provide more control over which addresses are allowed to connect.

Add Your Next Gateway Capability from WisDM

Gateway functionality does not have to stay fixed at installation. WisDM Remote Extension Install makes it possible to introduce supported WisGateOS 2 extensions as new requirements emerge, with WisDM providing the place to manage those changes.

Ready to try it? Log in to WisDM and push your first extension.

Welcome to the RAKwireless Bulletin.

This edition covers new modules for LoRaWAN, firmware updates, deployment-ready tutorials, and real-world use cases across cold chain, public safety, and global logistics.

We also recap our recent event presence across Europe and Australia, and share updates from the LoRa^® Alliance ecosystem, including a new leadership role for RAKwireless within the community.

Here's what happened across the RAK ecosystem this month.

Deployment Solutions and Product Updates

[New Product] RAK3172-F Module: Added 512 KB Flash for Support

Our latest module for LoRaWAN, RAK3172-F Module, includes a 512 KB external flash, enabling FUOTA-ready architectures and rollback-oriented firmware recovery for safer remote IoT firmware updates.

Designed as a pin-compatible upgrade from its previous generation module, it helps developers move faster from existing designs to long-term, maintainable IoT deployments.

RAK3172-F Module for LoRaWAN® with External Flash

Explore

[New Product] WisGate Soho Lite: Cost-Optimized Gateway for LoRaWAN

We launched a new cost-optimized gateway of the RAK7266 series, designed for deployments where cellular connectivity is not required but reliable networking for LoRaWAN is still essential.

By removing the LTE functionality, the RAK7266S variant of the WisGate Soho Lite significantly reduces entry cost while keeping deployment simple and flexible. This makes it an ideal solution for smart buildings, campuses, retail environments, and small-scale IoT networks where budget efficiency matters.

WisGate Soho Lite without LTE

Explore

Deployment Tutorials and Resources

Meshtastic Device Guide: Choosing the Right Option for Your Setup

We published an ultimate guide comparing RAKwireless Meshtastic devices by use case, skill level, setup style, power source, and deployment needs.

A compact tracker works well for bags, bikes, field teams, and everyday carry. A handheld is better for direct messaging. A repeater helps extend coverage. A gateway or station is useful when your mesh needs MQTT, dashboards, or cloud visibility.

Whether you're looking for a compact tracker for field teams or a full gateway with MQTT and dashboards, this guide helps you find the right fit.

Video Guide: Choosing the Raspberry Pi Meshtastic Station You Need

Our video comparison breaks down exactly where the WisMesh Station Standard (22 dBm) and WisMesh Station HP (1W / 30 dBm) perform best. We also included deployment tips that matter more than raw output power and how to monitor your mesh network locally with MQTT and Grafana.

Video Tutorial: Configure RAKwireless Gateway for LoRaWAN The Things Network (TTN) EU1

We published a new video tutorial showing how to configure a RAKwireless gateway to connect to TTN EU1 cluster using Packet Forwarder mode.

The guide walks through gateway registration on TTN, Packet Forwarder configuration, frequency plan selection, and gateway connection verification. This approach helps technicians and integrators simplify gateway deployment for LoRaWAN on European networks.

Video Tutorial: Build a Multi-Gateway LoRaWAN Network

We created a step-by-step video guide showing how to build a multi-gateway network for LoRaWAN using RAKwireless gateways in built-in network server mode. The setup is broken down into five simple steps and is ideal for industrial IoT, smart agriculture, and remote deployments where reliability and scalability matter.

Events and Industry Presence

Gavin Brown Appointed Vice Chair of LoRa Alliance DSMF

We're proud to share that RAKwireless’ VP of Strategic Growth & Design Partner Gavin Brown has been appointed Vice Chair of the Device & Solution Makers Forum (DSMF), a key working group within the LoRa Alliance.

The DSMF brings together device and solution maker members to share challenges, best practices, and practical insights that support the continued growth of the LoRaWAN ecosystem.

His appointment reflects our deepening commitment to the LoRaWAN community and our role as a Strategic Contributor to the LoRa Alliance.

Hardware Pioneers Max 2026

Gavin Brown attended the Hardware Pioneers Max 2026 at ExCeL London. He took part in conversations with those building the next generation of connected devices across IoT and LoRaWAN, focusing on practical discussions about turning concepts into deployable solutions.

Electronex Australia 2026

At Electronex Australia, WisDM and WisToolBox lead Ting Huang and Glyn High Tech Distribution showcased how our BACnet Gateway and Field Tester Pad help simplify connected building deployments from BACnet integration to field testing.

The Things Conference 2026

We're proud to return to The Things Conference in Amsterdam this year as a Strategic Contributor to the LoRaWAN ecosystem. Get to see what we're working on and connect with our product experts.

• Carl Erick Rowan will live-demo real-world low-power LoRaWAN performance using the RAK3172-F module.
• Xose Pérez will deliver a keynote on using AI to simplify troubleshooting in large-scale deployments for LoRaWAN.

Stay tuned as we share additional updates ahead of the event.

Reach out to our team through LinkedIn to book a meeting in advance.

IoT Sparks 2026

We will be at IoT Sparks 2026 in Valencia, Spain on October 7. Two of our teammates will be onsite and available for meetings.

• Xose Pérez will present a keynote presentation showing how AI can help engineers quickly diagnose gateway issues and troubleshoot complex deployments on LoRaWAN.
• Gavin Brown will be there to answer your questions on deployment partnerships, go-to-market strategy, and scaling IoT projects from pilot to production.

Community and Social Updates

Cold Chain Visibility with MOKOSMART

Together with IoT device manufacturer MOKOSMART, we showcased an end-to-end cold chain logistics use case that pairs MOKO's BLE sensing and logging devices for LoRaWAN with WisGate Edge Lite 2. This joint solution brings together cost-efficient item-level sensing, reliable edge connectivity, and scalable infrastructure for temperature-sensitive supply chains.

Developer and Platform Resources

RAKwireless Featured in John Teel’s Recommended LoRa Module Picks

John Teel posted a YouTube video that highlights mistakes to avoid with wireless modules when building connected products. RAKwireless was among the pre-certified LoRa module vendors recommended by the YouTube channel Predictable Designs with John Teel. It is a valuable resource for hardware developers evaluating wireless modules for production.

IoT Uptime Beyond Battery Specs

IoT information hub Talking IoT highlighted how RAKwireless approaches uptime not through raw battery specs, but through guaranteed outcomes with a 7-day SLA, industrial-grade design, and long-life LiFePO4 chemistry built for harsh environments.

As deployments scale, the gap between theoretical capacity and real-world performance becomes impossible to ignore. RAK's approach shifts the focus from raw numbers to accountable power infrastructure where uptime is engineered, not assumed.

Special Highlight

SecurePulse Systems: Scaling Public Safety with LoRaWAN

SecurePulse Systems faced a challenge where it struggled to scale its safety systems across an entire campus or school district. After outgrowing its Zigbee-based setup, it moved to LoRaWAN to build a more scalable and reliable emergency alert system. With fewer gateways, the team was able to cover larger school campuses, improve response speed, and reduce deployment complexity.

Loginex: LoRa 2.4 GHz for Global IoT Logistics

Tech-based logistics service Loginex faced a challenge of dealing with the complexity of different regional frequency plans when it comes to moving shipments across land, air, and sea. What they did was combine LoRa 2.4 GHz with modular gateways and hybrid support, simplifying deployment across different logistics environments while reducing hardware complexity for global shipment and asset tracking.

TL;DR:

• New product launches included RAK3172-F with added 512 KB external flash and FUOTA support and the cost-optimized WisGate Soho Lite.
• Gavin Brown appointed Vice Chair of the LoRa Alliance DSMF.
• Event recaps: Electronex Australia and Hardware Pioneers Max 2026 (ExCeL London).
• Upcoming events: The Things Conference 2026 (Amsterdam, Sep 22–23) and IoT Sparks 2026 (Valencia, Oct 7).
• Meshtastic Device Guide published comparing devices by use case, skill level, and deployment needs.
• Video tutorials on gateway configuration and multi-gateway setup on LoRaWAN.
• WisMesh Station vs WisMesh Station HP video comparison showing deployment tips, placement, and local monitoring.
• Community highlights and use cases: SecurePulse Systems (public safety), MOKOSMART (cold chain visibility), Loginex (global logistics), Virunga (conservation), and Talking IoT (uptime engineering).
• RAKwireless featured in John Teel's YouTube video as a recommended pre-certified LoRa module vendor.

In short: WisDM Metrics is a no-code LoRaWAN gateway monitoring capability inside WisDM, using available WisGate metrics for fleet dashboards without a separate telemetry pipeline. Grafana is among the LoRaWAN visualization tools used for customizable, cross-system observability, but a DIY stack requires teams to build and maintain the surrounding data pipeline. Many teams can use both.

“We Already Have Grafana. Why Do We Need WisDM Metrics?”

“We already collect gateway data and display it in Grafana. Why should we add another monitoring capability?”

That is a fair question. Grafana is established, flexible, and capable of turning many data sources into sophisticated dashboards. But the real comparison is not which platform can draw the better chart. It is how much work sits behind that chart.

Gateway telemetry must be collected, structured, stored, and connected to Grafana. Someone must build and maintain the queries, manage the database and retention policies, and repair the pipeline when an exporter, metric name, or label changes. The dashboard structure must also be designed to represent locations, clients, and gateways as a LoRaWAN fleet.

WisDM Metrics handles that routine monitoring path inside WisDM. Teams can use WisGate metrics already available in WisDM to create projects, dashboards, and widgets without assembling or maintaining a separate monitoring stack.

Grafana provides maximum flexibility for customized, cross-system observability. WisDM Metrics reduces the setup and ongoing maintenance needed for everyday gateway for LoRaWAN visibility.

WisDM Metrics and Grafana Solve Different Parts of the Monitoring Problem

What WisDM Metrics Provides

WisDM Metrics sits inside the existing WisDM gateway management environment, so teams start with gateway metrics, gateway inventory, location relationships, and fleet context already available inside WisDM.

A project can represent a site, customer, or monitoring scenario. Each project can contain multiple dashboards with configurable widgets for gateway health, connectivity, system performance, and LoRaWAN packet metrics. Users can:

• Filter by label: gateway, location, or firmware version
• Filter by metric value: apply a comparison and threshold, for example CPU utilization above 50%
• Select a time range
• Apply count, sum, average, minimum, maximum, or last value
• Choose an appropriate chart, table, or single-value display

Last value is typically paired with a single-value display to answer "what is the last value reported by this gateway," while the aggregations answer "how has the fleet behaved over this period."

No separate data source or dashboard platform needs to be deployed. For dashboard creation, WisDM Metrics provides a no-code workflow: users can create and configure dashboards without writing query-language expressions.

What a Grafana DIY Stack Requires

Grafana is primarily the visualization layer. A complete implementation commonly follows a longer path:

1. Expose, collect, or transform gateway telemetry.
2. Store it in Prometheus, InfluxDB, or another compatible database.
3. Define metric names, labels, and retention.
4. Connect the data source and configure queries.
5. Build panels, variables, and alerts.
6. Secure, back up, monitor, and maintain the stack.

This flexibility is valuable when a company already has a mature observability environment and needs to combine gateway data with application, cloud, or infrastructure metrics.

WisDM Metrics vs. Grafana DIY Stack at a Glance

Comparing WisDM Metrics with a Grafana DIY stack is less about choosing a universal winner than choosing an operating model. Teams researching Grafana alternatives LoRaWAN deployments can use should also consider how much of the monitoring stack they want to build and maintain. 

WisDM Metrics places supported gateway monitoring inside the same environment used to manage WisGate fleets. A Grafana-based stack provides broader control over data sources, queries, transformations, and visualizations, but that freedom also makes the customer responsible for the surrounding pipeline.

The table below shows where each approach is strongest. WisDM Metrics favors faster deployment, simpler dashboard creation, and less monitoring-stack upkeep. Grafana favors highly customized analysis and cross-system observability. Some organizations may choose one as their primary gateway view, while others may use both for different operational needs.

The most important differences appear before and after a chart is displayed: how the data reaches it, who configures it, and who keeps the full monitoring path running.

Setup Effort: Start With Gateway Metrics or Build the Monitoring Path

The difference is the starting point. WisDM Metrics begins inside a WisDM organization. Grafana-based monitoring begins with the team’s telemetry pipeline.

How to Visualize LoRaWAN Data Without Grafana Using WisDM Metrics

Open a project or create one. Each project can contain multiple dashboards.

1. Create a dashboard.

2. Select Add widget and choose a visualization type.

3. Enter the widget details.

4. Select a metric type and metric.

5. Choose an operation, and optionally filter by label or by metric value.

6. Select Retrieve metrics to preview the result, then select Add widget.

After adding widgets, set the dashboard period and, if needed, filter all widgets by gateway serial number. WisDM already has the organization, gateway inventory, locations, and supported metric choices. Users define the monitoring structure through projects, dashboards, and widgets.

A mature Grafana environment may already have most of this foundation in place. The continuing difference is who maintains it.

Read more: Stop Checking Gateways for LoRaWAN® One by One with WisDM Metrics

Query Languages: Selecting a Metric Versus Engineering a Query

Grafana’s query experience depends on the connected data source. Prometheus may use PromQL, while InfluxDB may use InfluxQL or Flux. SQL and other syntaxes may apply elsewhere.

Building a dependable panel requires more than valid syntax. The dashboard administrator must understand:

• Data structure: metric names, labels, and how gateway records are modeled
• Time behavior: windows, aggregations, missing or stale data, and counter resets
• Query design: filtering, grouping, and performance at the required fleet scale

WisDM Metrics places these routine choices in the interface. Users select a supported metric, choose an operation, apply the relevant fleet filter, and set the dashboard time range.

Let’s take this operational question as an example:

How many uplink packets with CRC errors were recorded across gateways at a particular location?

In WisDM Metrics, select the CRC-error metric, apply the location filter, and choose the required aggregation. In a Grafana DIY stack, the team must first ensure that gateways expose the data, map it correctly into the selected database, and write or configure the appropriate query.

Or a threshold question:

Which gateways are reporting CPU utilization above 50%?

In WisDM Metrics, select the CPU utilization metric and apply the value condition. In a Grafana DIY stack, the same question is expressed as a query-language comparison against the collected series. This assumes the metric is exposed, named, and labeled consistently across every gateway in the fleet.

Query languages are not inherently undesirable. They provide powerful control for custom calculations, transformations, and correlations across systems. The advantage of WisDM Metrics is narrower: routine LoRaWAN gateway questions do not require users to understand the underlying query language or maintain its data model.

LoRaWAN Visibility Starts With the Available Gateway Data

Teams evaluating the best IoT dashboard for LoRaWAN should first consider what gateway data the platform can access, organize, and display.

Grafana can visualize, transform, and correlate LoRaWAN metrics when the required gateway telemetry is available through connected data sources. In a DIY stack, the depth of that visibility depends on which gateway statistics are collected and how consistently they are modeled.

Metrics Available Within WisDM

The supplied WisDM reference lists supported metrics across three areas:

• Gateway and system: online and offline states, gateway status, system uptime, CPU utilization, available memory, GPS status, observed GPS satellites, and SD card status
• Network and backhaul: interface uptime, received and transmitted traffic trends, cellular link status and signal level, plus gateways using cellular, Ethernet, or Wi-Fi
• LoRaWAN packets: downlink packets reporting success or error, and uplink packets with CRC errors, valid CRC, or no CRC information

Default filter labels include location, gateway serial number, and firmware version, carrying gateway and fleet context into dashboards. Widgets can also filter on the metric value itself, so a dashboard can show only the gateways that cross a defined threshold.

Reproducing That Depth in Grafana

Grafana can display comparable information when the surrounding stack supplies it. This means deciding which gateway statistics to export, how to model gateways, locations, firmware versions, and interfaces, and how to keep those labels stable across firmware and integration changes.

In an established observability environment where gateway data must sit alongside application, cloud, and infrastructure metrics, that work is often worth doing.

The Long-Term Difference: Who Maintains the Stack?

An existing Grafana environment can reduce the initial setup, especially when telemetry collection, storage, and access controls are already standardized. The longer-term consideration is ownership. A team still needs to keep the WisGate integration working as firmware, metric names, labels, credentials, or infrastructure requirements change.

That responsibility typically covers:

• Data path: Collectors, MQTT processing, exporters, and integrations.
• Data layer: Database performance, retention, backups, and query compatibility.
• Monitoring layer: Dashboard versioning, access controls, certificates, and alerts.

WisDM Metrics is included in all WisDM plans at no additional cost. Grafana is not inherently expensive; it offers open-source and commercial options. The relevant cost comparison is the infrastructure and staff time required to maintain the complete DIY implementation.

Which Monitoring Approach Fits Your Team?

The choice depends on your existing infrastructure, technical resources, and monitoring scope.

• Choose WisDM Metrics when operations teams need no-code WisGate visibility inside WisDM.
• Choose Grafana DIY when observability specialists need cross-system analysis and complete technical control.
• Use both when Grafana covers company-wide observability and WisDM Metrics supports gateway operations.

Existing Grafana users do not need to replace dashboards that already work. WisDM Metrics adds a faster, LoRaWAN-focused layer for the teams managing the gateway fleet each day.

Log in to WisDM and build your first Metrics dashboard.

Frequently Asked Questions

Does WisDM Metrics replace Grafana?

No. WisDM Metrics focuses on routine monitoring of WisGate fleets inside WisDM. Grafana remains useful for highly customized, cross-system observability. Teams can keep their existing Grafana dashboards.

Is WisDM Metrics included in my current WisDM plan?

Yes. WisDM Metrics is included in all WisDM plans at no additional cost.

Do I need PromQL or another query language?

No. Users select a supported metric, operation, time range, and filters through the WisDM interface. This workflow does not require PromQL, InfluxQL, Flux, SQL, or another query language.

Can I filter by metric value, not just by label?

Yes. In addition to label filters such as location, gateway serial number, and firmware version, widgets can filter on the metric value itself using a comparison and threshold.  For example, showing only gateways reporting CPU utilization above 50%.

Which WisGate gateways and firmware versions support Metrics?

WisDM Metrics uses data from supported gateways managed in WisDM. Current WisDM requirements specify WisGateOS 1.2.2 or later, with the latest firmware recommended. Hardware-specific metrics depend on the gateway’s available features and interfaces.

What LoRaWAN metrics are available at launch?

Launch metrics include downlink packets reporting success or error and uplink packets with valid CRC, CRC errors, or no CRC information. The complete list appears in the WisDM Metrics documentation.

Choosing an indoor gateway for LoRaWAN often starts with channel capacity, available backhaul, power input, network server support, and remote management.

For US enterprise projects using LTE, those specifications are only part of the comparison. Buyers may also need to confirm the exact cellular model, carrier status, antenna arrangement, remote administration options, and the documentation required for internal approval.

The WisGate Edge Lite 2 Verizon RAK7268CV2-V is designed for US deployments. Its position is clearest when a project combines indoor 8-channel coverage, Verizon LTE backhaul, and a documented carrier-certified model for procurement or IT review.

For a closer explanation of how LTE compatibility differs from carrier certification, read What Verizon Certification Means for Gateway Deployments for LoRaWAN^®.

Highlight Summary

What to Compare in an Indoor Gateway for US LTE Deployments

A useful comparison should connect published specifications to the deployment process. The questions below help separate general feature matching from requirements that affect installation, approval, and long-term operation.

How Our Verizon-Certified Gateway Compares with Other Indoor Gateways for LoRaWAN

There is no single best gateway for LoRaWAN. RAK7268CV2-V, Kerlink, Milesight UG65, MultiTech Conduit, and TEKTELIC KONA gateways address different combinations of connectivity, management, resilience, integration, and carrier requirements.

The comparison reflects official manufacturer materials available as of July 2026. Before purchasing, confirm the exact SKU, modem, region, accessories, and current carrier documentation.

What the Comparison Shows

WisGate Edge Lite 2 Verizon does not stand apart because every individual capability is unique. The competing gateways also provide combinations of LTE, PoE, network server support, remote management, or resilience features.

Its advantage becomes clearer when the decision combines three requirements:

1. An indoor 8-channel gateway for LoRaWAN
2. LTE backhaul intended for Verizon-network use in the United States
3. A documented Verizon-certified variant that can support procurement and IT review

Certification does not replace an organization’s cybersecurity, vendor, data-handling, or network review. It addresses the carrier-status question while the remaining approval checks continue through the normal process.

Which Buyers Benefit Most from the WisGate Edge Lite 2 Verizon?

Facility and Building Managers

RAK7268CV2-V fits smart building, HVAC, occupancy, leak detection, and energy-monitoring projects that use Verizon LTE. Its external LTE antenna helps improve cellular signal reception compared with an integrated internal antenna. This matters when the gateway is installed in a utility room, equipment area, cabinet, or another location with weaker reception. WisDM also allows remote management when regular site visits are inconvenient.

System Integrators

A distinct Verizon-certified model gives integrators a repeatable part number for proposals, bills of materials, deployment checklists, and customer approval packages. Teams can reference the same carrier status, antenna arrangement, power range, and management platform across similar projects.

Enterprise IT and Procurement Teams

The documented carrier position gives review teams a clearer starting point than a general claim that a gateway supports LTE. Secure MQTT/TLS, WisDM management, pre-provisioning, and supported forwarding modes provide additional information for operational and security assessment.

IoT Developers and Solution Architects

RAK7268CV2-V supports a built-in network server, Basics Station, Packet Forwarder, and MQTT bridging with TLS. These options allow architects to assess the gateway for local, private-cloud, or third-party network server designs while retaining Verizon LTE backhaul.

When Another Gateway May Be the Better Fit

WisGate Edge Lite 2 Verizon is not automatically the right choice for every indoor deployment. Another model may deserve closer evaluation in the following cases:

• No cellular backhaul is required. An Ethernet or WiFi gateway, including RAK7268V2, may meet the requirement with less hardware than an LTE model.
• The project uses another carrier. Verify the carrier-approved hardware list and the exact cellular configuration before selecting a gateway.
• Backup power is the leading requirement. A KONA Micro configuration with battery backup may warrant closer review.
• The organization already uses another gateway platform. Existing device management, provisioning, and support workflows may outweigh the benefit of changing vendors.
• The installation is exposed to outdoor conditions. Select an outdoor-rated gateway rather than treating an indoor enclosure as suitable for weather exposure.

Learn more: How to Choose the Right Gateway for Your IoT Deployment

Final Gateway Selection Checklist

Before selecting an indoor gateway for a US deployment, confirm the following requirements:

• Will the primary backhaul use Ethernet, WiFi, LTE, or a combination?
• Which US carrier will provide the cellular connection?
• Is certification required for the exact gateway model?
• Does the site need external LTE antennas or a specific mounting arrangement?
• Which power source and DC input range are available?
• How will the team provision, monitor, diagnose, and update deployed gateways?
• Which network server and forwarding method will the architecture use?
• What documentation must procurement, IT, or the customer approve?

Choose the WisGate Lite 2 Verizon When the Requirements Converge

For projects using Verizon LTE, RAK7268CV2-V brings carrier certification into the same model as external LTE antennas, PoE, 9–36 V DC input, secure data forwarding, WisDM fleet management, pre-provisioning, network server flexibility, and frame buffering.

Its strongest case is not based on a longer feature list. Its value comes from combining Verizon certification with enterprise gateway management and flexible power and backhaul options for indoor US deployments.

For many enterprise IoT projects in the United States, a gateway that “works on LTE” is not always enough.

The device may support LTE backhaul, connect the sensors, forward data, and run the right gateway software. But for real deployments, especially those tied to enterprise networks, facility operations, or system integrator projects, technical compatibility is only one part of the approval process.

Procurement teams may ask whether the gateway is carrier-certified. IT teams may need documentation before allowing the device onto an approved hardware list. Facility teams may want assurance that cellular backhaul will work reliably on the network they already use.

That is where carrier certification matters.

For teams deploying LoRaWAN over Verizon LTE, Verizon certification provides an important layer of confidence for procurement, IT approval, and enterprise rollout.

WisGate Edge Lite 2 Verizon RAK7268CV2-V offers a Verizon-certified indoor gateway option with LTE Cat 4, external LTE antenna support, PoE, and WisDM for enterprise rollout and remote management.

Why Carrier Certification Matters in US Enterprise IoT

Carrier certification matters because enterprise IoT deployments often need to pass more than a technical test.

A gateway may support LTE, but that does not automatically mean it fits a company’s procurement rules, IT security review, or approved device process. In many US organizations, especially those already using Verizon for enterprise connectivity, carrier-certified hardware is easier to approve, specify, and standardize.

That is the practical difference between LTE support and carrier certification. LTE support means the hardware and modem are capable of operating on compatible LTE networks. Carrier certification means the device has completed the carrier's certification program and has been validated against that carrier's requirements for operation on its network.

For small tests, that difference may not matter. For enterprise rollouts, multi-site deployments, or customer projects where approval delays can affect schedules, it can shape the gateway decision from the start.

Meet The Verizon-Certified WisGate Edge Lite 2 RAK7268CV2-V Variant

The WisGate Edge Lite 2 RAK7268CV2-V is the Verizon-certified variant of the WisGate Edge Lite 2 product line. It is built for US deployments where LoRaWAN coverage, LTE backhaul, and carrier approval need to work together before rollout.

WisGate Edge Lite 2 Verizon keeps the core WisGate Edge Lite 2 feature set while adding the certification path needed for Verizon-network deployments.

WisGate Edge Lite 2 Verizon is especially relevant when the project needs:

• Indoor 8-channel LoRaWAN coverage
• LTE Cat 4 backhaul
• Verizon certification for US deployments
• External LTE antenna support
• PoE and 9-36V DC input
• WisGateOS 2 and WisDM cloud management
• Zero Touch Provisioning
• Secure MQTT over TLS and LoRa® frame buffering
• Compatibility with major LoRaWAN network servers

What’s New Compared with RAK7268V2 and RAK7268CV2?

The main difference is the deployment requirement each variant is built for. RAK7268V2 is for indoor sites that already have Ethernet or WiFi. RAK7268CV2 adds LTE Cat 4 for cellular backhaul. RAK7268CV2-V adds Verizon certification for US deployments where carrier approval is required or preferred.

WisGate Edge Lite 2 Verizon does not create a separate gateway category. It adds a Verizon-certified option to the WisGate Edge Lite 2 lineup, with external LTE antenna support and 9–36V DC input for deployments that need stronger cellular reception, wider power flexibility, and carrier-approved hardware.

How Our Verizon-Certified Gateway for LoRaWAN Reduces Procurement and IT Approval Friction

For enterprise IoT, deployment delays often happen before the gateway is installed.

A facility team may know where sensors are needed. A system integrator may already have the network design. An IT team may know which LoRaWAN network server or cloud platform will be used. But the project can still pause if the gateway cannot pass device approval, procurement review, or carrier requirements.

WisGate Edge Lite 2 helps reduce that friction by giving teams a Verizon-certified indoor gateway option for US deployments.

For organizations already using Verizon enterprise connectivity, this helps align gateway deployment for LoRaWAN with existing carrier requirements instead of treating approval as a separate obstacle.

Deployment Benefits: External LTE Antenna, ZTP, WisDM, Secure MQTT/TLS, and Frame Buffering

Verizon certification helps with approval, but RAK7268CV2-V also needs to work well in real indoor IoT environments. These features support reliable LTE backhaul, easier rollout, remote management, and secure LoRaWAN data handling.

External LTE Antenna Support

Indoor LTE performance depends on gateway placement, wall materials, cabinet location, and signal quality. RAK7268CV2-V supports two external LTE antennas to help improve reception in weak-signal indoor areas, equipment rooms, and industrial spaces.

PoE and 9–36V DC Input

RAK7268CV2-V supports PoE and 9–36V DC input, giving teams more flexibility when powering the gateway through Ethernet infrastructure or available facility power.

Zero Touch Provisioning

ZTP helps reduce manual setup by allowing the gateway to arrive pre-configured for the intended deployment. This is useful for repeatable or multi-site rollouts. Instead of configuring every gateway individually on site, teams can prepare a consistent configuration before units are deployed.

WisDM Cloud Management

WisDM lets teams monitor, configure, and update gateways remotely. This helps reduce unnecessary site visits and supports easier management across multiple deployed gateways.

Secure MQTT/TLS and Network Server Flexibility

RAK7268CV2-V supports secure MQTT/TLS and common LoRaWAN network server options, including ChirpStack, The Things Stack, AWS IoT Core for LoRaWAN, Actility, and Loriot.

LoRa Frame Buffering

Buffered packets are forwarded automatically once connectivity is restored. This supports more reliable monitoring for smart buildings, equipment rooms, and remote indoor sites.

Which Version Should You Choose?

Choose the WisGate Edge Lite 2 variant based on the deployment environment, backhaul requirement, and approval requirement.

Also, see how we compare the RAK7268CV2-V with other indoor gateways.

For teams that are not sure how to choose the right gateway, the deployment checklist should start with four questions:

1. Will the gateway use Ethernet, WiFi, or LTE?
2. Is the site using Verizon LTE in the US?
3. Does procurement or IT require carrier-certified hardware?
4. Does the installation need external LTE antenna support or wider DC input?

If the answer includes Verizon LTE and certification requirements, RAK7268CV2-V is the best fit.

Frequently Asked Questions: Verizon, Other Carriers, Power Input, Indoor/Outdoor Use, and Pricing

Is RAK7268CV2-V a completely new gateway?

No. RAK7268CV2-V is not a separate gateway family. It is the Verizon-certified variant of WisGate Edge Lite 2 Verizon, designed for US deployments where carrier approval is required or preferred.

What is the difference between RAK7268V2, RAK7268CV2, and RAK7268CV2-V?

RAK7268V2 is the non-LTE version for Ethernet and WiFi deployments. RAK7268CV2 adds LTE Cat 4 connectivity for cellular backhaul. RAK7268CV2-V is the Verizon-certified version for US deployments where Verizon certification is required or preferred.

Does RAK7268CV2-V only work on Verizon?

Verizon certification does not prevent the gateway from operating on other compatible LTE networks. Compatibility with another carrier depends on that carrier's supported LTE bands, SIM policies, and certification requirements.

Why choose the Verizon-certified version if the standard CV2 already has LTE?

Choose RAK7268CV2-V when certification matters for the deployment. A standard LTE gateway may be technically suitable, but enterprise buyers may still need formal carrier approval before procurement, IT, or deployment teams can move forward.

Does WisGate Edge Lite 2 Verizon support PoE?

Yes. WisGate Edge Lite 2 Verizon includes PoE, which is useful when Ethernet and power can be delivered through the same network path.

What power input does RAK7268CV2-V support?

The WisGate Edge Lite 2 Verizon lineup supports PoE and DC power input options. For RAK7268CV2-V, the available DC input range is 9–36V.

Is WisGate Edge Lite 2 Verizon for indoor or outdoor use?

WisGate Edge Lite 2 Verizon is an indoor gateway. For outdoor or rugged deployments that need IP67 protection, the product content points to rugged RAK gateway options such as WisGate Soho Pro.

What network servers are supported?

WisGate Edge Lite 2 Verizon supports multiple network server and protocol options, including the built-in LoRa Network Server, UDP Packet Forwarder, Basics Station, MQTT Bridge, secure MQTT with TLS encryption, ChirpStack, The Things Stack / The Things Network, AWS IoT Core for LoRaWAN, Actility, and Loriot.

Managing IoT infrastructure becomes harder as deployments grow. In Microsoft’s IoT Signals survey, conducted with IoT Analytics, 72% of manufacturing respondents named scalability as their main concern.

For LoRaWAN operators, that challenge includes seeing how individual gateways are behaving across the fleet. 

A deployment may appear operational while some gateways begin showing weaker cellular connections, rising CRC errors, unusual traffic, or reduced available memory. When every gateway must be opened separately, it becomes difficult to identify which one needs attention or how its readings compare with the rest of the fleet.

WisDM Metrics changes that workflow. It is a no-code gateway fleet monitoring into WisDM that brings data from selected gateways into one fleet-wide view.

See the Fleet Before Opening Gateway Pages

A WisDM Metrics dashboard gives you a fleet-wide starting point. You can review online and offline status, gateway resources, connectivity, and LoRaWAN performance without moving between individual gateway pages.

You begin by selecting the period and gateways you want to review. These dashboard-level controls update the scope across the widgets. This allows the same dashboard to examine the wider fleet or a narrower set of gateways without rebuilding each chart.

Charts reveal how measurements change over time, while single-value widgets summarize important conditions at a glance. When an unusual value or trend appears, tables and filters help identify the gateways contributing to it. Data can be narrowed using labels such as location, gateway serial number, and firmware version.

From there, you can open the affected gateway’s device page for closer examination. The workflow moves from reviewing fleet conditions, spotting an exception, narrowing the results, and identifying the relevant gateway to beginning device-level troubleshooting.

WisDM Metrics does not replace detailed gateway investigation. It helps you answer the question that comes first: Which gateway should I investigate?

Build Dashboards Without Query Language

WisDM Metrics organizes monitoring through projects, dashboards, and widgets.

Projects create a workspace for related monitoring needs, such as a customer deployment, region, or internal team.

Each project can contain multiple dashboards, so operators can separate fleet availability, cellular backhaul, gateway resources, and LoRaWAN packet behavior instead of placing every measurement in one view.

Each dashboard is built from individual widgets. A widget displays the measurements and visualization needed to answer a specific operational question, whether that means following a trend, comparing gateway values, or identifying readings that require closer attention.

You can select the relevant gateways, metric, filters, and chart type directly through the WisDM interface. A preview shows how the widget will appear before it is added to the dashboard, so no query language is required.

Choose the View That Answers the Question

WisDM Metrics supports several widget types for presenting gateway data. The right view depends on whether you need one fleet value, a trend over time, a comparison, a distribution, or the gateways behind a result.

Value chart

A value chart highlights one measurement in a large, readable format. Use it when you need an immediate answer to a direct question, such as how many industrial gateways for LoRaWAN meet a selected condition.

Line chart

A line chart follows a measurement continuously across the selected period. It helps you identify spikes, drops, repeated fluctuations, or gradual movement that may not be obvious from a single value.

Bar chart

A bar chart makes values across separate intervals easier to compare. You can quickly see which periods recorded higher or lower measurements without following a continuous line.

Stacked bar chart

A stacked bar chart displays related measurements within the same intervals. It helps you compare the total value while also seeing how each measurement contributes to it.

Area chart

An area chart emphasizes the magnitude of a measurement as it changes over time. The filled area makes overall volume, sustained increases, and sharp changes easier to recognize.

Pie chart

A pie chart shows how a total is distributed among a small number of categories. You can compare each category’s share using the segment size, value, and percentage shown in the legend.

Table

A table identifies the specific gateways contributing to a result. You can review gateway names alongside details such as location, serial number, EUI, and the selected measurement, then open the relevant device or location page.

Widget settings such as legends, thresholds, metric colors, and filters are configured in the widget builder. A live preview shows how the selected view will present the data before it is added to the dashboard.

This structure keeps monitoring organized as deployments grow. One project can hold a fleet-wide health dashboard alongside narrower dashboards for a particular location, customer, or operational requirement. Teams can begin with a broad view, then move to the dashboard and widget that provide the detail needed for investigation.

View Gateway Health and LoRaWAN Operations Together

WisDM Metrics brings gateway health and LoRaWAN performance into the same dashboard. Its measurements cover four main areas of fleet monitoring:

For the complete list, see the supported WisDM metrics and filter labels.

Templates provide a starting point for common monitoring requirements. The System Overview shown here brings several gateway conditions together, including offline state, reboot activity, OTA errors, and SD card status.

Viewing these measurements together adds context when a gateway’s behavior changes. A gateway may remain online while its available memory declines, cellular connection weakens, or LoRaWAN packet errors increase. WisDM Metrics helps you recognize those conditions and determine which gateway requires closer examination.

Build Your First Dashboard in WisDM

WisDM Metrics is built into WisDM rather than offered as a separate monitoring product. Select the gateways relevant to your deployment, add the measurements you need, and organize each dashboard around the operational questions your team needs to answer. 

Not sure where to begin? Start with one of these dashboard setups:

Fleet Availability

Bring gateway online state, system uptime, offline gateways, and frequent reboots into one view. This dashboard helps you identify availability issues and determine which gateways require closer examination.

Backhaul Health

Track cellular signal, connection status, network interface uptime, and received or transmitted traffic. Reviewing these measurements together helps reveal connectivity changes affecting particular gateways or locations.

LoRaWAN Packet Quality

Monitor uplinks with valid CRC, uplinks with CRC errors, successful downlink reports, and downlink reporting errors. This dashboard provides a focused view of changes in packet handling across the selected fleet.

Every WisDM plan includes Metrics at no additional cost.

Frequently Asked Questions About WisDM Metrics

What is WisDM Metrics?

WisDM Metrics is the fleet-level monitoring and dashboard capability built into WisDM. It brings data from selected gateways into one view, helping teams monitor fleet conditions, identify exceptions, and determine which gateways require closer investigation.

Which gateway metrics can it monitor?

WisDM Metrics covers gateway resources and system state, including CPU utilization, available memory, system uptime, online status, and storage conditions. It also monitors network interface uptime and traffic, cellular signal and connection status, LoRaWAN uplink and downlink packet statistics, and deployment details such as GPS status, location, gateway serial number, and firmware version.

Can I filter dashboards to specific gateways or locations?

Yes. Dashboard-level controls let you select the gateways included in the view and adjust the scope without rebuilding each widget. Data can also be narrowed using supported labels such as location, gateway serial number, and firmware version.

Can WisDM Metrics compare different periods?

Yes. Metrics Comparison lets you choose two periods and select the dashboard widgets you want to compare. Results appear side by side and can include average, minimum, and maximum values, along with numerical and percentage changes. Comparisons can also be saved, reopened, renamed, exported as a PDF, or deleted.

Is WisDM Metrics included with every WisDM plan?

Yes. Every WisDM plan includes Metrics at no additional cost.

Table of Contents

• What Is the Best Meshtastic Device in 2026?
• Quick Answer: Best Meshtastic Devices by Category
• Best for Modular and Budget Builds
• Best for Trackers & Everyday Carry (EDC)
• Best for Standalone Handhelds
• Best for Low-Power & DIY Nodes
• Best for Repeaters & Range Extension
• Best for High-Power Deployments
• Best for Gateways & MQTT
• How to Choose the Best Meshtastic Device for Your Setup
• Example Meshtastic Setups by Use Case
• Where to Buy Meshtastic Devices
• RAKwireless vs Other Popular Meshtastic Devices
• FAQ: Best Meshtastic Devices in 2026

What Is the Best Meshtastic Device in 2026?

The best Meshtastic device is not always the most expensive or most powerful option. The right choice depends on what you want to build, where you plan to use it, and how much setup work you want to handle.

Some users need an affordable Meshtastic starter kit for learning. Others need a compact tracker for everyday carry, a handheld communicator for hiking, a solar repeater for better coverage, a gateway for MQTT workflows, or a board-level development kit for a custom IoT project.

Meshtastic devices use LoRa® radio technology to create off-grid mesh communication networks. Instead of relying on cellular towers or internet access, devices can pass messages through nearby nodes in the mesh. This makes Meshtastic useful for hiking groups, neighborhoods, farms, field teams, events, emergency kits, remote sensors, and community communication projects.

For beginners, the main question is simple: Which Meshtastic device should I buy in 2026 based on my use case, budget, and skill level?

This guide compares the best Meshtastic devices by category, including beginner starter kits, compact trackers, standalone handhelds, low-power DIY boards, outdoor repeaters, high-power nodes, gateways, MQTT stations, coverage-testing setups, and sensor-focused builds.

↑ Back to top

Quick Answer: Best Meshtastic Devices by Category

Quick recommendation:

Diagram of six Meshtastic device choices: modular kit, tracker, handheld, repeater, gateway station, and WisBlock nodes.

↑ Back to top

Best for Modular and Budget Builds: WisBlock Meshtastic Starter Kit, WisMesh RAK3312 Starter Kit, and WisMesh RP2040 Starter Kit

Modular starter kits are best for users who want an affordable way to learn Meshtastic hardware, test different modules, compare antennas, and build a custom node. They are a good fit for technical beginners, makers, and developers, but they are not the easiest choice for every first-time user. Because these kits use exposed circuit boards and modular components, users should be comfortable handling electronics and following setup documentation.

Good modular and budget choices include:

WisBlock Meshtastic Starter Kit

The WisBlock Meshtastic Starter Kit is best for users who want a modular WisBlock-based starting point. It is a strong choice for learning how Meshtastic hardware works, testing different device roles, and experimenting with modules, antennas, enclosures, batteries, and sensors.

WisBlock Meshtastic Starter Kit

WisMesh RAK3312 Starter Kit

The WisMesh RAK3312 Starter Kit is best for users who want an ESP32-S3-based modular Meshtastic kit with WiFi, BLE, and LoRa®. It is a good fit for private LoRa mesh testing, off-grid communication experiments, and users who want a budget-friendly board-level setup that can grow into different Meshtastic roles.

WisMesh RAK3312 Starter Kit

WisMesh RP2040 Starter Kit

The WisMesh RP2040 Starter Kit is best for users who prefer a Raspberry Pi® RP2040-based development path. It is useful for prototyping, sensor-ready builds, and beginner-to-intermediate users who want to test Meshtastic with optional GNSS or sensor modules.

WisMesh RP2040 Starter Kit

Choose a starter kit instead of a ready-to-use handheld when you want to learn, build, and customize. A finished pocket device is better when you want an enclosure, battery, and a more complete form factor from the beginning.

• Best for: Modular learning, budget-friendly builds, prototyping, and technical beginners
• Why users choose it: Starter kits give users more control over hardware, antennas, modules, enclosures, and device roles.
• Choose this if: You are comfortable handling circuit boards and want to build or customize a Meshtastic node.
• Consider another option if: You want a ready-to-use device with enclosure, battery, and minimal hardware handling.
• Recommended RAKwireless fit: WisBlock Meshtastic Starter Kit, WisMesh RAK3312 Starter Kit, or WisMesh RP2040 Starter Kit

↑ Back to top

Best for Trackers & Everyday Carry (EDC): WisMesh Tag

Meshtastic trackers and everyday carry devices are useful when you need a compact node for location sharing, outdoor trips, field work, bags, bikes, equipment, or remote assets. For RAKwireless, the main tracker and EDC option is the WisMesh Tag.

WisMesh Tag

WisMesh Tag is a portable Meshtastic tracker built for users who want a small, ready-to-go device for location tracking and mesh messaging. It is a strong fit for hiking, bikepacking, field teams, asset tracking, and everyday carry because it combines a compact card-style form factor with GNSS, Bluetooth configuration, integrated antennas, and a durable enclosure.

WisMesh Tag is especially useful when location sharing matters more than direct messaging. It is not meant to replace a handheld communicator with a larger display or keyboard. Instead, it works best as a small tracker that can stay with a person, bag, bike, tool case, vehicle, or outdoor asset.

WisMesh Tag

WisMesh Tag

Key reasons users choose WisMesh Tag include:

• Compact, card-style design for everyday carry
• Built-in GNSS for location tracking
• 1000mAh internal battery for portable use
• IP66 enclosure for outdoor conditions
• Integrated LoRa, BLE, and GPS antennas
• Bluetooth configuration through the Meshtastic app
• USB-C and magnetic charging options
• Reset/bootloader button for easier firmware handling
• Classic Black and limited Blue Edition color options

Choose WisMesh Tag if you need a small Meshtastic tracker for location sharing, outdoor activities, bags, bikes, tools, field teams, or asset visibility.

• Best for: Everyday carry, outdoor tracking, bags, bikes, equipment, and field teams
• Why users choose it: WisMesh Tag is compact, durable, easy to carry, and built for Meshtastic location tracking.
• Choose this if: You need a small tracker for location sharing or asset visibility.
• Consider another option if: You need a keyboard, larger display, or phone-free messaging.
• Recommended RAKwireless fit: WisMesh Tag

↑ Back to top

Best for Standalone Handhelds: WisMesh Pocket V2, WisMesh Pocket Mini, WisMesh TAP V2, WisMesh TAP, or WisMesh Board ONE Pocket

Standalone Meshtastic handhelds are useful when users want more than a small tracker. These devices are better for messaging, checking device status, testing field communication, or using Meshtastic with less dependence on a phone.

Good standalone handheld options include:

WisMesh Pocket V2

The WisMesh Pocket V2 is a strong, ready-to-use choice for users who want a compact Meshtastic device with an enclosure, GNSS module, acceleration sensor, OLED display, LoRa® antenna, and rechargeable battery. It is a good fit for off-grid communication, outdoor testing, and users who want a more complete pocket device.

WisMesh Pocket V2

WisMesh Pocket Mini

The WisMesh Pocket Mini is better for users who want the smallest and simplest pocket option. It is lighter and smaller than the WisMesh Pocket V2, with a 1000mAh battery and internal antennas. It does not include an OLED display or location-tracking functionality, so it is best for users who want a compact Meshtastic client rather than a full handheld communicator.

WisMesh Pocket Mini

WisMesh TAP V2

The WisMesh TAP V2 is the best fit when direct messaging matters most. It includes a touchscreen, on-screen keyboard, GNSS/GPS, SD card map function, buzzer, SX1262 LoRa® connectivity, and a 3200mAh battery. Choose it for phone-free messaging, field coordination, emergency response, and outdoor communication.

WisMesh TAP V2

WisMesh TAP

The WisMesh TAP is a touchscreen Meshtastic device with GNSS and an on-screen keypad. It is a good option for users who want a handheld interface for off-grid communication.

The WisMesh TAP V2 is the stronger choice for users who want newer Meshtastic UI features, multi-color display, map function, and more complete field features.

WisMesh TAP

WisMesh TAP

WisMesh Board ONE Pocket

The WisMesh Board ONE Pocket is best for users who want a ready-to-use Meshtastic node in a durable, enclosed form factor. It comes pre-assembled, includes a LoRa® antenna, OLED display, 1000mAh battery, and an optional GNSS module. This makes it a good choice for users who want a simple enclosed device without coding, wiring, or 3D printing.

WisMesh Board ONE Pocket

Choose a handheld if messaging, screen visibility, or direct device interaction matters more than simple location tracking. Choose the WisMesh Tag instead if you only need a compact tracker for bags, bikes, equipment, or asset visibility.

• Best for: Field messaging, hiking groups, outdoor testing, emergency kits, and phone-free communication
• Why users choose it: These devices give users more direct interaction than a basic tracker.
• Choose this if: You want a portable Meshtastic device with a screen, touchscreen, keypad, OLED display, or more complete enclosure.
• Consider another option if: You only need compact tracking or asset visibility.
• Recommended RAKwireless fit: WisMesh Pocket V2, WisMesh Pocket Mini, WisMesh TAP V2, WisMesh TAP, or WisMesh Board ONE Pocket

↑ Back to top

Best for Low-Power & DIY Nodes: WisMesh Base Board, WisMesh Board ONE, WisBlock Meshtastic Starter Kit, and WisMesh RAK3312 Starter Kit

Low-power Meshtastic boards and DIY nodes are best for users who want more control over the enclosure, antenna, battery, sensors, and device role. These options are useful for custom nodes, remote placements, solar-ready builds, sensor projects, and users who want to experiment beyond a finished handheld device.

Good low-power and DIY options include:

WisMesh Base Board

The WisMesh Base Board is a strong fit for builders who want a flexible board-level starting point. It is useful for users who want to choose their own modules, add sensors, connect an OLED display or GNSS module, and design a custom enclosure or power setup.

WisMesh Base Board

WisMesh Board ONE

The WisMesh Board ONE is best for users who want a compact Meshtastic board with more built-in convenience. It works well for DIY users who still want a cleaner path toward a finished node, especially when paired with an enclosure, antenna, battery, and optional GNSS.

WisMesh Board ONE

WisBlock Meshtastic Starter Kit

The WisBlock Meshtastic Starter Kit is a good choice for users who want a modular WisBlock-based learning path. It gives builders a practical way to test Meshtastic roles such as client, tracker, router, repeater, or sensor node before moving into a more custom build.

WisBlock Meshtastic Starter Kit

WisMesh RAK3312 Starter Kit

The WisMesh RAK3312 Starter Kit is best for users who want an ESP32-S3-based Meshtastic build with Wi-Fi, BLE, and LoRa®. It is a good fit for off-grid communication testing, private mesh experiments, and users who want a starter kit that can grow into different Meshtastic roles.

WisMesh RAK3312 Starter Kit

Choose one of these board-level options if you want to build around a specific power source, antenna setup, enclosure, or sensor requirement. Choose a ready-to-use handheld instead if you want a finished device with minimal assembly.

• Best for: Solar nodes, remote nodes, custom enclosures, sensor projects, and developer builds
• Why users choose it: Board-level devices give more control over power, size, sensors, and enclosure design.
• Choose this if: You want to build a custom Meshtastic device around a specific role.
• Consider another option if: You want a finished product with minimal setup.
• Recommended RAKwireless fit: WisMesh Base Board, WisMesh Board ONE, WisBlock Meshtastic Starter Kit, or WisMesh RAK3312 Starter Kit

↑ Back to top

Best for Repeaters & Range Extension: WisMesh Repeater and WisMesh Repeater Mini

Repeaters are useful when a Meshtastic network needs better coverage across farms, neighborhoods, outdoor sites, campsites, events, remote assets, or community mesh projects. Range depends on terrain, buildings, antenna height, placement, power, and local regulations, so a well-placed repeater can often improve a mesh more than simply adding another handheld device.

Good repeater and range-extension options include:

WisMesh Repeater

The WisMesh Repeater is the better choice for long-term outdoor coverage. It is designed for reliable Meshtastic range extension in remote or fixed locations, with an outdoor-ready enclosure, solar battery life options, Bluetooth Low Energy setup, and mounting options for wall or pole installation. Choose it for farms, remote properties, outdoor infrastructure, and larger mesh deployments that need stable coverage.

WisMesh Repeater

WisMesh Repeater Mini

The WisMesh Repeater Mini is better for portable or quicker deployments. It combines a compact enclosure, rechargeable battery, integrated solar panel, and mounting options, making it useful for campsites, temporary field setups, events, trail coverage, and smaller outdoor networks. Choose it when you need a lighter repeater that is easier to place and move.

WisMesh Repeater Mini

Choose a repeater when handheld nodes are blocked by hills, trees, buildings, distance, or poor antenna placement. For the best results, place the repeater higher, reduce obstructions, check the correct frequency region, and plan the power source before installation.

• Best for: Farms, neighborhoods, outdoor sites, events, hiking areas, and community mesh coverage
• Why users choose it: Repeaters extend coverage by relaying messages from better locations.
• Choose this if: You need better range across a wider area.
• Consider another option if: You only need short-range testing or personal carry use.
• Recommended RAKwireless fit: WisMesh Repeater or WisMesh Repeater Mini

↑ Back to top

Best for High-Power Deployments: WisMesh 1W Booster Starter Kit, 1W Module for LoRa with SX1262 + SKY66122 Booster, and WisMesh Station/WisMesh Station HP

High-power Meshtastic deployments are best for advanced users planning longer-range links, backbone nodes, fixed outdoor installations, or coverage across wide areas. These setups need more planning than beginner nodes because antenna placement, frequency region, transmit power limits, power source, enclosure, and site conditions all affect performance.

Good high-power options include:

WisMesh 1W Booster Starter Kit

The WisMesh 1W Booster Starter Kit is a good fit for users who want to build a higher-power Meshtastic node for long-range testing or backbone-style deployments. It is better suited for advanced users who understand antenna placement, power planning, and local transmit power rules.

WisMesh 1W Booster Starter Kit

1W Module for LoRa® with SX1262 + SKY66122 Booster

The 1W Module for LoRa® with SX1262 + SKY66122 Booster is best for builders who want to add a 1W LoRa radio module into a custom Meshtastic or WisBlock-based setup. Choose this when you want more control over the board, enclosure, power system, and final node design.

1W Module for LoRa® with SX1262 + SKY66122 Booster

WisMesh Station/WisMesh Station HP

WisMesh Station/WisMesh Station HP is a stronger fit for fixed infrastructure, long-range backbone planning, gateway-adjacent deployments, outdoor network anchors, and users looking for a gateway for Meshtastic. It is better for users who need a more complete station-style option rather than a board-level booster build.

WisMesh Station/WisMesh Station HP

High-power hardware is not always the first fix for poor range. In many deployments, better antenna height, clearer line of sight, improved repeater placement, or a better power plan can solve the problem before increasing transmit power.

Use high-power Meshtastic options only where they are allowed. Always check the correct frequency region, transmit power limits, antenna gain rules, and local regulations before buying or deploying high-power hardware.

• Best for: Long-range backbone nodes, fixed outdoor deployments, advanced range planning, and high-power Meshtastic builds
• Why users choose it: High-power options can help advanced users plan wider-area Meshtastic coverage when placement, antenna, and compliance requirements are handled properly.
• Choose this if: You need a high-power node, station, or booster-based build for long-range planning.
• Consider another option if: A better antenna location, elevated repeater, or standard outdoor repeater would solve the range issue.
• Recommended RAKwireless fit: WisMesh 1W Booster Starter Kit, 1W Module for LoRa^® with SX1262 + SKY66122 Booster, or WisMesh Station/WisMesh Station HP

↑ Back to top

Best for Gateways & MQTT: WisMesh WiFi MQTT Gateway, WisMesh Ethernet MQTT Gateway, WisMesh Station/WisMesh Station HP, or WisMesh Pi HAT

Gateways are useful when a Meshtastic network needs to connect with MQTT, dashboards, cloud workflows, monitoring tools, or fixed infrastructure. These devices are not always required for simple offline messaging, but they become important when users need visibility, data flow, or a stable bridge between Meshtastic devices and external systems.

Good gateway and MQTT options include:

WisMesh WiFi MQTT Gateway

The WisMesh WiFi MQTT Gateway is best for users who want to connect Meshtastic devices to MQTT or cloud workflows over WiFi. It is a good fit for sending sensor data, location information, and text messages to an MQTT broker without relying on Ethernet cabling. Choose it for labs, homes, small deployments, farm monitoring, and locations where WiFi is available and stable.

WisMesh WiFi MQTT Gateway

WisMesh Ethernet MQTT Gateway

The WisMesh Ethernet MQTT Gateway is better when reliability matters most. It uses a wired Ethernet connection, making it a stronger choice for fixed infrastructure, industrial environments, mission-critical networks, and sites where WiFi may be unstable. Choose it when the gateway needs to stay connected for continuous MQTT data transmission.

WisMesh Ethernet MQTT Gateway

WisMesh Station/WisMesh Station HP

WisMesh Station/WisMesh Station HP is a stronger fit for fixed stations, long-range network anchors, and more advanced deployments. The standard station works well for general fixed infrastructure, while the HP version is better for users planning higher-power or wider-area deployments where legally allowed. Choose this option when the station needs to serve as a more complete Meshtastic infrastructure point.

WisMesh Station/WisMesh Station HP

WisMesh Pi HAT

The WisMesh Pi HAT is best for Raspberry Pi® users who want to build their own Meshtastic gateway or station. It is a good fit for developers, labs, custom dashboards, and Raspberry Pi®-based setups where users want more control over software, sensors, and integrations.

WisMesh Pi HAT

Choose a gateway when the mesh needs MQTT, dashboard visibility, cloud connection, remote monitoring, or structured data collection. Choose a regular handheld, tracker, or repeater instead if the goal is only local off-grid messaging between nearby nodes.

• Best for: MQTT, cloud visibility, fixed stations, dashboards, monitoring, and IoT workflows
• Why users choose it: Gateways connect Meshtastic networks to broader systems and make deployments easier to monitor.
• Choose this if: You need a fixed bridge between Meshtastic and MQTT, cloud, Ethernet, WiFi, dashboards, or Raspberry Pi workflows.
• Consider another option if: You only need offline messaging between nearby Meshtastic nodes.
• Recommended RAKwireless fit: WisMesh WiFi MQTT Gateway, WisMesh Ethernet MQTT Gateway, WisMesh Station/WisMesh Station HP, or WisMesh Pi HAT

↑ Back to top

How to Choose the Best Meshtastic Device for Your Setup

The best Meshtastic device depends on your use case, device role, setup style, power source, portability needs, skill level, range expectations, and regional rules. Use the criteria below to narrow your choice.

1. Choose by Use Case

2. Choose by Device Role

3. Choose by Setup Style

4. Choose by Power Source

5. Choose by Portability

6. Choose by Skill Level

7. Choose by Range Needs

Range depends on terrain, antenna placement, antenna height, environment, device role, and regional regulations. A repeater placed in the right location can often improve a mesh more than simply choosing a more powerful handheld.

For better coverage, start with placement first. A higher repeater location, clearer line of sight, better antenna position, and reliable power source may solve the range issue before high-power hardware is needed.

For range extension, choose WisMesh Repeater or WisMesh Repeater Mini.

For advanced high-power or backbone planning, consider WisMesh 1W Booster Starter Kit, 1W Module for LoRa with SX1262 + SKY66122 Booster, or WisMesh Station/WisMesh Station HP, only where allowed.

Before buying a high-power device, ask:

• Is the current problem caused by terrain, buildings, trees, or poor antenna placement?
• Would a better antenna position solve it?
• Would an elevated WisMesh Repeater or WisMesh Repeater Mini help more?
• Is the selected transmit power legal in the region?
• Does the deployment need one high-power node or several better-placed nodes?

8. Check Frequency and Compliance

Frequency and transmit power rules vary by country or region. Always choose the correct frequency region before buying and configuring a Meshtastic device. High-power options should be used only where allowed.

Before purchasing, check:

• Frequency region
• Device role
• Transmit power rules
• Antenna gain rules
• Battery or power source
• Enclosure needs
• GPS/GNSS needs
• MQTT or gateway requirements
• Product bundle contents
• Required accessories

↑ Back to top

Example Meshtastic Setups by Use Case

A strong Meshtastic deployment is usually a combination of devices. A user may start with a starter kit, add a tracker or handheld, install a repeater for better coverage, and then add a gateway for MQTT, dashboards, or fixed infrastructure.

Use the examples below as starting points.

First Meshtastic Test Setup

A first Meshtastic test setup should match the user's comfort level. Non-technical users may prefer an enclosed ready-to-use device, while technical beginners and makers may prefer a modular starter kit for learning and customization.

Recommended setup:

• One ready-to-use pocket device or tracker for simple testing
• Or one modular starter kit for users comfortable with circuit boards
• Phone app or web setup
• Optional second node for testing mesh communication

Why it works:
A single device is useful for setup practice, but a second node helps users understand how mesh communication works. This setup is ideal for learning firmware setup, region selection, app pairing, messaging, and basic antenna behavior.

Recommended RAKwireless fit:

• WisMesh Pocket V2 or WisMesh Pocket Mini for a simpler first device
• WisMesh Tag for compact tracking and everyday carry
• WisBlock Meshtastic Starter Kit, WisMesh RAK3312 Starter Kit, or WisMesh RP2040 Starter Kit for modular testing

Hiking Group Setup

A hiking group needs portable devices, reliable power, and enough coverage for the terrain.

Recommended setup:

• Two to five handheld or pocket communicators
• Optional tracker for location sharing
• One elevated repeater for trail or campsite coverage

Why it works:
Pocket and handheld communicators help group members send and receive messages. A tracker helps with location sharing, while an elevated repeater can improve coverage around a campsite, ridge, or trail area.

Recommended RAKwireless fit:

• WisMesh Pocket V2
• WisMesh Pocket Mini
• WisMesh TAP V2
• WisMesh TAP
• WisMesh Board ONE Pocket
• WisMesh Tag
• WisMesh Repeater Mini or WisMesh Repeater

Everyday Carry Setup

An everyday carry setup should be small, simple, and easy to keep charged.

Recommended setup:

• Compact tracker or pocket device
• Internal battery
• Phone app connection
• Small antenna or internal antenna depending on device type

Why it works:
The device stays portable while still participating in the mesh. This setup is a good fit for bags, bikes, walks, events, travel, and local community testing.

Recommended RAKwireless fit:

• WisMesh Tag
• WisMesh Pocket Mini
• WisMesh Pocket V2
• WisMesh Board ONE Pocket

Emergency Neighborhood Mesh

An emergency neighborhood mesh should focus on coverage, simple use, and reliable fixed nodes.

Recommended setup:

• Multiple handheld or pocket nodes
• One outdoor repeater
• One gateway or station where MQTT, dashboards, or cloud visibility are needed

Why it works:
Handheld or pocket devices are useful for people in the area. A repeater improves coverage across the neighborhood. A gateway or station adds broader visibility when the deployment includes MQTT or dashboard workflows.

Recommended RAKwireless fit:

• WisMesh Pocket V2
• WisMesh Pocket Mini
• WisMesh TAP V2
• WisMesh Board ONE Pocket
• WisMesh Repeater or WisMesh Repeater Mini
• WisMesh WiFi MQTT Gateway
• WisMesh Ethernet MQTT Gateway
• WisMesh Station/WisMesh Station HP

Farm or Outdoor Asset Tracking

A farm or outdoor asset setup needs tracking, outdoor coverage, and optional data visibility.

Recommended setup:

• Compact trackers for assets, tools, vehicles, or field teams
• Outdoor repeater for wider coverage
• Gateway or station for MQTT, dashboards, or remote monitoring

Why it works:
Trackers help identify where assets are located. A repeater helps cover wider outdoor areas. A gateway or station can connect the deployment to dashboards, MQTT workflows, or fixed monitoring setups.

Recommended RAKwireless fit:

• WisMesh Tag
• WisMesh Repeater or WisMesh Repeater Mini
• WisMesh WiFi MQTT Gateway
• WisMesh Ethernet MQTT Gateway
• WisMesh Station/WisMesh Station HP

Community Backbone Setup

A community backbone setup is for users planning a more serious local mesh with fixed nodes, elevated placement, and reliable power.

Recommended setup:

• High-power node, booster-based build, or station where allowed
• Elevated antenna placement
• Reliable power source
• Compliance and antenna planning

Why it works:
Backbone nodes need stable placement, reliable power, and careful configuration. High-power options can be useful only when legally allowed and properly planned. Antenna height and site selection are just as important as device power.

Recommended RAKwireless fit:

• WisMesh Station/WisMesh Station HP
• WisMesh 1W Booster Starter Kit
• 1W Module for LoRa^® with SX1262 + SKY66122 Booster
• WisMesh Repeater or WisMesh Repeater Mini for range extension

Developer DIY Setup

A developer DIY setup is best for builders who want to test sensors, power systems, enclosures, or custom hardware workflows.

Recommended setup:

• Starter kit or board-level hardware
• Sensors or accessories
• Custom enclosure
• Gateway or station where MQTT is needed

Why it works:
This setup gives developers more control over the device role and hardware stack. It is useful for prototyping custom nodes, environmental monitoring, asset tracking, or remote data collection.

Recommended RAKwireless fit:

• WisBlock Meshtastic Starter Kit
• WisMesh RAK3312 Starter Kit
• WisMesh Base Board
• WisMesh Board ONE
• WisBlock sensor builds
• WisMesh Pi HAT
• WisMesh WiFi MQTT Gateway or WisMesh Ethernet MQTT Gateway where MQTT is needed

Coverage Testing and Mapping Setup

A coverage testing setup helps users validate a deployment before installing fixed nodes.

Recommended setup:

• Portable Meshtastic handhelds or pocket devices
• Repeater for coverage testing
• Gateway or station for MQTT, dashboards, or field data visibility
• Antenna accessories for placement and optimization

Why it works:
Coverage testing helps identify signal gaps, repeater locations, antenna improvements, and power needs before a permanent installation.

Recommended RAKwireless fit:

• WisMesh TAP V2 or WisMesh TAP for direct device interaction
• WisMesh Pocket V2, WisMesh Pocket Mini, or WisMesh Board ONE Pocket for portable testing
• WisMesh Repeater or WisMesh Repeater Mini
• WisMesh Station/WisMesh Station HP
• WisMesh WiFi MQTT Gateway or WisMesh Ethernet MQTT Gateway
• WisMesh Pi HAT for Raspberry Pi-based testing

↑ Back to top

Where to Buy Meshtastic Devices

The best place to shop for RAKwireless Meshtastic devices is the official RAKwireless store. The Meshtastic collection includes RAK Meshtastic starter kits, trackers, handhelds, repeaters, gateways, stations, board-level options, and accessories in one place.

Before buying, make sure the device matches your region, device role, power plan, skill level, and setup needs. Also check the selected frequency, bundle contents, antenna requirements, enclosure options, and accessory recommendations on the product page.

Buying Through RAK Partner Distributors

Some customers may prefer to buy through a regional RAK partner distributor for local availability, shipping, or promotions. Product availability may vary by distributor, so check each partner’s website regularly before purchasing.

If buying from the United States, check Rokland for RAKwireless product availability and promotions.

If buying from the Netherlands, check Hexaspot for Meshtastic-compatible products, WisBlock modules, and accessories.

If buying from Sweden or another EU location, check PileupDX.com for Meshtastic devices, WisBlock sensors, and select RAKwireless products.

If buying from Australia, check IoT Store for RAKwireless products, remote monitoring solutions, sensing products, and telecommunications-related options.

↑ Back to top

RAKwireless vs Other Popular Meshtastic Devices

Many Meshtastic devices can work well. The better choice depends on whether the user values price, enclosure, power efficiency, expandability, setup speed, outdoor installation, or long-term deployment flexibility.

This section is not about saying one device is always better than another. It is about matching the hardware to the use case.

RAKwireless Starter Kits vs Heltec-Style Beginner Boards

Heltec-style beginner boards are popular with budget-focused users and hobbyists who want an affordable way to start testing Meshtastic. They can be a good fit for experimentation and simple learning.

RAK starter kits are a better fit when the user wants a more modular path, more expansion options, and a clearer route from beginner testing to custom builds. WisBlock-based kits are especially useful for users who want to add GNSS, displays, sensors, or custom power setups.

Choose a Heltec-style beginner board if price is the main priority and the project is mostly experimental.

Choose a RAK starter kit if you want a more expandable hardware path and plan to grow beyond a basic node.

WisMesh Tag vs SenseCAP T1000-E-Style Trackers

SenseCAP T1000-E-style trackers are well known among Meshtastic users looking for compact, ready-to-carry tracking devices.

WisMesh Tag is a strong fit for users who want a compact Meshtastic tracker within the RAK ecosystem, especially if they are also considering RAK repeaters, gateways, and WisBlock-based expansion.

Choose a compact tracker based on battery needs, GNSS behavior, enclosure, antenna design, regional frequency, and how it will be carried.

WisMesh Pocket vs LilyGO T-Echo-Style Handhelds

LilyGO T-Echo-style devices are popular among users who want a handheld-style Meshtastic device with a built-in screen and portable form factor.

WisMesh Pocket is a good fit for users who want a RAK Meshtastic handheld or pocket communicator that can pair with a wider RAK ecosystem of starter kits, repeaters, stations, and accessories.

Choose based on enclosure, screen, battery, antenna, documentation, availability, and how much you value ecosystem consistency.

WisMesh TAP / Key-Style Devices vs T-Deck-Style Communicators

T-Deck-style devices appeal to users who want a keyboard communicator experience. They can be useful for direct messaging and more phone-free interaction.

WisMesh TAP or key-style devices fit a similar search intent for users who want more direct device input than a basic tracker or screen-only node. The best choice depends on keyboard needs, display preference, device size, battery, firmware workflow, and availability.

WisMesh Repeater vs DIY Solar Repeater Builds

DIY solar repeaters can be effective for experienced builders who want full control over enclosure, solar panel size, battery, antenna, and mounting hardware.

WisMesh Repeater options are a better fit when users want a more purpose-built path with less design work. A ready-to-use repeater can reduce setup complexity, especially for farms, neighborhoods, event sites, remote properties, and community mesh projects.

Choose DIY if you want full control and enjoy building. Choose WisMesh Repeater if you want a cleaner deployment path.

WisMesh Station vs Raspberry Pi-Based Gateway Builds

A Raspberry Pi-based gateway can be a flexible DIY option for technical users who want to assemble and configure their own system.

WisMesh Station is a better fit for users who want a more integrated station or gateway path. It can reduce the time needed to select parts, assemble hardware, and prepare a fixed deployment.

Choose a DIY Raspberry Pi gateway if you want full control over the build. Choose WisMesh Station if you want a more complete RAK gateway or station option for fixed infrastructure, MQTT, monitoring, or backbone workflows.

↑ Back to top

FAQ: Best Meshtastic Devices in 2026

↑ Back to top

Welcome to the RAKwireless Bulletin.

This month's bulletin highlights new Meshtastic infrastructure, LoRaWAN^® deployment resources, product updates, community projects, and industry events.

Featured highlights include the launch of the new WisMesh Station and WisMesh Pi HAT, along with valuable deployment resources and inspiring projects from the community.

Here's what happened across the RAK ecosystem this month.

Deployment Solutions and Product Updates

[New Product] WisMesh Station / WisMesh Station HP

We just launched the WisMesh Station, a ready-to-run Meshtastic-compatible gateway and base station built on Raspberry Pi^® 4.

Designed for reliable fixed deployments, it comes preloaded with a complete local-first software stack, including meshtasticd, Mosquitto MQTT, Node-RED, and Grafana. Housed in a rugged enclosure, it eliminates the need for OS installation, device flashing, or manual software setup. Simply power it on and start configuring your network.

WisMesh Station / WisMesh Station HP

Build with WisMesh Station

[New Product] WisMesh Pi HAT (RAK6421)

We also introduced the WisMesh Pi HAT RAK6421, a Meshtastic-ready Raspberry Pi HAT that brings WisBlock modularity to the Raspberry Pi ecosystem.

With support for modular WisBlock radios, GPS expansion, and HAT+ auto-discovery, RAK6421 enables plug-and-play Meshtastic gateway and relay node builds. The 1W radio option makes it suitable for long-range deployments where coverage matters most.

WisMesh Pi HAT (RAK6421)

Build with WisMesh Pi HAT

[Product Update] WisMesh 1W Booster Starter Kit in 868 MHz

The WisMesh 1W Booster Starter Kit expanded this month, adding a 868 MHz, covering real ISM bands for Europe

Powered by an nRF52840 + SX1262 + SKY66122 RF front end, the kit delivers 1W transmission capability for long-range Meshtastic mesh networks in outdoor, off-grid, and community deployments.

WisMesh 1W Booster Starter Kit in 868 MHz

Build your Meshtastic network

[Product Update] WisMesh Tag (Blue Edition)

The WisMesh Tag is now available in a Blue Edition, offering the same IP67-rated protection, 1000 mAh battery, and stable GPS and Bluetooth performance in a new color option for field deployments.

WisMesh Tag (Blue Edition)

Choose your WisMesh Tag

[New Tool] LOPTIMIZER by Pilot Things: LoRaWAN Field Optimization Tool

We introduced LOPTIMIZER, a portable LoRaWAN field optimization tool built on WisBlock.

Designed for pre-deployment planning, LOPTIMIZER helps teams compare installation locations, evaluate sensor placement options, and estimate battery impact before committing to a permanent setup, thereby reducing costly trial-and-error in the field.

LOPTIMIZER by Pilot Things: LoRaWAN Field Optimization Tool

Learn about LOPTIMIZER

Events and Industry Presence

Asia Tech x Singapore 2026

We were at the Asia Tech x Singapore 2026 with the LoRa^® Alliance on May 20–22, at Singapore Expo.

On Day 1, we showcased the full RAKwireless product ecosystem (WisGate, WisDuo, WisNode, and WisBlock) at the LoRa Alliance booth. Our VP of Strategic Growth & Design Partner Gavin Brown joined the Smart Cities panel alongside Semtech's Olivier Beaujard, exploring how LoRaWAN is powering real-world smart city deployments.

Fire Safety Event (FSE) 2026

At the Fire Safety Event at the NEC Birmingham last April 28-30, we demonstrated IoT solutions for fire safety and emergency monitoring, showcasing how LoRaWAN-based sensors and gateways can enable real-time alerts and build safety systems.

Deployment Tutorials and Gateway Management

Raspberry Pi-based Meshtastic Gateway for Always-On Deployments

We published a comprehensive blog covering how to run a Meshtastic-compatible gateway running on Raspberry Pi for always-on deployments.

The guide walks through setting up meshtasticd on Linux, configuring MQTT and dashboards, managing logging, enabling remote access, and integrating the WisMesh Pi HAT RAK6421. It’s everything needed for a permanent, reliable Meshtastic infrastructure node.

Read more

Auto Add Device in WisGateOS 2

We published a new video tutorial showing how to use the Auto Add Device feature in WisGateOS 2 to register OTAA devices instantly. If you want to eliminate manual key entry and reduce setup time during LoRaWAN network provisioning, this video is for you.

Watch tutorial

Gateway WiFi AP Mode Setup

We released a video tutorial on configuring a gateway for LoRaWAN using WiFi AP Mode, enabling initial setup without a LAN cable. This is especially useful for field deployments where wired connectivity isn't immediately available.

Watch tutorial

Auto Connect a RAK Gateway to TTN

We have a new YouTube tutorial that walks you through how to auto-connect a RAK gateway to The Things Network (EU1) using Packet Forwarder mode, covering configuration steps from start to finish for European LoRaWAN deployments.

Watch tutorial

Build a Multi-Gateway LoRaWAN Network

We posted a step-by-step guide that shows how to build a multi-gateway LoRaWAN network using a central gateway and extender gateways with the built-in network server. The tutorial is ideal for industrial IoT and smart agriculture deployments that require broader coverage without external infrastructure.

Watch tutorial

Community and Social Updates

RAK3112 Community Build: Agricultural IoT Node

We’re happy to have shared a developer's custom IoT node design built on the RAK3112 (ESP32-S3 + SX1276), featuring solar panel charging, RS485, and I2C interfaces for agricultural monitoring applications.

The build demonstrated how RAKwireless modules enable purpose-built field devices for real farming use cases.

RAK4631 Open-Source OBD2 BLE Temperature Monitor

A community member built a solar-assisted, energy-harvesting car temperature dashboard powered by the RAK4631 (nRF52840).

The open-source project combines OBD2 vehicle data with BLE connectivity, showing how WisBlock hardware supports creative edge computing applications beyond traditional IoT.

WisMesh Pi HAT Community Discussion

The launch of the WisMesh Pi HAT sparked active discussion on r/meshtastic, with operators sharing feedback on reliability, local MQTT workflows, and the value of standardized hardware for repeatable Meshtastic deployments.

Running Reliable Meshtastic on Raspberry Pi

A dedicated Reddit thread explored best practices for running reliable and scalable Meshtastic on Raspberry Pi, covering always-on gateway stability, relay node management, and long-term deployment considerations.

Developer and Platform Resources

Proven LoRaWAN Use Cases

We published a compilation of 11 proven LoRaWAN use cases powered by RAKwireless. It covers real-world deployments across smart farming, water networks, industrial IoT, wildlife conservation, smart buildings, and airports.

The guide serves as a practical reference for teams evaluating where LoRaWAN delivers the most value in production environments.

Special Highlight

TempGuard Networks: Predicting Cold-Chain Failures with BLE-to-LoRaWAN IoT

This month's spotlight goes to TempGuard Networks in Brazil. The company uses RAKwireless hardware to predict temperature failures before food or medicine gets spoiled across supermarkets and pharmacies.

Their hybrid BLE-to-LoRaWAN architecture deploys 80 BLE sensors, 4 BLE-to-LoRaWAN bridges, and 1 RAK7268CV2 gateway per branch that delivers live readings every three seconds and AI-driven drift detection at around $1,000 per location, compared to $2,400 with direct sensors for LoRaWAN alone.

Now rolling out across Carrefour supermarkets in Brazil, TempGuard Networks shows what happens when the right architecture meets reliable hardware: lower costs, simpler management, and the dependability that regulated industries demand.

Learn why TempGuard Networks chose RAKwireless.

This Month in One View

This month's updates showed a clear progression toward production-ready infrastructure from new Meshtastic gateway hardware and LoRaWAN deployment tutorials to firmware improvements, community-driven builds, and global event presence across Asia and Europe.

As the Meshtastic and LoRaWAN ecosystems continue to evolve, expect more deployment-focused resources, hardware updates, and community stories in the coming months.

IoT Made Easy,
The RAKwireless Team

TL;DR:

• RAKwireless focused on Meshtastic gateway infrastructure and LoRaWAN deployment tools.
• Event highlights included Asia Tech x Singapore and the Fire Safety Event 2026.
• New product launches featured WisMesh Station, WisMesh Station HP, and WisMesh Pi HAT (RAK6421).
• WisMesh 1W Booster Starter Kit is now available in 868 MHz
• LOPTIMIZER launched as a portable LoRaWAN field optimization tool.
• Tutorials covered Raspberry Pi-based Meshtastic gateways, Auto Add Device, WiFi AP Mode, TTN auto-connect, and multi-gateway networks.
• Community highlights included TempGuard Networks' cold-chain monitoring and open-source WisBlock builds.
• The 11 Proven LoRaWAN Use Cases guide provides a practical deployment reference.

Raspberry Pi is a trademark of Raspberry Pi Ltd.

1. Core Challenge & Pain Points

The Problem

Cold chain failures rarely occur inside highly controlled warehouses. Instead, they cluster during transit and at physical handover points where environmental visibility drops to zero.

According to industry research:

• The Food and Agriculture Organization (FAO) reports that roughly 14% of global food is lost between harvest and retail, with temperature deviation during logistics being a major contributing factor.
• Industry estimates suggest that up to 20% of temperature-sensitive biopharmaceutical products may be compromised during cold chain transportation due to temperature excursions and handling issues.

Key Pain Points

• In-Transit Data Gaps: Fixed monitoring networks only cover warehouses. Once trucks hit the road, connectivity drops, leading to unnoticed temperature excursions and broken compliance logs.
• Item-Level Cost Barrier: While cellular trackers offer real-time updates, their high per-unit cost and aggressive power consumption make pallet-level or item-level deployment economically unfeasible. Conversely, traditional standard LoRaWAN deployments lack mobility when moving outside static gateway infrastructure.
• No Proof of Integrity: Without continuous and tamper-proof logging across the entire journey, receivers often lack verifiable evidence of temperature compliance, leading to disputes, rejected shipments, and financial losses.

2. Typical Customer Scenario 

Consider a high-value, temperature-sensitive pharmaceutical shipment moving from a manufacturing facility in Mexico to a distribution center in Texas.

The journey begins with Handover 1 (Factory to First-Mile Carrier), where cargo is exposed to extreme ambient heat on an unshaded tarmac during loading. It then faces Handover 2 (Border Cross-Docking & Customs), where transferring goods to a domestic US fleet requires physical inspection, leaving trailer doors open and introducing risks of temperature spikes and cargo tampering. Finally, during Handover 3 (Final-Mile Delivery), scheduling mismatches at the destination warehouse force the truck to idle outside for hours, compromising product integrity just steps from the finish line due to cumulative stress across these unmonitored custody gaps.

3. The Hybrid Solution: BLE + LoRaWAN Architecture

By combining low-cost, item-level Bluetooth Low Energy (BLE) sensing with long-range, infrastructure-grade LoRaWAN connectivity, this joint solution achieves continuous visibility from origin to destination.

MOKOSMART BLE Sensors: Affordable, ultra-low-power tags placed directly on individual cargo/pallets for sensing.

• M4 Pro Waterproof Tag: Designed for warehouse asset tracking and temperature monitoring. Features data memory for offline backup.
• S05T Temperature Logger: A disposable, lightweight logger for export shipments. Stores up to 60,000 records and uploads data via BLE gateways.
• L02S Multiple Sensor: All-in-one tag tracking temperature, humidity, door open/close (hall effect), and transit shocks (accelerometer).
• DL002 Temperature Sensor Probe: Industrial-grade sensor with a 5-year lifespan and 60,000 local record storage; ideal for reusable cold chain containers.

MOKOSMART LoRaWAN Loggers：Long-range wireless logging designed for facility-wide coverage and real-time cloud uploading.

• DL001-LW LoRaWAN® Data Logger: A facility data logger featuring LoRaWAN® connectivity, built-in Flash storage, and a local display for real-time temperature, humidity, and battery status.

RAKwireless WisGate Edge Lite 2 (RAK7268CV2) Gateway: The network backbone deployed at fixed transit nodes to bridge edge data to the cloud.

• RAKwireless WisGate Edge Lite 2 (RAK7268CV2): An 8-channel industrial indoor gateway. Built for deep signal penetration in concrete/metallic environments (warehouses, distribution centers). Supports Ethernet, Wi-Fi, and Cellular backhaul.

4. End-to-End Logistics Journey 

Origin (Logistics Park / Cold Storage): Pallets are equipped with MOKOSMART BLE sensors. The DL001-LW actively scans these local BLE signals, aggregates the environmental data, and instantly transmits it to the cloud via the warehouse's static RAKwireless WisGate Edge gateway, preventing compromised goods from leaving the platform.

In-Transit (Refrigerated Truck): As the truck leaves the warehouse gateway zone, item-level BLE sensors continuously track individual pallets and broadcast data to the cabin-mounted DL001-LW data hub. Without active gateway coverage on the highway, the DL001-LW securely caches all incoming historical BLE sensor logs onto its built-in Flash storage, completely eliminating highway communication blind spots.

Destination (Retail Store / Distribution Center Bay): Upon arrival at the destination receiving bay, the DL001-LW automatically reconnects with the facility’s static RAKwireless gateway. It executes an immediate LoRaWAN data uplink of all cached in-transit logs to the cloud, generating a complete, unbroken audit trail before the trailer doors are even opened.

5. Key Benefits of the Joint Solution

• Seamless BLE-to-LoRaWAN Bridging: Combines the cost-efficiency of BLE tags with the long-range capability of LoRaWAN.
• Edge Reliability: RAK WisGate Edge Lite 2 ensures high throughput, strong signal penetration in metallic/concrete environments (like walk-in freezers), and built-in network server capabilities for local processing.
• Data Continuity (No Blind Spots): The storage mechanism of the DL001-LW guarantees that even without cellular or gateway coverage on the highway, the compliance log remains unbroken.
• Cost Efficiency & Scalability: Lowers total cost of ownership by using affordable BLE sensors for individual pallets, requiring only one LoRaWAN logger per truck/zone.

6. Conclusion

Cold chain operators do not just need data; they require continuous, verifiable visibility across complex custody handovers. By pairing MOKOSMART’s edge BLE sensing portfolio and scanning loggers with RAKwireless’s industrial gateway infrastructure, logistics providers can eliminate blind spots, protect high-value cargo, and deliver absolute proof of compliance from factory shelf to retail bays.

About MOKOSMART
MOKOSMART is a leading manufacturer and provider of ODM, OEM, and IoT devices in China. The company specializes in IoT technology and offers a comprehensive range of products, including BLE, LoRaWAN®, Wi-Fi, RFID, GPS, LTE, UWB, and other wireless technologies. MOKOSMART's commitment to innovation and diverse wireless solutions paves the way toward a connected future.

About RAKwireless
RAKwireless is a global IoT infrastructure provider specializing in end-to-end LoRaWAN solutions, including gateways, developer tools, and cloud integration platforms. Its WisGate series is widely deployed in industrial IoT applications such as smart cities, smart agriculture, logistics, and asset tracking. RAKwireless focuses on simplifying IoT deployment through open, scalable, and edge-ready architecture, enabling enterprises to rapidly build robust low-power wide-area networks.

• A reliable Meshtastic base station needs stable power, external antennas, enclosure, local MQTT, dashboards, and clear setup.
• DIY builds offer full customization, while ready-to-run gateways help users move faster from setup to deployment.
• WisMesh Station supports dense local coverage, while WisMesh Station HP fits long-range relay and backbone deployments where allowed.

Portable Meshtastic nodes are great for personal use, field testing, hiking, events, and early network building. But as a mesh network grows, many operators eventually need something more stable: an always-on gateway or base station that can help extend coverage, relay messages, process local data, and support monitoring workflows.

That is where a purpose-built Meshtastic base station becomes useful.

Instead of starting from separate boards, enclosures, antennas, power supplies, operating system images, MQTT setup, and dashboard configuration, a ready-to-run Meshtastic gateway gives you a more streamlined path from hardware to deployment.

This guide walks through what to look for in a reliable Meshtastic base station, how to compare DIY and ready-to-run options, and how to choose between WisMesh Station and WisMesh Station HP depending on your coverage goals.

Quick Answer: What Should a Meshtastic Base Station Include?

A reliable Meshtastic base station should provide stable power, external antennas, a protected enclosure, a dependable software stack, local MQTT processing, and clear setup steps. For more advanced deployments, it should also support dashboards, automation workflows, sensor expansion, and the right RF power option for the environment.

WisMesh Station combines these elements in a ready-to-run Raspberry Pi 4-based Meshtastic gateway/base station with meshtasticd, Mosquitto MQTT, Node-RED, and Grafana preinstalled. It is available in Standard Power and High Power versions, giving users a clearer choice between dense local coverage and longer-range relay or backbone deployments.

What a Reliable Meshtastic Infrastructure Node Needs

A good Meshtastic network is not just about adding more nodes. It is about placing the right type of node in the right location.

Here are the key things to look for.

1. Stable Power for Always-On Operation

A base station is usually expected to stay online for long periods. That means power stability matters more than it does for a casual portable node.

Look for a system that can run continuously from a dependable power source and support long-running services without constant manual intervention.

2. A Protected Enclosure

If the node is meant to sit in one place and support ongoing coverage, it should not be left as a loose stack of boards and cables. A proper enclosure helps protect the hardware, organizes the build, and makes the setup easier to place on a shelf, inside a cabinet, or near a deployment point.

WisMesh Station uses a full metal enclosure, making it more suitable for gateway/base station use than an exposed board-and-HAT setup.

3. External Antenna Support

Antenna placement has a major effect on LoRa mesh performance. For a base station or relay node, external antenna access gives operators more flexibility when planning coverage.

WisMesh Station includes external antenna ports for LoRa and GPS, allowing users to plan antenna placement more intentionally than they could with many compact portable nodes.

4. A Stable Software Stack

A Meshtastic gateway/base station may need more than Meshtastic firmware alone. Depending on the deployment, operators may want local MQTT, dashboards, automation flows, and sensor data handling.

That usually means installing and maintaining several services, including:

• meshtasticd
• MQTT broker
• Node-RED
• Grafana

Having those tools preinstalled can reduce the time between unboxing and configuration.

5. Local Data Handling

For community networks, emergency communications, event deployments, and off-grid monitoring, local-first operation can be a major advantage.

A local MQTT broker and dashboard stack can help users collect, route, visualize, or automate mesh-related data without relying on an external cloud service for every workflow.

6. Clear RF Power Options

Not every deployment needs the same power level. Dense urban networks and indoor gateway setups may not need high RF output. Rural links, hilltop relay points, and long-range backbone deployments may benefit from a high-power option where local regulations allow it.

DIY or Ready-to-Run: Choosing the Right Meshtastic Gateway Path

DIY is a big part of the Meshtastic community. It gives users flexibility, control, and room to experiment with different radios, antennas, enclosures, power setups, sensors, and software tools.

For many users, that is exactly the point.

A DIY Meshtastic gateway powered by Raspberry Pi can be the right choice if you want to learn every layer of the system, customize every component, or build around specific project requirements. It also gives experienced builders the freedom to choose their own hardware stack and software approach.

A ready-to-run Meshtastic base station is for a different situation.

It makes sense when the goal is to move faster from planning to deployment, especially for users who already know they need an always-on gateway or relay node. Instead of sourcing each part and configuring every service from scratch, users can start from an integrated platform and focus on coverage, placement, configuration, and operation.

What WisMesh Station Includes

WisMesh Station / WisMesh Station HP is a ready-to-run Meshtastic gateway and base station built around Raspberry Pi 4. It combines LoRa mesh communication, local MQTT processing, dashboard tools, and WisBlock expansion in one enclosed system.

At a high level, WisMesh Station includes:

Standard vs HP: Which Version Fits Your Coverage Goal?

WisMesh Station comes in two versions: Standard Power and High Power. Both use the same ready-to-run platform. The main difference is output power and the type of deployment each version is best suited for.

Choose WisMesh Station if:

You are building coverage in an area where nodes are relatively close together.

This can include:

• Neighborhood meshes
• Campuses
• Indoor or near-building gateways
• Dense urban networks
• Community networks with several nearby nodes

Standard Power is usually the better fit when the goal is stable local coverage rather than maximum output power.

Choose WisMesh Station HP if:

You are trying to connect more distant areas or strengthen a sparse network.

This can include:

• Hilltop relay points
• Rural links
• Long-range backbone nodes
• Wider-area community coverage
• Installations where antenna height and line of sight can be optimized

The HP version provides 1W / 30 dBm output capability at the hardware level. Actual performance depends on antenna placement, terrain, line of sight, interference, configuration, and local regulations.

Important note: Always review local rules for frequency band, transmit power, antenna gain, and duty cycle before using high-power LoRa hardware. It is the user’s responsibility to configure the device in compliance with local spectrum regulations.

Local-First Operation: MQTT, Node-RED, and Grafana Without Cloud Dependency

One of the biggest advantages of a Raspberry Pi-based Meshtastic gateway is that it can do more than relay messages.

With WisMesh Station, the local software stack includes meshtasticd, Mosquitto MQTT, Node-RED, and Grafana. This gives operators a base for communication, automation, and monitoring workflows directly on the device.

Why Local MQTT Matters

MQTT can help route Meshtastic data into other systems. For example, a Meshtastic node with MQTT can support local message handling, sensor data workflows, and integration with dashboards or automation tools.

For users building community networks, preparedness systems, event networks, or remote monitoring setups, this can be useful because local workflows can continue without depending on an external cloud service for every step.

Why Node-RED Matters

Node-RED helps users build automation flows without writing everything from scratch. It can connect MQTT data to actions, alerts, dashboards, or other systems.

Users may want to:

• Trigger alerts from sensor readings
• Route mesh messages to another local service
• Build simple automation flows for events or monitoring
• Process data before sending it to another system

Why Grafana Matters

Grafana helps turn data into dashboards. For base station operators, dashboards can make it easier to observe system behavior, sensor readings, or other local data streams.

Instead of deploying only a radio, users get a platform that can support communication and visibility.

Deployment Scenarios

WisMesh Station can support several types of Meshtastic deployments. The right setup depends on the network layout, terrain, coverage target, and level of local data handling needed.

1. Community Mesh Operator

A community mesh operator may want to expand coverage across a neighborhood, town, or campus. In this case, the priority is often an always-on gateway/base station with good antenna placement, dependable power, and clear configuration.

Recommended fit: WisMesh Station for dense or local coverage; WisMesh Station HP for wider-area relay points where regulations allow.

2. Long-Range Relay or Backbone Operator

A relay or backbone operator may want to connect distant areas or strengthen a sparse network. These deployments usually benefit from elevated placement, careful antenna planning, and a hardware platform that can stay online for extended periods.

Recommended fit: WisMesh Station HP, especially for rural links, elevated relay points, and backbone nodes where 1W operation is permitted.

3. Preparedness or Emergency Communications Organizer

Preparedness groups may need a local communications hub for events, outages, drills, or community response planning. In these scenarios, local-first operation and dependable coverage can be important.

Recommended fit: WisMesh Station or WisMesh Station HP depending on the coverage area, with local MQTT and dashboards used for monitoring and workflows.

4. Maker or Integrator Building MQTT Workflows

Some users want to route mesh data into custom automations, dashboards, or sensor systems. For them, the value is not only LoRa mesh coverage. It is also the integrated software stack.

Recommended fit: WisMesh Station for local gateway and automation workflows, with WisBlock expansion for sensors and IO as the project grows.

Comparison: Ready-to-Run Station vs DIY vs Portable Nodes vs Industrial Gateways for LoRaWAN^®

Different hardware categories support different parts of a wireless network. The key is choosing the right tool for the job.

Learn more about the WisMesh Station / WisMesh Station HP.

FAQ: Common Questions About Meshtastic Base Stations

Why not build a Meshtastic gateway powered by Raspberry Pi myself?

You can. DIY is a strong option if you want full control over every component and enjoy building your own stack.

A ready-to-run solution makes more sense when you want to reduce setup time, avoid sourcing separate parts, and start from an integrated gateway/base station platform with the core local stack already included.

Do I need internet for WisMesh Station?

WisMesh Station can run local services directly on the Raspberry Pi, including Meshtastic services and an MQTT broker. This allows local communication, routing, and data handling within the mesh and connected systems without relying on a cloud service for every workflow.

Internet access may still be useful for updates, remote access, or integrations depending on your configuration.

Is 1W legal where I live?

It depends on your country or region. Frequency plans, transmit power limits, antenna gain rules, and duty cycle requirements vary.

WisMesh Station HP provides high RF output capability at the hardware level, but users are responsible for configuring the device in compliance with local regulations.

How much range can I expect?

Range depends on many factors, including:

• Antenna placement
• Antenna gain and matching
• Height above ground
• Terrain
• Buildings, trees, and other obstructions
• Local interference
• Mesh topology
• Frequency plan and transmit power settings

Elevated placement and clearer line of sight generally improve performance. Dense urban environments usually introduce more obstruction and interference, while rural or elevated deployments may support longer links.

Which region or frequency should I choose?

Choose the frequency plan that matches your local regulations and Meshtastic region settings. Always confirm the correct band, transmit power, duty cycle, and antenna rules for your deployment location.

What sensors can be added?

WisMesh Station supports WisBlock expansion. Compatible sensor options include modules for temperature and humidity, barometric pressure, environmental sensing, CO2, ambient light, UV light, IR temperature, RTC, and GPS-related use cases.

This makes the platform useful not only as a Meshtastic gateway/base station, but also as a local monitoring and telemetry hub.

Can WisMesh Station integrate with an existing Meshtastic network?

Yes. WisMesh Station is designed to work as a Meshtastic gateway/base station or relay node using compatible Meshtastic protocols and clients. It can help extend coverage, support message routing, and provide local data workflows through the preinstalled software stack.

Is WisMesh Station only for advanced users?

No. It is designed to reduce the amount of setup needed to get a Raspberry Pi-based Meshtastic gateway/base station running. Users still need to configure network settings, region settings, channels, antenna setup, and deployment details, but the core local stack is already included.

Raspberry Pi is a trademark of Raspberry Pi Ltd.

The Raspberry Pi has become one of the most popular platforms for running Meshtastic, and it is easy to see why. It brings the flexibility of Linux into the mix, allowing you to run meshtasticd Raspberry Pi deployments alongside MQTT brokers, dashboards, logging tools, and automation workflows. On paper, it feels like the perfect foundation for building something more powerful than a typical handheld node within a LoRa communication system.

But if you have ever tried running a Raspberry Pi Meshtastic setup for more than a few days, especially in an always-on role, you have probably noticed something doesn’t quite hold up. The issue is rarely the software. More often, it is the hardware stack holding everything together. A Raspberry Pi Meshtastic node is only as reliable as the way its radio, sensors, and interfaces are connected.

The Common Problems With DIY Meshtastic Raspberry Pi Builds

A lot of Raspberry Pi Meshtastic setups work fine at first. The weak points usually show up later, once the node is expected to stay online and do more than basic testing.

• USB radios can drop unexpectedly
  What starts as a simple connection can become unreliable over time, especially after long runtimes or small power dips. This is a common reason users search for how to fix Raspberry Pi USB disconnect issue.
• Loose cables create avoidable failure points
  USB connectors, jumper wires, and adapters can shift, wear out, or disconnect, turning a working node into something that needs constant checking.
• Extra features add extra complexity
  As soon as you add GPS, sensors, Node-RED, Grafana, or other tools used in wireless sensor networks, the wiring and dependency chain gets harder to manage.
• Each build ends up slightly different
  Small changes in parts, layout, or wiring make one setup harder to reproduce exactly on the next node.
• Scaling becomes harder than expected
  What works for one experiment does not always translate into a clean process for building multiple nodes the same way.
• The setup was never really built for long-term use
  Many DIY builds are good for testing ideas, but not for serving as a stable, always-on infrastructure or a stable Meshtastic node setup.

Why meshtasticd Changes the Role of Raspberry Pi Nodes

There is an important shift that happens when you move from firmware-based nodes to running meshtasticd on a Raspberry Pi. At that point, you are no longer just running a simple node. You are building something closer to an IoT gateway architecture.

Firmware-based devices are typically portable. They are designed for mobility, low power consumption, and simplicity. They do their job well, but they are not meant to host complex services or act as permanent network anchors.

A Raspberry Pi running meshtasticd plays a very different role. It becomes a Raspberry Pi LoRa gateway, a relay, or even a backbone node. It can bridge data into MQTT, feed dashboards, log activity, and support automation workflows. It is no longer just participating in the mesh; it is helping define a scalable mesh networking hardware environment.

That shift comes with new expectations. Infrastructure nodes are expected to stay online, maintain consistent connectivity, and operate without constant intervention. For that to happen, the hardware integration between the Pi and the radio must be just as stable as the software running on top of it.

What a Cleaner Meshtastic Raspberry Pi Setup Should Provide

A cleaner Raspberry Pi Meshtastic setup should do more than look organized. It should reduce the hardware weak points that cause downtime and make the build easier to repeat across multiple nodes.

A reliable setup should provide:

• Direct radio integration to avoid USB adapters and loose jumper wires.
• Stable power and data connections for long runtimes in gateway or relay roles.
• Modular expansion for adding GPS, sensors, or different LoRa radios without rebuilding the whole setup.
• Linux workflow compatibility so meshtasticd can run alongside MQTT, dashboards, logs, and automation tools.
• Repeatable deployment so one successful build can become the model for future nodes.

This is what separates a quick prototype from a Raspberry Pi Meshtastic gateway that is ready for real deployment or even a modular Raspberry Pi IoT gateway.

Introducing WisMesh Pi HAT RAK6421

WisMesh Pi HAT RAK6421 gives Raspberry Pi Meshtastic builds a cleaner way to connect WisBlock LoRa radios, GPS, and sensors without USB adapters or loose wiring. It serves as a purpose-built Raspberry Pi LoRa HAT designed for structured deployments.

It creates a more stable, repeatable base for gateways, relays, and backbone nodes running meshtasticd.

WisMesh Pi HAT RAK6421

Explore WisMesh Pi HAT RAK6421

Key Features That Matter for Real Deployments

When you move from a DIY setup to something you expect to run continuously, the small details start to matter a lot more. It is no longer just about getting a node online, but about keeping it stable, easy to manage, and consistent across deployments.

This is where the WisMesh Pi HAT RAK6421 shifts the experience from a collection of parts into a more structured system, with each feature solving a very specific problem that builders often run into.

These features make it a strong candidate for the best LoRa HAT for Raspberry Pi, especially when reliability and scalability matter.

Example Use Cases

Once your Raspberry Pi setup becomes stable and repeatable, it stops being just a project and starts becoming something you can actually deploy with confidence. Instead of constantly checking connections or troubleshooting random issues, you can begin thinking in terms of roles within a network.

The different ways this kind of setup can be used become much clearer when you break them down:

Each of these scenarios reflects a shift in mindset. Instead of building a single node to experiment with, you are building parts of a larger system. And in that system, consistency and uptime are not optional. They are what make the network usable in the real world.

These deployments are typical in wireless sensor networks and low-power wide-area network environments.

How the WisMesh Pi HAT RAK6421 Compares to Generic LoRa HATs and DIY Setups

There are many ways to get a LoRa radio working with a Raspberry Pi, and most of them will get you to the same starting point. A USB radio or a generic LoRa HAT can be enough to bring a node online, send messages, and experiment with the network. For testing ideas or learning how Meshtastic works, that flexibility is often exactly what you need.

The difference becomes more noticeable over time, especially when the node is expected to run continuously or be deployed as part of a larger network. At that stage, the question shifts from “Does it work?” to “Will it keep working, and can I build more of them the same way?”

The comparison below shows how each setup path changes as the priority shifts from simply getting a node online to keeping it reliable and repeatable over time.

WisMesh Pi HAT RAK6421 stands out by combining a Pi-hosted Linux stack with WisBlock modularity, radio and sensor expansion, HAT+ auto-discovery, and support for high-power radio options. The result is not just a working node, but a platform that can be deployed consistently across multiple locations.

What You Need to Build a Working Node

It is important to understand that the HAT itself is only one part of the system. A complete setup typically includes a Raspberry Pi, such as a Pi 4 or Pi 5, along with a compatible LoRa radio module and an antenna. Depending on your use case, you might also add GPS or sensor modules to expand functionality.

On the software side, meshtasticd provides the core service, either through manual setup or a preconfigured system image. Once everything is in place, the hardware and software come together to form a node that is ready for long-term operation.

A complete Meshtastic setup is a combination of hardware and software layers working together as seen below:

So how does it work?

The Raspberry Pi acts as the main system, running Linux and hosting meshtasticd. The WisMesh Pi HAT RAK6421 sits directly on top of it, acting as the structured interface that connects radios and expansion modules without relying on USB or loose wiring.

From there, the LoRa radio handles communication, while optional GPS and sensor modules extend the node’s capabilities depending on your use case. The antenna ensures proper signal transmission, and on the software side, meshtasticd enables integration with tools like MQTT, Node-RED, or dashboards.

The HAT is not the node itself, but the foundation that makes the entire system cleaner, more stable, and easier to replicate.

Build a Cleaner Raspberry Pi Meshtastic Gateway

At some point, most Raspberry Pi Meshtastic setups reach a turning point. What starts as a simple and flexible DIY build begins to show its limits when it is expected to run continuously or support a larger network. Small issues like USB disconnects or loose wiring stop being minor inconveniences and start becoming real obstacles.

Moving to a cleaner, more structured approach changes that experience entirely. Instead of managing a fragile setup, you begin working with a system that is easier to trust, easier to replicate, and better suited for always-on roles like gateways, relays, and backbone nodes.

WisMesh Pi HAT RAK6421 is designed to support that transition by providing a modular and reliable hardware foundation for Raspberry Pi-based Meshtastic deployments. It helps turn a collection of components into something that behaves more like infrastructure.

If you are ready to move beyond experimentation and build something more stable, you can start by learning how to design your setup the right way.

Welcome to the RAKwireless Bulletin.

This month’s roundup focuses on real-world IoT deployment, covering LoRaWAN^® tools, developer resources, gateway management features, and ecosystem updates that help teams move from prototype to scalable production.

Let’s take a look at what happened in the last month and what’s coming next.

Events and Industry Presence

mioty Days 2026

We will join mioty Days 2026 on May 12–13 at the Fraunhofer Research Campus in Waischenfeld, Germany.

Xose Pérez, one of RAK’s Product Owners, will be there to share ideas and help define solutions for the mioty ecosystem.

Asia Tech x Singapore 2026

We will also take part in Asia Tech x Singapore 2026 with the LoRa Alliance from May 20–22, at Singapore Expo.

Together with the LoRa Alliance, Gavin Brown, our VP of Strategic Growth & Design Partner, will be at Hall 3, Stand 3C3-1 to help showcase what LoRaWAN can do through real products, real use cases, and real-world conversations. RAKwireless has also been invited to speak at the event.

MWC Barcelona 2026

RAKwireless was at MWC Barcelona 2026, with Xose Pérez representing the team onsite at Fira Barcelona Gran Via in Barcelona, Spain.

The event created a strong opportunity to connect practical IoT strategy across LoRaWAN and 5G, as well as engage with the wider LoRaWAN ecosystem during the LoRa Alliance International Network Reception.

HANNOVER MESSE 2026

RAKwireless attended HANNOVER MESSE 2026 at the Hannover Exhibition Grounds in Hannover, Germany, from April 20–24.

Gavin Brown met with attendees to discuss how LoRaWAN can create value for industrial solutions, from pilot projects to full deployment.

LoRaWAN Deployment Solutions & Product Updates

[New Product] Nordic nRF52840 BLE Core Module RAK3401

This month, we introduced the low-power Nordic nRF52840 BLE Core Module RAK3401.

Designed for compact battery-powered or solar-powered devices, RAK3401 combines low power consumption, a TCXO for stable timing, and flexible interfaces including UART, I2C, SPI, ADC, USB, and GPIO. It also supports modular expansion, including pairing with the RAK13302 1W transceiver module for LoRa® for future long-range connectivity needs.

Nordic nRF52840 BLE Core Module

Start building with RAK3401

[Product Update] WisMesh 1W Booster Starter Kit in 868 MHz

The WisMesh 1W Booster Starter Kit is now available in 868 MHz, making it easier for users in Europe to build long-range Meshtastic networks with 1W transmission capability.

This new variant expands accessibility for off-grid communication, outdoor deployments, and community mesh networks. The launch was also supported by community-built projects that showed how developers are already putting the platform into practice.

WisMesh 1W Booster Starter Kit in 868 MHz

Build 868 MHz Meshtastic network

[Product Update] WisMesh Tag

The WisMesh Tag remained a strong focus this month as a compact, rugged Meshtastic GPS tracker built for real deployments.

Its positioning centered on practical reliability: IP66-rated protection, longer uptime with a 1000 mAh battery, stable GPS and Bluetooth performance, easier recovery through a reset button, and CE certification for Europe. The messaging emphasized real-world field use rather than DIY novelty.

Now, it's available in Blue Edition.

WisMesh Tag, The Pocket-Sized, Compact Meshtastic Tracker

Choose your WisMesh Tag

[New Product] BACnet Gateway for LoRaWAN RAK7437

Connect LoRaWAN sensors to BACnet-based building systems without rebuilding point tables, dashboards, or BMS logic.

One of the most important solution updates was the continued rollout of the BACnet Gateway for LoRaWAN RAK7437.

The gateway is designed to simplify how sensors for LoRaWAN are integrated into BACnet-based Building Management Systems. Its key value lies in Data Point Mapping, which decouples physical sensors for LoRaWAN from BACnet logic. This allows sensors to be replaced without rebuilding BACnet point tables, modifying BMS logic, or updating dashboards.

BACnet Gateway for LoRaWAN®

Simplify LoRaWAN-to-BACnet integration

LoRaWAN Deployment Tutorials & Gateway Management

Our new tutorial showed how to use the SD Card Health Check feature in WisGateOS 2 to keep gateways running smoothly.

The video explained how to access SD card status, understand status indicators such as Normal, Not Detected, and Abnormal, and troubleshoot common issues before they lead to bigger failures. The value is simple: earlier detection means fewer disruptions and more reliable long-term operation.

Watch tutorial

Keep gateways for LoRaWAN online by automatically switching between Ethernet, WiFi, and Cellular connections when the primary link fails.

We also published a tutorial on Multi-WAN Backup in WisGateOS 2.

The walkthrough showed how a gateway can automatically switch between Ethernet, WiFi, and Cellular connections when the primary link fails. For remote and mission-critical deployments, this feature helps maintain uptime even when network conditions change unexpectedly.

Watch tutorial

Another tutorial focused on Automatic Log Rotation in WisGateOS 2.

This content explained how log rotation helps prevent SD card overflow, manage long-term storage use, and keep gateways performing well over extended deployments in the field. It also covered log retention, buffer size, and access to local log files.

Watch tutorial

For developers, we released a LoRaWAN FUOTA demo on the RAK3172 using RUI3 v5 and ChirpStackOS.

The step-by-step video covered application setup, device configuration, OTAA join, multicast delivery, and firmware fragment transfer. Since the feature is still in early beta, the content was clearly positioned as a learning and testing resource rather than a production workflow.

Watch tutorial

Community and Social Updates

WisMesh Tag Community Feedback

We asked the Meshtastic community on Reddit on which feature upgrade people would prefer for the WisMesh Tag, such as screen options, charging improvements, or color variants.

WisMesh Tag Follow-Up Q&A

A follow-up Reddit post then summarized the most common questions from users.

The recap covered battery life, GPS performance, indoor messaging, ruggedness, and EU readiness. That kind of follow-up content strengthened the sense that product messaging is being shaped by real user concerns.

Developer and Platform Resources

RAKwireless Developer Portal

Access LoRaWAN developer tools, WisDM APIs, documentation, and gateway management resources in one place.

One of the month’s most important platform updates was the first release of the RAKwireless Developer Portal.

The portal is now live as a streamlined entry point for developer resources, helping users discover and test tools more easily in one place.

What’s Available Now

The first release currently includes:

• WisDM APIs for gateway fleet management and integrations
• developer-focused documentation and guides to help users get started faster

What’s Coming Next

More resources are already planned for future updates, including:

• WisGateOS 2 Extension SDKs for custom gateway features
• more tools, tutorials, and examples as the portal evolves

This launch is important because it improves discoverability and creates a stronger foundation for long-term developer engagement across the RAKwireless ecosystem.

Special Highlight

Embedded World 2026: The Shift From Proof-of-Concept to Deployment

A few weeks after the Embedded World Exhibition & Conference 2026, one message stood out clearly from the conversations at the RAKwireless booth: IoT is moving beyond proof-of-concept and into deployment.

Attendees showed the strongest interest in practical scaling challenges, including reliability in dense RF environments, coverage validation before rollout, integration with existing systems, and making edge intelligence more useful in real deployments.

That interest was reflected in the solutions that drew the most attention, especially:

• BACnet Gateway (RAK7437) for bringing LoRaWAN into BACnet-based building management systems
• Bridge IO for connecting LoRaWAN devices into existing infrastructure more easily

The same practical focus also carried into IoT Stars, where Xose Pérez shared why Edge AI adoption depends on experience, not just models, using real stories of both success and failure.

For RAKwireless, Embedded World was not just about visibility. It was a valuable moment for understanding what customers need to move from prototype to production with greater confidence.

This Month in One View

This month’s updates showed a consistent pattern across product messaging, educational content, event presence, and community engagement.

More product launches, tutorials, and ecosystem updates are on the way.

TL;DR:

• RAKwireless focused on LoRaWAN deployment tools and IoT solutions.
• Event highlights included MWC Barcelona, HANNOVER MESSE, and Innovation Zero.
• Upcoming events include mioty Days and Asia Tech x Singapore 2026.
• Product updates featured RAK3401, WisMesh 1W Booster Kit, and WisMesh Tag.
• The BACnet Gateway RAK7437 helps connect LoRaWAN sensors to BMS platforms.
• New WisGateOS 2 tutorials covered SD Card Health Check and Multi-WAN Backup.
• Additional tutorials covered log rotation and end device LoRaWAN FUOTA testing.
• The RAKwireless Developer Portal launched with WisDM APIs, docs, and guides.
• More developer tools, tutorials, and SDKs are planned.
• Embedded World showed IoT moving from proof-of-concept to real deployment.