{% extends "base.html" %} {% block title %}Radio Settings - MeshCore Bot{% endblock %} {% block content %}

Radio Settings

Total Channels

-

Available Slots

-

Channels with Feeds

-

Empty Channels

-

Radio Parameters
100–1700 MHz
Changing radio parameters affects all nodes on the same frequency.
Node Settings
Response Path Hashing
Hash bytes per hop for outgoing (response) paths — mode 0 is the legacy default; larger hashes avoid relay collisions but need firmware 1.14+ mesh-wide.
Default Region Scope
The radio's own default region, stored in firmware and used for any send the bot does not scope itself. Max 30 ASCII characters including the #, which is added if you omit it. Blank clears it, and the radio then floods unscoped. Once the bot sends a scoped message it leaves the radio in forced-unscoped mode, so this default stops applying until the bot scopes another send. If the bot should post under a region, set it in Region Scopes below rather than relying on this.
Identity & Adverts
{% if device_name_managed %} Managed by [Bot] bot_name in config.ini — reapplied at startup. {% else %} Advertised name (max 32 bytes). {% endif %}

Mesh Behavior
New-contact handling is managed by [Bot] auto_manage_contacts in config.ini. Extra ACKs improve delivery at the cost of airtime. Telemetry permissions control who may request each reading type.

Advanced Tuning
Write-only: current values cannot be read back from the device. Both fields are required and affect relay timing/duty-cycle behavior.
Region Scopes

A region code confines a channel message to repeaters holding that region's key, instead of flooding the whole mesh. These are bot settings in config.ini, not device settings, so they are not read from or written to the radio — the radio's own Default Region Scope is above, and only covers sends the bot does not scope itself. See the Region Warnings page for how much unscoped traffic this mesh actually carries.

Which scopes the bot replies to
Comma-separated. The leading # is added if you omit it.

Default outgoing scope
Used for sends that have no scope of their own — scheduled messages, feeds, webhooks — and for a reply whose incoming scope could not be matched. It never overrides a mirrored reply scope.
Channel Management
Index Name Type Feed Count Status Actions
Loading...
{% endblock %} {% block extra_js %} {% endblock %}