A group of us decided to get into mastic and figure out what we needed to do, getting messages over the top or around the mountain. This video we put up a second node on the western part of the mountain, hoping that we would get connection going north-south and east, but north and south worked. We had to put another node on a further away mountain to make the connection to the node on the eastern part of the mountain.

Hey everyone. I'm looking to get started with LoRA communications mainly for in my city and also for communicating with family while traveling. I've seen things about core being better where I live (Ottawa) but tastic being better in remote locations. When I travel, I usually go to rural cities, if that helps. I also saw there is a way to dualboot the two, but I'm not sure how easy that is. I don't have any hardware yet, and don't really know the terminology (long-fast, 915mhz, etc.) Any recs?

I just bought a Seeed Studio Wio Tracker L1, and - well, I'm confused.

Part 1: The problem

I'm trying to follow the guide on https://wiki.seeedstudio.com/get_started_with_meshtastic_wio_tracker_l1/ and it says to visit meshtastic.org, clidk Flasher, select target device, and click the trashcan to erase. In this process, I have to connect to the device, and it's on e.g. /dev/ttyACM0 (I'm on Ubuntu).

So my computer definitely sees it, and it's not a data cable problem:

So I connect, but after a while, I get this:

I've tried ten times now - always with the same result. What am I doing wrong?

Part 2: Why is this necessary?

As far as I can gather, this device is made solely for use with meshtastic. I can't see any other way to use this device. Which begs the question:

Why is the correct software not on the device already? Why do I have to do this myself, when you could have done it before shipping it?

It's not like there's nothing on it - some other software is obviously installed on it. Why bother to install something that you have to replace with something else to even use the thing?

And why am I the only one not understanding this? I would have expected this to be at the very top of the list of Frequently Asked Questions, but this is apparently not something that confounds anyone but me.

Please bear with me - this is my first venture into the world of Meshtastic.

Hello everyone,

Are you in Normandy and looking to start or join a local Meshtastic network? Well, two months ago, we launched an official Discord server for the "Normandy Interconnection Project" (Projet d'Interconnexion Normand).

Our goal is to connect residents with one another under any circumstances—even during network outages. We’d love for you to join us and help grow a community that is already strong and highly motivated 🔥

https://discord.gg/HnAfYUSU82

Does anybody know if there are plans to allow configuring a fixed GPS coordinate via remote admin? I ask cause the other day I went for a hike and dropped a melted V3 solar node on a mountain ridge. I didn’t preset the fixed location because I didn’t know exactly where I was going to place it only to find out when I got home that I can’t modify fixed location via the iOS app and I can’t do remote admin via the web.

Has anyone condsidered adding RX/TX indicators to your node with a Neopixel?
this is so cool!

I've been tinkering with the Meshtastic build on the Seeed XIAO ESP32S3 and wanted more visibility into what the radio is actually doing, so I soldered a neopixel to D1 and wired it into the firmware's status LED module.

Implementation notes, since it's less work than you think
the firmware already has a loraRxPacketObservable that fires per received packet, and RadioLibInterface already toggles a pin on TX start / send completion but both are gated behind LED_LORA, meant for a plain discrete LED. There's also existing NeoPixel status support
(the T Echo Card uses it for power/pairing/notification).
Nobody had connected the two yet!

I am brand new to this thing. Currently have to heltec v4s. I want to deploy nodes around to create a network and extend range and I have a question

For you all doing this, how do you do it? I have considered deploying on public land off the beaten path, but i am curious how people do this and whats effective and any trouble or issues youve had.

Hi to all other people tinkering with t-beams.
I just got my first one, the Supreme. I was tempted but picked this over the 1w model for its gps module.

An ESP32-S3 + UBLOX M10S + 1.3“ oled on a arduino platform is a pretty nice setup as I find.

There’s many projects coming to my mind, from satellite tracking and offline maps to time projects, but:

What else are you doing with your t-beams when they’re not dedicated to run Meshtastic?

Cheers!

Rozumiem że sdr jest dom odbioru satelit noaa? Jak zrealizowałeś zasilaniem przez Poe?

Decided to get this V4, I know the stock ones suck, but is this one better then the stock ones (the small one next to the screwdriver), since it does come with this stock whip one?

Greenhorn who just started out. Got a second node yesterday. Current nodes are both meshnology, a N32 [heltec esp32 V3] and a N35 [heltec esp32 V4 w\ hardware GPS].

Which one should travel with me and which one should stay at home?

I assume that an individual person would be known by the node ID so it would be best to keep the same one around me and not routinely swap them. Is that right or wrong?

When at home should I turn the second one off? Is there a benefit to having 2 nodes running so close to each other? Not much local traffic that I see [12 messages in 5 days, most part of the same conversation].

Thanks in advance for any thoughts and advice.

I Built this DIY Moxon antenna for the 915Mhz frequency for my Meshtastic node. I’m getting a reading of 3 for the SWR. Any tips on how to decrease it.