Skip to content

FreqMapper v1.0.20

Summary

FreqMapper v1.0.20 protects people with multiple enrolled Meshtastic radios from having a radio upgraded to Meshtastic 2.8.1 or later matched to a different enrollment. The production API now requires proof that the old and new node IDs belong to the same physical radio before it updates an existing enrollment.

What's new

None in this release.

Improvements

  • The upcoming Android and iPhone updates identify an upgraded radio by reconstructing its former node ID locally from that radio's own hardware information. The raw hardware address is not sent to or stored by FreqMapper.
  • Pre-2.8 radios and newly enrolled post-2.8 radios continue to use their normal node IDs, so several distinct radios can remain enrolled on the same phone.

Fixes

  • Fixed an identity-matching path that could offer the wrong existing enrollment when a phone had more than one radio enrolled.
  • The API now rejects an existing-enrollment update when the installed app cannot prove that the selected enrollment belongs to the connected radio. It no longer treats a matching name or the presence of only one enrollment as identity evidence.

What you need to do

Normal radio enrollment and wardriving require no action. If a Meshtastic firmware upgrade changes an existing radio's node ID, wait for the next FreqMapper Android or iPhone update before choosing Update existing radio.

Mobile availability

The server-side protection is available in production with this release. Updated Android and iPhone builds containing the exact radio-matching flow have not been published yet; their availability will be announced through their normal testing channels.

Known limitations

  • Current mobile builds cannot complete the new proof-based update flow after a node-ID change. The server will block that update instead of risking changes to a different enrolled radio.
  • Installing the forthcoming mobile update is required to relink a pre-2.8 enrollment automatically after the same physical radio changes to its Meshtastic 2.8.1-or-later node ID.