mtjk is a separately published distribution of the Meshtastic Python
library, maintained while changes are validated and selectively upstreamed.
Work began in September 2025 to stabilize connection interfaces and message delivery for mmrelay. The modernization work keeps existing Meshtastic Python usage compatible:
- package import namespace remains
meshtastic - CLI command remains
meshtastic - existing API compatibility is intentionally preserved
It is intended to be a drop-in, backward-compatible replacement for upstream.
This is a temporary fork of meshtastic/python. It exists to ship fixes and improvements while they are validated and upstreamed selectively.
This repository does not accept pull requests. Community development efforts should be directed to the upstream project. If you find a fix or improvement here that you would like to carry upstream, please do so.
- major BLE and interface internals were refactored for maintainability while keeping compatibility shims in place
- concurrency and lifecycle paths were tightened to reduce race-condition and shutdown edge cases
- CI and release workflows were modernized, including Trusted Publisher-based PyPI release flow
For technical details, see:
- REFACTOR_PROGRAM.md: rationale and early change log for the major refactor work maintained here.
- COMPATIBILITY.md: canonical inventory of compatibility shims, deprecations, and migration mapping.
- CONTRIBUTING.md: local setup, CI-equivalent checks, and contributor workflow conventions.
pipx is recommended for CLI tools so each app gets an isolated environment.
If you previously installed upstream meshtastic, remove it before installing mtjk.
# If installed with pipx:
pipx uninstall meshtastic || true
# If installed with pip in a Python environment:
python3 -m pip uninstall -y meshtasticpipx install mtjkmeshtastic --versionTo install the latest unreleased version from this repository (clean install):
# If you previously installed upstream via pipx, remove it first:
pipx uninstall meshtastic || true
pipx uninstall mtjk || true
pipx install "git+https://github.com/jeremiah-k/mtjk.git@develop"pipx upgrade mtjk
pipx uninstall mtjkDependency name is mtjk, but import namespace remains meshtastic.
Important:
- If your dependency spec says
meshtastic, you will install upstream. - Use
mtjkin dependency specs for this package. - The package does not provide
import mtjk.
mtjk
Unreleased from Git:
mtjk @ git+https://github.com/jeremiah-k/mtjk.git@develop
If you need optional CLI extras in a dependency spec:
mtjk[cli]
mtjk[cli] @ git+https://github.com/jeremiah-k/mtjk.git@develop
[project]
dependencies = [
"mtjk",
]Unreleased from Git:
[project]
dependencies = [
"mtjk @ git+https://github.com/jeremiah-k/mtjk.git@develop",
][options]
install_requires =
mtjkUnreleased from Git:
[options]
install_requires =
mtjk @ git+https://github.com/jeremiah-k/mtjk.git@developimport meshtastic
import meshtastic.serial_interface
interface = meshtastic.serial_interface.SerialInterface()
interface.sendText("hello mesh")
interface.close()Report mtjk-specific issues here:
Please do not file mtjk-specific issues with upstream maintainers.
- Versions match upstream releases with a
.postNsuffix (e.g.,2.7.8.post1is the firstmtjkrelease based on upstream2.7.8). - Create a GitHub release with tag
vX.Y.Z[.postN](or push the tag manually). This triggers the PyPI publish workflow via Trusted Publisher. - Trusted Publisher workflow expects the git tag version to match
pyproject.tomlexactly. - Supported tag formats are
vX.Y.Z...orX.Y.Z...(both map to the same package version check). - PyPI Trusted Publisher must match this repo/workflow/environment tuple:
jeremiah-k/mtjk+.github/workflows/pypi-publish.yml+pypi-release.