Menu Close

Unified messaging


Messages from APRS clients to MeshCom nodes:
It is possible to send a text message from any APRS client to a MeshCom node.

Destination callsign: A valid MeshCom node callsign. Valid callsigns are all callsigns that are registered as ONLINE on the MeshCom server dashboard.

Text: max. 180 characters of text are accepted by the MeshCom server for this transmission. The rest of a message is truncated.

Conditions for sending messages from the APRS cloud to MeshCom
  • The destination callsign must be known to the APRS cloud so that it exists on the MeshCom server
    • This happens when a callsign regularly sends position reports to the APRS cloud Attention: a callsign must have an SSID from -1 to -99. So OE1KBC-1 and not OE1KBC
  • The following messages are not accepted by the MeshCom server
    • APRS types PARM, UNIT, EQNS, BITS (telemetry messages) Will only take place from MeshCom 4.0 onwards if the MeshCom server also collects data.
Messages from MeshCom nodes to APRS clients:

The message is formatted as follows:

Switch to DM message with destination call sign.

Then start the DM text entry from with "APRS:" and append the desired text

  • Examples:
  • DM OE3MZC-7 APRS:Greetings to your vacation home
  • DM oe1kbc-7 aprs:greetings from OE
One option is to return to MeshCom from the Internet:<eigenes Rufzeichen>

SOTA spots via APRS2SOTA:

If you have registered your callsign (from which the message is sent) with Steward G0LGS (see instructions at ) you can create a SOTA spot with the following message.


Select DM message in the APP. Enter destination callsign APRS2SOTA.

Im text folgendes eingeben: <Ass/Ref> <Freq> <Mode> [callsign] [comment]

  • Example:
  • TEXT OE/OO-303 145.500 FM OE5JFE/P Spot via Meshcom

APRS2SOTA Meshcom SPOT Test.png


Messages from MeshCom nodes as email to the I-NET cloud:

All messages are sent as a direct message (DM) to the receiver WLNK-1

1) login and wait for password request

2) Enter password letters as requested

3) Commands see