Skip to content

πŸš€ [Feature Request]: Visual indication on message display to show if message travelled through MQTT serverΒ #1546

@domusonline

Description

@domusonline

OS

iOS

Description

The idea is to implement what already exists in the Android application and is explained in this RFE:

meshtastic/Meshtastic-Android#2028

It would be nice if we could easily check by looking at a message if it was transported through MQTT along the way. I believe the MeshPacket contains a flag (via_mqtt) that signals this, so hopefully it would be easy to obtain and show it

Most users are concerned if they receive or are received through MQTT hops. I believe it's important to be able to identify at the message level if it passed through MQTT.
With this enhancement this could be visually evident (Android opted to show a small cloud in the message "header").

There is one particularity for nodes directly connecting to the MQTT server. The message will not contain the via_mqtt flag if retrieved directly by this node. But the recent protobufs changes for the meshpacket included a transport field showing if the message was retrieved directly from MQTT server (in this case it should be shown as "MQTT message". If the transport protocol was RF/LoRa, then the via_mqtt flag should be checked.

It would be important to have the same functionality in both apps, as the current lack of this feature in iOS generates many confusions (Android user identifies an MQTT transmit, iOS user asks "how can I check that?" etc.).

Thank you

Participation

  • I am willing to pay to sponsor this feature.
  • I am willing to submit a pull request for this feature.

Additional comments

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    StaleMarked stale by the bot, will be closed automatically soonenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions