Status Message support #53

New issue

Open

opened 2026-05-03 19:15:38 +03:00 by skobkin · 1 comment

skobkin commented

2026-05-03 19:15:38 +03:00

Owner

Status Message support

Code Reference

Explanation

Status Message module is a new/experimental Meshtastic module for broadcasting
a short free-form status string for a node. It appears intended to give users a
proper place for “bio/status” text instead of overloading the node long name.

Technical details:

Module config:
- ModuleConfig.statusmessage.node_status
- Type: string
- Meaning: configured node status text to periodically rebroadcast
Mesh payload:
- Protobuf message: StatusMessage
- Field: string status = 1
Port number:
- NODE_STATUS_APP = 36
Firmware behavior:
- If node_status is non-empty, firmware creates a StatusMessage payload.
- The message is broadcast to NODENUM_BROADCAST.
- It is sent on channel 0.
- want_response is false.
- Priority is BACKGROUND.
- Broadcast interval is 12 hours.
- On startup, if a status is already configured, the first send is scheduled
  shortly after boot, currently around 2 minutes.
- Receive-side handling currently appears minimal: incoming StatusMessage
  packets are decoded and logged, but not clearly persisted into NodeDB by
  the module itself.
Current support state:
- The module is not yet documented in the public Meshtastic module docs.
- Client support may need to be gated by firmware version, since Android
  release notes mention hiding Status Message config until firmware v2.8.0.
- Naming is inconsistent across the code/protobufs:
  - config: statusmessage.node_status
  - payload: StatusMessage
  - portnum: NODE_STATUS_APP
  - module class: StatusMessageModule

Expected client support:

Expose/edit the local node status string from module config.
Decode packets with portnum NODE_STATUS_APP.
Parse the payload as StatusMessage.
Display the received status string for the sending node if useful.
Be careful not to assume firmware currently stores remote statuses in NodeDB.

# Status Message support ## Code Reference - https://raw.githubusercontent.com/Athar5443/Meshtastic/refs/heads/develop/src/modules/StatusMessageModule.cpp - https://raw.githubusercontent.com/Athar5443/Meshtastic/refs/heads/develop/src/modules/StatusMessageModule.h ## Explanation Status Message module is a new/experimental Meshtastic module for broadcasting a short free-form status string for a node. It appears intended to give users a proper place for “bio/status” text instead of overloading the node long name. Technical details: - Module config: - ModuleConfig.statusmessage.node_status - Type: string - Meaning: configured node status text to periodically rebroadcast - Mesh payload: - Protobuf message: StatusMessage - Field: string status = 1 - Port number: - NODE_STATUS_APP = 36 - Firmware behavior: - If node_status is non-empty, firmware creates a StatusMessage payload. - The message is broadcast to NODENUM_BROADCAST. - It is sent on channel 0. - want_response is false. - Priority is BACKGROUND. - Broadcast interval is 12 hours. - On startup, if a status is already configured, the first send is scheduled shortly after boot, currently around 2 minutes. - Receive-side handling currently appears minimal: incoming StatusMessage packets are decoded and logged, but not clearly persisted into NodeDB by the module itself. - Current support state: - The module is not yet documented in the public Meshtastic module docs. - Client support may need to be gated by firmware version, since Android release notes mention hiding Status Message config until firmware v2.8.0. - Naming is inconsistent across the code/protobufs: - config: statusmessage.node_status - payload: StatusMessage - portnum: NODE_STATUS_APP - module class: StatusMessageModule Expected client support: - Expose/edit the local node status string from module config. - Decode packets with portnum NODE_STATUS_APP. - Parse the payload as StatusMessage. - Display the received status string for the sending node if useful. - Be careful not to assume firmware currently stores remote statuses in NodeDB.

skobkin added the

enhancement

label

2026-05-03 19:15:38 +03:00

skobkin commented

2026-05-03 19:16:19 +03:00

Author

Owner

Should be already implemented in skobkin/meshgo#134

skobkin self-assigned this

2026-05-03 19:16:24 +03:00