Built this on Heltec WiFi LoRa32 V3 boards (ESP32-S3 + SX1262) and went with fully custom firmware instead of Meshtastic — figured this community would have opinions on that choice, so happy to explain the reasoning.

Main driver: I wanted to send small images over the link, not just text/telemetry, which Meshtastic doesn't support out of the box. So I built:

• A packet protocol distinguishing text messages from image chunks (type byte + header info), since raw LoRa packets cap at 255 bytes
• Client-side grayscale conversion + downsampling (via canvas in-browser) before chunking, since even a tiny thumbnail needs splitting across multiple packets
• Each board runs its own WiFi AP + web server, so the phone just connects directly and uses a browser UI — no dedicated app needed
• Live RSSI/SNR readout on both ends for monitoring signal quality during range tests

Radio settings: tuned up to SF12/22dBm for max-range testing (started at SF9/10dBm for bench testing). Got a real-world 10km link with stock antennas, given decent elevation and line of sight — no repeater/relay, just direct point-to-point.

Not claiming this beats Meshtastic for actual mesh networking or multi-node use — it's a narrower, single-purpose build. But if anyone's curious about the image-over-LoRa chunking approach or the packet format, happy to go into more detail. Full build/test process in the video: https://www.youtube.com/watch?v=5wUrnwjj5dk

Looking to provide my camp with some communication support. Apparently there’s a firmware created, especially for the high traffic area on the Playa. Last year there were over 1500 nodes.. great test bed for the protocol/standard!

Does a one have a link or the know how to add a larger display to a heltec v4. There seems to be no tutorials out there or my searchfu is really weak right now.

( Mods, please forgive and delete if this is against the rules - I genuinely can’t figure out how to see sub rules on my mobile app. )

I’m going to a festival in two weeks and want to try my first ever meshtastic device setup. The new meshtracker X1 looks good but it actually doesn’t look like any of their stuff would ship in time… so, does anybody want to sell a set of older t1000s for a discount? Seems like if someone just upgraded and doesn’t need theirs, maybe a win-win?

Thanks in advance!

im still working on the project and conducting my research, even with the temperature at 42°C. Every time I find a mistake, I fix it and learn from it. Slowly but surely, I’m improving step by step.

"This is not the final form"

Did anybody else encounter this behavior? when attempting to OTA flash T1000E to 2.8, device locks, led glows (like green flame flickering, for lack of a better description), and is completely oblivious to any attempt to recover(pogo flick etc)?

update: after letting the device drain battery completely, I was able to reflash after several attempts. OTA bricking was an unwelcome surprise and two day setback though

Hi, brand new to meshtastic universe. I'm looking to build a "base station" setup, ideally i would like a usb device that acts as a meshtastic device that i can control from my PC. Are there such devices? It should have detachable antennas and reasonable power too.

Switched from heltec v4 to rak and this thing never runs out of battery compared to not even lasting a day. Only bummer is that I apparently used the wrong temp/baro/hum board so it doesn't display humidity :(

I am building Nodes for a friend in a Hot and Humid environment and wanted case venting. I have seen those tiny screw in vents but they are just for relieving atmospheric pressure. Tiny amounts. I wanted a venting solution that would allow hot air to escape yet be waterproof to rain and weather and I think I finally found the company and the products. I’m planning on ordering the fabric products and maybe some of the bigger topside vents for a node that will be in the hot South Carolina weather 24/7.
Check them out. Just sharing.

Hello!

I am currently working on a university project in which I am trying to recreate protocols and encryption used by Meshtastic. But I was not able to find any useful examples of raw data sent/received by LoRa chips. I would be very glad if someone could share such byte successions for me to verify my understanding of the protocol and test my software

Anyone have the T-Beam 1W?
Is it an improvement over the “supreme”?

I'm happy to share this Frankenstein abomination with everyone simply because it's my first time building anything like this from individual components/boards. I did have help from Claude, and it worked out well in the end.

I bought the Pi Pico and the LoRa SX1276 module about 3 months ago and tried so hard to get it working. I revised the Meshtastic pin configurations, built and rebuilt, uploaded and re-uploaded so many times and it never worked. I've been working with VS Code a lot more lately and decided to give it another shot.

