Maxx Control (MaxxControl)

Maxx Control (MaxxControl): per-amplifier web UI and open REST API. Control one amp in the browser; use Maxx Remote when you need multi-amp projects.

Maxx Control (also written MaxxControl) is the control surface built into every Innosonix amplifier: a browser web UI plus an open REST API on the device. Use it for one amplifier when you want local control with no desktop install, or when a media-control / home-automation system should talk to a single amp. That includes micro MAXX — same webpage and API as other MAXX models. For many amplifiers, rooms/groups, and offline projects, use Maxx Remote instead.

When to use what

NeedTool
One amp, quick local tweaks, no installMaxx Control (this section)
Many amps, rooms/groups, offline projects, undoMaxx Remote
Network / IP / firmwareIDFM first

Access (brief)

  1. Set a reachable IP (and hostname) with IDFM, or use the address shown on the device front panel.
  2. Open the UI in a browser: http://<ip>/ (many networks also accept http://<hostname>.local/).
  3. On-device REST documentation (full OpenAPI / Swagger): OVERVIEW page → REST API DOC (lower right), served as http://<ip>/…/doc/maxx_rest_api.html.

HTTP is on port 80. The API base path is /rest-api.

What this docs site covers

This section focuses on REST API usage for integrators and third-party systems, plus third-party plugins that wrap that API.

Start here

  1. REST API overview — auth, hierarchy, OPTIONS, where the full schema lives
  2. REST API use cases — mute, volume, status, save, EQ, and more under Common use cases
  3. AES67 / SDP subscribe — patch a channel to an AES67 / SDP stream
  4. Third-party plugins — Q-SYS, Loxone, and similar (single device each)

REST API

Maxx Control REST API on each Innosonix amplifier: auth, hierarchy, OPTIONS, AES67 / SDP subscribe, and where the full OpenAPI lives.

Third Party Plugins

Third-party plugins that use the Maxx Control REST API against a single amplifier.