Open RichieFrame opened 2 weeks ago
try the TRACKER role?
Tried TRACKER, and TAK_TRACKER, behaved the same as TAK in that they show the standalone t-echos on the maps but did not show the ATAK device on the other ATAK node, and global chat is not received by the other node. In TAK_TRACKER the meshtastic device's long name shows up on the other ATAK map/contact list, as would be expected because it is broadcasting its own PLI packets independent of ATAK.
I just installed the latest plugin version and meshtastic app on both devices and they can now see eachother!! I also have functional chat via the global geochat room but not user to user
After messing around a bit, I saw it was throwing an error with a local LAN IP when trying to direct message, I had started up ATAK initially with both devices on WIFI, then did the mesh tests with it turned off on one device.... somehow it had pinned its IP as the message target, restarting ATAK is now allowing direct messages to be sent in addition to global, and sending map pins is also working albeit slowly (30s)
I have 2 devices (wisblock) in TAK mode, both connected to Android phones running the latest ATAK, latest official plugin, and latest Meshtastic app. I have 2 devices (t-echo) running in TAK_TRACKER mode. All 4 devices are running 2.4.3 firmware. When all devices were configured as client, the app saw the position updates for all trackers, the trackers saw position updates for all clients, and all messaging was functional.
In ATAK, I can see the tracker nodes, the positions update every 3 mins as configured, though they contain no altitude or DOP data. The tak nodes however cannot see eachother, and sent messages in ATAK chat are also not received on the other node. If I reconfigure the tak node with GPS as TAK_TRACKER it can be seen by the other tak node. If I send a message using the app from a tak node, it is received by all other nodes.
This leads me to believe the following: Meshtastic mesh is stil working ATAK is communicating with the plugin The plugin is communicating with the app Something is wrong in the chain, preventing TAK packets from ATAK getting to the mesh, or preventing received TAK packets from being accepted by other nodes
By the issues list this does not appear to be a known issue, if there is some kind of setting I am missing in ATAK to have it send I do not know what it would be. I can attempt to make changes, test pre-release plugins, and get debug logs if any of that will help.