PyCCU3
This project has two clients for the CCU2/3.
It is recommended to install the xml-api external software into your ccu.
The current tested version is 2.3.
You could also leverage the old xml-rpc client which is also available in this package. It is not recommended using it as it does not have any encryption and passwords are transmitted in clear-text.
XML-API
Supported endpoints
statelist.cgidevicelist.cgiversion.cgiroomlist.cgiprogramlist.cgifunctionlist.cgi
1 maintainer
Metadata
1 maintainer
Release files for pyccu3 0.0.6
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 | |
|---|---|---|---|---|
| pyccu3-0.0.6.tar.gz | 8.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyccu3-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.5 kB
Release files / pyccu3-0.0.6.tar.gz
| Download URL | pyccu3-0.0.6.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c203ff24bc5c39d9f2e5e52193f7cb3064496ff30af7bb35c14a0d2ae94b5075
|
|
BLAKE2b-256 checksum How to use checksums |
0193c9ae21ef46cc32c642d9576711f78eaa2a56168193f56c982850cf98392a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 5, 2026.
Transparency logRelease files / pyccu3-0.0.6-py3-none-any.whl
| Download URL | pyccu3-0.0.6-py3-none-any.whl |
|---|---|
| Size | 10.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2da56ab3354ffe83e4fb9b238ba5f21f61e3e38428b66dcbf2c56d6a629b1dd
|
|
BLAKE2b-256 checksum How to use checksums |
32b927934c259ea8c5a039bf899738e1cffceac8340b17dab0b9d3d60541d854
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 5, 2026.
Transparency logSecurity for pyccu3 0.0.6
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 pyccu3-0.0.6.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 Jun 5, 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.
