In the world of Internet of Things (IoT), the sub-GHz spectrum is a frontier of immense promise, offering the holy grail of long-range and low-power communication. Two fundamentally different philosophies are vying to define this frontier. On one side stands Wi-Fi HaLow (IEEE 802.11ah), a direct evolution of the familiar, IP-based Wi-Fi standard, engineered for higher bandwidth and seamless integration. On the other lies the diverse and adaptable LoRa landscape, a collection of distinct networking protocols all built upon the same remarkable long-range radio technology.

For many new to LPWAN mesh networking, MeshTastic often appears as a starting point due to its affordability and active community. It can get you from zero to sending a basic mesh message relatively quickly. For some, it may seem like a convenient entry into mesh networking.

In this post, I’ll dive into what makes MeshTastic tick, where it excels, and where it falls short based on my own experience using it across various scenarios.

Long-range Sub-GHz wireless mesh networks have become essential for modern communication, particularly in remote areas where traditional infrastructure is impractical or impossible. By utilising lower frequencies (typically below 1 GHz), Sub-GHz networks can achieve remarkable range, low power consumption, and the ability to penetrate obstacles such as buildings and dense forests.

These characteristics make Sub-GHz mesh networks ideal for applications in IoT, outdoor communication, emergency response, and industrial networks. But with numerous technologies now available, choosing the right one for your needs can be challenging.

In an emergency, information is as vital as water. The official advice is clear: “leave early.” But how do you act on that advice when the power is out, the mobile network is congested to the point of failure, and the emergency broadcaster’s tower has been consumed by the very fire you’re trying to flee?

This isn’t a hypothetical. As Fiannuala Morgan chillingly documented in her article, “No power, no phone, no radio: why comms dropped out during the Central Victorian fires{target="_blank”}", this is the reality for communities across Australia. The wholesale replacement of resilient copper landlines with power-dependent NBN connections, coupled with the shutdown of the 3G network, has created a communications infrastructure that is dangerously brittle in the face of climate-fuelled disasters.

EDIT [2018-06-05]: I have updated the code with the Firmware 1.18.+ releases. The code is available at our Growing Data Foundation Github.

These notes are to assist Australian IoT enthusiasts to get started in connecting a LoPy to The Things Network as it is unfortunately (not yet) straight forward to make them work with the current AU-915 TTN Channel plans. As the initiator of the local Adelaide Community of The Things Network I have been experimenting with a number of devices to connect sensors to #TTNADL. One of my personal favourites is the Pycom LoPy as a nice middle-ground between capabilities and technical complexity.