mirror of
https://github.com/mikecarper/MeshCore.git
synced 2026-11-04 10:57:27 +00:00
3369 lines
79 KiB
HTML
3369 lines
79 KiB
HTML
|
||
<!doctype html>
|
||
<html lang="en" class="no-js">
|
||
<head>
|
||
|
||
<meta charset="utf-8">
|
||
<meta name="viewport" content="width=device-width,initial-scale=1">
|
||
|
||
<meta name="description" content="Documentation for the open source MeshCore firmware">
|
||
|
||
|
||
|
||
<link rel="canonical" href="https://mikecarper.github.io/MeshCore/terminal_chat_cli/">
|
||
|
||
|
||
<link rel="prev" href="../cli_command_availability/">
|
||
|
||
|
||
<link rel="next" href="../companion_protocol/">
|
||
|
||
|
||
|
||
|
||
|
||
<link rel="icon" href="../assets/images/favicon.png">
|
||
<meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.8.0">
|
||
|
||
|
||
|
||
<title>Terminal chat cli - MeshCore Docs</title>
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../assets/stylesheets/main.57a0d79d.min.css">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:300,300i,400,400i,700,700i%7CRoboto+Mono:400,400i,700,700i&display=fallback">
|
||
<style>:root{--md-text-font:"Roboto";--md-code-font:"Roboto Mono"}</style>
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../_stylesheets/notification_builder.css?v=20261006-channel9">
|
||
|
||
<link rel="stylesheet" href="https://unpkg.com/leaflet@1.9.4/dist/leaflet.css">
|
||
|
||
<link rel="stylesheet" href="../_stylesheets/extra.css">
|
||
|
||
<link rel="stylesheet" href="../_stylesheets/firmware_picker.css?v=20261013-pick-first-1">
|
||
|
||
<link rel="stylesheet" href="../_stylesheets/telemetry_decoder.css?v=20261022-noise-history">
|
||
|
||
<link rel="stylesheet" href="../_stylesheets/management_decoder.css">
|
||
|
||
<link rel="stylesheet" href="../_stylesheets/filter_tool.css">
|
||
|
||
<link rel="stylesheet" href="../_stylesheets/preset_test.css?v=20260923-2">
|
||
|
||
<link rel="stylesheet" href="../_stylesheets/esp32_partition_catalog.css?v=20261001-1">
|
||
|
||
<script>__md_scope=new URL("..",location),__md_hash=e=>[...e].reduce(((e,_)=>(e<<5)-e+_.charCodeAt(0)),0),__md_get=(e,_=localStorage,t=__md_scope)=>JSON.parse(_.getItem(t.pathname+"."+e)),__md_set=(e,_,t=localStorage,a=__md_scope)=>{try{t.setItem(a.pathname+"."+e,JSON.stringify(_))}catch(e){}}</script>
|
||
|
||
|
||
|
||
|
||
|
||
</head>
|
||
|
||
|
||
<body dir="ltr">
|
||
|
||
|
||
<input class="md-toggle" data-md-toggle="drawer" type="checkbox" id="__drawer" autocomplete="off">
|
||
<input class="md-toggle" data-md-toggle="search" type="checkbox" id="__search" autocomplete="off">
|
||
<label class="md-overlay" for="__drawer"></label>
|
||
<div data-md-component="skip">
|
||
|
||
|
||
<a href="#terminal-chat-cli" class="md-skip">
|
||
Skip to content
|
||
</a>
|
||
|
||
</div>
|
||
<div data-md-component="announce">
|
||
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<header class="md-header md-header--shadow" data-md-component="header">
|
||
<nav class="md-header__inner md-grid" aria-label="Header">
|
||
<a href=".." title="MeshCore Docs" class="md-header__button md-logo" aria-label="MeshCore Docs" data-md-component="logo">
|
||
|
||
<img src="../_assets/meshcore.svg" alt="logo">
|
||
|
||
</a>
|
||
<label class="md-header__button md-icon" for="__drawer">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M3 6h18v2H3zm0 5h18v2H3zm0 5h18v2H3z"/></svg>
|
||
</label>
|
||
<div class="md-header__title" data-md-component="header-title">
|
||
<div class="md-header__ellipsis">
|
||
<div class="md-header__topic">
|
||
<span class="md-ellipsis">
|
||
MeshCore Docs
|
||
</span>
|
||
</div>
|
||
<div class="md-header__topic" data-md-component="header-topic">
|
||
<span class="md-ellipsis">
|
||
|
||
Terminal chat cli
|
||
|
||
</span>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<script>var palette=__md_get("__palette");if(palette&&palette.color){if("(prefers-color-scheme)"===palette.color.media){var media=matchMedia("(prefers-color-scheme: light)"),input=document.querySelector(media.matches?"[data-md-color-media='(prefers-color-scheme: light)']":"[data-md-color-media='(prefers-color-scheme: dark)']");palette.color.media=input.getAttribute("data-md-color-media"),palette.color.scheme=input.getAttribute("data-md-color-scheme"),palette.color.primary=input.getAttribute("data-md-color-primary"),palette.color.accent=input.getAttribute("data-md-color-accent")}for(var[key,value]of Object.entries(palette.color))document.body.setAttribute("data-md-color-"+key,value)}</script>
|
||
|
||
|
||
|
||
|
||
|
||
<label class="md-header__button md-icon" for="__search">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M9.5 3A6.5 6.5 0 0 1 16 9.5c0 1.61-.59 3.09-1.56 4.23l.27.27h.79l5 5-1.5 1.5-5-5v-.79l-.27-.27A6.52 6.52 0 0 1 9.5 16 6.5 6.5 0 0 1 3 9.5 6.5 6.5 0 0 1 9.5 3m0 2C7 5 5 7 5 9.5S7 14 9.5 14 14 12 14 9.5 12 5 9.5 5"/></svg>
|
||
</label>
|
||
<div class="md-search" data-md-component="search" role="dialog">
|
||
<label class="md-search__overlay" for="__search"></label>
|
||
<div class="md-search__inner" role="search">
|
||
<form class="md-search__form" name="search">
|
||
<input type="text" class="md-search__input" name="query" aria-label="Search" placeholder="Search" autocapitalize="off" autocorrect="off" autocomplete="off" spellcheck="false" data-md-component="search-query" required>
|
||
<label class="md-search__icon md-icon" for="__search">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M9.5 3A6.5 6.5 0 0 1 16 9.5c0 1.61-.59 3.09-1.56 4.23l.27.27h.79l5 5-1.5 1.5-5-5v-.79l-.27-.27A6.52 6.52 0 0 1 9.5 16 6.5 6.5 0 0 1 3 9.5 6.5 6.5 0 0 1 9.5 3m0 2C7 5 5 7 5 9.5S7 14 9.5 14 14 12 14 9.5 12 5 9.5 5"/></svg>
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg>
|
||
</label>
|
||
<nav class="md-search__options" aria-label="Search">
|
||
|
||
<button type="reset" class="md-search__icon md-icon" title="Clear" aria-label="Clear" tabindex="-1">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M19 6.41 17.59 5 12 10.59 6.41 5 5 6.41 10.59 12 5 17.59 6.41 19 12 13.41 17.59 19 19 17.59 13.41 12z"/></svg>
|
||
</button>
|
||
</nav>
|
||
|
||
<div class="md-search__suggest" data-md-component="search-suggest"></div>
|
||
|
||
</form>
|
||
<div class="md-search__output">
|
||
<div class="md-search__scrollwrap" tabindex="0" data-md-scrollfix>
|
||
<div class="md-search-result" data-md-component="search-result">
|
||
<div class="md-search-result__meta">
|
||
Initializing search
|
||
</div>
|
||
<ol class="md-search-result__list" role="presentation"></ol>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="md-header__source">
|
||
<a href="https://github.com/mikecarper/MeshCore/" title="Go to repository" class="md-source" data-md-component="source">
|
||
<div class="md-source__icon md-icon">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"><!--! Font Awesome Free 7.1.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2025 Fonticons, Inc.--><path d="M439.6 236.1 244 40.5c-5.4-5.5-12.8-8.5-20.4-8.5s-15 3-20.4 8.4L162.5 81l51.5 51.5c27.1-9.1 52.7 16.8 43.4 43.7l49.7 49.7c34.2-11.8 61.2 31 35.5 56.7-26.5 26.5-70.2-2.9-56-37.3L240.3 199v121.9c25.3 12.5 22.3 41.8 9.1 55-6.4 6.4-15.2 10.1-24.3 10.1s-17.8-3.6-24.3-10.1c-17.6-17.6-11.1-46.9 11.2-56v-123c-20.8-8.5-24.6-30.7-18.6-45L142.6 101 8.5 235.1C3 240.6 0 247.9 0 255.5s3 15 8.5 20.4l195.6 195.7c5.4 5.4 12.7 8.4 20.4 8.4s15-3 20.4-8.4l194.7-194.7c5.4-5.4 8.4-12.8 8.4-20.4s-3-15-8.4-20.4"/></svg>
|
||
</div>
|
||
<div class="md-source__repository">
|
||
mikecarper/MeshCore
|
||
</div>
|
||
</a>
|
||
</div>
|
||
|
||
</nav>
|
||
|
||
</header>
|
||
|
||
<div class="md-container" data-md-component="container">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<main class="md-main" data-md-component="main">
|
||
<div class="md-main__inner md-grid">
|
||
|
||
|
||
|
||
<div class="md-sidebar md-sidebar--primary" data-md-component="sidebar" data-md-type="navigation" >
|
||
<div class="md-sidebar__scrollwrap">
|
||
<div class="md-sidebar__inner">
|
||
|
||
|
||
|
||
|
||
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
|
||
<label class="md-nav__title" for="__drawer">
|
||
<a href=".." title="MeshCore Docs" class="md-nav__button md-logo" aria-label="MeshCore Docs" data-md-component="logo">
|
||
|
||
<img src="../_assets/meshcore.svg" alt="logo">
|
||
|
||
</a>
|
||
MeshCore Docs
|
||
</label>
|
||
|
||
<div class="md-nav__source">
|
||
<a href="https://github.com/mikecarper/MeshCore/" title="Go to repository" class="md-source" data-md-component="source">
|
||
<div class="md-source__icon md-icon">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"><!--! Font Awesome Free 7.1.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2025 Fonticons, Inc.--><path d="M439.6 236.1 244 40.5c-5.4-5.5-12.8-8.5-20.4-8.5s-15 3-20.4 8.4L162.5 81l51.5 51.5c27.1-9.1 52.7 16.8 43.4 43.7l49.7 49.7c34.2-11.8 61.2 31 35.5 56.7-26.5 26.5-70.2-2.9-56-37.3L240.3 199v121.9c25.3 12.5 22.3 41.8 9.1 55-6.4 6.4-15.2 10.1-24.3 10.1s-17.8-3.6-24.3-10.1c-17.6-17.6-11.1-46.9 11.2-56v-123c-20.8-8.5-24.6-30.7-18.6-45L142.6 101 8.5 235.1C3 240.6 0 247.9 0 255.5s3 15 8.5 20.4l195.6 195.7c5.4 5.4 12.7 8.4 20.4 8.4s15-3 20.4-8.4l194.7-194.7c5.4-5.4 8.4-12.8 8.4-20.4s-3-15-8.4-20.4"/></svg>
|
||
</div>
|
||
<div class="md-source__repository">
|
||
mikecarper/MeshCore
|
||
</div>
|
||
</a>
|
||
</div>
|
||
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href=".." class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Home
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--nested">
|
||
|
||
|
||
|
||
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_2" >
|
||
|
||
|
||
<label class="md-nav__link" for="__nav_2" id="__nav_2_label" tabindex="0">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Firmware and tools
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<nav class="md-nav" data-md-level="1" aria-labelledby="__nav_2_label" aria-expanded="false">
|
||
<label class="md-nav__title" for="__nav_2">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
|
||
Firmware and tools
|
||
|
||
|
||
</label>
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../firmware_picker/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Firmware picker
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../notifications/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Notifications
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../preset_test/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Preset test
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../filter_tool/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Filter tool
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../telemetry_decoder/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Telemetry decoder
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../management_decoder/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Management decoder
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--active md-nav__item--nested">
|
||
|
||
|
||
|
||
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_3" checked>
|
||
|
||
|
||
<label class="md-nav__link" for="__nav_3" id="__nav_3_label" tabindex="0">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Documentation
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<nav class="md-nav" data-md-level="1" aria-labelledby="__nav_3_label" aria-expanded="true">
|
||
<label class="md-nav__title" for="__nav_3">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
|
||
Documentation
|
||
|
||
|
||
</label>
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--nested">
|
||
|
||
|
||
|
||
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_3_1" >
|
||
|
||
|
||
<label class="md-nav__link" for="__nav_3_1" id="__nav_3_1_label" tabindex="0">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Getting started and features
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<nav class="md-nav" data-md-level="2" aria-labelledby="__nav_3_1_label" aria-expanded="false">
|
||
<label class="md-nav__title" for="__nav_3_1">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
|
||
Getting started and features
|
||
|
||
|
||
</label>
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../faq/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Faq
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../full_profiles/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Full profiles
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../role_feature_switches/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Role feature switches
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../full_companion_features/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Full companion features
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../companion_radio_full/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Companion radio full
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../full_companion_usb_switcher/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Full companion usb switcher
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../companion_offline_queue/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Companion offline queue
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../halo_keymind_settings/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Halo keymind settings
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--nested">
|
||
|
||
|
||
|
||
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_3_2" >
|
||
|
||
|
||
<label class="md-nav__link" for="__nav_3_2" id="__nav_3_2_label" tabindex="0">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Firmware updates and partitions
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<nav class="md-nav" data-md-level="2" aria-labelledby="__nav_3_2_label" aria-expanded="false">
|
||
<label class="md-nav__title" for="__nav_3_2">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
|
||
Firmware updates and partitions
|
||
|
||
|
||
</label>
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../upgrading_1.17.1.8_to_1.17.1.9/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Upgrading 1.17.1.8 to 1.17.1.9
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../ota_user_guide/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Ota user guide
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../ota_easy/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Ota easy
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../lora_ota_automation/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Lora ota automation
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../ota_nrf52_bootloader_update/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Ota nrf52 bootloader update
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../ota_nrf52_qspi/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Ota nrf52 qspi
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../ota_meshtower_v2_sdcard/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Ota meshtower v2 sdcard
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../esp32_partition_catalog/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Esp32 partition catalog
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../esp32_wifi_partition_migration/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Esp32 wifi partition migration
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../heltec_v4_wifi_partition_migration/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Heltec v4 wifi partition migration
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../host_cli_service/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Host cli service
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--nested">
|
||
|
||
|
||
|
||
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_3_3" >
|
||
|
||
|
||
<label class="md-nav__link" for="__nav_3_3" id="__nav_3_3_label" tabindex="0">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Radio, networking, and power
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<nav class="md-nav" data-md-level="2" aria-labelledby="__nav_3_3_label" aria-expanded="false">
|
||
<label class="md-nav__title" for="__nav_3_3">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
|
||
Radio, networking, and power
|
||
|
||
|
||
</label>
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../radio_profiles/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Radio profiles
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../radio_presets/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Radio presets
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../fleet_management/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Private fleet management
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../room_services/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Room services
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../carrier_wave/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Carrier wave
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../espnow_bridge_setup/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Espnow bridge setup
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../rs232_bridge_setup/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Rs232 bridge setup
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../udp_bridge_setup/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Udp bridge setup
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../WiFi/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
WiFi
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../flood_filtering/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Flood filtering
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../gps_tracking/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Gps tracking
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../companion_lost_reply/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Companion lost reply
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../sensor_tracker/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Sensor tracker
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../nrf52_power_management/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Nrf52 power management
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--active md-nav__item--nested">
|
||
|
||
|
||
|
||
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_3_4" checked>
|
||
|
||
|
||
<label class="md-nav__link" for="__nav_3_4" id="__nav_3_4_label" tabindex="0">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
CLI and protocol reference
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<nav class="md-nav" data-md-level="2" aria-labelledby="__nav_3_4_label" aria-expanded="true">
|
||
<label class="md-nav__title" for="__nav_3_4">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
|
||
CLI and protocol reference
|
||
|
||
|
||
</label>
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../cli_commands/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Cli commands
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../cli_build_matrix/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Cli build matrix
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../cli_command_availability/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Cli command availability
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--active">
|
||
|
||
<input class="md-nav__toggle md-toggle" type="checkbox" id="__toc">
|
||
|
||
|
||
|
||
|
||
|
||
<label class="md-nav__link md-nav__link--active" for="__toc">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Terminal chat cli
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<a href="./" class="md-nav__link md-nav__link--active">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Terminal chat cli
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<label class="md-nav__title" for="__toc">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
Table of contents
|
||
</label>
|
||
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#companion-wifi-browser-terminal" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Companion WiFi browser terminal
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#local-maintenance-commands" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Local maintenance commands
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#companion-contact-and-channel-tx-profiles" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Companion contact and channel TX profiles
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#companion-media-and-ssh-tx-profiles" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Companion media and SSH TX profiles
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#esp32-full-companion-ethernet" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
ESP32 Full Companion Ethernet
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#companion-usb-mode" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Companion USB mode
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#commands" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Commands
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../companion_protocol/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Companion protocol
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kiss_modem_protocol/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kiss modem protocol
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../packet_format/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Packet format
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../payloads/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Payloads
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../ota_protocol/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Ota protocol
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../management_reports/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Management reports
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../stats_binary_frames/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Stats binary frames
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../number_allocations/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Number allocations
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../qr_codes/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Qr codes
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../docs/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Docs
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../research/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Research
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--nested">
|
||
|
||
|
||
|
||
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_5" >
|
||
|
||
|
||
<label class="md-nav__link" for="__nav_5" id="__nav_5_label" tabindex="0">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Releases
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<nav class="md-nav" data-md-level="1" aria-labelledby="__nav_5_label" aria-expanded="false">
|
||
<label class="md-nav__title" for="__nav_5">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
|
||
Releases
|
||
|
||
|
||
</label>
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../releases/1.18.0.1/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Current - 1.18.0.1 USA Cascade
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--nested">
|
||
|
||
|
||
|
||
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_5_2" >
|
||
|
||
|
||
<label class="md-nav__link" for="__nav_5_2" id="__nav_5_2_label" tabindex="0">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Previous releases
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<nav class="md-nav" data-md-level="2" aria-labelledby="__nav_5_2_label" aria-expanded="false">
|
||
<label class="md-nav__title" for="__nav_5_2">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
|
||
Previous releases
|
||
|
||
|
||
</label>
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../releases/1.17.1.9/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
1.17.1.9 USA Cascade
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../releases/1.17.1.8/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
1.17.1.8 USA Cascade
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../old-releases/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Older releases
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../test-results/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Test Results
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="md-sidebar md-sidebar--secondary" data-md-component="sidebar" data-md-type="toc" >
|
||
<div class="md-sidebar__scrollwrap">
|
||
<div class="md-sidebar__inner">
|
||
|
||
|
||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<label class="md-nav__title" for="__toc">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
Table of contents
|
||
</label>
|
||
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#companion-wifi-browser-terminal" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Companion WiFi browser terminal
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#local-maintenance-commands" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Local maintenance commands
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#companion-contact-and-channel-tx-profiles" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Companion contact and channel TX profiles
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#companion-media-and-ssh-tx-profiles" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Companion media and SSH TX profiles
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#esp32-full-companion-ethernet" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
ESP32 Full Companion Ethernet
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#companion-usb-mode" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Companion USB mode
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#commands" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Commands
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
|
||
</nav>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="md-content" data-md-component="content">
|
||
|
||
<article class="md-content__inner md-typeset">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="https://github.com/mikecarper/MeshCore/edit/keymindCascade/docs/terminal_chat_cli.md" title="Edit this page" class="md-content__button md-icon" rel="edit">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4zm10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1z"/></svg>
|
||
</a>
|
||
|
||
|
||
|
||
|
||
<!-- meshcore-hosted-doc-link:start -->
|
||
<p class="meshcore-hosted-doc-link"><a href="https://mikecarper.github.io/MeshCore/terminal_chat_cli/">View this page on MeshCore Docs</a>.</p>
|
||
<!-- meshcore-hosted-doc-link:end -->
|
||
|
||
<h1 id="terminal-chat-cli">Terminal Chat CLI</h1>
|
||
<p>Below are the commands you can enter into the Terminal Chat clients:</p>
|
||
<p>For a timed RF carrier test on SX1262 or LR1110, use <code>cw on 2.5</code> or
|
||
<code>cw2 on 2.5</code>, then <code>cw off</code> to stop early. See <a href="../carrier_wave/">carrier-wave RF checks</a>
|
||
for profile selection, limits, and status commands.</p>
|
||
<h2 id="companion-wifi-browser-terminal">Companion WiFi browser terminal</h2>
|
||
<p>On ESP32 WiFi Companions with WebConfig, open the node's LAN IP address and
|
||
select <strong>CLI</strong>. The browser runs the same commands as the USB terminal and
|
||
Full Companion's TCP terminal on port 5002, including contact import, contact
|
||
selection, messages, remote login/commands, and delayed RF replies. Run <code>help</code>
|
||
to list commands compiled into the device. Enable the tab with
|
||
<code>set wifi.cli on</code> and sign in with the node admin password. The setup AP does
|
||
not expose this full terminal.</p>
|
||
<p>For example, copy the complete <code>meshcore://...</code> string from <code>card</code> on another
|
||
Companion, then run these commands on the receiving Companion:</p>
|
||
<pre><code class="language-text">import meshcore://<full-contact-card-data>
|
||
list
|
||
to <contact-name-or-prefix>
|
||
</code></pre>
|
||
<p>Replace the placeholders; a bare public key is not a contact card. Import is
|
||
queued for signature validation, so use <code>list</code> to confirm the contact appears.
|
||
Explicit import works with manual contact addition enabled and bypasses the
|
||
automatic discovery type/hop filters. It still respects contact storage limits;
|
||
a full contact table follows the configured overwrite policy. <code>to</code>
|
||
remains selected for subsequent <code>send</code>, <code>path</code>, <code>login</code>, and <code>cmd</code> commands
|
||
within this terminal session.</p>
|
||
<p>Only one USB, TCP, or browser text terminal owns the session at a time. An
|
||
idle startup USB prompt can be borrowed by WiFi. Use <code>disconnect</code> or the
|
||
browser's <strong>disconnect</strong> button to release it. Closing the page releases the
|
||
session; if the connection disappears, it expires after 60 seconds without a
|
||
poll. Long replies page into the browser automatically, and incoming replies
|
||
continue appearing after a command finishes. Terminal scrollback starts at
|
||
4 KiB and can grow to 32 KiB for unread output, preferring PSRAM; it shrinks
|
||
after reading and is freed when the session expires. If output exceeds the
|
||
available buffer while unread, the browser reports the missing output.</p>
|
||
<p>USB protocol-switch and USB MOTA ownership commands still apply to the USB
|
||
connection. Use the WiFi MOTA seeder on port 5001 for a host folder over WiFi.</p>
|
||
<h2 id="local-maintenance-commands">Local maintenance commands</h2>
|
||
<p>Supported ESP32-S3/SX1262 Full Companions also support
|
||
<a href="../radio_profiles/#meshtext-channel-chat">Meshtext channel chat</a>:</p>
|
||
<pre><code class="language-text">set mt.shortname MIKE
|
||
send mt.nodeinfo 0
|
||
channel 0 Hello
|
||
</code></pre>
|
||
<p>Use a configured <code>mt-</code> channel slot. Chat carries only the entered text. After
|
||
the first successful over-air chat transmission per used channel/identity per
|
||
boot, the firmware queues a separate standard name/ID NodeInfo advertisement.
|
||
Automatic metadata waits for a 250 ms quiet TX gap so the peer can resume RX.
|
||
<code>send mt.nodeinfo</code> can also request one explicitly. Neither contains GPS or
|
||
coordinates. No NodeInfo is sent just from booting, configuration, receiving
|
||
traffic or a timer. The long name comes from the existing node name;
|
||
<code>get mt.shortname</code> shows the effective four-byte short name. These commands
|
||
are not added to smaller or feature-disabled builds.</p>
|
||
<p>MT chat uses <code>flood.retry.count</code> (<code>0</code>–<code>15</code>) to retry when no matching forwarded
|
||
copy is heard. A heard repeat stops retries, but is not a recipient delivery
|
||
receipt. NodeInfo has at most one retry, only with a nonzero count and
|
||
<code>flood.retry.advert on</code>, with an extra one-minute wait. For example:</p>
|
||
<pre><code class="language-text">get flood.retry.count
|
||
set flood.retry.count 3
|
||
set flood.retry.advert on
|
||
get mt.retry
|
||
</code></pre>
|
||
<p><code>get mt.retry</code> shows retry/heard/exhausted counters, pending work and the
|
||
configured count; it does not change settings. With <code>set mt.hops 0</code>, no peer
|
||
can forward a copy, so heard-repeat retries are disabled. The original chat
|
||
and first-use NodeInfo are unaffected.</p>
|
||
<p>This does not make the Companion relay other people's MT packets. See
|
||
<a href="../radio_profiles/#heard-repeat-retries">heard-repeat retries</a> for the airtime
|
||
limits, exact-packet matching and cancellation rules.</p>
|
||
<p>Local means a connection directly to the node: USB, BLE or WiFi/Ethernet
|
||
Companion protocol, a TCP terminal, or the browser CLI on the LAN. These
|
||
connections can use the following commands when the role and build include
|
||
the corresponding feature:</p>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th>Command</th>
|
||
<th>Result</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td><code>stats-core</code>, <code>stats-radio</code>, <code>stats-radio-diag</code>, <code>stats-packets</code></td>
|
||
<td>Runtime diagnostics</td>
|
||
</tr>
|
||
<tr>
|
||
<td><code>get public.key</code></td>
|
||
<td>Read-only node identity public key; Companion returns <code>></code> followed by 64 uppercase hex characters</td>
|
||
</tr>
|
||
<tr>
|
||
<td><code>get prv.key</code></td>
|
||
<td>Node identity private key; Companion requires private key export enabled in the build</td>
|
||
</tr>
|
||
<tr>
|
||
<td><code>get password</code></td>
|
||
<td>Infrastructure admin password; ESP32 WiFi Companion reports management-password status without revealing it; other Companions report no admin password</td>
|
||
</tr>
|
||
<tr>
|
||
<td><code>password <new-password></code></td>
|
||
<td>Change the saved admin password on infrastructure and ESP32 WiFi Companion</td>
|
||
</tr>
|
||
<tr>
|
||
<td><code>erase</code></td>
|
||
<td>Erase stored identity and settings; reboot for a fresh node</td>
|
||
</tr>
|
||
<tr>
|
||
<td><code>get wifi.pwd</code></td>
|
||
<td>Stored WiFi password on WiFi builds</td>
|
||
</tr>
|
||
<tr>
|
||
<td><code>get mqttN.password</code>, <code>get mqttN.token</code></td>
|
||
<td>Stored credentials for MQTT slot N</td>
|
||
</tr>
|
||
<tr>
|
||
<td><code>get acl</code>, <code>log</code></td>
|
||
<td>Infrastructure ACL or captured packet log; these stores do not exist on Companion</td>
|
||
</tr>
|
||
<tr>
|
||
<td><code>get guest</code>, <code>set guest on</code>, <code>set guest off</code>, <code>get guests [page]</code></td>
|
||
<td>Repeater guest-login control and current guest sessions</td>
|
||
</tr>
|
||
<tr>
|
||
<td><code>get logins [page]</code></td>
|
||
<td>Recent repeater login attempts, with 12-character public-key prefixes</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p>The command text is the same for direct connections. A binary Companion app
|
||
can send <code>0x42</code> (<code>CMD_RUN_CLI_COMMAND</code>) followed by the ASCII command, without
|
||
switching into terminal mode. The response is <code>0x1D</code> (<code>RESP_CODE_CLI_REPLY</code>)
|
||
followed by the reply text. For example, payload <code>42 67 65 74 20 70 61 73 73 77
|
||
6f 72 64</code> runs <code>get password</code>. USB framing remains the normal Companion frame;
|
||
BLE and TCP use their existing Companion transport framing.</p>
|
||
<p><code>set freq <MHz></code> is available on these local connections and through authorized
|
||
LoRa administration, just like <code>set radio</code>. It saves the frequency without
|
||
changing bandwidth, spreading factor, or coding rate and requires a reboot to
|
||
apply. Infrastructure roles also apply the board's transmit-power limit.</p>
|
||
<p>Commands relayed to another node using <code>cmd</code> travel over LoRa and retain the
|
||
remote restrictions on local-only maintenance and secret reads. These local
|
||
permissions do not add an ACL or packet-log store to Companion. Use <code>list</code> or
|
||
the binary contacts operations for Companion contacts. Interactive chat
|
||
commands still use the text terminal or their corresponding binary protocol
|
||
operations.</p>
|
||
<p>The browser CLI requires station/LAN mode, <code>wifi.cli on</code>, and the node admin
|
||
login. Configuration forms keep password fields masked; explicit local CLI
|
||
getters return their values, except ESP32 WiFi Companion's status-only
|
||
<code>get password</code>. Existing USB/BLE/TCP clients and explicitly authorized remote
|
||
CLI contacts retain their administrative command access. HTTP authentication
|
||
does not add a password handshake to the raw TCP services.</p>
|
||
<h2 id="companion-contact-and-channel-tx-profiles">Companion contact and channel TX profiles</h2>
|
||
<p>Choose where the Companion transmits to a contact or group channel:</p>
|
||
<pre><code class="language-text">set tx.user "Alice Jones" radio2
|
||
get tx.user "Alice Jones"
|
||
set tx.channel 0 both
|
||
set tx.channel #wardriving radio
|
||
get tx.channel 0
|
||
</code></pre>
|
||
<p>Values are <code>auto</code>, <code>radio</code>, <code>radio2</code>, <code>both</code>, and <code>off</code>. <code>auto</code> follows
|
||
<code>radio2.cross</code>; explicit choices override it. Radio2 must still be in <code>rxtx</code>
|
||
mode, and a <code>radio2</code>-only send fails when it cannot transmit. These settings
|
||
persist and also apply to messages sent by the phone app. Use exact names,
|
||
a channel index, or <code>key:<unique public-key prefix></code> for a contact.
|
||
See the <a href="../radio_profiles/#companion-tx-routing-by-contact-or-channel">routing guide</a>
|
||
for which requests/replies are covered and how to reset a choice.</p>
|
||
<h2 id="companion-media-and-ssh-tx-profiles">Companion media and SSH TX profiles</h2>
|
||
<pre><code class="language-text">get tx.media
|
||
set tx.media radio2
|
||
get tx.ssh
|
||
set tx.ssh radio
|
||
</code></pre>
|
||
<p>Each setting accepts <code>auto</code>, <code>radio</code>, <code>radio2</code>, <code>both</code>, or <code>off</code>, defaults to
|
||
<code>auto</code>, and is saved across reboot. <code>tx.media</code> handles Open TAK binary media;
|
||
<code>tx.ssh</code> requires a tunnel app using the explicit SSH application tag, not
|
||
an existing untagged SSH connection. See the
|
||
<a href="../radio_profiles/#companion-media-and-ssh-tx-routing">application routing guide</a>
|
||
for the framing and routing rules. Ordinary text keeps its existing route.</p>
|
||
<h2 id="esp32-full-companion-ethernet">ESP32 Full Companion Ethernet</h2>
|
||
<p>Use <code>set ethernet.radio <MHz>,<kHz>,<SF>,<CR>[,<preamble>]</code>, then
|
||
<code>set ethernet on</code>. <code>get ethernet</code> reports state; <code>set ethernet off</code> closes
|
||
the KISS service and releases its radio2 lease. Settings survive reboot.
|
||
This is a separate whole-link mode, not the tagged <code>tx.ssh</code> application route.
|
||
Normal USB/BLE/Companion TCP stay in Companion mode. The host instead uses
|
||
KISS-over-TCP port 5003 on trusted station WiFi, with MTU 230.
|
||
See <a href="../radio_profiles/#esp32-companion-ethernet-over-lora-kiss">Ethernet setup and radio2 restrictions</a>.</p>
|
||
<h2 id="companion-usb-mode">Companion USB mode</h2>
|
||
<p>Updated 1.17.1.6 USB Companion builds, including ordinary and Full builds, start
|
||
in ASCII at 115200 baud. A valid framed app command automatically selects Binary
|
||
Companion. You can open a terminal without a start token:</p>
|
||
<pre><code class="language-sh">picocom --baud 115200 /dev/ttyACM0
|
||
</code></pre>
|
||
<p>Current source waits for input before printing the USB banner. Press Enter or
|
||
type a command. This preserves the clean first response needed by binary apps;
|
||
see <a href="../test-results/companion_usb_client_validation/">USB client validation</a> for release status.</p>
|
||
<p>For older firmware or a port already in Binary mode, use:</p>
|
||
<pre><code class="language-sh">picocom --baud 115200 \
|
||
--imap spchex \
|
||
--initstring $'+++MESHCORE-TERM-START\r' \
|
||
/dev/ttyACM0
|
||
</code></pre>
|
||
<p><code>--initstring</code> sends this exact terminal-start line automatically:</p>
|
||
<pre><code>+++MESHCORE-TERM-START
|
||
</code></pre>
|
||
<p>The carriage return is required in Binary mode. Control tokens are recognized
|
||
only as complete CR/LF-delimited lines, so the same text embedded in unrelated
|
||
unframed input cannot switch modes accidentally.</p>
|
||
<p>Binary Companion frames can contain terminal control bytes. The <code>spchex</code> input
|
||
map renders those bytes as bracketed hexadecimal during the short transition
|
||
instead of allowing them to change the local terminal's character set or
|
||
display state. It leaves high-bit bytes unchanged so a UTF-8 terminal displays
|
||
emoji and non-ASCII text normally. Do not add <code>8bithex</code> unless you explicitly
|
||
want UTF-8 bytes displayed as sequences such as <code>[f0][9f][91][8b]</code>. Once the
|
||
terminal banner appears, the start sequence has already succeeded; do not
|
||
enter it again as a terminal command.</p>
|
||
<p>Send the following exact sequence to return to the binary protocol:</p>
|
||
<pre><code>+++MESHCORE-TERM-STOP
|
||
</code></pre>
|
||
<p>If logging shares the primary USB port (ESP32), first run <code>set usb.logging off</code>.
|
||
With logging still on, the stop token reports an error and keeps ASCII logging
|
||
active. nRF52 Full's separate logging port can remain enabled.</p>
|
||
<p>An observable USB session reset restores ASCII after clearing the previous
|
||
client's state. Native USB with DTR can detect a terminal closing; ESP32 hardware
|
||
USB Serial/JTAG detects bus resets and physical host loss. USB-to-UART bridges
|
||
usually cannot detect a terminal closing. Use the start token on ports that
|
||
remain in Binary mode; idle time does not select ASCII.</p>
|
||
<p>Both modes use the same port at 115200. Selecting 57600 is not a portable mode
|
||
switch: native USB CDC devices ignore the requested baud, while USB-to-UART
|
||
devices really change the UART timing and receive corrupt data. Binary mode is
|
||
the framed Companion API used by apps and <code>meshcli</code>; close the terminal before
|
||
opening that port from an app.</p>
|
||
<p>All USB Companion builds automatically switch when they see a complete
|
||
<code><</code>-prefixed Companion frame at an empty prompt. The explicit start/stop tokens
|
||
remain available. See <a href="../full_companion_usb_switcher/">Companion USB CLI and binary switcher</a>
|
||
for the state machine and limitations.</p>
|
||
<h2 id="commands">Commands</h2>
|
||
<p>ESP32 and nRF52 Full Companions include an offline World English Bible lookup:</p>
|
||
<pre><code class="language-text">get reader 3:16
|
||
get reader 2
|
||
get reader 2:2-12
|
||
</code></pre>
|
||
<p>These select a verse, an entire chapter, or an inclusive verse range from the
|
||
embedded corpus. Local USB/TCP/browser terminals stream the complete selection
|
||
in small chunks, keeping the radio loop running while the terminal drains.
|
||
A new command or disconnected session cancels unfinished output. Text uses
|
||
plain ASCII punctuation with unchanged wording and capitalization.</p>
|
||
<p>In the app's USB/BLE CLI, each reply stays within the existing frame limit.
|
||
Follow the displayed <code>Next: get reader ...</code> command to continue a long verse
|
||
or advance through the selected chapter/range. The optional final number is
|
||
the page within the first verse of that command, for example <code>get reader 21:17 2</code>.
|
||
The continuation command retains the requested range's end.
|
||
See <a href="https://github.com/mikecarper/MeshCore/blob/keymindCascade/tools/bible/README.md">Reader lookup and compression</a> for the
|
||
source, supported build profiles and memory costs.</p>
|
||
<pre><code>set freq {frequency}
|
||
</code></pre>
|
||
<p>Set the saved LoRa frequency. Example: <code>set freq 915.8</code>. Available over local
|
||
connections and authorized LoRa CLI; reboot to apply.</p>
|
||
<pre><code>set tx {tx-power-dbm}
|
||
</code></pre>
|
||
<p>Sets LoRa-chip transmit power in dBm. The firmware rejects values outside the
|
||
radio/board limit; external-PA boards can have a lower input-power ceiling than
|
||
the radio chip itself.</p>
|
||
<pre><code>set name {name}
|
||
</code></pre>
|
||
<p>Sets your advertisement name.</p>
|
||
<pre><code>get bluetooth.name
|
||
set bluetooth.name {name|default}
|
||
</code></pre>
|
||
<p>Shows or changes the complete Bluetooth device name without changing the mesh
|
||
advertisement identity. A custom name may contain spaces and is limited to 31
|
||
valid UTF-8 bytes. <code>default</code> restores <code>MeshCore-<node name></code>. The saved change
|
||
takes effect after reboot. <code>get ble.name</code> and <code>set ble.name</code> are short aliases.</p>
|
||
<pre><code>set pin {0-999999}
|
||
</code></pre>
|
||
<p>Saves the Bluetooth pairing PIN. For example, run <code>set pin 654321</code>, then
|
||
<code>reboot</code> to activate it. <code>set pin 0</code> removes the saved override and restores the
|
||
build's default/generated PIN policy after reboot; it does not disable Bluetooth.
|
||
Existing bonds can reconnect without PIN entry, so forget the phone's device
|
||
entry and pair again if needed. See <a href="../cli_commands/#set-the-bluetooth-pairing-pin-companion">Bluetooth pairing PIN</a>.</p>
|
||
<pre><code>get bluetooth.mac
|
||
set bluetooth.mac {address|random|random-every-boot|random-after-connect|default}
|
||
get bluetooth.stealth
|
||
set bluetooth.stealth {on|off}
|
||
</code></pre>
|
||
<p>Shows or changes the Bluetooth identity on Companion builds with BLE. A
|
||
literal address must be BLE random-static, such as <code>C2:11:22:33:44:55</code>.
|
||
<code>random</code> generates and saves one address; <code>random-every-boot</code> generates a new
|
||
one on each startup (<code>random everyboot</code> is also accepted).
|
||
<code>random-after-connect</code> keeps its address across unused power cycles, then
|
||
rotates on the next boot after an authenticated connection. <code>default</code> or
|
||
<code>clear</code> restores the factory address without changing the stealth flag.
|
||
Reboot, forget the old phone entry, and pair again after an address change.
|
||
<code>get ble.mac</code> and <code>set ble.mac</code> are short aliases.</p>
|
||
<p>The independent <code>bluetooth.stealth</code> flag defaults off and preserves the chosen
|
||
address policy. With it on, the node is discoverable until its first
|
||
authenticated pairing, then accepts only that bonded peer. Custom and saved
|
||
random addresses keep the bond across boots; rotating modes reopen pairing
|
||
when the address rotates, leaving stealth enabled. It still transmits the
|
||
directed or allowlisted packets BLE requires for reconnection. Repeating <code>on</code>
|
||
keeps the bond. Send <code>off</code>, then <code>on</code>, then reboot to reopen pairing manually.
|
||
<code>ble.stealth</code> is the short alias. Flag changes require reboot.</p>
|
||
<pre><code>set lat {latitude}
|
||
</code></pre>
|
||
<p>Sets your advertisement map latitude. (decimal degrees)</p>
|
||
<pre><code>set lon {longitude}
|
||
</code></pre>
|
||
<p>Sets your advertisement map longitude. (decimal degrees)</p>
|
||
<pre><code>set af {air-time-factor}
|
||
</code></pre>
|
||
<p>Sets the transmit air-time-factor. Deprecated - use <code>set dutycycle</code> instead.</p>
|
||
<pre><code>get powersaving
|
||
set powersaving {on|off}
|
||
</code></pre>
|
||
<p>Shows or changes Companion device power saving. On ESP32 this controls CPU and
|
||
GPS idle behavior; it does not change LoRa RXPS or WiFi modem sleep.</p>
|
||
<pre><code>get usb.logging
|
||
set usb.logging {on|off} [reboot]
|
||
get usb.debug
|
||
set usb.debug {on|off}
|
||
</code></pre>
|
||
<p>Shows or changes persistent USB packet output and a separate verbose-debug
|
||
preference in an ordinary USB-loggable Companion or Full Companion.
|
||
<code>usb.logging</code> is the master; debug output requires the master and <code>usb.debug</code>
|
||
to be on. RAW and RX/TX packet records need only the master. Use
|
||
<code>set usb.debug off</code> with packet logging for USB-to-MQTT capture.
|
||
<code>get usb.debug</code> reports saved intent, even while the master is off. Disabling
|
||
the master does not clear it. Debug defaults off for fresh installs and older
|
||
preferences without the new field; it still needs compiled debug support.
|
||
Changing debug verbosity takes effect without a reboot.</p>
|
||
<p>Current source also accepts <code>get usb.watchdog</code> and saved
|
||
<code>set usb.watchdog off|on|auto</code>. Auto is the default and requires 14 continuous
|
||
healthy logging-client days before saving On. Exact USB stats polls, not merely
|
||
USB attachment, renew the client lease. See
|
||
<a href="../usb_logging_watchdog/">USB logging watchdog</a> for USB-only repair, increasing
|
||
physical-fault reboot intervals, status fields, and ownership/storage safeguards.</p>
|
||
<p>USB Companion and Full start off on a fresh install with the logging master
|
||
disabled to protect framed traffic.
|
||
nRF52 Full changes its interface count after a reboot and keeps Companion on
|
||
interface <code>00</code>. Every ESP32 Full Companion has one TTY and needs no reboot:
|
||
logging uses the active text terminal, disables framed Binary Companion on
|
||
USB, and continues accepting <code>set usb.logging off</code>. Turning logging off leaves
|
||
the port in the normal ASCII terminal, matching fresh firmware. Send
|
||
<code>+++MESHCORE-TERM-STOP</code>, or let a Companion app send a valid framed probe, to
|
||
switch it to Binary Companion afterward.
|
||
Full Companion emits complete received frames as uppercase ASCII <code>RAW:</code> hex
|
||
followed by decoded RX summaries where possible; TX summaries are separate.
|
||
These are best-effort records, not atomic pairs or a durable capture.
|
||
nRF52 interface <code>02</code> is logging-only: send CLI/control commands on interface
|
||
<code>00</code>. A single-port bridge that queries identity on its logging port needs
|
||
separate control-port support before it can use that dedicated log endpoint.</p>
|
||
<pre><code>reboot
|
||
</code></pre>
|
||
<p>Sends an acknowledgement, then reboots the Companion one second later. The
|
||
delay gives either the USB terminal or the Full Companion TCP terminal on port
|
||
5002 time to deliver the reply before its transport disappears.</p>
|
||
<pre><code>get radio.rxps
|
||
get radio.rxps.config
|
||
set radio.rxps {off|on|level 1-10 [preamble 16|32]|rx_us sleep_us}
|
||
</code></pre>
|
||
<p>Shows or changes LoRa receive duty cycling on supported radios.
|
||
<code>get radio.rxps.config</code> also reports the saved level and preamble assumption so
|
||
automation can restore a level-based preference exactly. Fresh Cascade
|
||
builds select level 8 with a 16-symbol timing assumption. The <code>preamble</code>
|
||
argument controls the RXPS calculation; it does not change the physical wire
|
||
preamble. A configured level is the minimum: when faster SF/BW settings shorten
|
||
the timing window, firmware raises the effective level only as far as needed,
|
||
up to level 10. Starting with v1.17.1.5, SF5-SF8 packets normally use a
|
||
32-symbol physical preamble. Firmware selects 64, then 128, only when every
|
||
shorter choice fails to enable RXPS at any level. The configured values remain
|
||
unchanged, so every radio change recalculates from the saved minimum. A slower
|
||
tuple returns to that exact level and the shortest viable wire preamble.</p>
|
||
<p>If neither adjustment leaves enough time for the radio to wake, RXPS stays
|
||
logically enabled but receives continuously instead of rejecting the radio
|
||
setting or starting an invalid duty cycle. The Companion terminal's
|
||
<code>get radio.rxps</code> reports this as <code>mode=continuous-fast</code> and reports any
|
||
<code>effective-level</code> or <code>effective-preamble</code> adjustment;
|
||
<code>get radio.rxps.config</code> reports the persisted preference. A later compatible
|
||
SF/BW change resumes duty cycling without another RXPS command.</p>
|
||
<p>For the SX1262+TCXO boards tested here, these fast combinations are the useful
|
||
RXPS boundary profiles (CR does not change the RXPS preamble timing):</p>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th style="text-align: right;">SF</th>
|
||
<th style="text-align: right;">BW (kHz)</th>
|
||
<th style="text-align: right;">Wire preamble</th>
|
||
<th style="text-align: right;">Effective preamble</th>
|
||
<th style="text-align: right;">Minimum effective level</th>
|
||
<th style="text-align: right;">RX / sleep</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td style="text-align: right;">7</td>
|
||
<td style="text-align: right;">500</td>
|
||
<td style="text-align: right;">32</td>
|
||
<td style="text-align: right;">32</td>
|
||
<td style="text-align: right;">7</td>
|
||
<td style="text-align: right;">2731 / 6101 us</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align: right;">6</td>
|
||
<td style="text-align: right;">250</td>
|
||
<td style="text-align: right;">32</td>
|
||
<td style="text-align: right;">32</td>
|
||
<td style="text-align: right;">7</td>
|
||
<td style="text-align: right;">2731 / 6101 us</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align: right;">5</td>
|
||
<td style="text-align: right;">125</td>
|
||
<td style="text-align: right;">32</td>
|
||
<td style="text-align: right;">32</td>
|
||
<td style="text-align: right;">7</td>
|
||
<td style="text-align: right;">2731 / 6101 us</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align: right;">5</td>
|
||
<td style="text-align: right;">250</td>
|
||
<td style="text-align: right;">64</td>
|
||
<td style="text-align: right;">64</td>
|
||
<td style="text-align: right;">8</td>
|
||
<td style="text-align: right;">1252 / 6424 us</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align: right;">6</td>
|
||
<td style="text-align: right;">500</td>
|
||
<td style="text-align: right;">64</td>
|
||
<td style="text-align: right;">64</td>
|
||
<td style="text-align: right;">8</td>
|
||
<td style="text-align: right;">1252 / 6424 us</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align: right;">5</td>
|
||
<td style="text-align: right;">500</td>
|
||
<td style="text-align: right;">128</td>
|
||
<td style="text-align: right;">128</td>
|
||
<td style="text-align: right;">8</td>
|
||
<td style="text-align: right;">626 / 6398 us</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align: right;">5</td>
|
||
<td style="text-align: right;">62.5</td>
|
||
<td style="text-align: right;">32</td>
|
||
<td style="text-align: right;">16</td>
|
||
<td style="text-align: right;">10</td>
|
||
<td style="text-align: right;">4096 / 6272 us</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p>The 64- and 128-symbol rows require the v1.17.1.5-or-newer adaptive-preamble
|
||
contract on every sender that may reach the RXPS receiver. Cascade/USA builds
|
||
on a Heltec V4 and WisMesh Tag (RAK4631 target) passed 16/16 packets in each
|
||
direction at both SF5/BW250/64 and SF5/BW500/128, CR5, 909.950 MHz. An older
|
||
sender makes a long-preamble timing window unsafe, so use continuous RX for a
|
||
mixed deployment. Retry packets use the same physical preamble as other
|
||
packets.</p>
|
||
<pre><code>get wifi.powersave
|
||
set wifi.powersave {none|min|max}
|
||
</code></pre>
|
||
<p>Shows or changes the persisted WiFi modem-sleep policy on ESP32 WiFi Companion
|
||
builds. Full Companion requires at least <code>min</code> while BLE is present and rejects
|
||
<code>none</code>. The WebConfig WiFi card and the normal binary Companion protocol expose
|
||
the same setting; binary clients do not need the terminal-start token. On an
|
||
ESP32 Full Companion whose primary mesh radio is ESP-NOW, <code>max</code> is also
|
||
unavailable because maximum modem sleep can make the
|
||
station miss ESP-NOW broadcasts, which the access point does not buffer. A
|
||
previously saved <code>max</code> value is capped to and reported as <code>min</code>, and a new <code>max</code>
|
||
selection is rejected. Such a WiFi/BLE/primary-ESP-NOW build therefore uses
|
||
<code>min</code>.</p>
|
||
<pre><code>get espnow.channel
|
||
set espnow.channel <1-13>
|
||
</code></pre>
|
||
<p>On builds whose primary mesh radio is ESP-NOW, this shows or saves the primary
|
||
radio's channel. The default is channel 1. Use only a channel permitted in
|
||
your region, and restart or power-cycle the node after changing it. Every
|
||
primary ESP-NOW peer must use the same channel.</p>
|
||
<p>On Full Companion, the setup AP and infrastructure-WiFi station also share
|
||
that channel, so the router's 2.4 GHz radio must remain fixed to it. Power
|
||
saving does not permit separate channels. <code>wifi.powersave max</code> is unavailable
|
||
on these ESP32 Full builds and <code>min</code> is the coexistence setting. This channel
|
||
setting is also distinct from <code>bridge.channel</code>, which controls the optional
|
||
ESP-NOW bridge transport. An updated LoRa-primary ESP-NOW bridge can join this
|
||
raw primary transport by selecting the same channel and running
|
||
<code>set bridge.format raw</code>; its default <code>wrapped</code> format remains the
|
||
bridge-to-bridge protocol.</p>
|
||
<pre><code>get radio.rxgain
|
||
set radio.rxgain {on|off}
|
||
get radio.fem.rxgain
|
||
set radio.fem.rxgain {on|off}
|
||
get radio.fem.txgain
|
||
set radio.fem.txgain {on|off}
|
||
</code></pre>
|
||
<p><code>radio.rxgain</code> changes the radio chip's boosted receive-gain mode. The FEM
|
||
settings control the external receive-path LNA or transmit-path gain on
|
||
supported boards. Changes are applied immediately and saved across reboots;
|
||
changing either receive-gain path also recalibrates the radio noise floor.
|
||
Boards without the respective control report it as unsupported.</p>
|
||
<pre><code>time {epoch-secs}
|
||
</code></pre>
|
||
<p>Set the device clock using UNIX epoch seconds. Example: time 1738242833</p>
|
||
<pre><code>advert
|
||
</code></pre>
|
||
<p>Sends an advertisement packet</p>
|
||
<pre><code>clock
|
||
</code></pre>
|
||
<p>Displays current time per device's clock.</p>
|
||
<pre><code>ver
|
||
</code></pre>
|
||
<p>Shows the device version and firmware build date.</p>
|
||
<pre><code>card
|
||
</code></pre>
|
||
<p>Displays <em>your</em> 'business card', for others to manually <em>import</em></p>
|
||
<pre><code>import {card}
|
||
</code></pre>
|
||
<p>Imports the given card to your contacts.</p>
|
||
<pre><code>list {n}
|
||
</code></pre>
|
||
<p>Lists favorite contacts first, then all remaining contacts. Each group is
|
||
ordered by the most recent advertisement. Optional <code>{n}</code> limits the displayed
|
||
contacts after applying that order.</p>
|
||
<pre><code>show
|
||
show adverts {on|off}
|
||
show channels {on|off}
|
||
show emergency {on|off}
|
||
</code></pre>
|
||
<p>Controls unsolicited receive output in the USB terminal. Plain <code>show</code> reports
|
||
the current settings, and <code>show {category}</code> reports one category. At boot,
|
||
advertisements and ordinary channel messages are hidden while <code>#emergency</code>
|
||
messages are shown. The three controls are independent, so <code>show channels on</code>
|
||
does not override <code>show emergency off</code>.</p>
|
||
<p>These filters affect terminal printing only. Messages still enter the offline
|
||
queue and are delivered through the binary Companion protocol. Changes remain
|
||
active when switching between terminal and binary mode and reset to their
|
||
defaults after reboot.</p>
|
||
<pre><code>to
|
||
</code></pre>
|
||
<p>Shows the name of current recipient contact. (for subsequent 'send' commands)</p>
|
||
<pre><code>to {name-prefix}
|
||
</code></pre>
|
||
<p>Sets the recipient to the <em>first</em> matching contact (in 'list') by the name prefix. (ie. you don't have to type whole name)</p>
|
||
<pre><code>path
|
||
</code></pre>
|
||
<p>Shows the saved outgoing path for the current <code>to</code> recipient. This command and
|
||
all path changes require a recipient to be selected first.</p>
|
||
<pre><code>path direct
|
||
path clear
|
||
path {hop-hash...}
|
||
</code></pre>
|
||
<p>Sets the outgoing path used by subsequent <code>login</code>, <code>send</code>, and <code>cmd</code> commands.
|
||
<code>direct</code> selects a zero-hop route. <code>clear</code> forgets the saved route, causing the
|
||
next operation to use flood routing and allowing normal path discovery to
|
||
learn a replacement.</p>
|
||
<p>Explicit paths use spaces, commas, or a mixture of both between hop hashes.
|
||
Each hop must contain exactly 2, 4, or 6 hexadecimal digits, and every hop in
|
||
one path must use the same width. Whitespace and hexadecimal letter case do
|
||
not matter. The setting is saved with the selected contact.</p>
|
||
<p>For example:</p>
|
||
<pre><code class="language-text">to Hilltop Repeater
|
||
path A1B2C3,D4E5F6
|
||
path 7773D0 7E7662
|
||
path
|
||
login my-admin-password
|
||
</code></pre>
|
||
<pre><code>login {admin-password}
|
||
</code></pre>
|
||
<p>Sends a remote login request to the current recipient. Select a repeater,
|
||
room, or other remotely managed node with <code>to {name-prefix}</code> first. The
|
||
password is masked with <code>*</code> while it is entered and must be 1-15 UTF-8 bytes;
|
||
longer passwords are rejected instead of truncated. Login uses the route shown
|
||
by <code>path</code>: a known or explicitly set route is direct, while an unknown route is
|
||
flooded.</p>
|
||
<p>Login results arrive asynchronously. A successful modern response displays
|
||
the remote ACL permissions byte and server protocol level. A wrong password,
|
||
an unreachable target, or a server that does not support remote login normally
|
||
produces a timeout because those nodes do not send a rejection packet.</p>
|
||
<pre><code>cmd {remote-command}
|
||
</code></pre>
|
||
<p>Sends CLI data to the current recipient. Wait for the login result before
|
||
sending the first command. The remote node applies its own ACL permissions,
|
||
and any reply appears asynchronously as <code>CLI -> from {name}</code>. The response
|
||
window is 300% of the route estimate. A routed send is displayed as
|
||
<code>DIRECT via path {hop,...}</code> with the exact prefixes copied into the packet; in
|
||
MeshCore, <code>DIRECT</code> is the route class for an explicit path, not a synonym for
|
||
zero hops. A matched reply also shows its local round-trip time, measured from
|
||
queueing the command through receiving the result. This includes both radio
|
||
directions and remote execution; it is not execution-only CPU time. Only one
|
||
terminal <code>cmd</code> can be pending at a time.</p>
|
||
<p>For example:</p>
|
||
<pre><code class="language-text">to Hilltop Repeater
|
||
login my-admin-password
|
||
LOGIN -> Hilltop Repeater accepted (ACL permissions 0x03, server v13)
|
||
cmd ver
|
||
cmd get radio
|
||
</code></pre>
|
||
<p>Repeater guest logins default to off. An admin can use <code>cmd set guest on</code> to
|
||
enable them or <code>cmd set guest off</code> to disable them and remove current guest
|
||
sessions immediately. These settings are saved and need no reboot. When enabled,
|
||
the configured <code>guest.password</code> applies; its blank default permits passwordless
|
||
guest access. Admin and assigned ACL access are unaffected. Room-server login
|
||
settings are unchanged.</p>
|
||
<p>Use <code>cmd get guests</code> or <code>cmd get guests 2</code> from an admin session to inspect the
|
||
repeater's guest entries. Each page shows one full public key and its last
|
||
activity time in UTC epoch seconds. Guests are held in RAM, so this is a list of
|
||
accepted sessions rather than proof that a device is currently reachable. They
|
||
are cleared by a reboot or <code>set guest off</code> and remain separate from <code>get acl</code>.</p>
|
||
<p>Use <code>cmd get logins</code> or <code>cmd get logins 2</code> from an admin session to inspect recent
|
||
login attempts. The repeater retains up to 16 distinct public keys in RAM, newest
|
||
attempt first, with up to two rows per page. Each row shows a 12-character hex
|
||
key prefix, the latest UTC epoch time, result, and attempt count. Repeated
|
||
attempts update the same full key's row; different keys sharing a displayed
|
||
prefix remain separate records.</p>
|
||
<p>Results distinguish accepted logins, wrong passwords, disabled guests,
|
||
replay/state rejection, and unavailable ACL capacity. Only authenticated,
|
||
complete login requests are recorded; anonymous owner, region, or clock requests
|
||
are excluded. Passwords and shared secrets are never stored. This bounded
|
||
history clears on reboot, survives <code>set guest off</code>, and does not show who is
|
||
currently online. A zero timestamp means the node's clock was unset.</p>
|
||
<p>The exact commands and permissions depend on the target firmware. <code>cmd</code> does
|
||
not run a command on the local Companion; it sends the text over LoRa to the
|
||
selected node.</p>
|
||
<p>Incoming direct-route messages are labeled <code>ROUTED</code>, not <code>DIRECT</code>. Forwarders
|
||
consume direct-route prefixes as the packet travels, so the destination cannot
|
||
recover the reply's actual hop history from the received packet. Use <code>trace</code>
|
||
when the return route itself must be verified.</p>
|
||
<pre><code>send {text}
|
||
</code></pre>
|
||
<p>Sends the text message (as DM) to current recipient.</p>
|
||
<pre><code>trace
|
||
</code></pre>
|
||
<p>Traces the saved round-trip route to the current recipient and displays the
|
||
SNR at each hop. Select the recipient first with <code>to {name-prefix}</code>.</p>
|
||
<pre><code>trace {name-prefix}
|
||
</code></pre>
|
||
<p>Traces a recipient directly without changing the current <code>to</code> selection. A
|
||
trace requires a known direct path; use normal messaging or path discovery
|
||
first if the terminal reports that no valid path is available. Only one
|
||
terminal trace can be pending at a time, and a missing response is reported as
|
||
a timeout.</p>
|
||
<p>For example:</p>
|
||
<pre><code class="language-text">to Hilltop Repeater
|
||
trace
|
||
trace Downtown
|
||
</code></pre>
|
||
<p>The displayed route uses one- or two-byte node hashes and per-hop SNR values.
|
||
Saved three-byte paths are traced with two-byte prefixes because the trace
|
||
packet format has no three-byte hash-size mode.</p>
|
||
<p>To trace an explicit route instead of a saved contact path, provide the prefix
|
||
size followed by the complete ordered route:</p>
|
||
<pre><code class="language-text">trace path 1 12 34 56 34 12
|
||
trace path 2 1234,ABCD,5678,ABCD,1234
|
||
trace path 4 12345678, ABCDEF01 89ABCDEF, ABCDEF01,12345678
|
||
</code></pre>
|
||
<p>Prefix separators may be spaces, commas, or any mixture of them. Each prefix
|
||
must contain exactly 2, 4, or 8 hexadecimal digits for a 1-, 2-, or 4-byte
|
||
trace respectively. Three-byte traces are not supported.</p>
|
||
<p>The prefixes are used exactly in the order entered. To receive the trace
|
||
result, enter the complete outward route followed by its return route, as in
|
||
the mirrored examples above. A route that does not return to this node will
|
||
eventually report a timeout.</p>
|
||
<pre><code>reset path
|
||
</code></pre>
|
||
<p>Resets the path to current recipient, for new path discovery. This is retained
|
||
as an alias for <code>path clear</code>.</p>
|
||
<pre><code>public {text}
|
||
</code></pre>
|
||
<p>Sends the text message to the built-in <code>Public</code> group channel.</p>
|
||
<pre><code>channels
|
||
</code></pre>
|
||
<p>Lists the configured channel slots and names without exposing their secrets.</p>
|
||
<pre><code>channel {name-or-slot} {text}
|
||
</code></pre>
|
||
<p>Sends a message to any configured channel by its exact name or numeric slot.
|
||
Use the slot shown by <code>channels</code> when a channel name contains spaces.</p>
|
||
<p>For example:</p>
|
||
<pre><code class="language-text">channels
|
||
channel #rgdata Hello from Eugene
|
||
channel 2 Another message
|
||
show channels on
|
||
</code></pre>
|
||
<p>Messages are UTF-8. Emoji use multiple bytes toward the available message
|
||
length, which also includes the sender-name prefix added over the air.</p>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
</article>
|
||
</div>
|
||
|
||
|
||
<script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script>
|
||
</div>
|
||
|
||
</main>
|
||
|
||
<footer class="md-footer">
|
||
|
||
<div class="md-footer-meta md-typeset">
|
||
<div class="md-footer-meta__inner md-grid">
|
||
<div class="md-copyright">
|
||
|
||
|
||
Made with
|
||
<a href="https://squidfunk.github.io/mkdocs-material/" target="_blank" rel="noopener">
|
||
Material for MkDocs
|
||
</a>
|
||
|
||
</div>
|
||
|
||
</div>
|
||
</div>
|
||
</footer>
|
||
|
||
</div>
|
||
<div class="md-dialog" data-md-component="dialog">
|
||
<div class="md-dialog__inner md-typeset"></div>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
<script id="__config" type="application/json">{"annotate": null, "base": "..", "features": ["content.action.edit", "content.code.copy", "search.highlight", "search.suggest"], "search": "../assets/javascripts/workers/search.a7633da7.min.js", "tags": null, "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": null}</script>
|
||
|
||
|
||
<script src="../assets/javascripts/bundle.c21346df.min.js"></script>
|
||
|
||
<script src="../_javascript/release_features.js?v=20261024-1"></script>
|
||
|
||
<script src="../_javascript/hosted_doc_links.js?v=20261007-1"></script>
|
||
|
||
<script src="../_javascript/notification_builder.js?v=20261006-channel9"></script>
|
||
|
||
<script src="https://unpkg.com/leaflet@1.9.4/dist/leaflet.js"></script>
|
||
|
||
<script src="../_javascript/firmware_picker.js?v=20261024-included-bootloader"></script>
|
||
|
||
<script src="../_javascript/telemetry_decoder.js?v=20261022-noise-history"></script>
|
||
|
||
<script src="../_javascript/management_decoder.js"></script>
|
||
|
||
<script src="../_javascript/filter_tool.js?v=20261002-hashbytes-2plus"></script>
|
||
|
||
<script src="../_javascript/preset_test.js?v=20260923-2"></script>
|
||
|
||
<script src="../_javascript/esp32_partition_catalog.js?v=20261001-1"></script>
|
||
|
||
|
||
</body>
|
||
</html> |