Skip to content

Releases

MeshKit 0.2.7

Choose a tag to compare

@thebitstick thebitstick released this 25 Oct 05:54

What's new

  • Works with MeshCore 1.18.0. Updating from 1.17.1 keeps a node's settings; installs, clean installs and Convert work on a Heltec V3 (companion, repeater and room server) and a Wio Tracker L1.
  • Converting to a repeater or room server now replaces the characters the firmware refuses in a name ([ ] \ : , ? *) with spaces, and the sheet says so. The repeater name field shows an error for them too.
  • ⌘S applies your changes on the Configure screens, so you can edit and apply with the keyboard.
  • The repeater's firmware version no longer shows a stray first line right after the board boots.
  • AGC reset interval now allows 0 to 1020 seconds, which is what the firmware accepts.

Known limits

  • Not notarised: Control-click ▸ Open on first launch.
  • The wrong-board warning needs a board that reports a recognisable USB name.
  • MeshCore's 23-byte advertised-name limit is taken from its source and hasn't been observed on air.
  • Restoring an nRF52 backup over serial was tested on 1.17.1; on 1.18.0 only installs and clean installs were run.

MeshKit 0.2.6

Choose a tag to compare

@thebitstick thebitstick released this 15 Oct 05:45

What's new

  • Install over USB on nRF52 boards. Updates, clean installs and restores no longer need the board's drive or the reset button. If USB fails, MeshKit offers the drive as before.
  • Convert between MeshCore and Meshtastic (nRF52 and ESP32), carrying the node's name and location across. Converting to MeshCore asks whether the board should become a companion, repeater or room server.
  • Node-name limits are shown as you type: MeshCore 31 bytes (23 when the node shares its location in adverts; repeaters and room servers are held to 23), Meshtastic 39 long / 4 short. A new "Share location in adverts" switch sets whether a companion advertises its location.
  • Backups are labelled with the firmware inside, there are manual Back up buttons for every kind, and Settings ▸ Backups can delete them all.
  • Works offline. Release lists and downloaded firmware are kept for 30 days.
  • Other MeshCore firmware. Add builds from other GitHub projects in Settings ▸ Firmware.
  • Automatic updates with Sparkle (Settings ▸ Updates).
  • Clearer install, convert and restore sheets, a bottom bar with the exact file and the Convert menu, and VoiceOver labels throughout.
  • Fixes for frozen windows when macOS asks about removable volumes, stale node names after renaming, and blank port and drive pickers.

Known limits

  • Not notarised: Control-click ▸ Open on first launch.
  • The wrong-board warning needs a board that reports a recognisable USB name.
  • MeshCore's 23-byte advertised-name limit is taken from its source and hasn't been observed on air.
  • Once, after a serial restore, a Wio Tracker L1 didn't answer until it was restarted. It didn't happen again in later runs on the L1 or a Heltec T096. If a board stays silent after an install, unplug it and plug it back in.

MeshKit 0.2.5

Choose a tag to compare

@thebitstick thebitstick released this 13 Oct 07:05

Fixes the serial port and bootloader drive menus showing blank when only one device is connected. Clearer wording when entering DFU mode from an install or restore sheet, and for the restore confirmation.

MeshKit 0.2.4

Choose a tag to compare

@thebitstick thebitstick released this 13 Oct 06:28

Other MeshCore firmware sources: add a GitHub project in Settings ▸ Firmware and pick it from the new Source menu in the MeshCore window. Builds from other projects carry a warning that they aren't from the MeshCore project. Also understands fork file names that carry their own version (USB and Bluetooth builds both show up).

MeshKit 0.2.3

Choose a tag to compare

@thebitstick thebitstick released this 13 Oct 06:06

Adds automatic updates (Sparkle). MeshKit checks for new releases and offers to install them; turn it off in Settings ▸ Updates. This version has to be installed by hand; later ones update in place.

MeshKit 0.2.2

