Skip to main content

Innosonix Amplifier integration for Home Assistant

My Home Assistant PyPI

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 sensors: master volume, PSU voltage, PSU load
  • Device health: error / warning problem binary sensors
  • Per-channel switches: amplifier enable and mute (all channels)
  • Per-channel volume: number entity in dB (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)
        print("master volume (dB):", await client.get_master_volume())
        print("psu:", await client.get_psu_status())
        channels = await client.get_channels()
        for ch in channels:
            print(ch.channel_id, ch.name, ch.amp_enabled, ch.muted, ch.volume)
        await client.set_channel_muted(1, True)
        await client.set_channel_volume(1, -6.0)

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

  1. Open HACS in Home Assistant.
  2. Go to Integrations → ⋯ → Custom Repositories.
  3. Add this repository's URL and choose the Integration category.
  4. Find Innosonix Amplifier in HACS and install it.
  5. 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

  1. In Home Assistant, open Settings → Devices & Services → Add Integration.
  2. Search for Innosonix Amplifier.
  3. Enter the host name or IP address of your amplifier (e.g. 192.168.1.50).
  4. Optionally enter a custom API key.
  5. Finish the flow.

Requirements

  • Home Assistant 2024.12 or newer

Metadata

Release files for innosonix 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for innosonix 0.3.0
File Size Uploaded Provenance
innosonix-0.3.0.tar.gz 23.0 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for innosonix 0.3.0
File Interpreter ABI Platform
innosonix-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 31.9 kB

Release files / innosonix-0.3.0.tar.gz

Download URL innosonix-0.3.0.tar.gz
Size 23.0 kB
Tags Source
SHA-256 checksum
How to use checksums
ea172be13d1b722b57f2a7776bef107104ff4e10ad61a6b5cb628e2a0f4513c2
BLAKE2b-256 checksum
How to use checksums
612dce73fe3d0bfdb349dec26f003028c2b92dd9771bd4623529394951540876
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 24, 2026.

Transparency log

Release files / innosonix-0.3.0-py3-none-any.whl

Download URL innosonix-0.3.0-py3-none-any.whl
Size 8.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
07c14854c55ade757e56136535377b06f505a195492749f98e89ca08ce79c090
BLAKE2b-256 checksum
How to use checksums
3711748c2d413e51a297df4b478c2fba6061499e701a4e490f812493bb22f5b0
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 24, 2026.

Transparency log

Security for innosonix 0.3.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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for innosonix-0.3.0.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 24, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page