MirAIe API for Python
Installation
pip install miraie-ac
Get started
import asyncio
from miraie_ac import MirAIeHub, MirAIeBroker
async def setup():
# Instantiate a MirAIeHub object
broker = MirAIeBroker()
# Instantiate a MirAIeHub object
hub = MirAIeHub()
# Intialize the hub (+91xxxxxxxxxx, password, broker)
await hub.init("<mobile>", "<password>", broker)
# Display list of available devices
print( hub.home.devices )
# Wait till connection has been established with the broker
async def waitForClient():
while not hasattr(broker, 'client') or getattr(broker, 'client') is None:
await asyncio.sleep(1)
await waitForClient()
# Now you can run any operation on the device(s)
hub.home.devices[0].turn_off()
asyncio.run(setup())
Logs can be enabled in Home Assistant as follows
logger:
...
logs:
...
custom_components.miraie: debug
...
Notes
Metadata
Release files for miraie-ac 1.1.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 | Provenance | Actions |
|---|---|---|---|---|
| miraie_ac-1.1.2.tar.gz | 9.5 kB | With provenance | Details for miraie_ac-1.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| miraie_ac-1.1.2-py3-none-any.whl | Python 3 | none | any | Details for miraie_ac-1.1.2-py3-none-any.whl |
Total release size: 21.7 kB
Release files / miraie_ac-1.1.2.tar.gz
| Download URL | miraie_ac-1.1.2.tar.gz |
|---|---|
| Size | 9.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab8097749acdafd9e1918ef8787965991721ad0c7bef4bd024ca91b60831c65c
|
|
BLAKE2b-256 checksum How to use checksums |
1120f3130015e4320eb907955c06f4fff03b12ffecdd5b434fed17b09d68d626
|
| 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 2, 2026.
Transparency logRelease files / miraie_ac-1.1.2-py3-none-any.whl
| Download URL | miraie_ac-1.1.2-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
82ba1a0aebbfdaa3b0eab419bb87ac9c2e4a8da832c29ce3c27a823ab3e77b4c
|
|
BLAKE2b-256 checksum How to use checksums |
7bb284c1e25e76255d48ae7f0099c231a87d40ed481d7d55f7f16f2cb936b60b
|
| 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 2, 2026.
Transparency logSecurity for miraie-ac 1.1.2
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 miraie_ac-1.1.2.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 Aug 2, 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.