Title: High Frequency Mesh Communication Observed in Version 2.4.x #4512
Oliver0804
started this conversation in
Troubleshooting
Replies: 8 comments 1 reply
-
|
Are you really doing your comparison against 1.X? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I apologize for the confusion. The correct version should be 2.3.x. I am currently attempting to roll back to a previous version to further investigate the issue. I will provide additional feedback if I gather more information. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@Oliver0804 can you post a |
Beta Was this translation helpful? Give feedback.
0 replies
-
I've made some progress. I encountered the same issue while using version 2.3.x, so I went back to check my iPhone. I found that the problem disappears when the MQTT feature is disabled—there are no excessively frequent TX transmissions. However, when MQTT is enabled, the T-Echo sends messages abnormally, 5 to 7 times in quick succession. App version 2.4.1(1121) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@Oliver0804 did you see #4502 ? perhaps it was that? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I believe this issues pre-dates that bug, and they have neighbors disabled. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Beta Was this translation helpful? Give feedback.
-
|
Actually, I reverted my T-Echo back to version 2.3.15... The two surrounding devices are using version 2.4.2 (specifically, one is a V3 and the other is a T-Beam). Through the SDR, I can see that the T-Echo is quite busy transmitting, but in fact, there is no one actually talking on the channel (which I confirmed by simultaneously monitoring the MQTT server). So, I'm not entirely sure what's going on. I believe that a low-power product shouldn't be engaging in such frequent transmissions. I also noticed that the T-Echo crashes and freezes roughly once a day. I'm now planning to use meshtastic --noproto to capture information at the moment of the crash. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description:
I've noticed a significant increase in mesh communication frequency in devices running version 2.4.x. Specifically, in version 2.4.1, devices like the T-Echo and T-Beam are frequently engaging in RF interactions, even when there are no other users or messages being exchanged. This behavior was not present in version 2.3.x, despite having more devices in the mesh network at that time.
Steps to Reproduce:
Set up two devices (e.g., T-Echo and T-Beam) with firmware version 2.4.1.
Ensure there are no active users or messages being sent in the mesh network.
Observe the frequency of RF interactions between the devices.
Expected Behavior:
The mesh communication should only occur when necessary, similar to the behavior in version 1.x.
Actual Behavior:
Devices on version 2.4.x are frequently communicating via RF, even when there is no apparent reason to do so.
Environment:
Devices: T-Echo, T-Beam
Firmware Version: 2.4.1
Previous Version with Expected Behavior: 2.3.x
Additional Information:
This issue could potentially lead to unnecessary power consumption and might affect the overall performance of the mesh network.
Beta Was this translation helpful? Give feedback.
All reactions