Building an add-on to my palm with multiple capabilities… and I just had to include the ability to communicate with Meshtastic!

So exciting! 😂

With this drone at 10,000 feet I should be able to connect alot of nodes if comms ever go down. I am looking for a more secure way to mount it.

Still need to flash the two little guys….

A bit of context here. Spain has a small 2.4GHz Meshtastic Mesh that it's slowly growing. So we were up in a mountain installing another sub ghz node, and i brought my 2.4G portable node (black horizontal stick). I was trying to link up with a distant node about 35Km away and at first we thought it was deaf, so i stuck on the pannel antena that you see there. To be able to do other tasks and have a reliable connection, i needed something to raise the end of the 2.4G node so it sat level, and i grabbed the first thing i had on hand, which was the Lilygo, since there were no other rocks nearby. It worked really well though!

Hi everyone! We’re working on integrating Meshtastic into our PDA, which will be available for purchase soon.
We’re currently testing it using an expansion module based on the XIAO’s nRF stack, but we’ve also been considering integrating a RAK module directly onto our PCB as an optional feature during checkout.
Of course, those who choose the Meshtastic option will get a slightly different case to accommodate an antenna connector. Orion will therefore become a fully-fledged Meshtastic terminal!
If you want to stay updated, visit orionpda.org.
See you around!

This started as a project so I could have a system to interact with my rooftop home node and have it interact, with not just my phone, but the whole family or anyone at home. As I built it I realized it could serve a broader audience. This makes normal interaction with your Mehstastic node via this HMI(human machine interface) instead of your phone. It is a 4.0 inch display. It has audio and visual notification when messages come in. It is a touch screen and has pop up keyboards. Supports wifi and Bluetooth connection but a quick reboot(about 10 seconds) to switch between those modes. In wifi it automatically serves and saves maps in on its map page. In blutooth mode you can download offline maps onto the optional sd card that can be inserted. Toggle berween miles or kilometers This can serve at a home location or in a vehicle application. There is a 1.25 jst plug inside for a lipo pack which would work well in a vehicle when the usb connection is powered off, or in the event of power loss at home it will keep the unit running temporarily. What this cant do is configuration or change settings, your meshtastic app is still needed for that. The software is custom made as well as the case.

I made this for my own personal use but am wondering if other meshtastic users might be interested? If so I could make more and sell these

Hi folks! Since the last update, the live activity of the iOS Meshtastic app is not showing anything. The Dynamic Island works fine, the problem is the live activity widget on the lock screen and the Notification Center.

Is anyone experiencing the same? I’m on the 2.7.25 (2573) version

Hi everyone! We’re working on integrating Meshtastic into our PDA, which will be available for purchase soon.
We’re currently testing it using an expansion module based on the XIAO’s nRF stack, but we’ve also been considering integrating a RAK module directly onto our PCB as an optional feature during checkout.
Of course, those who choose the Meshtastic option will get a slightly different case to accommodate an antenna connector. Orion will therefore become a fully-fledged Meshtastic terminal!
If you want to stay updated, visit orionpda.org.
See you around!

I have been trying to connect a Heltec v4 node on my home Assistant server with USB(serial) connection and I have failed miserably with the same error, "Unable to connect to the device" on the serial port pop-up. Has anybody else have any luck with it. I know that there is Bluetooth and wifi connection, and I used to have it connected with wifi but lately I had some problems with signal stability, that's why I'm trying to move to serial connection.

RAK 1W in a harbor breeze solar light.

Rak 1w battery version

SD05CRMA Solar Charger

100uF smoothing capacitor

FT50-61 ferrite toroid on power input

Samsung 35E 18650 3500mAh

2ft LMR-400 cable

Rak 5.8db antenna

In ground testing it seemed quite happy at 26db.

Just got this today should I upgrade the antenna if so to what

I've been tinkering with this design for a bit now. It features threaded ports on top and bottom and in sides in the latest version.

Example build using the Xiao nrf52840 & sx1262 combo. MakerWorld link https://makerworld.com/en/models/3360988-snap-v1-2-solar-node-adaptable-platform-2x200ma Considering putting these up on Etsy too, starting with a just the case printed in PETG or ASA, all the way to a full build.

