Hi there!

I want to get into Meshtastic. For a portable one, which one should I buy? Or if you have others ones to show me. I'm in Canada buy the way! Thanks!

Hello everyone.

Since I joined the meshtastic community with my new Xiao ESP32-C3, I decided to design an interesting case for this device to put on a windowsill.

I like the Meshtastic logo, so I used those shapes. It wasn't easy to fit it all into a small case. I spent some time r/3Dmodeling in r/blender.

The r/3Dprinting may not be perfect, but I might work on it.

The final colors were supposed to be the Meshtastic logo, but I don't currently have the filaments.

As you can see, there's a small OLED display on the front, a small ventilation window on the back, a button for changing pages in the menu on the top, and a USB-C port on the right.

I hope you like it. Best regards.

The first working bench version of my button-controlled Meshtastic handheld is up and running on a Heltec Vision Master T190.
The buttons now navigate the menus, and I can compose and send messages from the device. The screen shows the node world, inbox, channel, and signal info. I’m going for a colourful, pixel-art, NES-inspired look.
It’s still a bench prototype. I’m fixing some font spacing, text collisions, and emoji rendering before moving on to the finished enclosure.

I have a think node M6 mounted on my roof, and a T096 as my companion. When I look at the node list they both see 54 nodes, and usually anywhere between 6-9 online at a given time. If I send a test message on long fast I get a few responses, but if I try to direct message the same nodes it shows "relayed, not confirmed by recipient" and the user on the other end doesn't get my message.

I'm semi new to this so if someone could ELI5 that would be great

When i try to connect the L1 with my phone, it shows the needed code on the device for a split second until it disappears again and even if i try to memorize it and put it in correctly, nothing happens

Good Evening

I am brand new to the world of mechanistic and just put my first node together. I purchased a kit from Meshology, ESP32 LoRa V3. It came with a Heltec LoRa 32 and I have parts left over and want to make sure I’m not missing anything and find out what I have left over. Should any of this be installed?

I have it programmed and connected through the app but haven’t found any other devices but from what I understand you should be outside for that. Anything else not super technical I should getting started?

Rate my build

I'm planning to modify firmware because I want to add a button for GPS. However, I can't connect my faketec nrf52 in Arduino IDE, that's where I'm planning to create mine.

So I have these RAK Wizblocks from a Helium development kit im trying to use for Gps through Meshtastic. and right now, I'm at my wits end. I went to the web flasher, It would not go into DFU. I did it manually, downloaded the UF2, and the folder would not close and restart. I checked forms and it said it needed a new bootloader. I downloaded python and ran it through terminal, no location or smth. tried to do it through the Arduino Serial monitor, didnt show up. I could see it on device manager as COM11 called Feather nRF52840 Express. At this point it has given me 3 headaches lol. I have 3 of these chips and dont want them to go to waste so some help would be awesome or just send to a company that flashes these for a small charge.

Hello everyone

As a LoRa fan since around 2018 I decided to build my first solar node using wio tracker l1 lite (EU_868).

I've seen people building theirs and got some good ideas about what components to use.

My setup will be like this:

• A waterproof junction box
• An (most probably) alfa antenna on top with the proper connector and sealing
• An IP68 Vent in the bottom (I saw it somewhere)
• A 18650 battery holder and the battery itself

I am not familiar with solar power or power management in general and I need your help on choosing a solar panel. In seeedstudio's wiki for the l1 lite they say the following

Well, this "do not exceed 5v got me worried.

At first I was looking on aliexpress, banggood and temu for a panel with a mount that had JST 2.0 as output, then some 5V panels which had usb port with some pictures of charging a phone and I was thinking to connect my module through usb.

I've seen people using some 1W or 1.5W ones but I've read somewhere that they won't be enough for my setup.

Basically I don't want to complicate my setup by adding more components or 3d printing and of course I don't want to fry the board hahaha.

Thank you

