> Moved to https://gitlab.com/lafwud/russound/
# Russound Python API Implements a Python API for selected commands to the Russound system using the RNET protocol predominantly developed to provide Russound support within home-assistant.io. The class is designed to maintain a connection to the Russound controller, and reads the state directly from the controller using RNET. In principle supported models include the CAS44, CAA66, CAM6.6 and CAV6.6. Although testing has only been done on CAA66 and CAV6.6. Function to control Russound implemented are:
####For a zone: * set_power * set_volume * set_source * toggle_mute * get_power * get_volume * get_source
####Controller level * all_on_off
test_harness.py shows some examples of usage.
2 maintainers
Metadata
2 maintainers
Release files for russound 0.2.0
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 | Actions Reset |
|---|---|---|---|---|
| russound-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for russound-0.2.0-py3-none-any.whl |
Release files / russound-0.2.0-py3-none-any.whl
| Download URL | russound-0.2.0-py3-none-any.whl |
|---|---|
| Size | 20.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e424c532b3e81dc1902cdf238e8a99adab8d810061340111db039a89e755e081
|
|
BLAKE2b-256 checksum How to use checksums |
b56dc04808cf905f7d35dcc7b7f237d04b81b389a01730beedf39911cf3ec84b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.6
|
Security for russound 0.2.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.
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
