Skip to main content
Version: 2.8

Community Apps

The Meshtastic ecosystem is highly extensible, and a number of community projects have been made to fit different people's needs. If you wish to create your own application or module, please read the information in the developers section, and tell us about your project on the forum.

Current community projects:

  • Meshtastic Web API - Meshtastic Web API provides a RESTful interface to interact with a Meshtastic node via a serial connection.
  • Mesh-metrics - Meshtastic repeater metrics scraper using meshtastic-cliCLI (Command Line Interface). A text-based interface used for interacting with software or devices like Meshtastic. to be ingested by node_exporter for use in Prometheus or Victoria Metrics Time series DB with a Grafana dashboard and sample alerting rules.
  • Node-RED Messages Node - Node-RED node to send and receive packets / text messages from a device connected via HTTP.
  • Harbor Scale - Grafana - A cloud-based solution for collecting, storing, and visualizing Meshtastic telemetry data using grafana.
  • MeshApp - A GPL-3.0 cross-platform desktop client for Meshtastic on Windows, macOS, and Linux. Connects over TCPTCP (Transmission Control Protocol). One of the three ways a client reaches a node, alongside serial and Bluetooth. Clients connect over TCP on port 4403., Serial / USBUSB (Universal Serial Bus). The wired connection used to power a device, flash firmware onto it, and communicate with it over serial., or BLEBLE (Bluetooth Low Energy). The default wireless connection between a node and a phone client. and combines multi-channel chat, direct messages, device configuration, telemetry, node maps, traceroute history, LoRaLoRaA low-power, long-range wireless communication technology used by Meshtastic devices to enable communication over distances of several kilometers without the need for cellular, Wi-Fi, or other traditional network infrastructures. packet inspection, MQTTMQTT (Message Queuing Telemetry Transport). A lightweight messaging protocol designed for small sensors and mobile devices, enabling efficient data transmission in the Meshtastic network for Internet connectivity and integration with IoT platforms. See https://en.wikipedia.org/wiki/MQTT. In Meshtastic, MQTT is used to connect a node to the internet, and can be used to connect multiple meshes to each other. proxy support, and a built-in Lua automation IDE.
  • Contact - A terminal-based Python chat and configuration client for Meshtastic devices.
  • MeshDash - A self-hosted, open-source web dashboard for Meshtastic mesh networks, connecting via Serial, TCPTCP (Transmission Control Protocol). One of the three ways a client reaches a node, alongside serial and Bluetooth. Clients connect over TCP on port 4403., BLEBLE (Bluetooth Low Energy). The default wireless connection between a node and a phone client., MQTTMQTT (Message Queuing Telemetry Transport). A lightweight messaging protocol designed for small sensors and mobile devices, enabling efficient data transmission in the Meshtastic network for Internet connectivity and integration with IoT platforms. See https://en.wikipedia.org/wiki/MQTT. In Meshtastic, MQTT is used to connect a node to the internet, and can be used to connect multiple meshes to each other., or WebSerial. Features real-time node monitoring, MeshShark packet analysis, GPSGPS (Global Positioning System). A satellite positioning system. A node with a GPS module determines its own location and can report that position to the mesh. mapping, direct messaging, telemetry analytics, task scheduler, auto-reply engine, traceroute, node config editor, plugin system, and Docker deployment.
  • MeshHessen Client - The MeshHessen Client is a .NET-based offline Windows application developed by the MeshHessen community for civil protection and emergency response, designed to run immediately without complex setup or technical expertise. It features maps (offline maps are currently Germany only), node visualization with labels and colors, alert highlighting/sounds, message logging, and supports serial, TCPTCP (Transmission Control Protocol). One of the three ways a client reaches a node, alongside serial and Bluetooth. Clients connect over TCP on port 4403./IP, and BLEBLE (Bluetooth Low Energy). The default wireless connection between a node and a phone client. connections.
  • MeshMonitor - A self-hosted web dashboard for monitoring Meshtastic and MQTTMQTT (Message Queuing Telemetry Transport). A lightweight messaging protocol designed for small sensors and mobile devices, enabling efficient data transmission in the Meshtastic network for Internet connectivity and integration with IoT platforms. See https://en.wikipedia.org/wiki/MQTT. In Meshtastic, MQTT is used to connect a node to the internet, and can be used to connect multiple meshes to each other. mesh networks in a single interface. Real-time node tracking, interactive maps, telemetry, messaging, multi-node remote administration, and automation (auto-responders, geofence triggers, scheduled messages). Includes an embedded MQTTMQTT (Message Queuing Telemetry Transport). A lightweight messaging protocol designed for small sensors and mobile devices, enabling efficient data transmission in the Meshtastic network for Internet connectivity and integration with IoT platforms. See https://en.wikipedia.org/wiki/MQTT. In Meshtastic, MQTT is used to connect a node to the internet, and can be used to connect multiple meshes to each other. broker, per-user access control, push notifications, and a REST API. Deploys via Docker, Kubernetes, or bare metal with SQLite, PostgreSQL, or MySQL.

Support for these projects should be sought from their respective authors.