Menu Close

Download MeshCom SmartPhone APP

Rainer OE1KFR has programmed the appropriate APP for MeshCom 4.0 and makes it available for download.

The latest firmware version is required for full compatibility! If a different application was flashed onto the nodes, you must perform an erase and then flash the MeshCom firmware. This option is available in Web Flasher.

Starting with firmware version 4.35p.05.01 and app version 4.27, a custom BLE pin query has been introduced.

If the default PIN on the node is 000000, PIN checking is disabled. The PIN can be changed directly on the node via the serial console using the

Command: --btcode (6-digit code)

In the app, you can change the PIN using the key icon in the Devices tab next to the node's Connect button, or in the Settings tab.
If the node is not connected via BLE, you can only change or reset the PIN on the phone in the Devices tab.

Bei falschen PIN wird die BLE Verbindung vom Node geschlossen. Der Pin muss >= 100000 und <= 999999 sein.

Please do not connect/pair via Bluetooth Devices in the system settings. Establish the connection directly in the app with the respective node. Please delete any old pairings!

Like the firmware, the source code for the app is also available on GitHub is also published.

Manuals (Thx to DG4NEU):
MeshCom-App-Manual-German
MeshCom-App-Manual-English

IPhone

Apple App Store Link:

https://apps.apple.com/at/app/meshcom/id6447483289

Install the APP and agree to the use of GPS.

iOS App Background fully supported.

Android

To install please use the Google Playstore:

https://play.google.com/store/apps/details?id=io.ionic.meshcom

Side-loading:

Dropbox link directly to the current release APK which can be installed directly.

Please do not forget it must: Location Service, Bluetooth and Messages must be allowed.

iOS app in the background:

Communication is maintained and messages are also forwarded to the phone. However, automatic time synchronization with the node no longer works.

Android app in the background:

There is a limitation of the framework used here. However, at least all battery optimizations and restrictions of the app must be disabled in the app settings in the system settings! The connection is maintained, but no more data is exchanged after a few minutes.

Release Notes:

MeshCom App 4.29

Previous version: 4.28a. Some new features require updated firmware (recommended: 4.35 v or newer). The required firmware versions are noted.

New

Chat & Messages

  • New chat design: All received messages (To All, Group, DM) now have a uniform look. The time and "via" are displayed on a single line, and the sender is highlighted. Light and Dark modes have their own colors, and iOS and Android each have their own bubble shape. In Light mode, the time and via text are darker and easier to read.
  • Acknowledgement with call sign: For messages sent by the user, the acknowledgment symbol indicates which station heard or acknowledged the message. A tooltip displays "heard by" or "acknowledged by". Gateway acknowledgments do not yet provide this information. (Requires current firmware)
  • "Unconfirmed" status for DMs: The node resends its own direct message up to 3 times (from firmware 4.35u onwards). If no confirmation is received after 6 minutes, the app displays an orange "Cloud offline" symbol. If the confirmation arrives later, for example after a reconnect, the status changes to "confirmed". The status remains correct even after switching tabs, using the background, and restarting the app.
  • Repeated messages only once: If the same DM reaches the app multiple times (retry copies with different message IDs), it will only be saved and reported once.
  • Foreign DMs filtered out at the gateway: If the app is connected to a gateway node, DMs between other stations no longer appear in the DM chat and no longer trigger a notification.

Settings

  • Manual Routing (Via): New section in the settings. You define a destination callsign, enable or disable Via, and reset it with RST. If you enter a callsign and immediately enable it, the app handles both in one step. The displayed status always comes directly from the node. (Requires firmware 4.35p and later; with older firmware, the app displays a notification instead.)
  • Web UI Password: Under Manual Routing, there is a new, expandable section called "Web UI Password." This allows you to set the password for the node's web interface (up to 19 characters, indicated by an eye icon) or delete it using RST. The app only displays the current password with newer firmware. Setting the password also works with older firmware.
  • Own NTP server: The Fixed IP Settings have a new, optional field called "NTP".
    • If the field is left blank, the node will use its default time server as before. A configured NTP server will be checked and transmitted along with the other IP fields.
    • The node only uses it with a static IP address.
    • A configured server is listed at the top of the WLAN or ETH overview.
    • RST also deletes it.
  • Send POS in TRACK mode: When TRACK is active, the button first queries the node's GPS status. With a GPS fix, it sends the position. Without a fix, you can choose whether to send a LoRa APRS position or a MeshCom position. Without TRACK, the button behaves as before.