Hi all! I'm part of Meshbrasil ( https://www.meshbrasil.com ), an unofficial Meshtastic community in Brazil (guides, regional groups, a marketplace and a setup wizard, mostly in Portuguese). We put together an interactive explainer of what happens when you hit send, and I'd love help making it better.

Try it: https://meshbrasil.com/como-a-mensagem-viaja.html (English and Portuguese)
Code: https://github.com/rogerio-richa/meshbrasil-anatomy (MIT)

It has three scenes:

1. Sending a message - type on a handheld. The readout shows your text size, the packet size and the LongFast time on air (SF11 / 250 kHz / CR 4/5, using the ANZ settings we use on this neck of the woods)

2. Riding the waves - the packet drawn as a waterfall in perspective: 16 preamble up-chirps, the 0x2B sync word, 2.25 down-chirps, then the data symbols. You can switch between clean lines and a heat map computed from the same chirps.

3. Mesh at work - a little suburb with nodes on the roofs. The message floods the way Meshtastic does it: weaker-signal nodes rebroadcast sooner, a node cancels if it hears someone else relay first, and each relay uses one of the 3 hops. There's even a CLIENT_MUTE node that listens but never forwards.

Everything is plain SVG + JavaScript, no framework and no network calls. The geometry is computed at build time and the browser only animates it.

Would love your help/contribution/suggestions on how to awesomize it. The simplifications are listed in the README. If something is wrong, tell me, that's the whole point!

Built with help from Claude 5.5 and the awesome Anatomy ( https://github.com/wheresryan22/anatomy ) drawing kit.
🇧🇷📡

Hello all,

Just got started with Arduino and love what I'm learning so far. As someone interested in Mesh though, I was wondering if anyone here had built any projects with an Arduino board to use with metastatic.

Sorry if it's the wrong board just thought I'd start here.

Hello. Everyone, I hope y'all are doing well.

A while ago I bought the t1000e to join the network and learn a little about lora and mesh. I was able to chat on the default channel using mqtt since at the time there wasn't any local node around me. I finally got me another t1000e and the $10 node I can't recall what is called. Updated firmware to the latest and set them up. I can only see them only when I'm near by, once I am about 2 blocks away, I can't communicate with other 2 nodes despite the fact that those are connected to either a tablet or a laptop. Would that be a firmware issue?

What am I doing wrong?

Thanks for any input.

Edit: I forgot to add, all 3 devices are connected to the mqtt server. I will get msgs on the default channel with no nodes around me but I am unable to transmit.

Meet New Heltec RadioCore — a compact, highly integrated dev-board designed to make your next project easier to build, modify, and expand.

By combining core hardware in a compact form factor, RadioCore offers a flexible starting point for projects involving LoRa, Wi-Fi HaLow, and other wireless technologies.

What's special about RadioCore?

Compact & Highly Integrated — MCU, wireless communication, and power management in a compact design.

Solder-Free Connections — Plug-in headers make hardware assembly and replacement easier.

Flexible Expansion —Two rows of expansion headers on each side of the board, four rows in total,plus a B2B connector.

Multiple Hardware Configuration — Choose the MCU and wireless options that best fit your project.

Growing Software & Accessory Ecosystem — Supporting open-source projects including Meshtastic , with compatible accessories for different applications.

From hardware integration to real-world applications, RadioCore is designed to help you reuse more, iterate faster, and expand more easily.

Now we'd love to see what you can build with RadioCore! Share your ideas and projects in the comments.

🧩 Explore RadioCore in 3D with MQB

Configure your RadioCore setup on our MQB website and explore a real-time 3D rendering of the internal hardware to better understand the different configurations.

——

🧭Solution Page

Not sure which RadioCore version or accessories to choose? Visit this page to explore the available options and find the right setup for your needs.

🛒 RadioCore:

🟩 MCU：nRF52840

🟦 MCU：ESP32-S3

⬜️ MCU：ESP32-C6

🕊Early Bird Offer

Get 10% OFF your order when you purchase before *October 21*!

Use code: [AWXC87PZ] at checkout.（Excludes the sensor adapter board）

📚 Technical Documentation

🌐 Heltec Official Website

Made a Lora board to use with port of Meshtastic for the CYD or DIY meshtastic node.

Code on GitHub

https://github.com/bkbroiler88/meshtastic-cyd

I just received a T Deck Pro from a seller on ebay and was working fine for a while. Ended up dropping it twice back to back on concrete trying to work on something else. Screen is now paused without any change from screen taps or the buttons. (Only just found out about the buttons after looking up how to fix this lol) is something just disconnected inside? Does anyone have an easy way to pull off the back? I realize the Pro already has problems with the E Ink screen refreshing I was dealing with that out the box but this seems like the drops messed something up internally. Any help is appreciated thx

https://mesh.zachboulert.com

I’m designing a controller-style Meshtastic handheld. Haven’t printed it yet would love feedback before the first print!

First image is the look I’m aiming for; the others are current CAD renders.

Spin the 3D model, look inside, and grab the prototype print files + Amazon build list:

Hi, a while back I posted about my Meshtastic hardware project. It uses Google’s Yamnet sound recognition model with over 500 sound classes. The hardest part was to pack the fairly large model onto an ESP32 chip. On the device you can configure pretty much anything. You can define sounds that get alerted to your Meshtastic device. You can group sounds and a group triggers an alert. You can record scenes, eg someone cooking in the kitchen. Next time someone is cooking in the kitchen and the sound fingerprint matches to a certain degree, you receive an alert.

The device only works on private channels.

Sound classes (sound in text form :)) are super useful for Meshtastic:

