haco Home Assistant Control Objects
haco greatly simplifies the process of exposing Home Assistant controls (e.g. Pull-down Lists, Number Sliders, Sensors, etc.) from a device - and handling the communication between both sides.
While the current implementation is in Python, the capability definitions for controls are designed to be shared across different languages. Support for additional languages (namely native support for Tasmota Berry) is planned.
Why MQTT?
You might wonder why we use MQTT instead of directly using Home Assistant's APIs. The reason is flexibility: using MQTT allows
haco to target any device or environment that has an MQTT client, not just those that can easily make HTTP requests or run a full HA integration. This makes it ideal for lightweight embedded systems and cross-platform utility.
Why Would I Want Such a Thing?
Integrating custom hardware or scripts with Home Assistant often involves a lot of boilerplate: defining MQTT topics, crafting JSON payloads for discovery, and managing state updates.
haco handles the heavy lifting, letting you define your device and its controls in clean, declarative Python.
If you're building a custom IoT device, a script to monitor your system, or just want a simpler way to bridge your code to Home Assistant, then you might find
haco useful.
How it Works
haco uses MQTT to communicate with Home Assistant. It automatically generates the discovery configurations required for Home Assistant to "see" your device and its entities. All you need to do is define a
Device with some Controls and start the ClientHaco.
Documentation
Metadata
Release files for haco 0.4.3
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 |
|---|---|---|---|---|
| haco-0.4.3.tar.gz | 17.2 kB | Without provenance | Details for haco-0.4.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| haco-0.4.3-py3-none-any.whl | Python 3 | none | any | Details for haco-0.4.3-py3-none-any.whl |
Total release size: 39.7 kB
Release files / haco-0.4.3.tar.gz
| Download URL | haco-0.4.3.tar.gz |
|---|---|
| Size | 17.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18f440ee95f134c9c461959afa84d4acc0bedefd6b2df7e3fe4585f6e15ebd55
|
|
BLAKE2b-256 checksum How to use checksums |
27c75c8594e731929d37c67f667e5d6c749240ae93cab35a9ee43f4e1ad7f1aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / haco-0.4.3-py3-none-any.whl
| Download URL | haco-0.4.3-py3-none-any.whl |
|---|---|
| Size | 22.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fbbe4541d81ae8fc95ac900c54337624c75e004bbb7ac722b82d5872523f42d1
|
|
BLAKE2b-256 checksum How to use checksums |
448859f5c9c0abbe319c3aa1f9515770f2a77fdf307bbcf24631ae2e8218f0d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for haco 0.4.3
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.