Info & Map

  • Firmware build date: In the Info tab, "BUILD: …" is now displayed under the Node firmware. This allows you to differentiate between firmware versions with the same version number. (Requires the latest firmware)
  • Firmware update notice: If the node is running firmware older than 4.35v, the app will display a message after connecting. The connection will remain active.
  • More information is now available on the map: The overlay now displays the APRS name, comment, and APRS symbol. If available, the INA226 bus voltage and current, as well as the MCP23017 inputs, are also shown.
  • App Log: The log window now has a copy button that copies the entire log, including app version, platform, and date, to the clipboard. It now holds 500 entries instead of 250. Additionally, the app logs each phase of the BLE connection setup with timestamps, which simplifies troubleshooting.

Improved

  • Node call sign: A leading zero in the SSID is removed (OE1KFR-02 → OE1KFR-2).
  • BLE disconnect notification: It now reliably appears on every tab, but no longer if you disconnected yourself.
  • Long press in chat: The context menu opens after 1 second instead of 0.8 seconds, so that it does not open accidentally while scrolling.
  • Technical basis: The app now runs on Ionic 9 and Capacitor 8.5.

Bug fixes

Connection

  • Android: Reconnect. The app now waits briefly after a disconnect before reconnecting. This prevents subsequent connection attempts from failing with a GATT error. A stuck disconnect ("Disconnection timeout") no longer blocks all further connection attempts until the app is restarted. Switching directly to a different node will no longer result in the new node being accidentally disconnected again.
  • Info tab query: The automatic query (info/location/weather) now starts immediately upon opening the tab. This also applies if you connect while the tab is already open.

News

  • Ack assignment: An acknowledgment now only applies to the most recent message with that ID. The node's counter resets to 0 after 1000 messages, and previously this resulted in older messages being incorrectly acknowledged.
  • Message ID: It is now read in the correct byte order, so acknowledgments are more reliably assigned to the correct message. (Messages saved before this update will no longer be associated with subsequent acknowledgments. This only affects older messages.)
  • Duplicate messages: Messages containing quotation marks in the text were previously not recognized as duplicates. This now works.
  • Eigene DMs: Bei eigenen DMs wird nur noch die angehängte Zähler-Kennung ({123) entfernt. Ein „{“ im eigentlichen Text bleibt erhalten.

Position & Map

  • Node name: It no longer disappears after the next beacon or a restart of the app.
  • Position data: Neighbor numbers from 10 onwards are now correct. A comment is no longer read as telemetry. The node timestamp is now read even without a via path.
  • Hardware IDs: Unknown hardware IDs appear as "Unknown (id)" instead of "undefined".

Settings

  • The gateway server selection will no longer remain empty if a web password is set on the node. (Requires current firmware)
  • In the Fixed IP Settings, the DNS field now displays "DNS" instead of "Gateway".

Android

  • The header is no longer too high.
  • The layout adapts better when the keyboard is opened.
  • The notification channels will be set up more reliably.

 

V4.28 Release Notes:

  • Chat Page now has vertical chat channels
  • Each chat channel has an audio icon to turn the sound on or off for notifications.
  • The chat channels also have a filter icon for filtering callsigns or text
  • Long-pressing an incoming message now offers two additional functions: "Block Callsign" and "Filter Text"
  • A long press in a chat also displays the "Reply To" option in chat channels other than Direct Messages and automatically inserts @callsign
  • The scroll position is now saved. When you scroll up, a button appears to scroll down.
  • The Chat Tab icon now displays a green dot when there are new messages
  • The chat channel displays a green mail icon when a new message arrives.
  • Fixed a bug where messages sent via the VIA function at the node—using a destination path—were treated as DMs.
  • The marker on the map now displays values only if they are either nonzero or represent a valid temperature.

V4.28a Release Notes:

  • Chat Page Channels Message Preview
  • Chat Page Channels: New Message Counter
  • Country PL added
  • MeshCom Server IT Italy added
  • Added HW T-Watch