riden-modbus
riden-modbus is an asynchronous Python library for reading and controlling Riden RD60xx bench power supplies over Modbus.
The library is backend-neutral: it consumes a modbus_connection.ModbusUnit and does not create or own the transport itself. Applications can therefore use tmodbus, pymodbus, or another backend supported by modbus-connection.
Features
- Object-oriented access to power-supply subsystems
- Automatic model probe with identity data (model, serial, firmware)
- Model-aware value scaling and output limits
- Full-map pooled reads — one Modbus request refreshes the whole device
- Read and write support with field-specific write validation
- All ten preset groups (M0-M9), including recall
- Neutral metadata for units, limits, steps, enums, and writable flags
Supported models
All models share one register map and differ only in scaling and limits:
| Model | ID register | Voltage scale | Current scale | Max output |
|---|---|---|---|---|
| RD6006 | 60060-60064 | 0.01 V | 0.001 A | 60 V / 6 A |
| RD6006P | 60065 | 0.001 V | 0.0001 A | 60 V / 6 A |
| RK6006 | 60066 | 0.01 V | 0.001 A | 60 V / 6 A |
| RD6012 | 60120-60124 | 0.01 V | 0.01 A | 60 V / 12 A |
| RD6012P | 60125-60129 | 0.001 V | range-dependent | 60 V / 12 A |
| RD6018 | 60180-60189 | 0.01 V | 0.01 A | 60 V / 18 A |
| RD6024 | 60241-60249 | 0.01 V | 0.01 A | 60 V / 24 A |
The RD6012P's current resolution follows its selected current range (register 20): 0.1 mA on the 6 A range, 1 mA on the 12 A range. The probe reads that register, and RD60xx must be constructed with the probed current_range; if the range is changed on the device, re-probe and rebuild the device object.
Device structure
An RD60xx object exposes the following subsystems:
| Attribute | Description |
|---|---|
info |
Model, firmware version, and serial-number information |
output |
Setpoints, live measurements, protection, CV/CC state, internal temp |
battery |
Battery-charging state, probe temperature, and Ah/Wh counters |
clock |
The device's real-time clock |
settings |
Front-panel menu options (buzzer, backlight, language, ...) |
presets |
The stored preset groups M0-M9 |
The register map is documented in the Baldanos rd6006 register notes and the ShayBox Riden register constants; addresses are plain zero-based Modbus addresses. Registers 12-13 are one 32-bit power value — an RD6018 tops out at 1080 W, past a single word's range. The Fahrenheit mirrors of the temperature registers (6-7, 36-37) are derived values and not modeled; the calibration registers (55-62) and maintenance registers (SYSTEM, bootloader) are deliberately left alone.
Basic usage
Install the library together with the desired modbus-connection backend.
Example using tmodbus and transparent RTU over TCP:
import asyncio
from modbus_connection.tmodbus import connect_serial
from riden_modbus import RD60xx
async def main() -> None:
# RTU framing over a socket is a serial link on a socket:// device.
connection = await connect_serial(
"socket://192.168.1.50:502",
framer="rtu",
)
try:
unit = connection.for_unit(1)
probe = await RD60xx.async_probe(unit)
if not probe.is_supported:
raise RuntimeError(f"Unsupported model: {probe.model_name}")
device = RD60xx(
unit,
model=probe.model,
current_range=probe.current_range,
)
await device.async_update()
print("Model:", device.info.model)
print("Output voltage:", device.output.voltage)
print("Output power:", device.output.power)
print("Battery charge:", device.battery.charge)
await device.output.set_voltage(13.5)
await device.output.set_current(2.5)
await device.output.set_enabled(True)
finally:
await connection.close()
asyncio.run(main())
For a serial/USB connection, open the port through the selected backend (the supplies default to 115200 baud, 8N1, station address 1).
Metadata and writes
The library is the source of truth for neutral Riden datapoint metadata:
- register reference
- value type
- model-aware scaling
- unit
- model-aware minimum and maximum
- step
- enum options
- writable state
Writes use:
await component.async_write_datapoint(field, value)
Field validation is applied before the value reaches the device; the RD60xx needs no write-unlock sequence.
ESPHome bridge firmware
esphome/rd60xx-serial-proxy.yaml is a ready-made, distributable firmware for the ESP8266 module inside the supply. It exposes the Modbus RTU TTL link through ESPHome's serial_proxy component, making the ESP a transparent serial bridge that Home Assistant can drive with this library.
The firmware contains no credentials, so prebuilt images can be flashed as-is: Wi-Fi is provisioned through the fallback hotspot's captive portal, the API starts keyless so Home Assistant generates and stores an encryption key on adoption, and name_add_mac_suffix keeps multiple supplies distinct. Build locally with esphome run esphome/rd60xx-serial-proxy.yaml.
CI compiles the firmware on every pull request that touches it, and pushes to main publish the built image to GitHub Pages with a browser-based ESP Web Tools installer, served at https://jesserockz.github.io/riden-modbus/.
Published firmware is built with the latest ESPHome release and versioned by calendar as YY.M.N, where N counts releases within the month (26.10.1 is the first release of October 2026). A weekly run rebuilds and republishes the firmware whenever a new ESPHome release has come out since the published build.
Command-line query tool
The repository contains script/query.py for querying a power supply without Home Assistant. It probes the model automatically.
Install the CLI backend:
python -m pip install -e ".[cli]"
Examples:
python script/query.py tcp 192.168.1.50 --unit 1
python script/query.py serial /dev/ttyUSB0 --unit 1
Use --framer rtu for transparent RTU over TCP or --framer socket for native Modbus TCP.
For a supply running the ESPHome bridge firmware, script/esphome_query.py does the same through the ESPHome native API instead:
python -m pip install -e ".[esphome]"
python script/esphome_query.py 10.0.0.5 --key <api-encryption-key>
Omit --key for a freshly flashed device that has not been adopted yet.
Development and tests
Install the project in editable mode and run the test suite:
uv sync
uv run pytest
uvx prek run --all-files
The test suite uses the in-memory mock backend provided by modbus-connection; no physical power supply or external Modbus server is required.
Releases
Every push to main updates a draft GitHub release: Release Drafter resolves the next version from PR labels, pyproject.toml is bumped to match, and the built distributions are attached to the draft — required up front because releases are immutable once published. While assets are still uploading the draft body carries a warning; once it disappears, the draft is ready to be published manually, which triggers the PyPI publish of exactly those attached files.
Metadata
Release files for riden-modbus 0.3.0
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 | Actions |
|---|---|---|---|---|
| riden_modbus-0.3.0.tar.gz | 38.2 kB | With provenance | Details for riden_modbus-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| riden_modbus-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for riden_modbus-0.3.0-py3-none-any.whl |
Total release size: 58.6 kB
Release files / riden_modbus-0.3.0.tar.gz
| Download URL | riden_modbus-0.3.0.tar.gz |
|---|---|
| Size | 38.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
405e5e707a23501aa413a638af3300f8a143de33aa650fcd79be356157ac744b
|
|
BLAKE2b-256 checksum How to use checksums |
f43df9d61b8b877bdc8318ee48f563853f7ea3e19501eabf0e4906a30aceb792
|
| 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 Oct 12, 2026.
Transparency logRelease files / riden_modbus-0.3.0-py3-none-any.whl
| Download URL | riden_modbus-0.3.0-py3-none-any.whl |
|---|---|
| Size | 20.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
336b47f49d7cf374362a2ece9713cef050c8ff16c2fd9cceee7622c988c4f392
|
|
BLAKE2b-256 checksum How to use checksums |
d13c0b1bbf972bf4af03e4dfeab9b1e4785f975d09de8aaf7e54899b69024b1e
|
| 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 Oct 12, 2026.
Transparency logSecurity for riden-modbus 0.3.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for riden_modbus-0.3.0.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 Oct 12, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.