This release is a pre-release and may not be stable for production use.
beebo-cli
Command line for beebo nodes: Heltec V4.3 headless MeshCore firmware that switches between companion and repeater roles. The CLI does the beebo-specific work: OTA updates, WiFi provisioning, transport selection (USB, BLE, WiFi), monitoring, health checks, RF measurement and analysis.
Install
$ pipx install --pre beebo-cli
$ beebo --version
Without pipx, use a virtual environment and pip install --pre beebo-cli. Needs Python 3.11 or 3.12. The plotting and analysis commands need an extra: pipx install --pre "beebo-cli[analysis]".
The package bundles a modified copy of meshcore-py (MIT), so it installs alongside an upstream meshcore without conflict.
Documentation
1 maintainer
Metadata
1 maintainer
Release files for beebo-cli 1.18.0.1.0rc15
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| beebo_cli-1.18.0.1.0rc15-py3-none-any.whl | Python 3 | none | any | Details |
Release files / beebo_cli-1.18.0.1.0rc15-py3-none-any.whl
| Download URL | beebo_cli-1.18.0.1.0rc15-py3-none-any.whl |
|---|---|
| Size | 733.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52824451fdf49469e5826218368b38a0174ee9e182c794820c08de28e789f08c
|
|
BLAKE2b-256 checksum How to use checksums |
29b6d87adf85820dd428df7910c2abe49fd4ff11b1e6b302113d6df2fc58a74b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for beebo-cli 1.18.0.1.0rc15
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
