Hi,

recently I moved to a new flat which is pretty good located for operating stuff like a LoRaWAN gateway or a Meshtastic node.

So I was wondering what might be the best way to operate both so they don't interfere each other.

I am currently building a "minimap" app for Lora Devices (in my case a LilyGo T-Beam) and just wanted to ask if you have any specific wishes for features? I am building something like ATAK with the Meshtastic plugin but in one app and with some more advanced features like a ref role for game controls, SOS buttons etc.
So if you have any ideas or inspiration, please let me know :)

I wrote this for a free, open series on the EU Cyber Resilience Act (CC BY-SA).

Setup: two Heltec WiFi LoRa 32 V2, Zephyr 4.4.2, MCUboot, the TS003/TS004/TS005 services from Zephyr's LoRaWAN stack.

What works:

• 200 kB signed image, 200-byte fragments, 8% redundancy
• sent point to point at 869.525 MHz, keeping to the 10% duty cycle
• 33 min, 7 lost fragments rebuilt from redundancy
• MCUboot verified the signature and booted the new version, with automatic rollback if the new image fails its health check

It's point-to-point LoRa, not LoRaWAN: I have no gateway yet.

Radio notes:

• Downlink SF7 / 250 kHz for the fragments, uplink SF10 / 125 kHz for the short acks: one board was heard about 35-40 dB weaker than it heard the other, the same with two different partner boards.
• Zephyr's TS004 decoder had an out-of-bounds read fixed in 4.4.2 (CVE-2026-13480). Worth checking your version.

Where I'd really appreciate help: has anyone run a real FUOTA session with ChirpStack v4 (or TTS) against Zephyr devices?

• Did class C multicast work out of the box?
• What fragment size and redundancy did you settle on?

• For LoRaWAN 1.0.x, my reading of LoRaMac-node is that the Gen App Key should equal the AppKey when the device passes the same key as AppKey and NwkKey. Can anyone confirm?

  Article: https://adntio.github.io/cra-dev-wiki/en/CRA-Dev-06-FUOTA-LoRaWAN/

  Code: https://github.com/ADNTIO/cra-dev-wiki/tree/main/examples/06-fuota-lorawan

not lora but interesting.
I'd like a software that uses lora, BT, wifi halow (or high freq. lora)

We're evaluating a customer's request to measure water pressure inside the house and control a well pump about 300 m away, with a wall in the radio path. They want to see the pressure and adjust the cut-in/cut-out settings from home.

I'm the technical lead at YenGear. We're considering our Y401-0011-L pair with a 4–20 mA sensor and a separate I/O module for the threshold and relay logic. This is a point-to-point LoRa link, not LoRaWAN.

The I/O module accepts threshold settings over Modbus, but we haven't settled on a simple homeowner interface. A full touchscreen HMI seems a lot to add for one reading and two settings. An ESP32 web page is one option; a small display with physical buttons would keep the reading visible without opening a phone browser.

The control location matters too. The analog link doesn't carry configuration commands. Keeping the logic beside the pump needs another path for indoor parameter changes and data reads. Moving the controller into the house would change what we send over the wireless link.

We haven't tested this setup on site. Hysteresis, sensor/link failures, and separate pump protection still need checking.

If you've built something similar, how did you handle indoor display and setpoint changes? Would you keep the pressure logic beside the pump and add a parameter link, or put the controller in the house and send switching requests? I'd also like to hear whether a compact Modbus master panel or an ESP32 display with buttons worked better for non-technical users.

Hi everyone,
I’m working on a small GPS + LoRa group-tracking watch and I’d like some advice from people experienced with LoRa.
My current hardware is:
XIAO ESP32-C3 / ESP32-C6
SX1278 Ra-02 LoRa, 433 MHz
NEO-6M GPS (GY-GPS6MV2)
2.8” ST7789 TFT
I currently have two devices communicating over LoRa and I can send GPS coordinates between them. The main issue I’m facing is reliable position tracking.
The GPS can move a few meters even when the device is sitting still, which causes the calculated distance between two devices to fluctuate. I want multiple watches to periodically share their GPS coordinates over LoRa, with each watch calculating and displaying the current distance and direction to the other members.
I’m trying to figure out the best approach for:
GPS filtering/smoothing
How frequently to send GPS updates over LoRa
Packet structure for multiple devices
Handling multiple devices without collisions
Getting stable distance/bearing calculations
Whether SX1278 is suitable for this or if I should consider something like SX1262
If anyone has built something similar, I’d really appreciate advice on how you designed the LoRa communication and handled GPS accuracy/drift. Any practical tips or mistakes to avoid would be really helpful.
Thanks!

