Simple Management Protocol (SMP) Client

smpclient implements the transport layer of the Simple Management Protocol. This library can be used as a dependency in applications that use SMP over serial (UART or USB), Bluetooth (BLE), or UDP connections. Some abstractions are provided for common routines like upgrading device firmware.

If you don't need a library with the transport layer implemented, then you might prefer to use smp instead. The SMP specification can be found here.

If you'd like an SMP CLI application instead of a library, then you should try smpmgr.

Install

smpclient is distributed by PyPI and can be installed with poetry, pip, and other dependency managers.

User Documentation

Documentation is in the source code so that it is available to your editor. An online version is generated and available here.

Development Quickstart

Assumes that you've already setup your development environment.

activate envr, the environment manager for bash, zsh, and PS:
```
. ./envr.ps1
```
run poetry install when pulling in new changes
run lint after making changes
run test after making changes
add library dependencies with poetry:
```
poetry add <my_new_dependency>
```
add test or other development dependencies using poetry groups:
```
poetry add -G dev <my_dev_dependency>
```
run tests for all supported python versions:
```
tox
```

Development Environment Setup

Install Dependencies

poetry==1.8.5: https://python-poetry.org/docs/#installation

Create the venv

poetry install

The venv should be installed to .venv.

Activate envr

envr supports bash, zsh, and PS in Linux, MacOS, and Windows. If you are using an unsupported shell, you can activate the .venv environment manually, use poetry run and poetry shell, and refer to envr-default for useful aliases.

. ./envr.ps1

Verify Your Setup

To verify the installation, make sure that all of the tests are passing using these envr aliases:

lint
test

Enable the githooks

The pre-commit hook will run the linters but not the unit tests.

git config core.hooksPath .githooks

Metadata

Release files for smpclient 4.4.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for smpclient 4.4.2
File	Size	Uploaded
smpclient-4.4.2.tar.gz	24.5 kB	Jan 30, 2025	Details

Built distribution (wheel)

Table of built distributions (wheels) for smpclient 4.4.2
File	Interpreter	ABI	Platform	Reset
smpclient-4.4.2-py3-none-any.whl 30.2 kB Jan 30, 2025	Python 3	none	any	Details

Total release size: 54.6 kB

Release files / smpclient-4.4.2.tar.gz

Download URL	smpclient-4.4.2.tar.gz
Size	24.5 kB
Tags	Source
SHA-256 checksum How to use checksums	`c6049c875e232d4f29703e754d455833410a1608a576bdc1b952304ef51bacab`
BLAKE2b-256 checksum How to use checksums	`39715cac5585e8aae5108d050343d6287dfe7a64a31bf109cdd62a5203777694`
Upload date	Jan 30, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.12.8`

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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/intercreate/smpclient
Publishing commit: github.com/intercreate/smpclient/tree/47410d3b9db24f767a7fee58446cc39931c5743f

Workflow

Publishing configuration: github.com/intercreate/smpclient/blob/47410d3b9db24f767a7fee58446cc39931c5743f/.github/workflows/release.yaml
Publishing logs: github.com/intercreate/smpclient/actions/runs/13060882010/attempts/1

Artifact

Subject: smpclient-4.4.2.tar.gz
SHA-256 checksum: c6049c875e232d4f29703e754d455833410a1608a576bdc1b952304ef51bacab Verifying attestations

Release files / smpclient-4.4.2-py3-none-any.whl

Download URL	smpclient-4.4.2-py3-none-any.whl
Size	30.2 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`bc4ff81901851a435ad944b64ee5274cf23af2fdfa744bc7a72b3d4479732ef6`
BLAKE2b-256 checksum How to use checksums	`0240a3f96a617a2a0e420f8f06b08695ed203a7d79d89dbf0255d74ec275c3e1`
Upload date	Jan 30, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.12.8`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/intercreate/smpclient
Publishing commit: github.com/intercreate/smpclient/tree/47410d3b9db24f767a7fee58446cc39931c5743f

Workflow

Publishing configuration: github.com/intercreate/smpclient/blob/47410d3b9db24f767a7fee58446cc39931c5743f/.github/workflows/release.yaml
Publishing logs: github.com/intercreate/smpclient/actions/runs/13060882010/attempts/1

Artifact

Subject: smpclient-4.4.2-py3-none-any.whl
SHA-256 checksum: bc4ff81901851a435ad944b64ee5274cf23af2fdfa744bc7a72b3d4479732ef6 Verifying attestations