[Bug]: messages lost between node and app

[Pitel]

Contact Details

Pitel on Discord

Checklist

• I am able to reproduce the bug with the latest version.

• I have updated to the latest Alpha firmware, and am able to reproduce the bug. Many issues are fixed quickly in alpha before the general beta release.

• I made sure that there are no existing OPEN or CLOSED issues which I could contribute my information to.

• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.

• This issue contains only one bug.

• I have read and understood the Contribution Guidelines.

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

• I actually read this list, and should be taken seriously.

Affected app version

2.7.10 (29319661) google

Affected Android version

Android 16

Affected phone model

Google Pixel 6

Affected node model

Heltec v3

Affected node firmware version

2.7.17 and 18

Steps to reproduce the bug

1. Connect to node
2. Wait for some message to arrive

Actual behavior

New message popup is shown on the node's display, but nothing on the phone.

Expected behavior

Message arrives on the phone.

Screenshots/Screen recordings

No response

Relevant log output

Additional information

I'm using WiFi. It happens at random. :(

[github-actions]

Thank you for your detailed bug report! However, it seems that the reproduction steps could be expanded for clarity. Could you please specify if there are any particular conditions or scenarios under which the messages are lost? Additionally, if there are any specific logs or error messages that can be helpful for troubleshooting, including those would be greatly appreciated.

Thank you!

[Pitel]

It was also reported by 2 other people on Discord. I don't know their exact setup.

[rob-fi]

I was going to reference #3727 but I see it was you that opened that one also. This is probably all the same issue?

Either way, can attest I'm having the same issue. Today I even sent my node a message directly, which was showed as confirmed delivered, then connected to the node via wifi and the usual sequence of it failing as detailed in #3727 (comment) happened and the message was lost.

Heltec WSL v3, v2.7.15. Android app v2.7.10 Google.

[DaneEvans]

This is apparently more an issue on wifi, despite that detail not making it to the bug report.

If so, I think it's firmware, as I'm seeing similar behaviour on a Heltec 3 via the python interface.

[5CORNERS]

For a long time, I have been using Bluetooth to connect to a stationary node on the Heltec V4. Yesterday, I connected via Wi-Fi. Today, I switched to other nodes via Bluetooth, and when I returned to connecting to the V4 via Wi-Fi, all messages in a huge number of chats, including personal messages, were lost — only two empty chats, LongRange and Services, remained.

[ogarcia]

As I say in my comment here the message sync is very weak.

My guess is that right now, when a device connects, messages that are not marked as downloaded are downloaded and marked so that they are not downloaded again. This should happen during the connection itself, and if it fails, it doesn't matter.

I believe that messages should be treated as separate entities and, taking advantage of the fact that each one has its own unique identifier, check which ones are on the device (which we are using to read) and which ones are not, so that in any case those that are not there are downloaded. If this were done, it would even be possible to work with several devices without any problems and it would be infinitely more resistant to failures.

[pypb]

Seeing the same issue with my RAK3312. Firmware 2.7.15, Android app connecting using wifi. My other device on bluetooth does not have this problem.

Going to see if I can debug it this weekend.

Edit: I've noticed that when this happens, which is most of the time, the Android app gets stuck at Modules config (12 / 14) after I click on the device to connect. It stays there until I get tired of waiting and click Disconnect and then connect again. Then it connects quickly, but I get no messages.

[jlariviere1]

I'm experiencing a similar issue, between the node and the phone. I
I have a T-Deck Pro (Firmware: 2.7.19.bb3d6d5), and it is paired with an Android Phone (up to date Brax3). I'm testing sending messages to a Wismesh Tag that is paired to a different device. Tested both direct message, and sending to a private group that both devices are in.
When I use the client / phone paired to the T-Deck Pro to send a message, there is an extreme delay compared to using the T-Deck Pro itself. The test message I sent out from the T-Deck Pro went out & was received almost immediately, there was about a 2 hour delay before the one sent from the phone went out & was received.

[github-actions]

This issue hasn not had any comment or update in the last 30 days. If it is still relevant, please post update comments. If no comments are made, this issue will be closed in 7 days.

[ogarcia]

I don't know what everyone else thinks, but to me, this bot that automatically closes issues just because they don't have any comments seems like the most absurd thing ever. Do the maintainers actually like spam?

[DaneEvans]

I like it far more than issues that never get closed because the reporter was the only one that experienced them, and they never came back.
We release 1-5 versions a week, the chances of bugs getting fixed without being targeted specifically, or a dev not closing a ticket are pretty high. There have been 15 released versions since this was reported, the network stack has been completely changed.

Take issue 3251, did we fix it? did it just disappear?

How much dev time do you want wasted on triage of the backlog?
We're currently at 15 unneeded minutes, but I can turn the bot off and rack it up to 15 hours if you'd like?

You haven't even answered the basic question of is it still happening?

I will say I no longer think that my addition is relevent - it's looking more like that was a brownout, as changing the heltecs power source has resulted in a stable network connection