Yamaha's whole AVR line — RX-A, RX-V, RX-S, TSR and HTR series — shares one control protocol: Yamaha Extended Control (YXC), an HTTP API under /YamahaExtendedControl/v1/ on port 80. That is why a single app entry covers the entire family instead of a per-model list.

Discovery is SSDP-based: the receiver's desc.xml must contain <manufacturer>Yamaha</manufacturer> and an X_yxcControlURL entry. Remote97 also probes port 80 (and 8081–8084 as fallback) to catch receivers that do not advertise reliably.

What you can control

Set it up

1

Enable Network Standby on the receiver

This keeps the YXC endpoint alive while the unit appears off. Without it, the receiver will not answer after standby.

2

Install Remote97 and join the same LAN

Download from the download page.

3

Run discovery

SSDP finds the receiver and confirms the manufacturer tag; a direct port-80 probe is used as a fallback.

4

Or add the IP manually

Useful on managed switches or VLANs where multicast discovery is filtered.

Why this beats a cloud-based remote

YXC is a LAN protocol. Commands do not leave your router, response times are a few milliseconds, and the remote keeps working during an internet outage. There is no account to create and no subscription for "premium" volume buttons. See why local IP control beats cloud hubs for the longer explanation.

Note: the older YNCA serial-over-IP style protocol on port 50000 is a different interface and is not used here. If a Yamaha device only answers on 50000, it will not appear as a YXC receiver.

Troubleshooting