LoRa

This project is an evolution of my earlier Raspberry Pi SDR experiments, branching from passive radio observation into active LoRa mesh participation using a T-Beam Supreme and a T-Deck Plus running Meshtastic. What started as monitoring signals and spectrum behavior on the Pi turned into hands on experimentation with real world mesh radios: tuning region and channel settings, comparing antennas, adjusting power, GPS, and routing behavior, and observing how a live mesh behaves while mobile versus stationary. The focus is not on building a finished device, but on understanding how configuration choices, environment, and movement affect discovery, acknowledgements, range, and reliability in an imperfect, real world LoRa network and documenting what works, what doesn’t, and what quietly fails when theory meets reality.

Project Logs

Collapse

Hmmm
Rhea Rae • 19 hours ago • 0 comments
Testing
Rhea Rae • 4 days ago • 0 comments
Prototype
Rhea Rae • 4 days ago • 0 comments
Print
Rhea Rae • 5 days ago • 0 comments
!Power
Rhea Rae • 5 days ago • 0 comments
Dummy
Rhea Rae • 01/05/2026 at 11:16 • 0 comments
What in the firmware !?
Rhea Rae • 12/26/2025 at 16:50 • 0 comments

Successful flash of ESP32-S3-WROOM-1-N16R8 using Meshtastic Web Flasher and the Heltec V3 Firmware oldest stable beta version. It has no Lora radio so all it can do is listen to MQTT currently, Bluetooth has to be shut off and it is connected to MQTT through WiFi network connection. At the moment sending messages to public MQTT channel is unsuccessful however I can view and log messages with it making it useful to me as I do not want to use MQTT on the Lily Go devices. I can connect to the ESP through usb on the Pi or over network on the tablet running the Meshtastic app.
Firmware
Rhea Rae • 12/22/2025 at 11:22 • 0 comments

The T-Beam Supreme is running Meshtastic firmware 2.7.16 alpha now, and the T-Deck is still on 2.7.15. I flashed the alpha to the T-Beam because I was having random Bluetooth dropouts on the stable version. It just wouldn’t stay paired after a couple weeks of use. Since switching, Bluetooth has been solid. No issues reconnecting, no lag or weird behavior in the app. Everything feels smoother and more reliable so far.

I have the Neighbor Info module turned on with the update interval set to 900 seconds. That gives me updates every fifteen minutes, which seems just right for how I use the device. It’s usually powered on for long stretches and rides with me, so I want to keep some awareness of what’s around without flooding the channel with unnecessary updates.

For history and memory, I’ve got it storing up to 50 records locally. That’s enough to remember which nodes I’ve seen more than once but not so many that it holds onto ghosts forever. I set the history return max to , and the return window to 30 min, so if another node asks for history, it only gets the latest stuff. That keeps the RF traffic clean and focused on what’s actually current instead of replaying old contacts from earlier in the day.

Range test mode is off. I’m not trying to flood the map or run fake signal spam just to make the mesh look more active. I’ve been running with MQTT off for a while now to keep the map honest, so range test would just mess that up also. It’s better to let actual signal interactions show up over time and build a real picture of what the mesh looks like around me.

The way it’s running now, the T-Beam is basically a quiet observer. It’s not trying to be the center of attention. It listens, tracks what’s nearby, and only sends what matters. No unnecessary noise, just real, useful contact. The alpha firmware has been running stable, and overall this setup feels solid. I’ll keep watching it, but so far no regrets.
Phone app does crash every once in a while during heavy load however the T-Beam is fully operational. No further Bluetooth issues.

-RR
Cold
Rhea Rae • 12/18/2025 at 15:42 • 0 comments

While running the T-Beam node for overnight data collection in my car, I initially used a 1P 3S battery pack built from LG 18650 cells manufactured in 2014. Despite matching cell voltages at full charge and rebuilding the pack twice, I consistently observed that one cell would drop below minimum voltage during overnight runs. This was especially prominent during cold conditions, with ambient temperatures reaching as low as 16°F (-9°C).

The failure pattern repeated: one cell would underperform and trip the pack, even after manual voltage balancing. This behavior is consistent with aged lithium cells showing increased internal resistance and reduced cold-weather capacity.

After two failures, I replaced the pack with a drone battery rated at 3000 mAh, consisting of two 1500 mAh 3S packs wired in parallel. These cells are newer (purchased this year), were always run in parallel from the start, and appear to be well balanced. Since switching, the system has remained stable and reliable during cold overnight use.

This confirms the expected behavior of degraded lithium-ion cells in cold conditions, especially when not capacity-matched. Future deployments will prioritize newer, pre-matched packs rated for temperature and discharge consistency.

-RR
Density Map
Rhea Rae • 12/15/2025 at 10:22 • 0 comments

This map shows the density of Meshtastic nodes detected across the region using LoRa radio only, with MQTT disabled. Each marker represents a unique node discovered through over the air communication, with store and forward enabled and neighbor discovery and is configured for a maximum of seven hops. The result highlights how far low power radios can reach when operating purely as a mesh, without relying on any internet backhaul or centralized infrastructure. Even with limited bandwidth, the network spans a wide geographic area, emphasizing the strength of distributed, peer to peer communication over unlicensed spectrum.
-RR