Node Naming Standard¶
A structured naming convention for JTXMesh-owned infrastructure — community relays, shared gateways, CERT go-kits, and other network nodes.
Scope
This standard is required for JTXMesh infrastructure nodes (shared relays, gateways, go-kits). Personal operator nodes are encouraged but not required to follow it.
Name Format¶
| Field | Description | Example |
|---|---|---|
JTX |
Network prefix (always JTX) |
— |
SITE |
3-letter location code | WTW |
ROLE |
3-letter function code | RTR |
ID |
Unique identifier (2–3 chars) | 01 |
SUF |
Optional placement suffix (1 letter) | T |
Rules
- Uppercase letters and numbers only
- Hyphens (
-) between fields, dot (.) before suffix - No spaces, emojis, or special characters
- Target ≤ 20 characters total
- Never include personal data or exact addresses
SITE Codes¶
This page is the canonical registry for all SITE and ROLE codes. Add new codes here before using them in production.
Fixed Locations¶
| SITE | Location |
|---|---|
WTW |
Water Tower West |
WTC |
Water Tower Central |
MLB |
Mule Barn |
SAP |
South Apartments |
NAP |
North Apartments |
HOM |
Home |
Mobile & Field¶
| SITE | Location |
|---|---|
MOB |
Mobile / vehicle-mounted node |
FLD |
Field-deployed / portable node |
Adding a new SITE
SITE codes must be unique across JTXMesh. Add new codes to this table and get them reviewed before deploying.
ROLE Codes¶
Roles describe function, not hardware. If a device changes firmware or platform, keep the ROLE stable as long as the function stays the same.
| ROLE | Meaning | Meshtastic | MeshCore |
|---|---|---|---|
CLT |
Client | CLIENT |
— |
MUT |
Muted client | CLIENT_MUTE |
— |
BAS |
Base / gateway-ish client | CLIENT_BASE |
Companion (when acting as a base/bridge) |
RTR |
Router / repeater | ROUTER |
Repeater |
SRV |
Room Server | — | Room Server |
RSR |
Room Server + Repeater | — | Room Server/Repeater |
CMP |
Companion (personal) | — | Companion |
ID Rules¶
The <ID> must be unique within a SITE + ROLE combination.
Preferred strategies:
- Asset / inventory ID (best):
01,02,A1,B2 - Short mnemonic (ok for small meshes):
OFF,CAR,BAG— avoid personal names
Avoid:
- Temporary adjectives like
NEW,TEST,BIGANT - Embedding antenna gain, power level, or other hardware details
Placement Suffix (Optional)¶
One letter after a dot to indicate physical placement.
| SUF | Meaning |
|---|---|
I |
Indoor |
O |
Outdoor |
T |
Tower / high site |
R |
Rooftop |
V |
Vehicle |
P |
Portable |
Meshtastic Field Mapping¶
Meshtastic has a 4-character short_name limit and a longer long_name field. Map the standard name as follows:
long_name¶
Use the full standard name (without the placement suffix):
short_name¶
Use SITE[0] + ROLE[0] + ID (4 chars max):
| Standard Name | short_name |
Derivation |
|---|---|---|
JTX-WTW-RTR-01 |
WR01 |
WTW + RTR + 01 |
JTX-MOB-CLT-01 |
MC01 |
MOB + CLT + 01 |
JTX-MLB-SRV-01 |
LS01 |
MLB + SRV + 01 |
JTX-FLD-RTR-A1 |
FRA1 |
FLD + RTR + A1 |
Collisions
Some SITE codes share a first letter (e.g., MLB and MOB both produce M), so MLB-SRV-01 and MOB-SRV-01 would both map to MS01. When this happens, adjust the ID to differentiate (e.g., MS01 vs MS02) or use the second SITE letter instead (e.g., LS01 vs OS01).
Worked Examples¶
Fixed Tower Router¶
| Field | Value |
|---|---|
| Standard name | JTX-WTW-RTR-01.T |
long_name |
JTX-WTW-RTR-01 |
short_name |
WR01 |
| Description | Heltec V3 | 915MHz | 6dBi omni | 25ft | JB |
Mobile Client¶
| Field | Value |
|---|---|
| Standard name | JTX-MOB-CLT-01.V |
long_name |
JTX-MOB-CLT-01 |
short_name |
MC01 |
| Description | T-Beam | 915MHz | stock whip | dash mount | JB |
Field Go-Kit (CERT)¶
| Field | Value |
|---|---|
| Standard name | JTX-FLD-RTR-01.P |
long_name |
JTX-FLD-RTR-01 |
short_name |
FR01 |
| Description | Heltec V3 | 915MHz | 3dBi portable | go-kit bag | CERT |
Hardware Details¶
Put hardware, antenna, height, and power info in the device Description/Notes field — not the node name.
Suggested format:
Governance¶
- All JTXMesh infrastructure nodes must follow this standard
- SITE and ROLE codes must come from the tables on this page
- Temporary names must be renamed within 30 days
- To add a new SITE or ROLE code, update this page and get it reviewed before deployment