# Full Command Reference

MeshCore has two command surfaces. The device-side **serial CLI** (canonical reference: `docs.meshcore.io/cli_commands`) uses bare `get`/`set` verbs and is used to configure repeaters and room servers over USB serial. The host tool **meshcore-cli** (invoked as `meshcore-cli`/`meshcli`) connects to a companion radio over BLE, TCP, or Serial; commands can be passed on the command line or entered in interactive chat mode. The tables below note which surface each command belongs to.

## Device Information &amp; Status

<table id="bkmrk-commandpurpose-infod"> <thead><tr><th>Command</th><th>Purpose</th></tr></thead> <tbody> <tr><td>`infos` (alias `i`)</td><td>meshcore-cli: print node info (public key, TX power, radio params, name, location). For firmware version use `ver`; for battery/telemetry use `self_telemetry` / `req_status`.</td></tr> <tr><td>`stats-radio` / `stats-core` / `stats-packets`</td><td>Serial CLI: radio stats (noise floor, RSSI/SNR, airtime), core stats (battery, uptime, queue), and packet counters. There is no bare `status` command.</td></tr> <tr><td>`contacts` / `list` (alias `lc`)</td><td>meshcore-cli: list known contacts (nodes you have received adverts from). Use `node_discover <filter>` (`nd`) to discover nodes by type, or `neighbors` on a repeater's serial CLI.</td></tr> <tr><td>`get <param>`</td><td>Read a setting (e.g. `get radio`, `get name`, `get tx`). Run `get help` for the parameter list. There is no `config get` command.</td></tr> </tbody></table>

## Configuration

<table id="bkmrk-commandpurpose-confi"> <thead><tr><th>Command</th><th>Purpose</th></tr></thead> <tbody> <tr><td>`set name <name>`</td><td>Set the node name (no `config set` prefix).</td></tr> <tr><td>`set tx <dbm>`</td><td>Set LoRa transmit power in dBm (valid 1–22 for SX1262). Choose a value that keeps EIRP within your region's limit — 36 dBm EIRP in the US per FCC Part 15.247. Setting too high may violate local law.</td></tr> <tr><td>`erase`</td><td>Restore factory defaults. **Serial-only and destructive.** There is no `config reset` command.</td></tr> <tr><td>`set lat <degrees>`</td><td>Set latitude in degrees.</td></tr> <tr><td>`set lon <degrees>`</td><td>Set longitude in degrees.</td></tr> <tr><td>`password <new_password>`</td><td>Set the admin password. Any node presenting this password is added to the admin ACL.</td></tr> </tbody></table>

## Messaging

<table id="bkmrk-commandpurpose-send-"> <thead><tr><th>Command</th><th>Purpose</th></tr></thead> <tbody> <tr><td>`msg <name> <message>` (alias `m`)</td><td>meshcore-cli: send a direct message to a contact by name.</td></tr> <tr><td>`public <message>` or `chan <nb> <message>`</td><td>meshcore-cli: send to the public channel (0) or to channel number &lt;nb&gt;. Channel messages flood to subscribers. There is no `broadcast` command.</td></tr> <tr><td>`msgs_subscribe` (alias `ms`)</td><td>meshcore-cli: display messages as they arrive. Use `recv` (`r`) / `wait_msg` (`wm`) to read them, or chat mode. There is no `listen` command.</td></tr> </tbody></table>

## Network &amp; Routing

<table id="bkmrk-commandpurpose-adver"> <thead><tr><th>Command</th><th>Purpose</th></tr></thead> <tbody> <tr><td>`advert`</td><td>Trigger immediate advertisement broadcast (flood). Use `advert.zerohop` for a zero-hop advert.</td></tr> <tr><td>`set flood.advert.interval <hours>`</td><td>Flood advert interval in hours (valid 3–168; default 12).</td></tr> <tr><td>`set path.hash.mode <0|1|2>`</td><td>Advert path hash size (0=1-byte, 1=2-byte, 2=3-byte; **default 0**). Affects only this node's own adverts, not forwarding or routing-table behaviour; requires firmware ≥ 1.14.</td></tr> <tr><td>`region put <name> [parent]`</td><td>Create a region. Names are user-defined (e.g. `region put #USA`) — there are no predefined US/state scopes. Flooding must be enabled separately.</td></tr> <tr><td>`region put <child> <parent>`</td><td>Create a nested region under a parent (e.g. `region put #Colorado #USA`). Names are user-defined, not ISO/region codes.</td></tr> <tr><td>`region save`</td><td>Save region configuration.</td></tr> </tbody></table>

## Repeater &amp; Room Server

<table id="bkmrk-commandpurpose-set-a"> <thead><tr><th>Command</th><th>Purpose</th></tr></thead> <tbody> <tr><td>`set agc.reset.interval <seconds>`</td><td>AGC reset interval in **seconds** (rounded down to a multiple of 4; 0 disables). Helps with receiver desensitization.</td></tr> <tr><td>`set repeat <on|off>`</td><td>Enable/disable packet repeating on a repeater or room server (default on).</td></tr> </tbody></table>

## Firmware &amp; Maintenance

<table id="bkmrk-commandpurpose-reboo"> <thead><tr><th>Command</th><th>Purpose</th></tr></thead> <tbody> <tr><td>`reboot`</td><td>Restart the device.</td></tr> <tr><td>`start ota`</td><td>Initiate an over-the-air firmware update (nRF52). Otherwise flash via the MeshCore web flasher or esptool/UF2. There is no `flash` command.</td></tr> </tbody></table>