We would love to hear from the community and would love to have regular posters or even just a 1 time guest post. To contribute to the blog please email [email protected] and we can work through getting the content added!
Build Guides
TBeam Supreme EDC
TBeam Supreme Build
Not long after working with the RAK boards I thought I would try out the tbeam. I had heard good things about it and wanted to really see what all of the hype was about. The original case that I found was a bit clunky and wasn’t overly well. So I threw it in a case just to hang out for a while and even then it really ended up in a drawer… Until now! I was thinking about our annual sales conference coming up and the Meshtastic network we would like to build again. I just happened to search again for a case that would work for this tbeam thinking I would carry it around and stumbled on the TBeam Supreme 3D printable cas from Alley Cat and after looking closer at it seemed to be solid. When I printed it, I can confirm it is solid, easy to print and easy to assemble. While I know there are tons of options out there this case has certainly made me a believer in the tbeam again.
Here is the parts list that I used:
TBeam: Lilygo TBeam Supreme
Batteries: Generic 18650 Batteries
Antenna: Amazon Lora 915 Antenna
Misc Screws and Nuts: 2 M3 nuts and 2 M3x8 bolts Local Hardware Store; I used Theisens as they have bulk
The base kit comes with the board, and antenna. I opted to add a different antenna. The stock antenna is not overly good according to the NanoVNA, but I find that the generic antenna from Amazon is spot on when it comes to the 915 mhz Lora that Meshtastic uses.
When printing the case I had to use the 13mm with nuts STL file to allow for the size of the Amazon antenna. Hats off to the creator for having multiple options for different antenna types without needing to import the STL and modify it yourself!
Assembling the tbeam into the case is really straight forward and doesn’t require anything to be modified from the frame of the board. The only thing I ended up having to do is move the GPS module (which is held in by double sided tape). I found that not putting the antenna on while putting the two halves of the case together
I opted to not do any of the insert types of the cases so I had to insert the M3 nuts into the bottom of the case before final assembly
| Top View | Inserted |
|---|---|
|
|
Here is what some of the final assembly looks like:
In anticipation of carrying around this node I also printed the bag clip which is working great!
I’ve really enjoyed this case and putting this back together again! It really has been nice to experiment again with this board. The larger battery has been helpful to keep it running throughout a day without having to charge it
WisMesh Pocket First Impressions
WisMesh Pocket First Impressions
The WisMesh Pocket from RAKWireless is a great place to get started in the world of Meshtastic. Its robust design, long battery life, and ease of use make it the perfect first node for anyone, beginner or experienced radio operator. The unit has a high-quality screen, well-printed case, an independent on/off switch, and GPS receiver preinstalled.
Initial impressions
I’ve had this device for three days so far. It arrived ready to go out of the box. The battery had 80% charge (your mileage may vary), and I have yet to charge it. At the time of writing, it is at 67% with intermittent GPS usage. You will have to update the firmware, as updates have been released since these were produced, but that is expected.
Functionality
Overall, the unit is very easy to use and understand. The screen is a good size, making reading off it easy, and has a good brightness. The unit isn’t too big, but not too small. It fits in jeans pockets comfortably if walking or working, and has a loop on the top of the case for a keychain or string. The included antenna leaves a bit to be desired, and I am considering upgrading mine.
Setup
One of the shining features of the WisMesh Pocket is that it’s ready to go out of the box. The unit ships pre-assembled with Meshtastic on it. All you have to do is connect your phone via the Meshtastic app, set your region, and away you go!
Final Thoughts
Overall, the WisMesh Pocket is a well-built unit that’s simple to use and understand. It is on the higher end of the Meshtastic Budget range, coming in at $99 at the time of writing, but you absolutely get what you pay for
RAK PoE Node
In this guide, I will go over the process of how I built my PoE-powered Meshtastic base station. This is an easy to build node that uses primairly official RAK components, so no soldering is required!
Parts list
Most of the parts for this build were purchased from Rokland. I highly recommend buying Meshtastic parts from Rokland where you can as they are absolutely great to work with.
- RAK Meshtastic Starter Kit
- ALFA Network Outdoor 915MHz LoRa antenna
- UFL/IPEX to N-Female connector
- RAK13800 Ethernet module
- RAK19018 PoE module
- Waterproof box
- Monoprice CAT6A cables
- RJ45 cable glands
Optional, if you don’t have a PoE switch:
You’ll also want to 3D print a mounting plate. I used the RAK19007 Mounting Plate by KBOX Labs.
Build guide
The first step is to assemble the RAK board. Installing the Ethernet and PoE modules is quite easy. The ethernet module simply screws into the RAK starter kit board, and the PoE module plugs right into the Ethernet module. I then proceeded to flash Meshtastic on the board and configure it to connect to my network using DHCP and uplink/downlink to the Iowa Mesh MQTT server.
The RAK board with Ethernet and PoE modules installed.
I highly recommend testing out the PoE functionality at this time, as there are reports of issues with this PoE module when paired with some switches due to the low power consumption of the RAK board. If you run into any issues, disabling PoE power saving features on the switchport can help. If you are still running into issues, I recommend using an 802.3af PoE injector to power your node.
Now that the board is configured, we are ready to start building the rest of the PoE node!
Using a step bit, I drilled a 5/8ths size hole on the top of the waterproof box for the antenna. I then screwed in the antenna, ensuring that the gasket built into the connector was touching the plastic box with no washers in front.
Next, I drilled a hole on the bottom of the box for the RJ45 cable gland using a step bit. If I was to do it all over again, I wouldn’t have centered this on the bottom of the box. If you ever need to remove the 5x5 grid, it’s in the way of the screws.
After installing the antenna connector and RJ45 cable gland, I screwed in the 3D-printed RAK mounting plate. I only screwed in two screws here, as I had soldered on some pin headers for a BME280 temperature, humidity, and barometric pressure sensor. I used some 3mm-0.5x6mm screws from Menards here. I placed electrical tape over the screws as I wasn’t able to find flat head ones.
The 3D printed mounting plate installed.
Finally, I screwed the RAK board into the 3D-printed mounting plate and connected the LoRa and Bluetooth antenas, and the Ethernet cables to the Ethernet board.
Below is a picture of the inside of the finished node. One addition I made was adding a BME280 environmental sensor which is connected to the RAK board through the I2C headers. I chose to use an external sensor since I was afraid the PoE module would throw off the readings, but it doesn’t seem to do so. If you wish to add enviornmental monitoring to your node, the official RAK sensor board would probably suffice.
Rak Solar Node
Rak Solar Node with Parts from Rokland
In this post, I’ll cover what I could call my standard solar node build. I could have gone the fancy route, but the goal was a simple self-sustaining node that would go in a fixed location and likely high up. So as power-conscious as possible and easy to service if we ever had to. Rokland was my natural go-to with a kit that had all of the parts and could be easily done.
Rokland makes nothing off of this. I just believe in their product set enough to make mention of it here!
The nice thing here is that it can all be ordered in one shot from their site.
Parts List:
Rokland Rak Wireless Starter Kit
Rokland Rak Wireless Solar Kit
Rokland Pole Mount Kit for Solar Node
Rokland 3000 mah Battery with 2.0 JST Connector
I want to point out right away that the battery is a Makers Focus 3000 mah battery. Don’t get caught up with the same batteries on Amazon. Most of them you’ll find will have a 1.5 JST connector which WILL NOT WORK. The Rak 19007 board requires a 2.0 JST Connector. You’ll either need to cut off the 1.5 JST and replace it or just buy the battery from Rokland. No mess, no fuss. I’ve kept an eye out for these on Amazon and rarely find them without some sort of modification.
I found that Rokland does have excellent instructions. If you were to substitute any of the parts in this list they show you which ones you should cut out on the base board. For the sake of this post, I ended up with the starter kit which includes the 19007 base board and the 4631 module board. Rak offers plenty of module options that you could add on from collecting Temp and Humidity and reporting it back through the mesh. You could add those on if you would like, but I opted not too
Instructions are here:
Rokland Solar Enclosure Instructions
Without modules, there is a handy way of mounting the battery on the unused part of the solar plate. I’ve been using Gorilla double sided tape as it seems to adhere very well to these things.
With a pair of side cutters snip or another tool that will cut out the correct location cut out the sections to fit the board. This is covered in the instruction manual very clearly which ones to trim out. For the 19007 Rak base board, it will look something like this when you are done
Using the supplied screws from the Rak starter kit put the baseboard on the solar plate. The USB port will face outwards from the edge of the plate. The nice thing is that it can only go one way based on the offset of the screw holes on the 19007.
Slide the plate into the solar enclosure and then install the supplied USB cable thing and the antenna port. Both will go from the outside in and be held tight by the supplied nuts for each. I opted to not use or hook up the special USB cable but left it in there because it sealed the case.
I hooked up the supplied Bluetooth antenna. I think this could go many places based on what you think, but I opted to put in on the side of the case opposite of the Rak board. There was a nice slack there to tuck under the battery and hide away for now.
The solar panel plug from the lid goes in to the left port (or smaller port) and the battery connector goes into the right port (or larger port)
When completed it will look a little something like this:
The only thing left is to put the mount brackets on the rear and mount it in a location that works!
As for the Antenna, this could be one of many things. I’ve standardized on the 8dbi Rokland Antenna. It has a good quality build and the kit comes with the mount to put up on a pole. I like this mount over the standard u bolts that other kits come with. I also can’t speak highly enough of the flat pigtails they make. They are meant to go into doors and windows, but I think they offer a nice level of protection over exposed cables, and at 18in are the right size to put the antenna right above the solar enclosure and keep everything nice and neat!
Hope this helps! As always find us on Discord or email and ask questions!
Heltec T114 Build
Heltec T114 for Everyday Carry
When I first got started into Meshtatsic I ended up with a few of the Heltec V3s. They were inexpensive and got me out to Vegas in a hurry. I was always annoyed by the battery life and just seemed so sluggish that I started to stray away from them and started going exclusively RAK wireless for base stations, Solar and carry nodes. I was stocking up on my supply Rak Wireless boards and took at chance on the Heltec T114. I had co-workers that were testing them with success so I thought I’d dip my toes. It was based on an NRF processor so it should at least have a good battery consumption.
So here we are with a base install of Meshtastic:
Full transparency, Muzi Works does sell a kit that does the same thing. I had ordered the board before finding the kit or the 3d prints so I opted to just get the battery from them and 3d print the case. They were generous enough to post their STL files on Printables! Hats off to them for that!
Parts List:
I had some of these parts lying around from other builds so feel free to swap out what works for you!
The first step was to install the antenna cable and route it through the channel they’d built. Hats off the Muzi Works guys for thinking about that as with other builds has the cable in the open. Once in there, you can screw down the connector to stay.
The second step was to remove the two screws that held the plastic shell and screen in place. The screen will be free to move around so be careful not to rip it off or somehow bend it. While the front of the case is face down, put the buttons in, hook up the antenna to the port on the board and put the two little screws in. This took me a few times because while the screen was loose it didn’t work to cooperate the first time times. Be patient and you’ll get it
The next step is to put the battery in the tray. Another feature of the case is a nice way of routing the battery cable so it avoids hitting the antenna and other parts of the board when the case is fully assembled.
That’s pretty much it. Plug the battery into the battery port (make sure it’s the correct way so you don’t burn out the board) and enjoy.
I have to say I’m impressed with the battery life. I opted to not put in the GPS and use the GPS from my phone when I care enough to do it, but this last just as good as my rak carry (which will be another post soon). It is responsive when you hit the buttons, the screen is easy to read and use and overall a good unit. I’ve not messed with other antenna as of yet, but the Amazon one seems to do the trick. As soon as I get my nanovna I might hook it up and find out how close to 915 it is!
Thanks for taking the time to read this. I hope it was helpful!
News
When In Doubt Client Mode
When In Doubt Always choose Client Mode (A guide to roles on our devices)
One of the things that need to be address up front as IowaMesh grows will be the appropriate use of the modes. Probably another controversial post much like the Ok to MQTT post, but it’s a good chance for all of us to look at the choices we make and out it effects the Mesh
So Lets get on with it!
Selecting the appropriate device role is crucial for maintaining an efficient and reliable Meshtastic mesh network. With recent updates to Meshtastic, certain roles have been refined or deprecated to enhance network performance. For mobile nodes and specific stationary scenarios, Client and Client Mute modes are often the most suitable choices. Let’s explore these roles and discuss the implications of misapplying routing roles.
Updated Meshtastic Device Roles: Meshtastic nodes can be configured with various roles, each tailored to specific functions:
-
Client: This is the default role for most nodes, enabling standard communication capabilities. Nodes in Client mode send and receive messages and participate in routing when necessary.
-
Client Mute: Similar to Client mode but with routing disabled. These nodes send and receive their own messages without relaying messages for others, reducing network congestion in areas with high node density.
-
Router: Intended for stationary nodes strategically placed to route messages and extend network coverage. Routers prioritize relaying messages from other devices and attempt to conserve power by reducing their own transmissions.
-
Repeater: Functions similarly to a Router but focuses solely on rebroadcasting messages without originating its own. Repeaters are typically used to enhance coverage in specific areas.
-
Router Late: A newer role designed for nodes that should act as routers but with a delayed rebroadcast, allowing other nodes to transmit first. This role helps in scenarios where a node is well-placed but should not dominate the routing process.
-
Sensor: For devices primarily gathering and transmitting sensor data. While they can route messages, their main function is to report telemetry, even during high channel utilization.
Notably, the Router-Client role has been deprecated in recent Meshtastic versions to simplify role assignments and improve network efficiency.
So lets look at some advantages and disadvantages
Advantages of Client and Client Mute Modes for Mobile Nodes:
- Network Efficiency Mobile nodes in Client mode can participate in routing when necessary, but in areas with dense network coverage, this can lead to redundant transmissions. Switching to Client Mute mode in such scenarios prevents unnecessary rebroadcasts, reducing the risk of packet collisions and network congestion.
- Battery Conservation Routing and rebroadcasting consume additional power. By operating in Client or Client Mute mode, mobile nodes conserve battery life, extending their operational duration—especially critical for handheld or portable devices.
- Stability and Reliability Mobile nodes frequently change positions, leading to variable connectivity. Assigning them as Routers can disrupt message paths when they move out of range. Keeping mobile nodes in Client or Client Mute mode maintains stable routing through strategically placed stationary routers.
While stationary nodes often serve as Routers to extend network coverage, certain situations warrant using Client or Client Mute modes Considerations for Stationary Nodes:
- Specific Use Cases: Nodes dedicated to particular functions, like sensors, may not need to route messages.
- High-Density Areas: In environments with numerous nodes, excessive routers can lead to packet collisions and reduced network performance.
So what are the risks of misapplying Router and Repeater Roles:
- Increased Packet Collisions
- Overuse of Routers and Repeaters, especially in close proximity, can cause simultaneous rebroadcasts, leading to higher noise levels and packet errors.
- Reduced Network Range Improperly placed routers may consume message hops prematurely, preventing packets from reaching more strategically located nodes and limiting overall network range.
- Asymmetrical Links
- Poor router placement can result in one-way communication, where messages are sent but responses cannot return, disrupting effective two-way communication.
Sometimes it’s hard not to be that guy but maybe with a little bit of explanation we can help make sure the mesh stays working well for everyone.
So I might argue here that Client will be the choice of modes for most of us. I might even go as far as Client Mute especially if you are travling by plane. The traveler bridges larges area’s for a while, but then breaks it again. Would love to hear your feedback as well! Hope this helps as we continue to grow the mesh here in Iowa!
Meshtastic v2.6 A Feature-Packed Release
Meshtastic v2.6: A Feature-Packed Release
Meshtastic recently announced the public release of Meshtastic v2.6, a major update that has been years in the making. This release introduces several exciting new features and improvements, making it the most feature-packed Meshtastic to date. Here’s a summary of what’s changed in Meshtastic v2.6.
Key Features in 2.6
1. Next-Hop Routing
After extensive preparation, implementation, simulations, and real-life testing, Meshtastic introduced a more efficient routing protocol for direct messages called “next-hop routing”. This new protocol is designed to optimize the delivery of direct messages.
Meshtastic uses a “managed flood” approach for message delivery, where multiple devices attempt to relay messages. While effective, this method can lead to network congestion especially for direct messages. Next-hop routing addresses this by designating a specific device to relay the packet, reducing unnecessary transmissions and improving overall network efficiency for direct messages. If a node moves or RF conditions change, the next-hop designation may become invalid. In such cases, the node will fall back to managed flooding at the last retransmission attempt if it does not hear its next-hop relay.
Next-Hop Header: The last two unused bytes of the unencrypted Meshtastic header denotes the current relayer and the next-hop node. This approach ensures minimal routing control overhead and memory usage while maintaining compatibility with older firmware versions.
Stages of Establishing A Next-Hop
- Initial Transmission: When a new message is directed to a single destination, it will use the managed flood approach.
- Acknowledgement or Response: If a response (e.g., NodeInfo response, acknowledgment, or traceroute) is received and the relaying device matches one of the original relayers, it is designated as the next-hop.
- Subsequent Transmission: Any future transmissions will use the designated next-hop node to relay the packet, reducing the number of devices involved in the process.
2. Meshtastic UI (MUI)
MUI is a brand-new interface for compatible standalone Meshtastic devices offering a seamless touchscreen experience, allowing users to interact with the network without needing a phone. MUI is still in early development, and Meshtastic is actively working on adding more features and improving performance.
MUI is compatible the following devices: LilyGo T-Deck, Seeed SenseCAP Indicator, unPhone, PICOmputer, T-HMI, Mesh-Tab,Raspberry Pi, LuckFox with TFT SPI and LoRa hat, or PC with Meshstick.
MUI Features
- Dashboard Screen: Displays device status, new messages, detected nodes, date and time, radio settings, GPS, sound, Wi-Fi, and MQTT.
- Node List: View, filter, and highlight nodes in your network.
- Chat Window: Send and receive messages with persistent message history.
- Dynamic Position Map: Pan and zoom with customizable map styles for better network visualization.
- Basic Device Configuration: Quickly set up and adjust basic settings without the need for the Meshtastic app.
- Handy Tools: Includes a mesh scanner, signal meter, traceroute, statistics, and packet log.
- Bluetooth Programming Mode: Easily update and configure devices wirelessly using Bluetooth.
- Improved Device State File Management: Meshtastic 2.6 introduces a more reliable way to handle device state and node data by separating them into distinct files. This change improves data integrity, reduces the risk of corruption, and makes recovery easier in the event of a filesystem issue or unexpected power loss.
3. Meshtastic over LAN (UDP)
Added support for messages to be sent over a local network (LAN) using UDP, currently available for ESP32 devices on WiFi. This feature allows nodes to communicate over a standard network connection, extending your mesh without relying solely on RF signals. This can be especially useful in locations with limited RF coverage or when bridging multiple Meshtastic networks over existing infrastructure.
4. Optimized LoRa Slot-Time Calculation
Meshtastic 2.6 includes improvements to LoRa slot-time calculations, making packet transmission more efficient. By reducing slot time, more slots become available within the same rebroadcast window, lowering the chance of packet collisions and improving overall network performance.
We have been testing the release on several devices for a few weeks, and encourage others to update to the latest firmware to take advantage of these new features. Meshtastic v2.6 represents a significant step forward in our mission to provide a robust and user-friendly mesh network.
Ok to MQTT (Why We Need It)
MQTT (The almost forbidden subject)
What do you think of when I say MQTT? In the nerd spaces I normally occupy that would be Message Queuing Telemetry Transport. In most cases, it’s a great way of getting telemetry data out of IOT devices into some sort of central repository.
In the early days of Meshtastic, it would seem that MQTT was a great way of getting data across larger places especially if there wasn’t enough RF to carry these messages along the way. With growing privacy concerns the developers at Meshtatsic opted (and introduced in 2.5 firmware) to include properties in the packet that ignore MQTT or even permit MQTT.
A user on Reddit I think said it the best: “MQTT is one of the best, and apparently worst parts of the project. I do feel that currently, privacy and security is at risk when using public MQTT (even the meshtastic server), to the point where people could get hurt. I don’t think people should avoid the project, but I do think people should know the extent of the issue, an issue so severe the team has been trying to sweep it under the rug (damage control). They even mute users who bring up the issue in the discord.” - Reddit Source
From the Offical Documents that explain the settings:
Ignore MQTT Setting this to option to 'true' means the device will ignore any messages it receives via LoRa that came via MQTT somewhere along the path towards the device. Note this only works when your device and the MQTT node are running at least firmware version 2.2.19.
OK to MQTT Acceptable values: true, false Default is false. When set to true, this configuration indicates that the user approves their packets to be uplinked to MQTT brokers. If set to false, nodes receiving your packets are requested not to forward packets to MQTT. This configuration only applies to Channels configured with the defaultpsk and eventpsk keys set in the Meshtastic Firmware; Channels with custom keys ignore this setting. Important: This is not a cryptographic solution but a polite request that is enforced in the official firmware
So if you’ve stuck with me this far, Thank You. There is an end in sight, I promise,
IowaMesh relies on MQTT right now to keep big parts of the state connected. Without it, there’d be isolated patches where people couldn’t communicate with each other. Our ultimate goal is to shift entirely to RF, but that’s still a work in progress. Once the network is more built out, we’re planning to cut MQTT use down. So for all of you RF purests out there I urge you to consider the bigger picture here.
We take your privacy seriously. If a packet comes into the mesh marked “Ignore MQTT,” we honor that—always have, always will. The Meshmap site has supported this from day one. But there are some things you should know about how this works.
If you choose to ignore MQTT or don’t enable the “OkToMQTT” setting, your messages won’t show up in the Text Messages list on Meshmap. Most head-end nodes have “OkToMQTT” turned on, so your messages will still make their way through the mesh, but they won’t be collected or displayed.
The other thing to keep in mind is that without MQTT, some messages might only reach certain people—or maybe not get through at all, depending on how the mesh is set up that day. RF will still work as expected though, so there’s always that!
Introductions Are in Order
Introducing KN0CTJ
When brainstorming ideas for this blog, it seemed fitting to kick things off with an introduction—so here’s mine.
I’m Calvin, and I recently became a part of both the Meshtastic and Amateur Radio communities following our annual sales conference in Las Vegas. During the event, a group of my colleagues and fellow tech enthusiasts came up with an idea: we’d all head to Vegas, use Meshtastic to communicate, and learn how it works while finally meeting in person. Many of us are scattered across the globe, so this was a unique opportunity to connect.
And so, the plan was set. Twenty thousand of my “closest friends” (our sales teams) descended upon Vegas. As soon as we touched down, Meshtastic nodes began popping up everywhere. About 100 of us actively participated, and I’m already looking forward to an even bigger turnout next year.
Here’s the Reddit post my coworker shared about the event: Reddit Meshtastic in Vegas
After those exciting four days in Vegas, the general recommendation was to find a local Amateur Radio club and see how I could contribute. Unfortunately, my experience with my local radio group wasn’t ideal, but it eventually led me to the Iowa Radio Operators Discord group. From there, I started building IowaMesh.net.
The inspiration for IowaMesh.net came from seeing folks traveling from the Chicago area, joining ChiMesh, and sharing their experiences. I thought it was time to get Iowa involved and see how far we could connect. Since Iowa is pretty spread out, I began with an MQTT server and hosted a meshmap to visualize communication. While implementing RF/Lora remains a goal, MQTT has proven to be a great starting point for linking people together. We’ve expanded coverage to Altoona and Des Moines and are now reaching Jefferson, Greene County, and Cedar Rapids—and we continue growing every day.
Before diving into radio and Meshtastic, I was a Systems & Network Engineer for various companies. Eventually, I traded my 2 AM troubleshooting sessions for a pre-sales engineer role. Although networking remains close to my heart, venturing into Radio, Wireless, and Meshtastic has allowed me to apply my skills in fresh, exciting ways outside of work. It’s been a fantastic change of pace from the “same old, same old.” I’m always happy to chat about networking, radio, or other nerdy projects!
Calvin (KN0CTJ)
Welcome To IowaMesh and the New Format
Welcome to IowaMesh.net
I wanted to take a moment and say welcome to anybody whos joining us here a IowaMesh! What started out as a simple Meshmap, MQTT hosted server and connecting a group of folks from Iowa Radio Operators has evolved into what you see here today. I can’t thank Ethan (@nv1k) for helping get the frame of this built and putting up with my 1000 stupid questions (I wasn’t a developer first; Network Engineer turned PreSales Enginneer). What you see here is hours effort making sure we can best serve the Iowa and potentially further.
We’ll start posting up blog posts with builds and hardware lists. Also have pages for other hardware recomendations and some setup guides for the beginner through the more advanced user. Bear with us as we continue to build out that material (and if you have recomendations send us a note!). Not that this is any bit of an excuse, but this isn’t our day job so we will be working on this as we can. But know that we are dedicated to keep this alive and well!
So whats next? We aren’t sure. We want to build out a backbone across Iowa that users within the State and those traveling through can utilize with Meshtastic. Either way we want to connect with you and your use case and learn more. How could we be a resource to your club or maybe individual effort.
Find us on Discord, Email us with ideas, Find the source on GitHub and We are looking forward to getting to know everyone!
Calvin (KN0CTJ)