I have a RX V-2700… Yeah pretty old but it does have an ethernet connection and I have streamed music to it in the past. Long ago I lost the remote, and I don’t recall if I left it to use DHCP or assigned an iP to it manually. I have been searching for its IP.
Can anyone tell me if it answers pings?
Any tricks to find the IP or reset the machine to factory default so it will get a new one?
Perfect, thank you! I’ll try that when I get home this evening. Hopefully it will come up and acquire a new IP via DHCP and I’ll find it.
A new remote is over $80. I found a compatible remote on Amazon for about $40 but even then, I’m probably replacing this receiver and hate to spend more on it before I do. I have used it for years without the remote!
UPDATE: Actually it can just reset the network parameters. I’ll try that first.
Use an HTTP query tool to figure out what the right syntax is for Zone 2 (below we’re querying for the main zone). You’d need to send the following command to the receiver. I personally use Postman: https://www.getpostman.com/
TYPE: HTTP POST
URL : http://<RECEIVER_IP_ADDRESS>/YamahaRemoteControl/ctrl
BODY: <YAMAHA_AV cmd="GET"><Main_Zone><Basic_Status>GetParam</Basic_Status></Main_Zone></YAMAHA_AV>
Just a note that I’ve updated the icons in the Device Handler… some of them will take automatically but others will require that you update the Device Handler code… just pull the latest from GitHub and your screen should look like this:
So, I have this working with my RX-V671. Power, mute, and inputs work. What doesn’t work well is volume. When it does respond, it does so seconds later. The Yamaha store app is instantaneous, however. Anything you can think of that I might have done wrong?
Ok so an update… I have this connected through google home. When I tell it to turn up the volume, it does so immediately. Im wondering if the delay is through the UI??
I ran into this issue before I published and fixed it, but somehow the fix didn’t make it into the repo… in any case, to fix the volume problem, update line 153 of the device handler. Latest device handler is in github.
Nice. I was wondering why the volume control was sketchy. Looks like you had to get rid of the decimal points.
I’m using this to control my receiver using voice commands with Google Home. One oddity, probably from google treating this as a dimmer, is if I tell it to increase volume, it cranks it to 100%, so that’s not very helpful. I set the volume limiter on the receiver to a reasonable level so that it doesn’t destroy anything, but I’m thinking I can do better.
If I tell Google Home to set the volume to 40%, 45%, or 50%, those are good volume levels, so I’d like to set he highest level to 55%.
It looks like “value * 9 / 5) * 5 - 800” is doing that scaling. If I want to give this volume control a limit of 55%, do I need to adjust this equation? Is there a better way?
Is there a way to decrease the time it takes for the app to recognize a change in the receiver? If I turn off the receiver the it still shows that its on in the app. I would like to use the receiver turning off to trigger other events.