Good idea. I may add a field to the smartapp so I can easily adjust the limit in the future.
Thanks for you help and really thank you for making this.
Good idea. I may add a field to the smartapp so I can easily adjust the limit in the future.
Thanks for you help and really thank you for making this.
Yes! That worked. Thanks!
I really didnt get it working fully in terms of changing the volume level, but I’ll give that link you provided a try. I was more trying to demonstrate how I thought the UI might be a prob…
Btw- I just discovered something and glad I figured out what was going on… In the app settings you can rename the inputs, but when you rename them you also break the link between the device handler. In other words, if you want HDMI1 as your first button, dont rename it in the app but still have it referenced as HDMI1 handler.
@Benjamin_Sell what do you mean? By default every source tile is named Source 1, Source 2, etc. If you want to rename the tiles, you need to just change the label in the device handler code (see Installation step 2) but all this does is change the label on the tile, not the tile behavior.
If you want to change the tile behavior and have the tile control a different source, you do that under app settings (see Installation step 5).
Maybe that wasn’t clear… so here’s an example: if I want the first tile to set HDMI1, I would do the following:
Source 1
to HDMI1
(this just changes the label)Source 1
to HDMI1
(this will tell the tile to set the source to HDMI1)Hope this makes sense…
Not really… the current implementation of this device handler is based on polling, which means that either you have to manually hit the refresh button to poll for the latest state or wait the 5 minutes or however long the SmartThings Hub decides to run a poll on the device.
A workaround which may work for you is through the use of the Pollster smartapp… check it out and let us know if it does the job: "Pollster" - A SmartThings Polling Daemon
If I ever get some time, I may look into moving this to an event based model, which would mean that the device handler would get the updates from the receiver in real-time.
Is RX-V581 model supported by this app ? I’m trying to use “SERVER” as an input to be able to play some tracks on a DNLA/NAS server not too much luck so far. Please help
Not sure… does the volume control work? Can you turn the unit on/off with this app? And I’m assuming you’ve gone into the Main Zone device config and changed the “Source 1” input value to SERVER
? And then it does nothing??
It may be that your Yamaha expects something else for the SERVER
input… if you can help find out what it is, we’ll be able to get to the bottom of it. Try these steps and report back: [RELEASE] Yamaha Network Receiver Basic Integration
Looks like none of the controls have any effect from within the App. I’ve setup Zone_B and added it into the App as per one of your earlier instructions. Attaching reply from the receiver via POSTMAN:
https://dl.dropboxusercontent.com/u/75329471/Yamaha%20RX-V581.txt
Great you got Postman setup… from the looks of it, the syntax is a little different. Couple things…
TYPE: HTTP POST
URL : http://<RECEIVER_IP_ADDRESS>/YamahaRemoteControl/ctrl
BODY: <YAMAHA_AV cmd="PUT"><Main_Zone><Power_Control><Power>On</Power></Power_Control></Main_Zone></YAMAHA_AV>
TYPE: HTTP POST
URL : http://<RECEIVER_IP_ADDRESS>/YamahaRemoteControl/ctrl
BODY: <YAMAHA_AV cmd="PUT"><Zone_B><Power_Control><Power>On</Power></Power_Control></Zone_B></YAMAHA_AV>
Looks like I can control Main Zone On/Off…nothing happens for Zone_B Here are the results from the POSTMAN:
https://dl.dropboxusercontent.com/u/75329471/Yamaha-RX-V581-Nov22.txt
Just got the RX-V679… So happy to see you’ve been working on ST integration! The above install works great; I modified Source 1 and Source 2’s tile names in the device handler to “TV/Optical” and “Pandora” (tile names), with “AV1” and “NET” as the respective app-configured sources.
NET wasn’t in the supported sources list, but I tried it on a whim, and sure enough, it works to pull presumably whatever your last selected net-app was. So, at least for the RX-V679, you can add NET to the acceptable input sources!
Keep up the good work!
Great to hear… also wanted to share that I just pushed updates to the SmartApp and device type to support Zone_B.
@kmmanley Thanks to help from @Oleg_W we now have support for Zone_B… for those receivers that have a Zone_B (not a Zone_2, Zone_3, etc) just update the SmartApp and device type code and setup your zones again. You should be good to go!
No in the code, but in the actual UI settings you can rename the inputs. I thought that was the reason that some of the buttons werent being being recognized. I obviously could be wrong there…
So, in the handler I had SOURCE 1 as HDMI1, but in the UI I had SOURCE 1 named as “AndroidTV”. When I changed them to match the handler it worked fine.
Yeah that’s right… in the device config, you actually set each source… so SOURCE 1 = HDMI, etc.
And then if you want to actually change the labels in the UI, you need to change them in the device handler code… so where label:"Source 1"
it would now read label:"Android TV"
And that should do it.
Just got this running, great! How would I make an automation task to select a specific input? It will power on, but since it’s a ‘switch’ I can’t figure out how to set the input.
Use the CoRE rules engine… you can select the inputs through it’s rules builder.
Great, thank you!
First let me say that this is awesome! I figured out a way to tell if my rx-a3050 was online or not by using another community app called Host Pinger. This was good because I could make if-then scenarios based on whether or not my AVR was on like if AVR is not on then wait 30 minutes then put PC in hibernation (accomplished by Event Ghost).
Now this has completed my AVR home automation! Along with Alexa, Harmony and now this App, I can create virtual switches that set perfect whole house scenes and volumes!!!
Alexa, set volume to 30%! Hell Yeah!!!
Thanks again!