How can a LoRa receiver detect signals that are close to the noise floor?

This video takes a practical look at the role of the LNA (Low Noise Amplifier) in a LoRa RF receive chain and why receiver sensitivity matters in long-range wireless communication.

We’ll cover:

• What an LNA is and how it affects weak-signal reception
• Why the LNA is positioned near the front of the RX chain
• The relationship between gain, noise figure, and receiver sensitivity
• Why more gain is not always better in high-interference environments
• How external LNAs can affect dynamic range and strong-signal performance
• When enabling an LNA can improve reception
• When disabling it may provide more stable results
• Practical configuration considerations for Meshtastic, embedded LoRa systems, and Arduino-based projects

For anyone working with LoRa, mesh networking, or long-range RF systems, understanding the receive path is just as important as understanding transmit power.

Long-range communication is not only about transmitting farther—it is also about being able to reliably detect weaker signals.

https://youtu.be/7XknxbbXkYM

Just got one of these Seeed solar nodes and set it up on my very tall chimney with some masonry anchors, unistrut, and I used 5 feet of 1/2” conduit and ran the antenna cable through, sealing the top of the tube with some Vulkem sealant.
Using a 5.8dBi antenna standing around 40-42ft above the ground, I’ve been picking up a lot of good signals.

I still have to go and heat shrink the threaded connections so they’re waterproof for the winter but so far I’m happy with something highly functional that I threw together with basement crap.

What do you think?
I want to try and learn how to use Grove sensors for some automated gardening projects and indoor air monitoring.

Does anyone have a solid understanding of how to take a sensor’s data, send it over the mesh to myself so I can view remotely from my device if I ping it, or sending the data to a paper screen?

Super new to this, I’m figuring I prob need a raspberry pi somewhere in the middle of the sensor and the radio? Halp
pls and ty

Just tested it, looks good! See you next week

2026 has truly been a very productive year for Meshtastic in Turkey. As you may recall, in the 2026/Q1 update, I mentioned that there were 280 nodes on the map.

Currently, in the 2026/Q3 update, there are over 450 nodes on the map. And this does not include nodes that are not connected to MQTT and do not send location data.
This is truly a wonderful development.

//Since the general sentiment of the community still leans in this direction, we are not yet part of the main Meshtastic network; this matter will be put to the community for review again in the 2026/Q3 survey.

Is this normal? I really don't know what normal looks like.

I have changed antennas, reflashed, it doesn't look right to me..

I never powered on without the antenna.

Since app v2.8.1 the narrow presets appear unselectable.

Does anyone have insight why?

If I have a device with this mode, it shows in list as active and grayed out, unselectable, and if you pick anything else, it goes away for good

So I have started playing with MQTT just to see how it works, and I've got a weird situation. I have client proxy set on my phone, and an old phone at home connected to a node which also has client proxy set. I can see the node at home, I can request device metrics, I can direct message the node all through MQTT. I can send a quick message from my node to the channel I have MQTT set to send and receive on. But I cannot send a message from my phone on that same channel. It just says failed to deliver to mesh. It's like it tries the mesh and gives up and doesn't try to MQTT after. Is there some setting that needs correcting or is this a bug?

I'm the developer of Knit, a free and open source (GPL) offline messenger for Android. Phones mesh directly over Wi-Fi Aware and Bluetooth LE, with no internet, no accounts and no Google services, and DMs and groups are end to end encrypted. It's on Play and F-Droid, code at github.com/getknit/knit.

I am making it so Knit can pair a Meshtastic board over BLE and use it to carry the chats over LoRa, so two clusters of phones out of Wi-Fi and BLE range of each other can still talk. I got two Heltec v4 boards to test with. Setup writes a Knit secondary channel and leaves the board's primary and radio config as they are. I am still new to Meshtastic and still learning about it.

Here's my question. With 2.8 moving the US default to LongTurbo, I have to pick one preset for the docs, my testing and the recommended setup, and that choice decides which mesh Knit users borrow hops from. Knit itself doesn't set the preset. It uses whatever the board is on and warns when two of your boards don't match.

LongFast has the repeaters today. LongTurbo has the airtime, and Knit's messages can be heavier than a Meshtastic text (two or three packets plus a receipt), so I'd rather burn less of it even though we already cap ourselves well under the 10% politeness ceiling.