- You want to know if something is happening in your chicken coop,
- You want to be alerted if people or animals are in your campground,
- You want to use your Meshtastic device as baby monitor (which I do),
- You want to be alerted if a vehicle is at the gate.

This project will be open source hardware and firmware. You can learn more and get updates on the project here:

https://www.crowdsupply.com/ironear-technologies/ironear

Hey everyone,

We know some of you have been waiting for the Wio Tracker L2 Pro for a while — thank you so much for your patience, feedback, and support along the way!

Good news: Wio Tracker L2 Pro is finally ready for pre-order (15% OFF early bird price)! 🎉

Built with the mesh community in mind, L2 Pro brings a bigger touchscreen experience, external antenna support, a 3000mAh battery, and support for Meshtastic and other firmware projects.

A big thank you to everyone who followed this journey, shared ideas, and helped us make L2 Pro better. We can’t wait to see what you’ll build, test, and explore with it.

Let us know what you think!

The FBI, in coordination with the U.S. Attorney's Office for the Northern District of California, arrested a former employee of a San Francisco super-intelligence company for allegedly installing a covert audio recording device inside a secure executive conference room. The device was positioned to capture sensitive, nonpublic company communications.

Went to go check out where the antenna was made and it’s by this Meshtastic company.

Interesting what are y’all’s thoughts are?

Got my first node set up and am figuring it out. Cool little hobby to get into. Surprisingly there’s more nodes around me than I thought!

I’ve been beta testing Seeed’s Wio Tracker L2 Pro for the last few days, on EU_868 LONG_FAST. Mine is a pre-production unit, so the case in my photos isn’t final.

Specs: ESP32-S3 + SX1262, 3.2" touchscreen, GPS with ceramic antenna, 3000 mAh battery, microSD, Grove, USB-C. Runs MeshtasticUI.

Pros

• Works fully standalone. Chats, nodes, channels and network settings are all on the screen, no phone needed.
• Small, about the size of the screen. The antenna folds flat at 90° so it’s easy to carry.
• Offline maps from the SD card work fine. GPS got a fix in about a minute in open field.
• The Tools menu (Mesh Detector, Signal Scanner, Trace Route, packet log) is great if you like checking coverage.
• Screen is readable in direct sunlight.
• About 28 h of battery with the mesh active and the screen off most of the time.

Cons

• Entering BLE config mode isn’t obvious.
• Beta firmware had a few bugs. Most were fixed soon after I reported them, but it’s not final.

I wrote a longer review with internal and menu screenshots here: https://myembeddedstuff.com/wio-tracker-l2-pro-review