Choose a tag to compare

@thebitstick thebitstick released this 13 Oct 05:34

Largely AI-written; see AI-DISCLOSURE.md. Not notarised: Control-click the app and choose Open on first launch.

New

  • DFU button next to every nRF52 serial port in the device list (and Device ▸ Enter DFU Mode): it puts the board into DFU mode whatever firmware it runs. A Meshtastic node is restarted into its UF2 drive; anything else, including firmware that doesn't answer, is restarted into serial DFU, and firmware then goes in through Install over USB serial.
  • nRF52 backups: UF2 installs now save the board's current firmware first (Backups ▸ nRF52 firmware) and a saved image can be restored. A failed backup stops the install before anything is written; the sheet has a switch to turn it off.
  • The app says "Bluetooth firmware" instead of "SoftDevice".

Tested on hardware: Wio Tracker L1 (DFU button from Meshtastic and from MeshCore, backup, restore, serial DFU installs) and Heltec V3 (MeshCore repeater, companion, room server; Meshtastic). Other boards are untested.

MeshKit 0.2.1

Choose a tag to compare

@thebitstick thebitstick released this 13 Oct 04:45

Largely AI-written; see AI-DISCLOSURE.md. Not notarised: Control-click the app and choose Open on first launch.

New

  • Install nRF52 firmware over USB serial DFU, like MeshCore's web flasher: no reset button, no bootloader drive, settings kept. Three-dot menu next to the board name ▸ Install over USB serial. Works with MeshCore's DFU package and Meshtastic's OTA package.
  • Device ▸ Restart into Bootloader (nRF52) for a connected Meshtastic node, which brings up the UF2 drive without the reset button.
  • The flash sheet shows which bootloader a board already runs (for the OTAFIX bootloader fix).

Fixed

  • nRF52 clean install on real hardware: the erase tool only continues once its USB serial port is opened, so MeshKit opens it while waiting for the drive to return.
  • The first connect to a freshly flashed board retries once instead of failing.

Tested on hardware: Heltec V3 (MeshCore repeater, companion, room server; Meshtastic stable and alpha) and Wio Tracker L1 (MeshCore companion and Meshtastic over UF2 and over serial DFU, clean install, bootloader update). Other boards are untested.

MeshKit 0.2.0

Choose a tag to compare

@thebitstick thebitstick released this 13 Oct 04:18

Largely AI-written; see AI-DISCLOSURE.md. Not notarised: Control-click the app and choose Open on first launch.

New

  • MeshCore ESP32 boards get Update (keeps identity and settings) and Clean install; nRF52 boards get Clean install too, using Meshtastic's erase tool.
  • Install / Download DFU bootloader fix for nRF52 boards (the OTAFIX bootloader that makes Bluetooth updates more reliable), in the three-dot menu next to the board name.
  • Welcome window plus separate MeshCore and Meshtastic windows with toolbar tabs; fuzzy firmware search by board or maker; board names carry the maker.

Fixed after testing on real boards

  • Repeater and room server settings showed a stray "> " in front of values, and slow set replies could land on the next command.
  • Sync clock on a repeater now sends time <epoch>; advert.interval accepts 0.
  • The first connect to a freshly flashed board retries once instead of failing.
  • nRF52 clean install: the erase tool only continues once its USB serial port is opened, so MeshKit now opens it while waiting for the bootloader drive.

Tested on hardware: Heltec V3 (MeshCore repeater, companion, room server; Meshtastic stable and alpha; update, clean install and flash restore) and Wio Tracker L1 (MeshCore companion, Meshtastic, clean install, bootloader update). Other boards are untested.

MeshKit 0.1.0

Choose a tag to compare

@thebitstick thebitstick released this 13 Oct 00:39

First public release. Largely AI-written; see AI-DISCLOSURE.md. Tested on a Heltec V3 only. Not notarised: Control-click the app and choose Open on first launch.