What it is
No Hassle AV controls a No Hassle AV eight-input, eight-output HDMI matrix that uses the HTTP /video.set protocol. It creates eight output selectors with your own input names, an Outputs: All selector that sends one input to every output, and Power on and Power off buttons. This guide describes the published v0.4.2 release.
The selectors show the routes the matrix last reported, including changes made by another controller. A failed status read normally makes them unavailable rather than showing an old command as current. The exception is a short grace window after a command: for 5 seconds after a routing command, and for 60 seconds after an accepted power command if the matrix had answered before, a failed read keeps the last reported routes. Those retained routes are not a new confirmation from the matrix. It is the matrix half of a pair; the amplifier is the separate No Hassle AV Amplifier integration.
My Setup
I route several sources to several displays and AV receivers with No Hassle AV. Version 0.4.1 failed my initial routing test. Version 0.4.2 passed my limited hardware acceptance checks for routing, power cycling, and recovery from network loss between November 5 and 7, 2026. This testing applies only to my own hardware and does not establish compatibility with every matrix.
Built around how the matrix reports
The matrix answers a status request with nothing useful almost every time and sends its full routing report once after a route changes. The integration polls every 15 seconds and a few times right after each command, and shows the routes the matrix last reported.
Built around the matrix's pauses
On the tested unit the matrix refuses connections for up to about a second after accepting a command, and power on takes its web server down for 8 to 45 seconds. The integration waits these out, keeping the last reported routes for a short time instead of marking everything unavailable.
Why I use it this way
A matrix with almost no feedback is easy to show wrongly. Apart from the short grace windows after its own commands, the integration marks the selectors unavailable when the matrix does not answer, instead of guessing.
What it can do
Per-output routing
Eight output selectors with your own input names, showing the device-reported route.
One input to every output
Outputs: All sends the chosen input to all eight outputs with one command, and shows a source only when all eight reported routes agree.
Explicit power commands
Power on and Power off send a command without assuming the current power state.
Strict replies
Replies are size-capped and strictly decoded, so a corrupted or unexpected response fails the poll instead of being trusted.
Install and connect
Before you start
- A No Hassle AV eight-input, eight-output matrix that uses the HTTP /video.set protocol. Other models and protocols have not been verified.
- Network access from Home Assistant to the matrix's HTTP port.
- Home Assistant 2026.9.4 or newer.
Install from the Marketplace
In Settings > Marketplace, search for No Hassle AV and select Install. If the integration can load right away, its setup opens; otherwise a repair asks you to restart Home Assistant. Before Home Assistant 2026.11, search for it in HACS, download it and restart.
Add the matrix
In Settings > Devices & services, add No Hassle AV and enter the matrix's address, its HTTP port and eight distinct input names. Setup saves the address without switching any output.
Upgrading from 0.2.x or 0.3.x
Follow the project's upgrade steps before updating. Older versions shipped in place of the built-in Monoprice integration, and keeping entity IDs needs an import step on 0.3.2 first.
Check the outputs
Rename the output entities to match where they go, and check the routes after the matrix is powered on.
Limits and caveats
- During the short grace window after a command, a failed status read keeps the last reported routes. Those are not a fresh confirmation from the matrix.
- After a Home Assistant restart the selectors show Unknown until the next route change or until someone opens the matrix's web page.
- If the matrix's own web page is open, it can take the routing report, and Home Assistant keeps showing the old route until the next change.
- There is no reliable power feedback over HTTP, so the Power sensor stays Unknown by design. Only HTTP is used; the RS-232 port was not tested.
- In one test the routes read differently after a power cycle, so check outputs after powering the matrix on. Reboot and factory reset are not exposed.