Sending data package only reboots remote device into ShortFast

[KlfJoat]

Hi,

When trying to send a data package between 2 EUDs, the remote Meshtastic device reboots into ShortFast, but the local device does not.

EUD "A"

• Amazon Fire HD 8 (12th Generation)
  • Wi-Fi: OFF
  • Nothing physically plugged in
  • Nothing connected via Bluetooth (besides the Meshtastic device)
• ATAK v5.5.1.3
  • No TakServer configured or available.
• ATAK Meshtastic plugin v1.1.18 - 5.5.0
  • Only send PLI and Chat messages over Meshtastic: OFF
  • Allow SWITCH command: ON
• Meshtastic for F-Droid v2.7.3 (downloaded from GitHub, installed via APK)
• Seeed Wio Tracker L1 Pro
  • Meshtastic v2.7.11
  • LongFast
  • Channel 0 is private
  • Slot: 20
  • Role: TAK

EUD "B"

• Google Pixel 7 Pro
  • Nothing physically plugged in
  • Nothing connected via Bluetooth (besides the Meshtastic device)
• ATAK v5.5.1.3
  • No TakServer configured or available.
• ATAK Meshtastic plugin v1.1.18 - 5.5.0
  • Only send PLI and Chat messages over Meshtastic: OFF
  • Allow SWITCH command: ON
• Meshtastic for F-Droid v2.7.3 (downloaded from GitHub, installed via APK)
• Lilygo T-Echo
  • Meshtastic 2.7.11
  • LongFast
  • Channel 0 is private
  • Slot: 20
  • Role: TAK

(Each setting was verified)

Regular messaging between devices works.

If I send from A to B, then B's Meshtastic device (Lilygo T-Echo) reboots into ShortTurbo. The Seeed Wio Tracker L1 Pro does nothing and remains in LongFast.

If I send from B to A, then A's Meshtastic device (Seeed Wio Tracker L1 Pro) reboots into ShortTurbo. The Lilygo T-Echo does nothing and remains in LongFast.

This also happened with 2.6.30 firmware, 2.6 apps, and v1.1.16 ATAK plugin, though then it rebooted into ShortFast, not ShortTurbo.

With 2.6 and 1.1.16, if I manually set both devices into ShortFast, they would send.

Now, with 2.7 and 1.1.18, if I manually set them to ShortFast, the remote device reboots into ShortTurbo. If I manually set both to ShortTurbo, when I hit send in ATAK, an ATAK window pops up for a quarter second too fast to read, then goes away, I get no error message, and I see no "Transfer" notification from ATAK.

[niccellular]

Thanks for reporting, I will look into this

[KlfJoat]

I just confirmed (rather than relying on my memory) the behavior on 2.6.x and 1.1.16.

I mixed the devices up a bit...

EUD "B"

• Same device
• Same ATAK version
• ATAK Meshtastic plugin v1.1.16
• Meshtastic for F-Droid v2.6.30 (uninstalled 2.7, direct installed this APK)
• Seeed Wio Tracker L1 Pro (switched devices from above)
  • Meshtastic v2.6.11
  • ShortFast
  • Channel 0 is private
  • Slot: 20
  • Role: TAK

EUD "C"

• Android Tablet
• Same ATAK version
• ATAK Meshtastic plugin v1.1.16
• Meshtastic for F-Droid v2.6.30 (uninstalled 2.7, direct installed this APK)
• Lilygo T-Echo (same T-Echo from above)
  • Meshtastic v2.6.11
  • ShortFast
  • Channel 0 is private
  • Slot: 20
  • Role: TAK

Data package transfer and CoT worked perfectly, because I was already on ShortFast on both sides.

If both are set to LongFast, I confirmed that the remote device reboots into ShortFast and stays there, but the local device does not.

Now for the possibly interesting things I found out...

1. Having one side use the ATAK Meshtastic plugin v1.1.16 and the other side use v1.1.18 did NOT work.

2. While testing with LongFast I made a configuration mistake at one point. The ATAK Meshtastic Plugin on EUD C had "Allow SWITCH command: OFF" while everything else was correct. When that was the case, while sending from B to C the LOCAL device on EUD B rebooted into ShortFast AND THEN IT REBOOTED BACK into LongFast. This was the first time I have seen what I assume is the intended behavior (though, I assume both devices are supposed to do that). The remote device on EUD C did not reboot and the EUD did not receive any data package.

[niccellular]

After 1.1.16 I believe was the updated protobufs/package names so the versions are probably not compatible.