Your scenes, running without your phone

Most integrations make your phone the middleman: the phone hears the command, the phone sends it, and the automation only works while the phone is awake and on the network.

AVR Maestro does not do that. It compiles your scenes into scripts that live on your hub, and the hub sends the commands to your receiver's local IP. The app's job ends when the sync finishes.

• Local-first: nothing is routed through a MiyaraHub server. Your hub and your receiver talk to each other.
• Phone-independent: once a scene is published it runs whether or not the app is installed on the phone that made it.
• Your assistant, not ours: Alexa, Google Assistant and Siri Shortcuts all reach these scripts through the hub you already trust. AVR Maestro adds no voice layer of its own.

• 1. Add your receiver to Home Assistant first. Settings › Devices & Services › Add Integration › Denon AVR (or HEOS), then your receiver's local IP. Home Assistant creates a media player entity for it.
• 2. Open Settings › Home Automation in AVR Maestro and tap the Home Assistant card.
• 3. Enter your Home Assistant address - a local one like http://192.168.1.150:8123, or your external Nabu Casa URL.
• 4. Log in and authorize. A secure in-app browser opens Home Assistant's own login. Your credentials go to Home Assistant, never to us.
• 5. It finds your receiver by itself. The app scans your media player entities and scores them on model, name and surround capability, then fills in the right entity for you.
• 6. Sync. Your scenes are built into scripts and uploaded. After that, editing a scene updates its script in the background - there is no button to remember.

Once it is synced

Build a dashboard worth looking at

Home Assistant now has a control for everything your receiver can be told to do, and no opinion at all about how to arrange them. The dashboard example is one arrangement with the full YAML: source and surround tiles that light up when they are the live one, volume in real dB, your Scenes reading their own names, and an honest map of what Home Assistant can and cannot see.

Not just scenes

Speaker Presets, Dirac and Audyssey, too

Turn on Sync Advanced Controls and the app publishes a script for far more than your scenes: every Speaker Preset, every Dirac Live filter slot, each Audyssey curve. A full sync on a Cinema 30 lands over seventy scripts, so a dashboard button or a voice command can load a Dirac filter or switch the room curve the same way it recalls a scene.

It reads, not only writes

Home Assistant can see what is active

A script can be run but never read, so early dashboards could switch the Audyssey curve or the Dirac slot with no way to show which one was on. The readings the app already holds - the live surround mode, the active Dirac filter, the speaker preset, the dimmer and dozens more - now publish as attributes on the receiver's status sensor, so a tile can light up for the setting that is actually running.

Home Assistant and Hubitat send commands to the receiver. Webhooks go the other way: when the receiver does something, tell anything else about it. Turn the receiver on and AVR Maestro posts a small message to an address you choose - that message is the webhook.

The four triggers

Narrowing is what makes them useful rather than noisy. "Active Input Changed" on every input is a firehose; the same trigger pinned to the one input your projector sits on is a light switch.

The input list is the one your own receiver reports, so it already reflects any source you have renamed or hidden. The scene list is your own scenes.

This is the Home Assistant route, which is the one most people want. Do the Home Assistant half first - the app needs something to point at.

In Home Assistant

• 1. Settings › Automations & Scenes › Create Automation › Create new automation.
• 2. Add Trigger › Webhook. Home Assistant generates a long random Webhook ID for you.
• 3. Replace it with something you will recognize - avr-power-on, avr-movie-night. Any name works as long as it is unique on your Home Assistant. Write it down; you type the same one into AVR Maestro.
• 4. Under the webhook's settings, allow POST. That is what AVR Maestro sends. Local-only is fine - the app is on your own network.
• 5. Add whatever you want it to do - dim the lights, close the blinds, start a scene - and save the automation.

In AVR Maestro

• 1. Settings › Home Automation › Webhooks, then Add First Trigger - or the + button once you have one.
• 2. Trigger Event - pick what should set it off. Choosing Active Input Changed or Scene Recalled adds a second box to narrow it down.
• 3. Where to send it - leave it on Home Assistant. The address is already known, because you linked it earlier on this same screen.
• 4. Webhook ID - type the same ID you used in Home Assistant. Nothing else has to match. Underneath, the app spells out the exact address it will post to - Sends to http://your-ha:8123/api/webhook/avr-power-on - so you can check it before you save.
• 5. Save. Then press Test on the trigger in the list. Your Home Assistant automation should run immediately.

Sending somewhere that is not Home Assistant

Switch Where to send it to Other and paste a full URL into Webhook URL. Anything that accepts a POST works - a Node-RED flow, an IFTTT applet, a script on a NAS, a Hubitat Maker API endpoint. That route stores the address exactly as you typed it, so if the destination moves you edit the trigger.

A small JSON body. The What it sends card on the same screen says it in plain language for the trigger you picked, so you never have to guess - and these are the field names your automation reads:

In a Home Assistant automation those arrive as {{ trigger.json.event }}, {{ trigger.json.source }} and so on. You can read them, or ignore them completely and just act on the fact that it fired. Most people do the second.

If you need a different shape - a service that expects its own format - open Send my own JSON instead under that card and write it there. It is folded away and marked Advanced because almost nobody needs it, not because it is discouraged.

In the order worth checking, because the first two are almost always it:

• Press Test first. It sends the same message the real trigger does, to the same address, and tells you which of three things happened: delivered, not delivered, or skipped because the trigger's own switch is off. If Test delivers and the real event does not, the problem is the trigger - most often an Active Input Changed narrowed to an input you are not actually switching to.
• Check the ID matches exactly. Home Assistant webhook IDs are case-sensitive and do not tolerate a stray space. The app prints the full address it will post to underneath the field - compare it with the one in your automation.
• Check the automation allows POST. A Home Assistant webhook trigger that only allows GET silently ignores what AVR Maestro sends.
• Check the trigger's switch is on. Each one has its own toggle in the list, and a switched-off trigger is skipped rather than failed.
• Triggers belong to one receiver. The list you are looking at is the list for the receiver currently selected. Another receiver has its own, so a rule made here does not fire for a different room.
• The app has to be watching. AVR Maestro is what notices the receiver changed, so nothing fires from a phone in your pocket with the app closed. That is the trade-off described at the top of this section, not a fault.
• Webhooks are part of Home Automation. Without that unlock the triggers are visible but nothing is sent, and Test says so rather than pretending it worked.