No description
  • Python 99.2%
  • Shell 0.7%
  • Makefile 0.1%
Find a file
github-actions eb964d78bb
Some checks are pending
CI / build (3.10) (push) Waiting to run
CI / build (3.11) (push) Waiting to run
CI / build (3.12) (push) Waiting to run
CI / build (3.9) (push) Waiting to run
CI / validate (3.10) (push) Waiting to run
CI / validate (3.11) (push) Waiting to run
CI / validate (3.12) (push) Waiting to run
CI / validate (3.9) (push) Waiting to run
bump version to 2.7.8
2026-03-02 17:30:29 +00:00
.github Update protobufs GH action 2026-02-14 10:47:14 -06:00
.reuse Clarify licensing in compliance with https://reuse.software/ 2024-06-27 19:30:52 +02:00
.trunk sort linters 2023-09-06 13:16:27 -07:00
.vscode fix launch.json punctuation 2025-07-26 22:35:18 -07:00
bin Add check for poetry install to regen-protobufs.sh 2025-07-17 10:49:23 +10:00
examples add waypoint parameter 2025-10-29 08:58:25 -07:00
extra move tuntest 2020-12-21 14:48:01 +08:00
info add nano_g1 2022-04-27 11:29:05 -07:00
meshtastic yolo away some pylint complaints 2026-03-02 10:22:21 -07:00
protobufs@e1a6b3a868 protobufs: v2.7.19 2026-03-02 09:51:43 -07:00
tests fix bitrot in an old sanity test - use correct namespace 2024-06-25 11:31:02 -07:00
.coveragerc fix code coverage CI false alarm? 2024-06-26 13:52:54 -07:00
.gitattributes mark protobufs folder as generated code for github 2024-08-21 22:27:18 -07:00
.gitignore Add T-Deck device support to Meshtastic CLI 2025-09-18 14:39:46 -06:00
.gitmodules Changes 2022-10-31 19:47:42 +10:00
.pylintrc fix linter warnings 2024-07-03 09:57:24 -07:00
example_config.yaml add to example config 2025-06-24 10:12:12 -07:00
exampleConfig.yaml establish trunk format 2023-03-31 20:09:59 +02:00
LICENSE.md rename and move license file 2025-06-25 12:23:00 -07:00
Makefile Changes 2022-10-31 19:47:42 +10:00
MANIFEST.in Add MANIFEST.in 2021-04-26 18:17:24 +02:00
poetry.lock Update some dependencies 2025-11-10 13:09:44 -07:00
pyproject.toml bump version to 2.7.8 2026-03-02 17:30:29 +00:00
pytest.ini fixes for working on mac air 2022-01-11 16:36:39 -08:00
README.md update README 2025-03-03 11:42:15 -07:00
standalone_readme.txt Update codecov link, remove current docs link, update standalone installation docs link 2024-03-30 10:17:02 -07:00
TODO.md BLE Support 2024-01-15 21:33:53 +01:00
vercel.json establish trunk format 2023-03-31 20:09:59 +02:00

Meshtastic Logo

Meshtastic Python

A Python library and client for use with Meshtastic devices.

codecov PyPI - Downloads CI CLA assistant Fiscal Contributors GPL-3.0

Overview

This small library (and example application) provides an easy API for sending and receiving messages over mesh radios. It also provides access to any of the operations/data available in the device user interface or the Android application. Events are delivered using a publish-subscribe model, and you can subscribe to only the message types you are interested in.

Call for Contributors

This library and CLI has gone without a consistent maintainer for a while, and there's many improvements that could be made. We're all volunteers here and help is extremely appreciated, whether in implementing your own needs or helping maintain the library and CLI in general.

If you're interested in contributing but don't have specific things you'd like to work on, look at the roadmap below!

Roadmap

This should always be considered a list in progress and flux -- inclusion doesn't guarantee implementation, and exclusion doesn't mean something's not wanted. GitHub issues are a great place to discuss ideas.

  • Types
    • type annotations throughout the codebase, and upgrading mypy running in CI to --strict
  • async-friendliness
  • CLI completeness & consistency
    • the CLI should support all features of the firmware
    • there should be a consistent output format available for shell scripting
  • CLI input validation & documentation
    • what arguments and options are compatible & incompatible with one another?
    • can the options be restructured in a way that is more self-documenting?
    • pubsub events should be documented clearly
  • helpers for third-party code
    • it should be easy to write a script that supports similar options to the CLI so many tools support the same ways of connecting to nodes
  • data storage & processing
    • there should be a standardized way of recording packets for later use, debugging, etc.
    • a persistence layer could also keep track of nodes beyond nodedb, as the apps do
    • a sqlite database schema and tools for writing to it may be a good starting point
    • enable maps, charts, visualizations

Stats

Alt