python-esp-bridge
Control every ESP32 peripheral from Python over USB serial — GPIO, PWM, ADC, DAC, touch, I2C, SPI, UART, Wi-Fi (with TCP/UDP sockets through the ESP32 radio) and BLE. Flash the bridge firmware once, then it's all Python.
from espbridge import Bridge
with Bridge() as esp: # USB first, then Bluetooth, then Wi-Fi
esp.gpio.mode(2, "output")
esp.gpio.write(2, 1)
print(esp.adc.read_mv(34), "mV")
esp.i2c.init(sda=21, scl=22)
print(esp.i2c.scan())
esp.wifi.connect("ssid", "password")
status, body = esp.net.http_get("http://example.com/")
- On-device rules react without the host in the loop
(
esp.watch.add("adc", pin=34, above=3200, do=("pwm", 13, 0))), andesp.radio_off()silences Wi-Fi + Bluetooth entirely for jitter-sensitive realtime work (frees ~110 KB heap, unlocks the ADC2 pins). - Firmware (flash once with Arduino IDE) and full docs: https://github.com/HamzaYslmn/python-esp-bridge
- Works on Raspberry Pi OS, Linux, Windows, macOS (Python ≥ 3.11, pyserial).
espbridgeCLI: connection info;espbridge ports: list candidate ports.
Metadata
Release files for python-esp-bridge 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| python_esp_bridge-1.0.1.tar.gz | 1.7 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python_esp_bridge-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.2 MB
Release files / python_esp_bridge-1.0.1.tar.gz
| Download URL | python_esp_bridge-1.0.1.tar.gz |
|---|---|
| Size | 1.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e4226740c5a21f70d7cecd85d538e85ec1cc2ae3fc0b246a808c2687821d405
|
|
BLAKE2b-256 checksum How to use checksums |
481366eecb8b4d577949044bb6d83300f691c825d6ad98a160221d8c0509ffbd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logRelease files / python_esp_bridge-1.0.1-py3-none-any.whl
| Download URL | python_esp_bridge-1.0.1-py3-none-any.whl |
|---|---|
| Size | 1.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
792315f798837f11b0daf61cab18459d589165881ae4dd94c9eb093639f772e4
|
|
BLAKE2b-256 checksum How to use checksums |
35d6e9a828f601ea645bbbdbbc7663f8dc245370207385368980ada31f3b4b4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logSecurity for python-esp-bridge 1.0.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for python_esp_bridge-1.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logA 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.