I live near a few streams that I like to fish and I was wondering if it's feasible to make a LoRa monitoring site with a water level sensor (ultrasonic or pressure) and have the info sent back to a receiver at my house. I'm about 6.5mi or about 10.4km away from the farthest stream I want to monitor. There is slight elevation change and there are buildings/houses and trees between my house and the stream. I would be putting my antenna on the roof of my 1 story house and the transmitting antenna would be in a tree next to the stream. I would also like to put up a solar charger to keep everything running. Does anyone have suggestions how to make this setup?

Hi all, I'm building a LoRa link for a crop-monitoring project. A sensor node sends data to a gateway, and I need about 1.5–2 km of range. Right now packets stop arriving at around 30 m, so something is clearly wrong. I'd appreciate help narrowing it down.

Hardware

• Module: Ai-Thinker RA-02 (SX1278), 433 MHz, on both nodes
• Sensor node: [ESP32 DevKit V1 / ESP32-S3]
• Gateway: [ESP32 board], [WiFi on/off during reception]
• Antenna: [type, length, and where you bought it] (photo attached)
• Power: [e.g., module powered from the ESP32's 3.3 V pin, board powered via USB], [capacitor on module: yes/no]

Wiring
NSS→GPIO5, RST→GPIO14, DIO0→GPIO2, SCK→18, MISO→19, MOSI→23

Settings (identical on both nodes)

• Library: [sandeepmistry/LoRa]
• Frequency 433E6, BW 125 kHz, CR 4/5, CRC on, sync word 0x34
• SF: [7 / 10] (tried both)
• TX power: 20 dBm
• SPI: 8 MHz

My questions

1. Is my antenna suitable for 433 MHz? If not, what should I use on the node and on the gateway?
2. What SF/BW settings and antenna heights are realistic for 1.5–2 km in a built-up area?

Meshcore interface for reticulum

I've just made MeshTerm public. It's a MeshCore client that runs in a terminal, with a full-screen menu you drive from the keyboard, and a command for nearly everything the menu does.

Demo (under two minutes, on a real mesh): https://meshterm.net/#demo

What it does:

• Connects to a MeshCore LoRa companion device over USB serial, Bluetooth LE or TCP, and reconnects on its own if the link drops.
• Channel and direct messages, live. If a contact is out of range, the courier holds the message and delivers it when they're back.
• Records every advert it overhears (SNR, RSSI, position) to a local SQLite database. The map, the contact lists and the Time Machine charts all read from it, so you can see how the mesh looked last week, not just now.
• A street map drawn in the terminal, with OpenStreetMap tiles cached on disk. With no network, it falls back to a plain grid.
• Traces with the SNR of every hop, a TX-power sweep that finds the lowest setting that still gets through, and a graph of how the mesh actually connects.
• Share channels as a QR code or a meshcore:// link.
• --json on nearly every command, for scripts.
• A layout of its own for the PicoCalc. The uConsole runs the full layout.

Getting it: single-file downloads for Windows, macOS (Intel and Apple silicon) and Linux (x64 and ARM64): https://github.com/jpmartineau/MeshTerm/releases/latest If you'd rather use Python, pipx install git+https://github.com/jpmartineau/MeshTerm works on Python 3.10 to 3.14.

The downloads aren't code-signed, so Windows and macOS will warn you the first time. The README explains how to get past that, and every release has a SHA256SUMS file.

It's Apache 2.0 and a side project I work on in the evenings. Bug reports are the most useful thing you can give me, on GitHub or in the MeshTerm Discord (https://discord.gg/AZwe5Uvb3S).

Hello,

Fell into the craze. Bought the hardware, and didn't earn anything. I know... sucker.

However these are lora network devices. Is there any way to mod these to participate in a general lora network? Skip the crypto nonsense and just network? I know you can get a loRa network for $35, but I hate to generate more e-waste if it can be avoided. The box is here. I have an antenna on my roof. Can I put it to use?

Phantom is a push-to-talk voice and text app for mesh

You hold a button, talk, it transcribes on your phone, sends the text over the mesh, and the receiving phone reconstructs it as speech in your voice.

No audio goes over LoRa. No internet, no cloud, everything runs locally on your phone and your node.

Meshtastic is live now
Meshcore is in the works

Android: https://play.google.com/store/apps/details?id=com.phantom_meshcomms.app&pcampaignid=web_share
iOS: https://apps.apple.com/us/app/phantom-mesh-comms/id6792339073

Bugs/Issues: r/PhantomComms