OpenTAKServer icon indicating copy to clipboard operation
OpenTAKServer copied to clipboard
verified publisher icon brian7704

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

Open ki6uve opened this issue 1 year ago • 1 comments

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 avatar Jul 15 '24 15:07 ki6uve

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.

ki6uve avatar Aug 15 '24 12:08 ki6uve