This module implements a Python client for the Russound I/O (RIO) and RNET protocol used to control Russound audio controllers. RIO supports a superset of the RNET feature set, allows for push notifications of system changes and supports TCP/IP and RS232 communication.
Supported Devices
- Russound MBX-PRE
- Russound MBX-AMP
- Russound MCA-C3
- Russound MCA-C5
- Russound MCA-66
- Russound MCA-88
- Russound MCA-88x
- Russound XSource (untested)
- Russound XZone4 (untested)
- Russound XZone70V (untested)
- Russound XStream-X5 (untested)
- Russound ACA-E5 (untested)
- Russound SMZ8
- Russound SMZ16-PRE
If your model is not on the list of supported devices, and everything works correctly then add it to the list by opening a pull request.
Which protocol should I use?
In most cases, this is already decided for you. Only a handful of devices support both protocols, and RIO is always recommended over RNET since it can provide real-time updates without polling.
| Device | RNET | RIO |
|---|---|---|
| Russound MBX-PRE | ✅ | |
| Russound MBX-AMP | ✅ | |
| Russound MCA-C3 | ⚠️ | ✅ |
| Russound MCA-C5 | ⚠️ | ✅ |
| Russound MCA-66 | ✅ | |
| Russound MCA-88 | ✅ | |
| Russound MCA-88x | ✅ | |
| Russound XSource | ✅ | |
| Russound XZone4 | ✅ | |
| Russound XZone70 | ✅ | |
| Russound XStream-X5 | ✅ | |
| Russound ACA-E5 | ⚠️ | ✅ |
| Russound SMZ8 | ✅ | |
| Russound SMZ16-PRE | ✅ | |
| Russound CAS44 | ✅ | |
| Russound CAA66 | ✅ | |
| Russound CAM6.6 | ✅ | |
| Russound CAV6.6 | ✅ |
✅ = Fully Supported, ⚠️ = Supported, RIO protocol preferred
Communication
The library supports the RIO protocol communication over TCP/IP or RS232 (Serial).
TCP/IP
The built-in ethernet port on the Russound device natively support the RIO protocol. Note: It is strongly recommended that the controller has a static IP address configured.
RS232 (Serial)
The RS232 port must be configured to use the RIO protocol instead of the RNET protocol for the library to function properly. This can be configured using the SCS-C5 configuration tool or the controller's Web GUI.
Acknowledgements
This is the continuation of the russound_rio package. This wouldn't be possible without the excellent work from @wickerwaka and @chphilli.
1 maintainer
Metadata
1 maintainer
Release files for aiorussound 5.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| aiorussound-5.0.2.tar.gz | 18.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aiorussound-5.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.2 kB
Release files / aiorussound-5.0.2.tar.gz
| Download URL | aiorussound-5.0.2.tar.gz |
|---|---|
| Size | 18.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
93e05c9df0ac868f6e079de7d313426a28d45b935cafcf7f4413f594b488da70
|
|
BLAKE2b-256 checksum How to use checksums |
d60b0d7b9f26099d1e2624ccb540a5c1941267d2dd6708dadd948d82c18a7d39
|
| 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 Aug 14, 2026.
Transparency logRelease files / aiorussound-5.0.2-py3-none-any.whl
| Download URL | aiorussound-5.0.2-py3-none-any.whl |
|---|---|
| Size | 20.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3b59a832e23a7bc6609281a5a82d070124d601764266f7363d42085cb3268e4f
|
|
BLAKE2b-256 checksum How to use checksums |
af95e5135f62ffc47436d945e4fedab11844c3c361a1b5f6febd1ab1837aaece
|
| 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 Aug 14, 2026.
Transparency log
