Category

Other

Hardware

Rak4631

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.7.15.567b8ea Alpha

Description

Hello

I have my RAK4631 node set as client_mute and using firmware 2.7.15.

I send out a message, replying to another message that comes in in channel 0.

It shows up in the app, so far, so good and unsuspect. Debug log of my sent-out-message:

to: 4294967295 (!ffffffff)
id: 4080155345
want_ack: true
decoded {
  portnum: TEXT_MESSAGE_APP
  payload: "xxxxxxxxx 3 hops. Gr\303\274ess  xxxx"
  reply_id: 3756052286
}
Decoded Payload:
{
xxxxxxxxx 3 hops. Grüess xxxx
}

34 minutes later, I get my own message again in the app, with the same id, this time indicating though that it has been around in the mesh and now returning to me. Coming from me, yes, same message id. Same replay-id.
Now, maybe this is important: the node mentioned as relay_node runs on firmware 2.6.11:

from: 1306336680 (!xxxxxxda8)
to: 4294967295 (!ffffffff)
id: 4080155345
rx_time: 1764358238
rx_snr: 2.75
rx_rssi: -105
hop_start: 5
relay_node: xxxxxxxxxxxch (!xxxxxx697)
transport_mechanism: TRANSPORT_LORA
decoded {
portnum: TEXT_MESSAGE_APP
payload: "xxxxxxxxx 3 hops. Gr\303\274ess xxxx"
reply_id: 3756052286
bitfield: 0
}
Decoded Payload:
{
xxxxxxxxx 3 hops. Grüess xxxx
}

@GUVWAF I remember in FW 2.13, you merged stuff into master that made duplicates disappear.
#8450

Here now in 2.7.15, the behavior happens again. I am unsure if it is related.

@h3lix1 I think you also worked on some duplicate removal stuff in 2.7.12: https://github.com/meshtastic/firmware/pull/8148/files

Is this maybe another case of the master branch not having important changes in it?
Does not look like it, though.
This time, compared to #8449, the bevavior is different.
Back in 2.7.12 and fixed in 2.7.13, it was other people's messages I received twice.
This time in 2.7.15, it is my own sent message I receive coming back at me from the mesh.

Relevant log output