LowMesh

MeshCore mobile app (Ripple)

MeshCore™ devices are often configured with Ripple-branded clients and related tools. Exact app names, store listings, and menu paths change between releases—always confirm against the README for your firmware version on github.com/meshcore-dev.

This page gives a typical flow and screenshot slots you can fill in. It is not a substitute for upstream release notes.

Screenshots below are placeholders in public/docs-images/meshcore/. Replace each placeholder-*.svg with a PNG or WebP using the same filename so the docs show real Ripple / MeshCore UI.

Before you open the client

  • LowMesh hardware ships with Meshtastic®—to use MeshCore™ / Ripple you must reflash first. Flash MeshCore™ firmware appropriate for your board—see MeshCore firmware and Flashing Guide.
  • Know whether your build is GUI, companion, repeater, or another role—that changes what you can configure from a phone.
  • Keep the device powered and within Bluetooth range for first pairing.

1. Install the official client

  1. Open the MeshCore / Ripple documentation for your release and follow the install link for your OS (mobile and/or desktop).
  2. Grant Bluetooth (and any USB permissions if you use serial).
  3. Avoid sideloading random APKs unless you trust the source.

Ripple / MeshCore client — installRipple / MeshCore client — install

2. Connect to the device

  1. Power the radio; wait for a stable boot (LED or screen depends on hardware).
  2. In the client, use scan / connect / add device (labels vary).
  3. If pairing fails, forget the device in OS Bluetooth settings and retry—same pattern as other BLE gear.

Ripple / MeshCore — Connect to deviceRipple / MeshCore — Connect to device

3. Identity and profile

Set node identity fields your group will recognize. MeshCore™ may use profiles or rooms instead of Meshtastic-style “channels”—copy values from your group’s coordinator so keys and names match.

Avoid embedding sensitive personal data in fields that may be visible on the mesh.

Ripple / MeshCore — Identity & profileRipple / MeshCore — Identity & profile

4. Network, rooms, and routing

Configure network or room settings per your firmware role:

  • Endpoints – Messaging and presence as supported.
  • Repeaters – Expect routing-centric options; you may not have a full messaging UI on device.
  • Room server – May require fixed networking or additional setup—read the release notes.

Regional RF limits still apply—wrong band or power is not a “MeshCore setting,” it is a legal issue. Review Radio & mesh concepts.

Ripple / MeshCore — Network / rooms / routingRipple / MeshCore — Network / rooms / routing

5. Verify with a second node

With another MeshCore™ node on the same plan (keys / rooms / profiles):

  1. Send a test message or observe neighbor / path UI if exposed.
  2. Walk through range tests before relying on the link in the field.

When documentation disagrees

If this page conflicts with MeshCore™ release notes or Discord/Matrix guidance, trust upstream and consider sending us a PR or admin note to update these screenshots and steps.

Related docs

Upstream