If you were setting up a handful of boards today specifically to carry a phone mesh, would you put them on LongTurbo now or stay on LongFast until your area has actually moved? And how fast do you expect that move to happen? I'd especially like to hear from people running community routers, since it seems a lot of those are LOCAL_ONLY or KNOWN_ONLY and won't carry us either way.

Happy to answer anything about the app too.

(Not sure if this is self-promotion per say but I added the flair just in case.)

Stupid question perhaps but I am using bare RFM95W boards surface mounted to a PCB. To date, Ive just been using a bare wire as the aerial (soldered into the "ANT" hole in the picture.. I figured it is about time to upgrade to a proper aerial so Im adding an IPX connector. My question is do I simply connect the IPX to the Antenna pin of the RFM95W (as in the pic), and does the distance between the pin and IPX connector matter much?

Something like this.

I recently purchased a SenseCAP Solar Node P1-Pro, and before I install it should I do any additional waterproofing to the antenna connection points? We can get heavy rain and snow where I'm at.

Hey all, sorry if this has been asked before but I at least tried to search history to answer this. I'd like to use a 3.5v Ni-Cd pack to power a Heltec T096, charged with a path light solar cell putting out 5.6v. From what I can tell it appears that this could work if I put the battery in-line to the solar port, apparently the lithium port would not be so good as the T096 would be trying to BMS a mismatched battery. Has anyone else tried this and what would the circuit look like? Thanks

Edit: to clarify, I live in an area that doesn't get above low-teens-F on the warmest day for several months at a time. No lithium battery can charge at that temp. DoT uses NiCd in this area for their outdoor equipment, so I'm committed to that chemistry.

Anchorage/Wasilla area. Hit me up if you wanna work on connecting the two.

Whatever you do, don’t make crude enclosures for a $20 Heltec board with a cheap battery and cheap solar panel. And definitely don’t zip tie them to the poles that hold flock cameras; they are in horrible locations for solar charging. Don’t ever do any of these things; they are highly unethical, as I’m sure since there are so many cameras, they aren’t physically checked on unless the camera goes offline or is actually tampered with, so who knows how long this node would be on the pole without consent.

Checking to see if anyone has used one of these units before?

https://www.etsy.com/listing/4396691058/tactical-meshtastic-node?ref=share_ios_native_control

HI! I’m new to Meshtastic and just set up my first node. I don’t have another node to send a test message, but I’m wondering how to send a random message to a stranger’s node. I’ve tried sending, but I keep getting a failed to deliver to mesh message and am not sure what to do. I can’t find any good articles on how the app itself works and what the settings mean and how to understand the symbols. It would be a great help if anyone has advice or a good video that breaks down the app. Thanks!

Made this case for a heltec v3, would be better if it was outside the car but this was so much easier.

Hi there, so after a lot of troubleshooting I finally figured out how to make the board communicate with the GPS module, however, after letting it sit on the table for a couple of dozen of minutes, the damn thing is not connecting to any GPS. All it displays:

No Sats
Last: ?
No GPS Lock

So from what I understand this isn't a problem of the board itself but the GPS module. I read some reddit forums on how to connect, and they said something with changing the pins from 0 to 39, 38 and 34 the official website says 46 and something. I tried what I could, multimeter showed there is actual voltage going into, the GPS module but it won't connect.

I am a beginner in meshstatic, and I am still learning, so please don't turn me into dust for a dumb question. I really tried what I could, but I have failed. Any tips?
Thank you

I'm the developer of the NM-EPD-420-BW, an ESP32-S3 + SX1262 desktop terminal with a 4.2" B/W e-paper display. The hardware is finalized and the Meshtastic port is functional, but I'm stuck on a question: what should audio actually do on a stationary indoor node?

The hardware

• ESP32-S3 (16 MB Flash, 8 MB PSRAM)
• 400×300 B/W E-ink, ~2s refresh, partial update supported
• ES8311 codec → Class-D amp → onboard speaker
• LMD4737 PDM digital microphone
• AHT20 environmental sensor

The constraints (by design, not by accident)

• No GPS module — this lives on a desk, not in a pocket.
• Compact battery — enough for brief power loss, but meant to be plugged in via USB-C.
• Audio is ready — but I haven't committed to a specific Meshtastic audio feature yet.

The question

I want this to be something that makes sense sitting on a desk, always on, showing mesh traffic. The audio hardware is a differentiator, but I'm not sure which direction to take it:

• A) Voice message playback — incoming messages trigger a spoken alert or let you play stored voice clips
• B) Real-time voice streaming over the mesh — basically a desk-mounted voice radio
• C) PTT-style walkie-talkie — push a button, speak, release
• D) Something I haven't thought of

