Innosonix Amplifier integration for Home Assistant
A Home Assistant integration that reads status information from Innosonix
amplifiers (MAXX series) over the built-in REST API, built on top of the
standalone innosonix Python client
library published on PyPI.
Features
- Device info sensors: model, serial number, software revision, channel count
- Device health: error / warning problem binary sensors
- Per-channel binary sensors: amplifier enabled and mute state (all channels)
- Configurable API key (defaults to the key shipped with the amplifier)
- Local polling, no cloud required
The Python client library
The innosonix package (src/innosonix) is a standalone async client for the
Innosonix REST API and works independently of Home Assistant:
pip install innosonix
import asyncio
import aiohttp
from innosonix import InnosonixApiClient
async def main():
async with aiohttp.ClientSession() as session:
client = InnosonixApiClient("192.168.1.50", session=session)
device = await client.get_device_infos()
print(device.model_name, device.sw_revision)
channels = await client.get_channels()
for ch in channels:
print(ch.channel_id, ch.name, ch.amp_enabled, ch.muted)
asyncio.run(main())
The Home Assistant integration lists the library as a requirement, so Home Assistant installs it from PyPI automatically during setup.
Installation
HACS
- Open HACS in Home Assistant.
- Go to Integrations → ⋯ → Custom Repositories.
- Add this repository's URL and choose the Integration category.
- Find Innosonix Amplifier in HACS and install it.
- Restart Home Assistant.
Manual
Copy the custom_components/innosonix folder into the custom_components
folder of your Home Assistant configuration directory, then restart Home
Assistant.
Setup
- In Home Assistant, open Settings → Devices & Services → Add Integration.
- Search for Innosonix Amplifier.
- Enter the host name or IP address of your amplifier (e.g.
192.168.1.50). - Optionally enter a custom API key.
- Finish the flow.
Requirements
- Home Assistant 2024.12 or newer
Metadata
Release files for innosonix 0.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 | |
|---|---|---|---|---|
| innosonix-0.1.2.tar.gz | 19.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| innosonix-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.3 kB
Release files / innosonix-0.1.2.tar.gz
| Download URL | innosonix-0.1.2.tar.gz |
|---|---|
| Size | 19.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a9c0ba9fe72df940bd8300d2a7b85ea9297fa020c8fe8bca03439f3474a76fff
|
|
BLAKE2b-256 checksum How to use checksums |
47e95e9af6c9a336b996b8e3d36006a08c2f34cdb194be4d23e46ebb1d18163d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logRelease files / innosonix-0.1.2-py3-none-any.whl
| Download URL | innosonix-0.1.2-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
245c1402ddd3b48949b09761d7ef1ce4f3e796a58402b30c37069b8361d2f2cf
|
|
BLAKE2b-256 checksum How to use checksums |
d785bc2cb2437cf9aad960d9f389d339f7c316753a5fc710b501af6057aacd6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logSecurity for innosonix 0.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for innosonix-0.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 Oct 23, 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.