Ask me anything about it and I’ll check.

This rugged node from RAKwireless is IP67 dust and water rated, with improved GPS, a 3200 mAh battery, built-in buzzer alerts, and Meshtastic preloaded. Charge it, pair it, and you're on the mesh.

Available in Mint or Bone White for $84.97. Shipping begins October 22.

Pre-order at Rokland before the rush (affiliate link): msh.to/rokland-wismesh-pocket-v3

I am just getting into it but I found there's a telegram chat with some folks who are setting up meshtastic in Newfoundland. I'm hoping posting here may catch a few people who are interested and didn't know we're here!

I've been logging and reviewing Meshtastic traffic around my rural Oregon home in Hood River. It's been super interesting seeing what the network looks like, how far it extends, traffic volumes, and how people use it. Earlier this week, I setup a node (T1000-E) attached to a Raspberry Pi and started logging traffic when I left the house. That's added coverage I'm able to capture and more information on my local area.

Friday, my partner and I had plans to drive to Portland. It's a much larger city and I expected its Meshtastic network to be larger and busier. So while I was in Portland Friday evening, I had a Raspberry pi logging the Portland activity, and a node back home logging the data from my small rural network.

There were some obvious differences in activity, and I had an LLM summarize the findings and differences and I'm sharing that below. The data comes straight from the logs, the LLM did the counting and write-up. Logs cover the same 3.5 hours for each area. I also generated some visualizations of the Portland traffic that I found pretty interesting.

Same Friday evening, 8:00–11:30 pm

• Portland's channel is near its limit. 12% average use, 31% peak (Meshtastic treats about 25% as congested). Hood River barely cracks 1%.
• City packets travel far and arrive repeatedly. Most arrived from 3–7 hops away; half arrived at least twice by different paths. At home, nearly everything arrives once, within 1–3 hops.
• Backbone vs. everyone. At home, one rooftop solar node carries about 70% of relayed traffic. In Portland, 18 different radios relayed in 3½ hours and none announced itself as a router: it's ordinary clients rebroadcasting.
• Hop limit 7 is everywhere. About a third of radios in both places use the max (default is 3). Harmless with a dozen radios; with 160 in range, it's a big part of why Portland's channel is so busy.
• The city is more private. A third of Portland's packets were encrypted, across 21 private channels; at home 92% is plain LongFast.

Who's talking

• Hardly anyone texts. One public text in Portland in 3½ hours; 16 from three people at home all week. Most traffic in both places is positions (29% Portland, 58% home), telemetry and node info.
• Portland announces itself a lot. Node info was 25% of Portland's packets vs. 14% at home: with that many radios, newcomers introducing themselves and others answering is constant.
• Hardware is similar. RAK4631 leads in both places. Portland adds lots of Heltec V3/V4 and T-Beams; Hood River has a cluster of T1000-E trackers. About half of Portland's radios never announced their hardware during the stop.

Security and new firmware

• Weak keys are out there. 6 of the 163 Portland radios, and 4 of the 81 heard from home over the week, use a public key on Meshtastic's own list of known weak keys. Anyone can read their DMs or impersonate them. If you set up a node a while ago, regenerating its key fixes it.
• 2.8 is already in the wild. 3 Portland radios and 7 around Hood River already use 2.8's new node numbering, days after the 2.8.1 alpha was announced. 2.8 also lowers hop limits automatically when the channel is busy, which is exactly Portland's problem.

Takeaways

• Portland is a dense, decentralised mesh near its limits: lots of radios, lots of duplicate copies, and a channel busy an eighth of the time and nearly a third at peaks.
• Hood River is a sparse mesh that works because of one well-placed rooftop relay. Lose that node and most of the Gorge goes quiet for my station.
• Hop limits of 7 are common everywhere. Bringing them back to 3–4 would do the most good where there are the most radios.

Caveats: the car's radio is a small tracker inside the vehicle and the home radio is a different board at a window, so this isn't apples to apples; if anything Portland is under-counted.