Skip to content

Offband Meshcore 1.1.2-beta.1 — public beta

Pre-release
Pre-release

Choose a tag to compare

@Strycher Strycher released this 24 Jun 04:15

🛑 Superseded by v1.1.2-beta.2 — please update; it fixes the Observer broker-pool error.

First public beta. It's a working cross-platform MeshCore client — please run it, push on it, and tell us what breaks.

Downloads

  • Windows (x64): OffbandMeshcore-1.1.2-beta.1-win-x64.zip — extract anywhere, run offband_meshcore.exe. (The VC++ runtime is bundled; no separate install.)
  • Android: OffbandMeshcore-1.1.2-beta.1.apk — sideload (enable "install from unknown sources").

⚠ Read first — known issues

  • Windows is unsigned. First launch shows SmartScreen "Windows protected your PC" → More info → Run anyway. A signed build comes later.
  • Missed public history after a long offline gap (#91). If your radio is disconnected for hours, on reconnect you may not receive all the public messages you missed — some trickle in slowly, some are dropped. A firmware-side fix is in progress.
  • Contact list can hang on connect (#86). On a companion connection, the red contact-loading bar can occasionally stick and never clear if a frame is dropped, so the app looks hung. Reconnect to clear it; a watchdog fix is planned.
  • MQTT broker / Observer features need newer firmware. Those screens only fully work on the firmware currently in review; on older firmware they're hidden/inert.

Highlights

  • Faster connect and channel sync; the connect retry that could stall the contact list is now capped.
  • Honest broker enable/disable — the app verifies the device actually applied the change instead of trusting the ack.
  • Broker runtime status + resolved-default hints in the Observer config.
  • Logs to disk for support — "Open logs folder" (desktop) / "Share logs" (mobile) on the BLE-log screen.
  • HH:MM timestamps + day dividers, @-mention autocomplete, hop-count badges, friendlier repeater path-hash labels, and more.

Reporting

Open an issue with your platform, device + firmware version, and (for a connection/sync bug) the log via the Share / Open-logs-folder button on the BLE-log screen.