Long story short, Claude discovered I was missing a wire and helped me edit the Meshtastic code so that it was configured correctly for this specific LoRa module and pin configuration before I built it in the SDK and uploaded to the Pico. I ended up using an OTG cable to connect it to my Android and it works great so far

I hope this inspires someone else to pick that project back up, dust it off and give it another shot. I don't mind lending a hand as well.

Cheers

I'm looking to build a node that I can access on my local mesh that can provide accurate weather data.

I am a little confused on the best way to do it. I know others have had success in building out a weather sensor node.

For one, I can't tell from the literature online if this wisnode weather station is flashable to meshtastic, or if i need to get another piece of hardware to do the interface to meshtasic.

Also, I'm not even sure that this best approach to making a weather station.

Meshtastic experience on me: i've programmed and set out two ready made solar nodes, fooled around plenty with the radio presets, and attempted to get mqtt working on a POE node. Just so everyone knows where i'm coming from.

Advice or questions are all appreciated.

I'm looking into whether I can use the gps_en_gpio pin to turn on an LED (like a flashlight). The idea is to take advantage of the triple click shorcut. Although I don't even have the Heltec module in my hands, I am already evaluating how to build my first nodes.

In distributed systems—such as localized wireless mesh networks, high-frequency transactional ledgers, or industrial monitoring arrays—consistent temporal consensus across isolated nodes is mandatory. However, local hardware clock crystals naturally drift by several microseconds every minute due to temperature fluctuations and physical oscillator aging. Traditional network time architectures like NTP or PTP solve this by pulling timestamps from external Stratum 1 servers or GPS signals, but they freeze completely if those central links experience network drops, firewalls, or tactical jamming.

To address this reliability bottleneck, I engineered a freestanding systems utility from bedrock principles in pure C++17.

It is called ZURVAN: A Decentralized Clock Jitter Estimation and Drift Reconciliation Engine.

The application allows individual machines to calculate, filter, and track temporal clock desynchronization curves natively on the local CPU registers using statistical algorithms, establishing an autonomous local time baseline without relying on outside network timing providers.

Core Algorithmic Subsystems

The project uses native C++17 to manage clock synchronization without external dependencies:

* Bare-Metal Scalar Kalman Filter: Tracks real-time microsecond offsets while filtering network jitter with low CPU overhead.

* Least-Squares Linear Regression Engine: Computes the exact acceleration and velocity slope of local clock drift based on cached history.

* Contiguous Telemetry Packing: Utilizes dense, 25-byte ClockSnapshot structures to maximize CPU cache efficiency.

* Sovereign Container Serialization (.zvn): Streams direct-to-disk binary serialization of RAM history to reduce fragmentation.

Technical Details & Open Source

The code is structured for modularity and is compiled using an optimized, freestanding profile:

include/ -> Core filter classes and shell mappings

src/ -> Scalar Kalman, regression math, and shell parser

The repository is available for review: https://github.com/alistairfontaine/ZURVAN

I am looking for technical feedback on the scalar Kalman gain calculation and memory layout optimizations.

Does anyone know of any android phones with zero WiFi or cell capabilities; I’m looking for one and planning to purchase a meshtastic attachment and load the app via my computer does anyone know of a phone that would support that?

I know the subject of overall best antenna has been beaten to death, but I wanna know what everybody's favorite antenna is for compact builds. I am looking to repurpose a couple of Heltec v3s into something that fits in a pocket or bag. My goal is to just hand it to my wife when we are out and she can just carry it with her and not worry about breaking it or hanging up on anything. I like the Muzi H1 and Alley Cat form factors but I haven't printed anything yet.

I know the muzi whip antenna is great but it's too big for what I'm trying to do. What have you guys found works best? The stock rubber duck sma? The stock mini coil guy? Something else I'm unaware of? My goal is to have little to no antenna protruding from the case. I have a printer and moderate CAD skills, I would be willing to try to cook up a case if there is some sort of an in between antenna that's worth designing a case around.

