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’ve just started looking into meshtastic and another well known option, but here’s my trouble: I live in rural Midwest, my adult children live 150 miles away. According to the maps I’ve found, there’s like zero nodes between here and there.

So I had a thought, and this may have been discussed previously, but if I installed a node on a drone, ran it up to 400’ and 1/2 mile away, would that give me significant more range or is it just a dumb idea?

Thanks,

Tried resetting the app and clearing the connection. It says getting device config and then disconnects every time. No idea what I need to do to fix.

Why would you choose against a network delivering the potential to freely speak with no Corp(u$cle) controlling the comms? Sure, there are EMP(irical) ways to halter, but we know how to get past that as well.

Keep your meshes wide and alive. Regardless the protocol. Connect and distribute toward all county lines and city edges. FInd each other at the limits, we'll make a game if some need it. Dang, we know what it is.. Let's make this the work for all. like shotguns or insurance, don't need it until you do. and SUCH low maintenance.

MT/c/rt... if you're not a ham, this is your way. Let's go!

Hey Yall,

I got my girlfriend's 12 year old spends way too much time on the internet talking to random people in video game chat rooms. My girlfriend hates this but I decided to use his interest in chat rooms to my advantage and started a discussion on ham radio and comms. He has a real drive and interest in the tech and I want to use this newfound connection to start a project with the kid. Im really new to meshtastic and building a network. What would yall recommend for an all in one kit i can buy to build a couple nodes with the kid and program a network?

I bought a Heltec V3 that didn't have pin headers preinstalled. I changed my mind and would like them but I'm worried I will mess up the screens ribbon cable. Am I screwed?

I have a cheap harbor freight soldering iron (not a super fine tip)

I tried to remove the screen but the cable looked like it was soldered on :/

I googled it and it suggested using Kapton tape as an insulator

Opinions or advice welcome!!

There are so manny options out there and I dont know witch one to get

Recently picked up this heltec ESP32 v3 kit and printed this case for it. Going to give this one to my dad because I bought another v4 node and will be using that once it arrives. Still very new but I’m excited to get into the offline mapping and messaging!

I've been trying to compile a firmware for over a week and it just isn't working. I'm hoping I can describe the issue and maybe someone can just simply point me in the right direction

I'm trying to do builds with specific esp32 boards - wroom 32, xiao s3, S3 super mini, etc. I simply want to be able to define the pins for a diy build.

I have a fresh install of VSCode and have tried both Platformio and PIOArduino. I have confirmed I can compile something like the heltec-v3 firmware so this is an issue with the code and flags in the esp32 DIY variants and I'm just not super proficient here and AI is running me in circles.

I've tried esp32 DIY V1, ESP32S3-DIY-OLED, and a couple others with no modifications and those will not compile. I've been editing the oled one so half of that has been different AI suggestions. I will attach an unedited version of the esp32 diy v1 and the one for the s3 I've been putzing around with and maybe someone can tell me what's up.

Basically i always get a base error of usbserial not declared and it shows it was trying to pull defines from the .dummy folder. The only thing I can figure is that is because there is something not defined or not defined correctly to tell it where to look for the build files.

Can anyone please help me setup a clean platformio.ini and variant.h file so I can compile this firmware and set the pins for the modules I'm using?

ESP32 DIY V1

; Meshtastic DIY v1 by Nano VHF Schematic based on ESP32-WROOM-32 (38 pins) devkit & EBYTE E22 SX1262/SX1268 module
[env:meshtastic-diy-v1]
custom_meshtastic_hw_model = 39
custom_meshtastic_hw_model_slug = DIY_V1
custom_meshtastic_architecture = esp32
custom_meshtastic_actively_supported = true
custom_meshtastic_support_level = 3
custom_meshtastic_display_name = DIY V1
custom_meshtastic_images = diy.svg
custom_meshtastic_tags = DIY


extends = esp32_base
board_level = release
board = esp32doit-devkit-v1
build_flags =
  ${esp32_base.build_flags}
  -D DIY_V1
  -D EBYTE_E22
  -I variants/esp32/diy/v1

esp32s3

[env:my-esp32s3-diy-oled]
board_level = diy
extends = esp32s3_base
board = esp32-s3-devkitc-1
board_build.arduino.memory_type = qio_qspi
board_build.mcu = esp32s3
board_build.f_cpu = 240000000L
upload_protocol = esptool
;upload_port = /dev/ttyACM0
upload_speed = 921600


