Meshtastic

What this portal is for

Mesh radio endpoint

Behavior in the current codebase

• Connects through the local Tater Meshtastic Bridge instead of requiring radio hardware inside the Tater process.
• Supports direct messages, selected mesh channels, mention-only or broader response policies, and per-node conversation sessions.
• Splits longer replies into compact numbered radio messages with configurable length and chunk limits.
• Rejects stale bridge backlog, remembers processed messages, and can resume either from now or from the last stored event.
• Uses the same current-speaker identity boundary and admin gating as Tater's other shared chat portals.

Direct portal support

45 current Verbas advertise direct support for this portal.

Configuration schema

• Allow Broadcast Replies select

  If true, channel traffic can receive channel replies.

  Key: allow_broadcasts Default: true Options: true, false
• Allow Direct Messages select

  If true, direct mesh messages can trigger replies.

  Key: allow_direct_messages Default: true Options: true, false
• Allowed Channels string

  Choose one or more mesh channels that Tater is allowed to answer on, including channel 0 if you want to allow it.

  Key: allowed_channels
• API Token password

  Optional bearer token expected by the bridge.

  Key: api_token
• Bridge URL string

  Base URL for the local Tater Meshtastic Bridge service.

  Key: bridge_url Default: http://127.0.0.1:8433
• Enable Chunking select

  Split long replies into numbered multi-part messages.

  Key: enable_chunking Default: true Options: true, false
• Max Chunks number

  Maximum number of numbered parts to send for one reply.

  Key: max_chunks Default: 3
• Max Message Age (sec) number

  Messages older than this are treated as backlog and will not trigger replies. Set 0 to disable.

  Key: max_message_age_sec Default: 300
• Max Outbound Length number

  Soft character limit for each outbound radio message chunk.

  Key: max_outbound_length Default: 160
• Poll Interval (sec) number

  How often to poll the bridge for new mesh messages.

  Key: poll_interval_sec Default: 3.0
• HTTP Timeout (sec) number

  Timeout for bridge API requests.

  Key: request_timeout_sec Default: 15.0
• Response Policy select

  When the portal should answer channel traffic.

  Key: response_policy Default: mention_only Options: mention_only, direct_only, all_messages
• Resume Mode select

  Choose whether the portal ignores existing bridge backlog on startup.

  Key: resume_mode Default: from_now Options: from_now, from_last_seen
• Session Mode select

  Choose whether memory is tracked per node or per node+channel.

  Key: session_mode Default: node_channel Options: node, node_channel
• Session TTL (sec) number

  How long to keep mesh chat history alive in Redis.

  Key: session_ttl_seconds Default: 21600
• Trigger Keywords string

  Comma-separated names that count as a mention on shared channels.

  Key: trigger_keywords Default: tater