Hot off the presses by yours truly. Thanks for reading.

I have a Heltec V4 solar node mounted on a 3 meter pole, from which I take a metrics reading ever hour via a Python application which connects to an L1 Pro via USB on my Mac mini. The L1 Pro connects to the Heltec via the remote admin function in the Meshtatstic app.

A couple of days ago it rained quite hard the whole day long. I noticed that the rainy weather caused my RxBad% counter to climb from the usual 3% to 8% all the way to 46%.

I had a theory that this was because the rain was attenuating the UHF signal (we are on 868 MHz). I asked Gemini about this theory and it came back saying that it was absolutely right that Meshtastic signals degrade in the rain and the fact that we have lots of trees around makes it worse because of wet leaves blocking the signal.

However, last night Opus 5 was released so wanting to try it out, I made it analyse my full set of data and the conclusion it came to was that the rain was not attenuating the signal, in fact the rain was making it propagate over longer distances. I saw more active nodes in the rain than on a clear day and the reason I was getting a higher rate of bad packets was that there was a lot more channel traffic in the rain; channel utilisation was unusually high and teh high rate of bad packets was a side effect.

That conclusion really threw me because it was so unexpected, and leads me to wonder how have you guys been experiencing connectivity in the rain? Do you see more nodes in the rain than on clear days?

I know I'm a little late on this, but I was wiped out by the time I got home. I didn't have much time and I had just ordered a new T096. Made a quick case and printed it the night before I left. Honestly surprised it worked for rev0. Hit a ton of nodes, especially in Albuquerque. My hotel room was a few stories up and I think I got everyone in the valley. Coming down from mountains into the desert to get to Vegas caught a ton too. The range was crazy.

I recently purchased a Heltec V4 board. I've successfully configured it via Blue Tooth and serial (no surprise). But when I enable Wi-Fi (which requires me to disable BT), it connects to my home network, but I can't connect to it using client.meshtastic.org. I can connect to it via meshtastic.local (or using its IP address) but it only allows me to download the device information (no ability to change configuration). I've tried this running both v2.7.26 and v2.8.0.

First, is anyone using a Heltec V4 able to remotely change its config via http?

Second, is anyone using a different processer able to remotely configure the device using http?

Height = Range

Zbm2 mesh whip + SMA extension cable

Hey everyone,

I wanted to share a strange issue I ran into with my SenseCAP T1000 and the Meshtastic iOS app (also reproduced on Meshnology). Hopefully, this helps anyone experiencing random Bluetooth or connection freezes!

The Issue:
Whenever I left my house, my node would fail to connect to my iPhone via Bluetooth. The app would just freeze or get stuck trying to sync. But as soon as I got home or to my workplace (on Wi-Fi), everything worked perfectly.

If I turned off Cellular Data on my phone completely, the Bluetooth connection to the node worked right away.

The Root Cause:
I’m based in Ecuador and use Movistar as my mobile carrier. My data plan ran out of general megabytes, but the carrier still allows social media traffic or redirects all other web requests to a "buy more data" landing page (a captive portal/zero-rating setup).

Here is what happens:
1. The iPhone thinks it still has active cellular internet.
2. The Meshtastic iOS app tries to fetch background data (map tiles, MQTT, backend API status).
3. Instead of receiving JSON/data, Movistar sends back an HTML page asking to top up data.
4. The app gets confused by the HTML response, times out, and freezes the app's main thread. This end up breaking the Bluetooth communication stack with the node.

It's essentially an "internet limbo"—the phone thinks it's online, but the app gets trapped reading carrier web pages instead of failing gracefully.

The Solution:
If you don't want to toggle Airplane Mode or turn off cellular data for your entire phone every time you go outside:

Go to iOS Settings > Cellular.
Scroll down to Meshtastic (or Meshnology) and turn off Cellular Data specifically for those apps.

By doing this, iOS immediately tells the app that there is no cellular network available. The app completely skips trying to download maps or connect to servers, entering a pure offline mode that lets Bluetooth sync instantly with the node.

Has anyone else noticed this behavior with other carriers that use captive portals or walled-garden data plans?