Possible bug preventing comms (Group & DMs) from ATAK/WinTAK clients back through RabbitMQ to stand-alone Meshtastic clients.

brian7704 / OpenTAKServer

Yet another open source TAK Server for ATAK, iTAK, and WinTAK

GNU General Public License v3.0

59 stars 6 forks source link

Possible bug preventing comms (Group & DMs) from ATAK/WinTAK clients back through RabbitMQ to stand-alone Meshtastic clients. #42

Open ki6uve opened 1 month ago

ki6uve commented 1 month ago

Friendly reminder to check code for possible bug that would prevent messages from progressing from ATAK or WinTAK clients, back through OTS / RabbitMQ to reach stand-alone Meshtastic clients that are not connected to OTS directly via the Meshtastic plugin in ATAK. AKA EUDs that are running Meshtastic app only, not ATAK.

ki6uve commented 4 weeks ago

This issue was resolved by correcting user configuration settings to assure that Meshtastic channel name was identical in both OTS web UI's Meshtastic tab and the OTS-associated Meshtastic gateway node's channel settings. This issue can be closed.