-
Notifications
You must be signed in to change notification settings - Fork 0
Configuring Channels
Channels are how you organize messaging on your Crow node. Each channel can be configured to route messages to AREDN, Meshtastic, MeshCore, APRS, or any combination.
The fastest way to create and configure a channel is using the /join slash command. See Slash Commands — Join / Leave for full details.
Create a hash-named channel (auto-generated key):
/join #TacNet
Create an AREDN-only unencrypted channel:
/join %PublicChat
Create an APRS group and channel together:
/join #TacNet KN6PLV KJ6DZB-4 radio check
This creates the channel, an APRS group with those callsigns, and sends an initial message.
Create an APRS group on a specific backend:
/join #TacNet backend=direwolf1 KN6PLV KJ6DZB-4 radio check
For additional join command options and syntax, see Commands — Join / Leave Commands.
The initial installation of Crow comes with three default channels accessible via the cog icon at the top-right of the channel box:
These channels provide access to:
- AREDN og== — Primary AREDN mesh channel (unencrypted)
- Meshtastic — Meshtastic device bridge channel
- MeshCore — MeshCore device bridge channel
Note: Messages on the primary AREDN channel are never automatically shared on Meshtastic or MeshCore networks unless you explicitly bind those bridges to the channel.
To add a new channel via the UI:
- Press the plus icon on the right of any current channel
- A new channel entry appears below it:
- Enter a Name and an ID or Key
- Configure additional options (backends, images, storage, etc.)
- The channel is saved immediately
A channel name and key together uniquely identify the channel. The key is also used to cryptographically secure messages when transmitted across Meshtastic or MeshCore networks. AREDN traffic is not encrypted.
Name: Human-readable channel identifier (e.g., "TacNet", "Alerts")
Key: Cryptographic identifier. You can:
- Paste a key if you have one from another party (supports Meshtastic and MeshCore formats)
- Generate a key using the new key dropdown:
Key Types:
| Key Type | Use Case | Networks |
|---|---|---|
| 1 byte & 256 bit | Explicit key pairs | Meshtastic |
| 128 bit | Maximum flexibility | Meshtastic + MeshCore |
| Meshtastic modem presets | Match Meshtastic default channels (e.g., MediumFast) | Meshtastic |
| MeshCore | Use MeshCore's standard primary channel | MeshCore |
Hash channel (#name) |
Auto-generated from channel name (MeshCore feature) | All networks |
Open key (og==) |
AREDN-only unencrypted channel | AREDN only |
If you start the channel name with # (hash), the key is automatically generated from the name and cannot be changed. This is a MeshCore convention that allows users to quickly create shared channels without exchanging complex keys.
Example: #TacNet will always generate the same key on any Crow node or MeshCore device.
Hash channels work across Crow, Meshtastic, and MeshCore.
Each channel can be bound to one or more bridges/backends to route messages to other networks. Backends are only available if they are enabled and configured on your node.
| Backend | Type | Prerequisite |
|---|---|---|
| Meshtastic | Device bridge | Meshtastic device configured on LAN. See Meshtastic. |
| MeshCore | Device bridge | MeshCore serial bridge configured. See MeshCore. |
| APRS | Radio gateway | APRS backend configured (APRS-IS, Dire Wolf, Xastir). See APRS. |
Via UI: When editing a channel, toggle checkboxes for each backend you want to bind:
- ☑ Meshtastic — Forward messages to Meshtastic device
- ☑ MeshCore — Forward messages to MeshCore device
- ☑ APRS — Forward messages to APRS network
Via Configuration File:
Edit crow.conf.override and add backend flags to channel entries:
{
"channels": [
{
"namekey": "TacNet AQ==",
"meshtastic": true,
"meshcore": true,
"aprs": true
}
]
}See Configuration — Bridge Configurations for full config details.
If you have multiple APRS backends configured (e.g., APRS-IS and Dire Wolf), you can bind a specific backend to a channel. Use the slash command:
/join #TacNet backend=direwolf1 KN6PLV KJ6DZB-4 message
Or configure in crow.conf.override:
{
"channels": [
{
"namekey": "TacNet AQ==",
"aprs": {
"backend_name": "direwolf1"
}
}
]
}See APRS for backend configuration and naming.
To change a channel's settings:
-
Press the cog icon to open the channels list
-
Click on the channel row to edit inline:
- Name: Click the name field to edit
- Key: Click the key field (cannot edit hash channels)
- Max Messages: Adjust storage limit
- Images: Toggle image support
- Backends: Toggle Meshtastic, MeshCore, APRS checkboxes
- Winlink: Toggle form support
-
Changes are saved immediately
For advanced options (e.g., specific APRS backend selection), edit crow.conf.override directly. See Configuration for all options.
AREDN devices have limited storage. Set the maximum number of messages this channel should retain. Older messages are automatically pruned when the limit is exceeded.
AREDN is high-bandwidth, so image sharing is supported. When enabled:
- Send/receive images on this channel
- Meshtastic/MeshCore: Placeholder text is sent (those networks don't support large image sizes)
- Storage: Images are stored in RAM and deleted if space is needed
- Size: Images are automatically reduced to ~1 MB before posting
Winlink forms can be created and shared on channels that have this enabled. You can:
- Create Winlink documents using installed form templates
- Send/receive Winlink forms with other nodes
- Store and archive forms in channel history
Enable this option only on channels where you want form support.
Any channel except the primary AREDN channel can be removed by:
- Pressing the cog icon to open the channels list
- Pressing the minus button on the right of the channel row
The channel and all its messages are deleted.
Common channel management slash commands:
| Command | Purpose |
|---|---|
/join #name |
Create/join a channel quickly |
/channels |
List all available channels |
/channels join <name> [key] |
Join by name |
/channels leave <name> |
Leave a channel |
/leave #name |
Leave and cleanup APRS group |
/groups |
List APRS groups |
/backends |
List APRS backends |
See Slash Commands for complete command reference.
- Configuration Reference — Advanced config options for channels and backends
-
Commands — Full slash command reference including
/joinand/channels - APRS — APRS backend setup and multi-backend configuration
- Meshtastic — Hardware and bridge setup for Meshtastic devices
- MeshCore — Hardware and bridge setup for MeshCore devices
- Winlink — Winlink form setup and usage
- Home
- Change Log
- Configuration
- Configuring Channels
- Backend Selection and Test Deployment
- Command Reference
- APRS Bridge
- LoRa Gateway Tags
- Meshtastic API Backend
- Memory Use
- Strict Gatekeeper
- Winlink
- USB Storage
APRS.mdBackend-Selection-and-Deployment.mdChange-Log.mdCommand-Reference.mdConfiguration.mdConfiguring-Channels.mdHome.mdLoRa-Gateway-Tags.mdMeshtastic-API.mdMemory-Use.mdStrict-Gatekeeper.mdUSB-Storage.mdWinlink.md_Sidebar.md
- Keep every
.mdwiki page linked here. - Keep
Home.mdand_Sidebar.mdin sync. - When a wiki page is removed, remove it from both the Home page inventory and this sidebar.