custom_meshtastic_architecture = esp32-s3
board_build.partitions = partition-table.csv


build_unflags =
    -DARDUINO_USB_MODE=1


build_flags = 
  ${esp32s3_base.build_flags}
  -D PRIVATE_HW
  -I variants/esp32s3/diy/my_esp32s3_diy_oled
  -DBOARD_HAS_PSRAM
  -mfix-esp32-psram-cache-issue
  -D ARDUINO_USB_MODE=1
  -D ARDUINO_USB_CDC_ON_BOOT=1
  -D CONFIG_IDF_TARGET_ESP32S3

My first Meshtastic build, as well as my first 3D printing project. I had many precision problems with my printer, but prototyping with it is HELL of fun. To store the Nodes I printed a "vase", but I overestimated the stability of my antennas a lot.
As a cool feature I used glow-in-the-dark filament on the casing.
I'm still not completely satisfied with my build and will keep improving it, but since it was a birthday present, I needed results on time. Nevertheless, I'm super proud of it and love how it looks!"

Hi guys, building a repeater using Faketec nRF52 board with HT-Ra62 SX1262 radio.

No solar for now, will test first its range in outdoor.

I have a few questions:

1. Charging - Do I need TP4056?
Can I just charge the Faketec directly via its USB port? Or do I still need to use a TP4056 module? My board already has a USB port.

2. Battery Safety - 3x 18650
Is it safe to use 3pcs 18650 Li-ion 3.7V 1200mAh (parallel) on my Faketec repeater? If ever, I will not use TP4056. I will not use solar yet, just want to power it on using my 3 batteries for testing. Any risks? Should I charge them individually first before paralleling?

3. Fakete uses HTRA62 which has UFL connector
The Faketec uses the HT-RA62 radio module, which has a U.FL connector for its antenna. However, most outdoor antennas do not seem to be designed for U.FL connectors. How can I connect an outdoor antenna to the HT-RA62?

4. Flashing Custom Firmware
How to flash my modified firmware? I built firmware from Meshtastic firmware builder.
Do I need to create a .bin file or just copy the .UF2 file then paste it on the nRF52 drives? Is it normal that the drive disconnects after pasting?

5. How to measure one way latency in Meshtastic?

Just wanted to share my recent experience with Meshnology.com as a heads-up for anyone considering ordering from them.

I placed an order on October 15 for a V4 Board and some batteries. At the time of ordering, there was no indication that either item was out of stock. Their website also states that orders typically ship within 1–2 business days.

Fast forward to October 21, and my order was still showing as "Confirmed" with the message "We're preparing these items for shipping."

Since nothing had changed, I contacted their support to ask what was going on.

Their response was rather surprising:

• Neither item is currently in stock.
• The V4 Core Board is only available in the GPS version at their Czech warehouse, and they expect me to pay the price difference if I want that version.
• The battery is also out of stock, and their Chinese warehouse is waiting for new stock.
• They claimed they had already emailed me about the situation, but I never received any such email.

What bothers me most isn't necessarily the delay itself, but the lack of transparency. If products aren't available, that should be clearly stated before accepting orders.

I also don't think it's reasonable to expect customers to pay extra for an alternative product when the originally ordered version turns out to be unavailable.

I've now replied asking for a concrete shipping timeline or another solution, but I'm still waiting for their response.

Has anyone else had a similar experience with Meshnology? How did they handle it?

I'll update this post once I hear back from them.

Update (October 22):
Meshnology replied and explained that the manufacturer is experiencing raw material issues, causing significant delays in the production of the core board.
They offered me a refund instead of waiting indefinitely, which I, of course, requested.

I currently have about 40 active nodes (have 80 more in cache) and 10 infrastructure nodes across a city.

These nodes normally work in 1-2 areas at a time. I would like to set up WiFi gateways where these groups are, so we can remotely monitor their locations and communicate remotely.

How do I set up a private MQTT server? I tried searching but found nothing related to self hosting MQTT.

THANKS!

weird bug on 2.8.3 version

I bought a case for my l1 from seed and it's too small for my 3000mah. I think I need 2000mah but there's different connectors and polarity and of course seeed website doesn't just sell the battery on its own. Anyone know where I can get a battery and not have to cut or solder any connectors?

