MeshMapper
500+
Downloads
Everyone
info
About this app
MeshMapper is a wardriving app for MeshCore mesh network devices. Connect to your MeshCore companion device via Bluetooth, send GPS-tagged pings to discover nearby repeaters, and contribute coverage data to the community mesh map.
FEATURES
• Bluetooth Low Energy connection to MeshCore devices
• Real-time GPS tracking with automatic ping mode
• Discover and track mesh network repeaters
• View signal strength (RSSI/SNR) for each repeater
• Automatic upload to MeshMapper community database
Help map mesh network coverage in your area and contribute to the growing MeshMapper community!
FEATURES
• Bluetooth Low Energy connection to MeshCore devices
• Real-time GPS tracking with automatic ping mode
• Discover and track mesh network repeaters
• View signal strength (RSSI/SNR) for each repeater
• Automatic upload to MeshMapper community database
Help map mesh network coverage in your area and contribute to the growing MeshMapper community!
Updated on
Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time.
No data shared with third parties
Learn more about how developers declare sharing
This app may collect these data types
Location
Data is encrypted in transit
Data can’t be deleted
What’s new
## [v1.1.1] [HOTFIX] - 2025-02-26
### Bug Fixes
- Fixed wildcard scope `#*` not being recognized, causing incorrect packet types to be sent. Zones with no regional scope return `#*` as the wildcard, but the app only matched `*`, causing it to derive a TransportKey and call setFloodScope() with the literal string. This resulted in all TX pings being sent as TransportFlood (0x00/0x14) instead of regular FLOOD (0x01/0x15).
### Bug Fixes
- Fixed wildcard scope `#*` not being recognized, causing incorrect packet types to be sent. Zones with no regional scope return `#*` as the wildcard, but the app only matched `*`, causing it to derive a TransportKey and call setFloodScope() with the literal string. This resulted in all TX pings being sent as TransportFlood (0x00/0x14) instead of regular FLOOD (0x01/0x15).
App support
phone
Phone number
+16135180588
About the developer
Christopher Schnobb
MrAlders0n@smal.ca
Canada
