[Bug]: Tak Integration : can't send Markers or chat messages in ATAK through Meshtastic

[Guylby]

Contact Details

No response

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.8.0 snapshot 29321761 universal debug

Affected Android version

Android 13 and 9

Affected phone model

Sony XQ-AD51 and XQ-BT52

Affected node model

Seeed T1000-E

Affected node firmware version

2.7.15

Steps to reproduce the bug

Hi,

I've been unable to send or receive any marker shared or any chat message (through all ATAK means: broadcast, all chat, direct message to contact)
I can send messages from the meshtastic app to the other meshtastic app without problems (shortfast tak private channel, direct message).
Each node show on the other phone in the contact list as connected and a marker is placed on the map with the Short Name + Full name of the node.

On the config side:
In the meshtastic app: in Settings>Tak Server:
Local tak server is ON both sides
Mesh to CoT converter is ON both sides
On both phones the Meshtastic tak server is connected (green status) and setup through the data package created by the meshtastic app

Both nodes are setup with TAK profiles.

I've run the TAK Mesh Test (Debug) on both sides with 0 errors (all 41 tests show all PLI, markers, contacts and chat messages on the other device, both sides)

The ATAK meshtastic plugin is disabled (if enabled it does not work either) and the app is restarted.

The full setup was fully working with Meshtastic 2.7.13 + ATAK Meshtastic plugin 1.1.42

Actual behavior

Nodes show on the map and in the contact list, but when sending markers or chat messages, nothing happens

Expected behavior

No response

Screenshots/Screen recordings

No response

Relevant log output

Additional information

No response

[kd2var]

I wanted to add some testing feedback from the Mesh-to-CoT work. The node/contact portion of the Mesh-to-CoT functionality has been working well in my testing with the new TAK server implementation.

The only issue I have encountered so far appears to be unrelated to Mesh-to-CoT itself. I have been testing a possible Android connection lifecycle issue where the node connection can become stale and require force stopping the app to recover. I am tracking that separately so it does not get confused with the TAK functionality.

For anyone following this issue, the Mesh-to-CoT feature is a new implementation that is actively being developed and tested. My understanding is that surfacing nodes as CoT contacts is the first step, and additional TAK integration features such as messages and waypoints may still require further implementation/testing.

If the goal is to continue expanding the TAK integration, I would be interested in seeing messages and waypoints supported as the next steps.

[jared-labs]

I may be reproducing a related Local TAK marker/POI problem. My results are not identical to the original report because PLI and GeoChat work reliably, but POI/marker exchange does not.

Test environment

• Meshtastic Android 2.8.0 official stable Google build 29321705 on both clients
• Previously reproduced on Meshtastic Android 2.7.14
• ATAK 5.6.0.12
• Google Pixel 9a running Android 17
• Samsung Galaxy Tab A7 (SM-T505) running Android 12
• Two Heltec V3 radios running Meshtastic firmware 2.7.26
• SHORT_FAST modem preset
• Private channel
• Built-in Local TAK Server enabled on both Android clients
• Local TAK data packages exported from Meshtastic and imported into ATAK
• Both Local TAK connections shown as connected in ATAK
• Legacy Meshtastic ATAK plugin disabled
• Radios normally configured as CLIENT

Results over the LoRa/Local TAK path

• Bidirectional ATAK PLI/location: PASS
• Bidirectional GeoChat: PASS
• Meshtastic node/contact visibility: PASS
• POI/general marker exchange: FAIL

Marker observations

• A blue affiliated tactical-entity symbol crosses the mesh when sent directly or broadcast. The receiving ATAK client displays it as a user/team-member contact. That may be correct for its CoT affiliation/type and is not being counted as a successful ordinary POI test.
• A green/ground tactical entity and the other tested marker/POI types do not appear on the receiving client.
• The same ATAK clients exchange map objects normally when connected through a conventional TAK Server.

Isolation performed

• Both clients were upgraded together from Meshtastic Android 2.7.14 to stable 2.8.0 build 29321705. The behavior did not change.
• The MQTT module, phone MQTT proxy, and channel MQTT uplink/downlink were disabled. The behavior did not change.
• Changing the test radios from CLIENT to TAK did not repair marker exchange and made PLI/GeoChat less reliable in this particular configuration.
• Returning the radios to CLIENT restored reliable bidirectional PLI and GeoChat.
• Restarting ATAK and generating fresh mesh traffic restores mesh-derived contacts.
• Release-build Android logs showed activity at the send times but did not expose the outgoing CoT type or marker name.

Because PLI and GeoChat pass in both directions, the loopback connection, radio link, private channel, and basic TAK transport are functioning. The remaining failure appears specific to at least some marker/POI object types or their conversion/transport path.

This may share a root cause with this issue, but I cannot confirm that because GeoChat fails in the original report and succeeds here. The behavior also reproduces across different manufacturers and Android versions.

I can run additional controlled tests or provide sanitized diagnostics if maintainers identify specific CoT types, debug builds, or test procedures that would be useful.

[Guylby]

I can confirm what @jared-labs is observing by switching the profile in both Meshtastic device from TAK to CLIENT

Geochat can be sent and received both sides but there is an issue:
each message creates a new duplicated contact, with an empty chat history (ATAK gives a notification with the message received but it won't show in the contacts chat windows):

ATAK PLI/location also has issues: the contact is added to the contact list instantly, but a marker is only placed on the map if the phone gps is ON, there is no way to use the linked meshtastic node gps in ATAK. ATAK also has alternate GPS sources, even manual placement. It would be useful if the meshtastic app could use this position information
If I understand correctly, at this moment the Meshtastic uses the phone location information to place the associated contact on the map.
If possible, it would be better if Meshtastic used the location information provided by ATAK (this opens all ATAK position sources: manual, from Meshtastic, from phone, from alternate sources, etc...) to place the contact marker on the map.

For POI/general marker exchange: same issues as stated above by @jared-labs : only the blue ground marker can be send, but it's received on the other device as a contact and blue team member.
All other POI types can't be sent currently