Skip to content

feat: Add Status Message module support#4163

Merged
jamesarich merged 8 commits intomainfrom
feat/status-message
Jan 25, 2026
Merged

feat: Add Status Message module support#4163
jamesarich merged 8 commits intomainfrom
feat/status-message

Conversation

@jamesarich
Copy link
Copy Markdown
Collaborator

@jamesarich jamesarich commented Jan 8, 2026

This commit introduces support for the Status Message module.

  • Adds a StatusMessage module configuration screen.
  • Displays the node status message in the node list and details views.
  • Implements handling for NODE_STATUS_APP packets.
  • Updates the database schema to store the node status.

depends on meshtastic/protobufs#835 and firmware support

@github-actions github-actions Bot added the enhancement New feature or request label Jan 8, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented Jan 8, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (71628ca) to head (8832a57).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #4163   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files          3       3           
  Lines         28      28           
  Branches       8       8           
=====================================
  Misses        28      28           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

This commit introduces support for the Status Message module.

- Adds a `StatusMessage` message type and its corresponding port number (`NODE_STATUS_APP_VALUE`).
- Implements a new settings screen to configure the `StatusMessageConfig`.
- Updates the `Node` data model and database entity to store the `nodeStatus` string.
- Displays the received status message in the node list and node details screens.
- Handles incoming status packets in `MeshDataHandler`.

Signed-off-by: James Rich <2199651+jamesarich@users.noreply.github.com>
This commit corrects the casing for the `statusmessage` property within the module configuration. The property is now accessed as `statusmessage` instead of `statusMessage`, aligning it with the protobuf-generated field name.

Signed-off-by: James Rich <2199651+jamesarich@users.noreply.github.com>
This commit enhances the `MockInterface` to support the handling and generation of node status messages.

- A mock response for `STATUSMESSAGE_CONFIG` requests is now implemented, returning a predefined status message.
- A new `makeNodeStatus()` function has been added to create `FromRadio` packets containing a `StatusMessage`.
- The mock node generation now includes a node status packet, allowing for better testing of status message display and handling in the UI.

Signed-off-by: James Rich <2199651+jamesarich@users.noreply.github.com>
This commit increments the Room database version from 32 to 33 and includes the corresponding exported schema file. This change is in preparation for adding the `node_status` column.

Signed-off-by: James Rich <2199651+jamesarich@users.noreply.github.com>
@jamesarich jamesarich marked this pull request as ready for review January 24, 2026 15:17
@jamesarich jamesarich added this pull request to the merge queue Jan 24, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to a conflict with the base branch Jan 24, 2026
# Conflicts:
#	core/database/schemas/org.meshtastic.core.database.MeshtasticDatabase/33.json
This commit increments the Room database version from 33 to 34 and includes the corresponding schema export file. It also adds an `AutoMigration` entry for the version bump.

Signed-off-by: James Rich <2199651+jamesarich@users.noreply.github.com>
@jamesarich jamesarich enabled auto-merge January 25, 2026 02:44
@jamesarich jamesarich added this pull request to the merge queue Jan 25, 2026
github-merge-queue Bot pushed a commit that referenced this pull request Jan 25, 2026
Signed-off-by: James Rich <2199651+jamesarich@users.noreply.github.com>
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jan 25, 2026
@jamesarich jamesarich added this pull request to the merge queue Jan 25, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jan 25, 2026
Signed-off-by: James Rich <2199651+jamesarich@users.noreply.github.com>
@jamesarich jamesarich enabled auto-merge January 25, 2026 13:56
@jamesarich jamesarich added this pull request to the merge queue Jan 25, 2026
Merged via the queue into main with commit 355d226 Jan 25, 2026
9 checks passed
@jamesarich jamesarich deleted the feat/status-message branch January 25, 2026 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant