[Bug]: Message Timestamp

[Greg-C10]

Category

Other

Hardware

Heltec V3

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

• Meshtastic UI aka MUI colorTFT
• InkHUD ePaper
• OLED slide UI on any display

Firmware Version

2.5.2

Description

I use an arduino like device to send a text message through my mesh device eventually getting to an mqtt server. An example of the message is below. I am having an issue trying to find documentation around the fields in the message and whether each field is from the original entry point (mesh device) into the mesh network or if some of the fields are being updated by each node receiving the message. Does the last node before mqtt overwrite previous values? The fields I am wondering about are from, sender, timestamp.

Additionally, how is timestamp maintained on the mesh device? Does it come from gps, wifi connection, other mesh nodes? If so, how frequently is it updated on the device?

{'channel': 1, 'from': 1128041132, 'hop_start': 7, 'hops_away': 0, 'id': 1686054518, 'payload': {'text': 'This is my test message'}, 'sender': '!433c8aac', 'timestamp': 1749248883, 'to': 4294967295, 'type': 'text'}

Relevant log output

[garthvh]

It is not sent over the air, it is recorded by the receiving device. Time comes from a gps, ntp or the mesh.

[Greg-C10]

Garth are you saying that the original timestamp is not sent with the message from Node A to Node B to Node C then to MQTT?