- #_shellntel Blog
- Posts
- DEF CON 33 and Meshtastic on the LILYGO T-Deck Plus
DEF CON 33 and Meshtastic on the LILYGO T-Deck Plus
Introduction
This is the third post in my ongoing series exploring Meshtastic. If you haven’t already, check out:
After two months of experimenting with various hardware setups, I decided to give the LILYGO T-Deck Plus a try. With its built-in screen, keyboard, and audio capabilities, it's arguably one of the most complete Meshtastic devices available today.
DEF CON 33: Field Testing in the Wild
I brought both the LILYGO T-Deck Plus and my preferred daily-use Meshtastic device (this one from Amazon) to DEF CON 33 to put them through real-world stress testing—and they both ran the special DEF CON firmware provided by the Meshtastic DEFCON project.

Firmware download page
DEF CON firmware splash screen
The custom firmware was slick and introduced three dedicated channels:
DEFCONnect
Hacker Comms
Node Chat
DEF CON channels
It was great to see this much community-driven coordination ahead of time.
iOS App Struggles
While I normally prefer the Amazon device paired with my phone, the iOS app absolutely struggled under the load at DEF CON, which I get as there was 2,000+ clients at one time and the most messages I’ve ever seen in my life:
Frequent freezes and long lag times
Occasional crashes
Overall sluggish performance that made it nearly unusable in real-time
Nodes on first arrival
Nodes during peak con
Nodes during peak con zoomed in (enhanced😂)
Nodes during peak con. 2,333 nodes!
T-Deck Holds Its Ground
In contrast, the LILYGO T-Deck Plus held strong. Despite the chaos of the venue and overloaded airwaves, it kept pace:
Messages were sending and receiving over short turbo
The onboard interface (while limited) remained stable
No dependency on a flaky app made all the difference
Messaging on the T-Deck
A Bit of DEF CON Lore...
There was also some buzz during the con that the DEF CON firmware might’ve been tampered with. A lot of people noticed a little ninja emoji (🥷) appearing next to their device names, myself included. Whether it was an easter egg, intentional branding, or something more mischievous... who knows? I erased and re-flashed my devices when I got home (and then threw them in the ocean j/k).
More information on the DEF CON firmware and the vulnerability at the Meshtastic official blog post.
TL;DR
At DEF CON, a new vulnerability in spoofing NodeInfo under ToFU and memory constraints was revealed.
Encrypted DMs and private keys remained secure.
The issue has been addressed, but highlighted the need for better UX, identity verification, and message signing moving forward.
Conclusion from the Field
The experience made me rethink my hardware preferences. At DEF CON scale, where infrastructure and app stability can’t be trusted, the T-Deck Plus’ all-in-one form factor became a huge advantage.
Why the T-Deck Plus?
The appeal is obvious: it's an all-in-one package. I don’t have to carry a LoRa device and a phone to send or receive messages. Everything I need is right there, keyboard, screen, antenna, and power. That makes it compelling not just for casual use, but also as a standalone emergency device. I've even considered keeping it powered down in a Faraday cage, just in case something wild like an EMP ever hits.
Packaging
Hardware Overview
Here’s what you get with the T-Deck Plus:
LoRa support for 433/868/915 MHz (model dependent)
Built-in full QWERTY keyboard
TFT display
Built-in microphone and speaker
Battery connector and charging support
MicroSD card slot
More packaging
It’s packed with features in a compact package, but with that comes added bulk and a steeper price tag.
Setup & Configuration
Getting Meshtastic on the T-Deck Plus was straightforward:
Flashing the firmware via Meshtastic Flasher worked without issue.
However, a few quirks surfaced:
The UI sometimes struggles with rendering names or emojis.
The built-in display is decent, but chat messages occasionally show up malformed.
Maps don’t work out of the box. You’ll need to preload them onto a MicroSD card (which I didn’t bother with).
Other nodes didn’t appear for at least five minutes.
Screenshot of the Meshtastic Mesh Map with lots of nodes active.
Real-World Use
Using the device in the field was a mixed bag.
What I Liked:
All-in-one functionality: I could send and receive messages without pairing it to my phone.
Great for emergencies: Could see this being super useful in an offline scenario or disaster recovery situation.
Decent display: For quick glances, it’s bright enough and legible outdoors.
The T-Deck Plus
What Fell Short:
$98 price tag: That’s steep. For not much more, you could grab a Hackberry-Pi_Zero or even a full-featured SDR rig.
Input is clunky: The keyboard is functional, but far from pleasant to use.
Firmware quirks: Chat names occasionally don’t display, and emojis are a no-go.
Map setup is manual: You’ll need to load files to a MicroSD card—not ideal
Device boot screen with Meshtastic.org logo and firmware version.
Close-up of the keyboard, showing key layout and trackball.
Honestly, it still feels a bit like a beta experience, but so did the Android and iOS apps six months ago. I expect future firmware updates will smooth these edges over.
Recommendation
Would I recommend the T-Deck Plus?
If you want an all-in-one, always-ready Meshtastic terminal: Yes.
If you're building a node for daily use or long-term field deployment: I’d stick with the simpler board I talked about in Part 1. It’s cheaper, comes with a case and battery, and works well paired with a phone.
Final Thoughts
Overall, I’m happy with the T-Deck Plus. It's powerful, portable, and packed with features. But the price and firmware quirks make it a better fit for enthusiasts than for casual users at least for now. I’ll be keeping an eye on future updates and may revisit this in another few months. Right before publishing this blog my T-Deck Plus will no longer power on. The charging light lights up; however, the screen and device never power on. I did have an issue when I first flashed the device where no other nodes were recognized. After flashing to an alpha version of meshtastic other nodes were recognized, then right before it died, I was having the same issue. I am working with LILYGO support, but I don’t expect much given the recent reviews with similar issues. At this time, I do not recommend the LILYGO T-Deck Plus Meshtastic. I will update this blog in the future with updates from my experience with LILYGO support.
Resources
Mesh the planet!