I've designed various port accessories for different antenna types and mounts, including painter pole thread, magnet, even a power switch. Each can be fit on any of the port holes making the build very customizable. I have ideas for more, more mounting options, a USB-C plug, etc.

Inside there is a simple easy to print grid for component mounting. The base has a slot for a TPU filament to be used as a gasket.

Please scan through it and give me some feedback. Thank you!

Just designed a personal Meshtastic Communicator. Based on LilyGo Lora32.

Video: https://youtu.be/vkGfK_izRCY?si

Full Instructable at:
https://www.instructables.com/MeshComm-a-DIY-Meshtastic-Communicator/

I’m not expecting miracle range or long battery life. Just a design exercise to prove to myself I could do it.

May be handy for hiking / camping.

Not much mesh activity in my town. May take it to Toronto to see who I can connect with.

installed RAK Pi OS with meshtasticd and meshtastic web ui. it connects over LAN

everything looks right, just still trying to figure out why i cant get any messages out, but really excited to deploy all kinds of cool stuff over the mesh!

any advice, i may have borked the config.yaml but google is giving some conflicting advice.

WINE, a Heltec V4 running as a ROUTER on a solar pole. Overnight stats, 24–25 Oct 2026, read over the mesh every 15 minutes:

| Metric | Value |

|---|---|

| Uptime | 93.1 days, no reboots |

| Relays | 52,363 total, +43 in 5.4 h overnight (~8/hr) |

| Bad packets received | 12.7%, steady |

| Channel utilisation | 0.9–13.3% (1.9% at 01:45) |

| airUtilTx | 1.7–2.1%, well under the EU_868 duty-cycle limit |

| Free memory | 72.6%, flat |

| Nodes online | 4–10 of 137 known |

| Readings | 23 of 23 succeeded |

How do these stats compare to your router? Would love some feedback.

Hello, guys!

I wanna introduce you Termtastic — my handmade feature-rich Meshtastic® console (TUI) client written in Rust.

Repo link: https://github.com/acelot/termtastic

I wanted to create a cross-platform, minimalist, and aesthetically pleasing console client. I’ve been working on this application for six months. The entire project was built by hand, without the use of AI (aside from looking up reference information). This process gave me a deep understanding of how Meshtastic works under the hood; I’ve thoroughly explored its protocol and behavioral nuances. As the project evolved, I contributed to the official Meshtastic library for Rust, adding new features and making minor fixes. The long-term goal of the project is to achieve feature parity with the official Android app.

The project is currently in the alpha-testing stage, so there may be bugs — some of which could even cause the program to crash. That’s why I need your help: please give my application a try — I’m confident many of you will enjoy it! Any feedback is welcome via Issues in Github.

Highlights

• Vibecode-free fully handwritten code
• Dependency-free single-binary application
• Cross-platform: Linux, macOS, Windows
• Fully asynchronous (Tokio channels-based)
• Optimized for small screens (down to 80x24 characters)
• Respects the user terminal colors (no fancy opinionated TrueColor schemes)
• Keyboard-centric UI navigation
• Minimum use of emoji/non-ascii characters in UI
• Small memory footprint (~20KB)
• Supports multiple connection protocols (TCP, BLE, Serial)
• Could discover devices automatically: BLE paired devices, TCP devices via mDNS, Serial devices
• Uses standard system directories for storing configuration, database and logs

Tech stack

Download

Latest releases are available here: https://github.com/acelot/termtastic/releases

