I built a standalone, offline-first command center for Meshtastic mesh networks that runs entirely inside a single HTML file. There’s no backend, no installation, and no internet connection required. It works on laptops, tablets, phones, and some smartwatches using only native browser APIs.
Key Features
One self-contained HTML file (51KB)
Works fully offline (PWA)
Connects via Bluetooth, WiFi, or USB Serial
Real-time map of all mesh nodes
Metrics: RSSI, SNR, hop count, routing details
Message console + logs
No frameworks, no build tools, no cloud services
Why I built it
Existing tools rely on mobile apps or desktop programs that depend on OS permissions, cloud APIs, or network access. For emergency communications, off-grid operations, research teams, and field deployments, I wanted a universal interface that would work anywhere, on any device, under any conditions.
Thanks! Under what conditions has this been tested so far?
Just feels like the right context to share before people with scarce attention (like everyone has scarce and precious attention) start investing some of it in your efforts
Again, I really appreciate the work and the share, just feels like it could use some clear context
The readme is obviously AI written, and is clearly incomplete. This leaves me wondering how accurate the rest of the readme is, and how much of the code is vibe coded slop. I know some people use AI to write docs for reasonable reasons, perhaps English isn't your primary language. But the readme smells of AI and a lack of attention to detail that feels worrying enough to me that I won't be using this, at least unless it gains traction amongst people I know and trust.
Key examples:
"[Insert your download link here]"
"License
Choose the license appropriate for your repository:
As pointed out partially by other comments, this project does not work and is simply a one-shot skeleton made by AI. The description is a complete lie.
No communication or Meshtastic features are actually implemented, as no data is parsed.
Maybe I'm missing something but it's not a self contained file if it has external imports. It appears to be using unpkg CDN for CSS and JS. There's also multiple files, no license file, a server in python (???) and many, many indications that this is just AI slop.
// Parse Meshtastic protobuf data here
// This is a simplified example - actual implementation needs protobuf parsing
console.log('Received BLE data:', data);
There’s no reason to think this works fine given the readme mentions the author is waiting on their first meshtastic device to test against and the install instructions include ‘insert download link here’.
It’s a shame this is just slop, an approach like this could be interesting, using web APIs instead of native apps… but iOS Safari doesn’t support Web Bluetooth so it’s not going to work on iPhones at all which is a big unmentioned limitation.
Tangential: Is there a commercial hand-held waterproof (ip67) enclosure for the RAK4631? Tons of 3d prints, only a handful of submergible designs, and while I'm thankful for those authors, there really isn't anything that could take a serious dunk that I've found.
Do you actually need a waterproof case? Lots of drone and rc people are just spraying boards with conformal coatings, and the seem to do fine with occasional dunkings even when powered up in salt water. I've seen quadcopters still "working" under water. I've seen people making submersibles that use known non-waterproof 3d printed boxes, then pumping them full of marine grade grease to eliminate any air voids that would allow water ingress.
Key Features
One self-contained HTML file (51KB)
Works fully offline (PWA)
Connects via Bluetooth, WiFi, or USB Serial
Real-time map of all mesh nodes
Metrics: RSSI, SNR, hop count, routing details
Message console + logs
No frameworks, no build tools, no cloud services
Why I built it Existing tools rely on mobile apps or desktop programs that depend on OS permissions, cloud APIs, or network access. For emergency communications, off-grid operations, research teams, and field deployments, I wanted a universal interface that would work anywhere, on any device, under any conditions.
Looking for feedback on:
Hardware compatibility (especially T-Watch S3, RAK, Heltec)
Browser behavior across different platforms
Missing features you’d like to see
Ideas for v2 and beyond
This is still early, and feedback is very welcome. Thanks for taking a look.
— Jordan Townsend
Just feels like the right context to share before people with scarce attention (like everyone has scarce and precious attention) start investing some of it in your efforts
Again, I really appreciate the work and the share, just feels like it could use some clear context
The readme is obviously AI written, and is clearly incomplete. This leaves me wondering how accurate the rest of the readme is, and how much of the code is vibe coded slop. I know some people use AI to write docs for reasonable reasons, perhaps English isn't your primary language. But the readme smells of AI and a lack of attention to detail that feels worrying enough to me that I won't be using this, at least unless it gains traction amongst people I know and trust.
Key examples:
"[Insert your download link here]"
"License
Choose the license appropriate for your repository:
Apache 2.0
MIT License
MPL 2.0
Ask if you’d like these generated for you."
No communication or Meshtastic features are actually implemented, as no data is parsed.
This post should be removed.
It’s a shame this is just slop, an approach like this could be interesting, using web APIs instead of native apps… but iOS Safari doesn’t support Web Bluetooth so it’s not going to work on iPhones at all which is a big unmentioned limitation.
Probably because it’s untested AI slop.