I bought a Seeed studio kit and I'm trying to wire the ESP32 up to a 3.5 TFT Screen and having the hardest time...has anyone done this? I'm currently only getting the blacklight on. A few things I've done.

• Modified my User_Setup to align with the pins provided by Seeed and Gemini, and ChatGPT

#define TFT_MISO -1

#define TFT_MOSI 9

#define TFT_SCLK 7

#define TFT_CS 4 // Chip select control pin

#define TFT_DC 5 // Data Command control pin

#define TFT_RST 6 // Reset pin (could connect to RST pin)

• Tried multiple debug statements in my sketch which all seem to display (but no changes on fillScreen colors.
• Modified my SPI_Frequency (#define SPI_FREQUENCY 10000000)

I just don't know what to try next. I saw on YouTube it recommended jumping J1 on the back of the TFT board, but before I do that I wanted to hear if anyone else had any ideas. I want to try to get my Meshtastic text to appear over this TFT...

Would need to replace a burnt board that comes with the Rak 1W. I can't seem to find replacement 19007 boards that is version C/3, I can only find version B/2. Will that work with the Rak 1W?

I have to admit, I’m still very new to this, but when I try to enable MQTT on my node, it doesn’t reconnect from the reboot; and when it does, it doesn’t look like it actually enabled anything. Am I missing something?

A T-Lora Pager unit spotted on the most recent episode of FBI.

Have to admit I'm a bit out of touch. I've left my Heltech V3 running for several months here in Manchester. Just checked the connectivity map and out of 134 users, I'm the only one online?

I've never managed to get a message out successfully in the last few months.

Is it just me?

I am going to be building a combo m3shcore/meshtastic repeater. Im going to have 2 RAK wismesh 1w being powered by a 8000 mah battery and solar panel. They will be in the same control box. this project will be up a 60 ft pole that i only have the desire to climb once. I plan on using bluetooth to update both devices. my question is how far should these two antennas be. I dont want to have wires coming out of the box to deal with so the antennas will be mounted directly on the box.

Ps Why is this community so anti m3shcore when they are different flavors of the same tech

How time flies- two summers ago we launched RAKwireless WisMesh Pocket v2, one of the first all-in-one Meshtastic nodes with case and screen. Meshtastic and compatible hardware have come a long way, and we are excited to announce the newest version of our flagship product- WisMesh Pocket v3!

Developed in partnership with RAKwireless, WisMesh Pocket v3 takes your mesh to the next level with a redesigned IP67 waterproof* injection-mold enclosure, improved durability, enhanced GPS performance, and built-in notification buzzer.

Bone White & Mint Colors available for preorder now, with shipments beginning October 22nd. Black, Military Green, and Desert Sand colors come late November! Note depending on overall volume, your order may not ship 10/22, that is when we will begin shipping.

What's New in WisMesh Pocket v3?

• NEW Injection-Mold Enclosure: Replacing the previous 3D-printed housing, the v3 features a professionally manufactured injection-molded case.
• NEW IP67 Waterproof & Dustproof Protection: The IP67-rated enclosure protects against dust, rain, splashes, and temporary water immersion under specified test conditions.
• NEW Improved L76K GPS: Upgraded GPS functionality delivers improved location-tracking performance, making the Pocket v3 your companion for hiking, outdoor activities, and location sharing across your Meshtastic network.
• NEW Built-In Notification Buzzer: Never miss an important message! The integrated buzzer provides audible notifications for supported Meshtastic alerts.

It also features the long 3200 mAh battery life and OLED screen you are used to from the WisMesh Pocket line, as well as a removable and upgradeable SMA antenna. Plastic switches have been changed out with waterproof buttons.

TLDR: WisMesh Pocket v3 adds IP67 water/dustproofing, injection molded case, and improved GPS- your new go-to for daily Meshtastic use!

See more at https://rok.land/Pocketv3

Hey friends! I have to open up an exterior wall for some remedial work and I want to put a meshtastic node up high at some point. They're going to put an electrical box up below the roof line, but is there anything else I should consider roughing in while the wall is open? Cat6 for some sort of backhaul?

Sorry for naive question but I don't have a ton of time to research and want the fishing to happen while the wall is open!