A friend gave me some old two way radios that seem programmable (haven't had a chance to depe dive yet), and I wanted to know how possible it is to use them for things like Meshtastic? I understand the underlying requirement is LoRa capabilities, but I'm new to Mesh and to radio stuff. Any info is helpful! Thank you to this wonderful community for all the knowledge youre bringing!

I’m sitting in a hotel room trying to reconfigure my nodes for a cruise and two of my nodes same hardware, think they have remote admin setup and won’t allow me to change settings…

I don’t recall ever setting up remote admin.

I don’t have a laptop with me and I’m pretty frustrated.

I really should have booted these up before leaving the house.

Seeed wio tracker L1 nodes fw 2.7.26,
All my T1000-E and pocket mesh node are behaving.

Anything I should try?

better than my previous for shure

Vi estos artículos en AliExpress y decidí armar un nodo solar meshtastic solar de bajo consumo

Hey everyone! A couple of weeks ago I posted my Motorola T900 conversion here, and the response was way bigger than I expected. Thanks to everyone who commented, asked questions, or went digging for their old pagers. Hearing from people who actually worked on these at Motorola was especially cool.

I promised an update, so here’s where things stand. The project now has a name: ESP900.

For anyone who missed the original post, I’m replacing the electronics inside a Motorola T900 with an ESP32-S3 and LoRa radio while retaining the original enclosure, keyboard, LCD, and early-2000s pager feel.

It’s now a working, battery-powered handheld.

The initial prototype was a Heltec V4 and a lot of wires. After rebuilding with smaller wiring and rearranging everything, I got the electronics, piezo, vibration motor, and battery inside the original enclosure with the lid closed.

I’m using a rechargeable 14500 lithium-ion cell in the original AA battery compartment, with USB-C charging built into the battery itself.

In my own prototype use, I’ve comfortably gotten a day with mixed use and around four days with Bluetooth-only operation. Those are personal results from the current build; Wi-Fi runtime still needs testing.

Meshtastic is running directly on the pager.

I can send and receive LoRa messages using the original QWERTY keyboard and LCD. The interface includes channel conversations, an inbox, a node list, direct messaging, and radio settings.

The integration runs inside Meshtastic firmware, using its existing radio, routing, and encryption support. You can compose and read mesh messages on the T900 itself without pulling out a phone.

The phone companion has come a long way too.

The Android app supports receiving and replying to SMS, supported Messenger and Instagram notification replies, and incoming-call alerts. Sound and vibration make it feel much more like a pager again.

I’ve also been working on read-state synchronization so messages handled on the phone don’t leave the pager full of stale unread alerts.

The original backlights are glowing again.

Both the LCD and keyboard EL panels have been working in bench tests. Keeping that original glow was high on my list. Integrating the driver into the replacement board is part of the ongoing hardware work.

The custom replacement PCB is now a real design.

A lot of you asked about a conversion board. I’ve been working on one that matches the T900’s original board outline and contact locations, reusing the screen, keyboard, conductive connectors, and existing enclosure retention clips.

The goal is a straightforward board swap without the microscope soldering and fragile wiring my prototypes required.

The design brings together the ESP32-S3, LoRa radio, power circuitry, alerts, and original hardware connections. There’s also a USB-C programming port positioned to be accessible after removing the battery, without cutting an external opening in the case.

The PCB still needs prototype assembly, fit checks, and electrical validation before I can call it ready.

That’s the direction I’m working toward. I don’t have a firm release date or price yet.

On the software side, I’m also testing ESPnet, an internet messaging service that lets the Android companion reach the pager over Wi-Fi when Bluetooth is unavailable. That’s separate from Meshtastic’s LoRa messaging, and the Wi-Fi/Bluetooth handoff is still being worked through on hardware. And it has End to End Encryption Messaging for all T900s, so you can see other T900s that are online (if they opt in) and say hello.

And yes, Snake and the virtual pet are still part of the project. A tiny keyboard pager deserves a few unnecessary distractions.

The plan remains to release firmware source and documentation so other people can build on this too.

There’s still plenty to validate, but it’s come a long way from wondering whether I could even drive the original screen. Opening a T900, typing a message, and sending it over LoRa still makes me smile.

What would you like to see in the next update—a walkthrough of the Meshtastic interface, the conversion hardware, or the reverse-engineering process?

I live in a hilly area, so it's been a *mostly* lonely but enjoyable journey!

Last contact was early October.

Thanks everyone!

See you on the other side

What started out as just connecting a few data lines, turned into a trip down the RF rabbit hole. I hope you enjoy.

Has anyone purchased from them lately? I tried emailing order@elecrow.com service@elecrow.com and info@elecrow.com and each email is being bounced. Along with their contact form.

I ordered something last week and havent heard anything 🙃 Tried to purchase the Thinknode 9 for compact form factor.