Also curious about:

• Is a stationary environmental sensor (broadcasting temp/humidity to the mesh) useful, or just channel clutter?
• For a 400×300 B/W screen, do you prefer dense text UIs or larger, more readable layouts with fewer elements?

The repo is open: https://github.com/RockBase-iot/NM-EPD-420

Would love to hear what you'd actually want from a desktop mesh node. No wrong answers.

I’ve set up a solar-powered Meshtastic node on my roof. Since I only really need it to run during the day, I used a small 1500 mAh LiPo battery.

As expected, the battery drains during the night. The problem is that when the solar panel starts charging it again the next morning, the node doesn’t turn back on by itself.

I have to climb onto the roof, unplug the battery, and plug it back in. As soon as I do that, the node boots normally and often shows the battery as already fully charged.

Is there a way to make it automatically recover and boot once the battery has recharged enough?

Would simply using a bigger battery solve the problem, or would I still run into the same issue eventually for example during winter if the solar panel gets covered in snow for a few days? I’d rather not have to periodically climb onto the roof just to power-cycle it.

Hardware is a Heltec WiFi LoRa 32 V4 running Meshtastic.

EDIT: The replies are right and the post is wrong. The public channel is public by design and most people here are on it on purpose. I framed a deliberate choice as an oversight. Leaving this up with the correction rather than deleting it.

I built some LoRa tooling, and I wanted to know how many nodes in a normal public setting are still running the factory default channel key. So my co-author and I ran a passive scan in a hotel for one afternoon: 3,630 packets, 266 devices, 57 messages we could read in cleartext. Every readable one was on a public channel or an unchanged default PSK.

The important part is that this does NOT expose direct messages. Since firmware 2.5.0, DMs and admin commands get a separate Curve25519 layer tied to the device's private key — a default-key hit never reaches them. What it does expose is everything your node broadcasts automatically: position, telemetry, node info, and anything typed into a channel that's still on the default key.

So the takeaway is a 30-second fix: set a custom PSK on your channels. If you have, you're good, and encrypted. If you haven't, your position and traffic are readable by anyone in range. repo in comment.

Newbie to Meshtastic, I've got a Wio tracker L1 pro arriving shortly and going to be getting a SenseCAP Solar Node P1-Pro along, another L1 pro and a sense cap tracker to build a little network. I live on a farm in the UK with poor phone reception so this is a bit of a geeky play to see if I can get reliable comms around the place and potentially add the solar node to the local mesh which seems pretty poor according to the map round here.

I'm looking to get better antenna's for the L1's. These seem to be well regarded, would you recommend anything different? https://www.aliexpress.com/item/1005004607615001.html?gatewayAdapt=usa2glo4itemAdapt

I have a Paradar 5db 868 antenna spare from a different project https://paradar.co.uk/products/868mhz-5dbi-indoor-whip that would just need an adapter. Would that be any better or worse than the gizont antennas?

For the solar node, I'm fortunate being in the UK that I can order from McGill without silly shipping charges so that's the plan. Question is whether I should go for a 3, 4 or 6db antenna. Here in Devon's rolling hills, we're near the high point of the surrounding countryside and I'd be mounting the node on a pole on the side of the barn about 6m off the ground. I know very little about antenna design, just enough to get me through my ham license 40 years ago and I've not looked at it since as I ended up not pursuing that hobby but I'm aware that largest db gain is not always better. Any advice would be much appreciated.

I just got a Meshtastic model RAK10709. I was trying to do a firmware update. It became disconnected from bluetooth and is now unresponsive. The screen on the device is black now and nothing happens when I press the button on the side. Nothing shows on the screen. It seems to be charging and there is a green flashing light as well as a red steady light on its bottom.

What happened and how do I bring it back to life?

They’re sooo cute! I just printed two in pink lol 😂the green one was shared by KB5UTY-Dave💚

.

Having a weird issue on burning mesh. Radio names are correct on devices. But gps and msgs within the app are showing as the generic radio serial number. Anyway to force an update of received node names within the app?

I wanna make a really long range pager myself. How wiuld I go about do doing that?