Also interested in the advanced api, @badsl and also interested in binding, but also no experience with creating. Maybe we can modify or expand the existing yamaha if it is indeed semi-compatible ?
Yes, the existing yamaha binding, or maybe the sonos binding could be a good point to start.
I will have a deeper look on it comin weekend (girlfrind is not at home 
). With enough time it should be no big problem… I hope i will find a way into it, and then share it on github so that you guys can help and improve.
You got mail 
Thanks!!
Hey Guys,
see attached the Basic and the Advanced API documentation in the current revision. The Yamaha UK Support provided them to me and asked me to mention that it is only intended to be used by AV Professionals if i share it. DONE
I really hope that we get that ball rolling now. Using the API calls via HTTP Binding and parsing via JSONPATH works like a charm. However a centralised Binding would be way nicer especially when looking at the Advanced API.
YXC_API_Spec_Basic.pdf (987.4 KB)
YXC_API_Spec_Advanced.pdf (561.7 KB)
3 Likes
Ah nice something going forward here.
I wasnt in the community for some time now.
Thanks for sharing the advanced spec, that was missing in my documents.
I am really excited about the ongoing process.
If there is a well starting point on github i hope that i am able to help you out not only with testing.
I work on Python implementation of Yamaha Extended Control API:
1 Like
Could you post your own implementations with the http binding in this Thread?
I am playing around with the http binding and jsonpath myself for my isx-80 radio, but when you already got some solutions it would be nice to share them.
Hey,
im in the process of renewing my whole installation so its actually not productive right now. I can give you two examples:
Number srt1500_volume "Livingroom Volume" (srt1500) {http="<[http://192.100.20.7:80/YamahaExtendedControl/v1/main/getStatus:60000:JSONPATH($.volume)]"}
String srt1500_input "Livingroom Input" (srt1500) {http="<[http://192.100.20.7:80/YamahaExtendedControl/v1/main/getStatus:60000:JSONPATH($.input)]"}
Those are just two quick examples that had proved to be working.
Im actually thinking about doing it without the HTTP Binding and JSON Path. you can directly send http get and put from the rule as well
Ok i see, you ar as far as i am already^^
// Yamaha ISX-80 MusicCast Radio
Switch Yamaha_McRadio_Power "Power [%s]" <switch> (YamahaIsx80McRadio) { http=">[ON:GET:http://192.168.178.34/YamahaExtendedControl/v1/main/setPower?power=on] >[OFF:GET:http://192.168.178.34/YamahaExtendedControl/v1/main/setPower?power=standby]"}
Switch Yamaha_McRadio_Mute "Mute [%s]" <soundvolume-0> (YamahaIsx80McRadio) { http=">[ON:GET:http://192.168.178.34/YamahaExtendedControl/v1/main/setMute?enable=true] >[OFF:GET:http://192.168.178.34/YamahaExtendedControl/v1/main/setMute?enable=false]" }
String Yamaha_McRadio_Input "Eingang [MAP(yamaha.map):%s]" <receiver> (YamahaIsx80McRadio) {http="<[yamIsx80McRadioStatus:10000:JSONPATH($.input)]"}
String Yamaha_McRadio_Volume "Lautstärke [%s]" <soundvolume> (YamahaIsx80McRadio) {http="<[yamIsx80McRadioStatus:10000:JSONPATH($.volume)]"}
Ofc all work in progress here too.
I am just playing a bit around since i still have exams to do which have a higher priority.
If someones interested, have collected some strings from the “getFeatures” api call and collected them for a mapping file:
net_radio=Net Radio
napster=Napster
spotify=Spotify
juke=Juke
airplay=Airplay
mc_link=MusicCast Link
server=Server
bluetooth=Bluetooth
tuner=Tuner
aux=Aux
power=Power
sleep=Sleep
volume=Volume
mute=Mute
I just want to cellect everythign here from scratch, to have as much background as possible when a possible binding development starts.
Again something for the collection:
String Yamaha_McRadio_Cur_Track "Artist: [%s]" <musical_note> (YamahaIsx80McRadio)
{http=
"<[http://IPADRESS/YamahaExtendedControl/v1/netusb/getPlayInfo:10000:JS(getIsxArtist.js)]"
}
String Yamaha_McRadio_Cur_Artist "Track: [%s]" <musical_note> (YamahaIsx80McRadio)
{http=
"<[http://IPADRESS/YamahaExtendedControl/v1/netusb/getPlayInfo:10000:JS(getIsxTrack.js)]"
}
Switch Yamaha_McRadio_prev_next "Play ->" <musical_note> (YamahaIsx80McRadio)
{http=
">[ON:GET:http://IPADRESS/YamahaExtendedControl/v1/netusb/setPlayback?playback=previous]
>[OFF:GET:http://IPADRESS/YamahaExtendedControl/v1/netusb/setPlayback?playback=next]",
autoupdate="false"
}
The Switch is set to autoupdate=false, to use it with two pushbuttons for previous and next track on my playlist.
Switch item=Yamaha_McRadio_prev_next label="Play ->" mappings=[ON="Previous", OFF="Next"]
The Strings are used as a current playing information.
getIsxArtist.js:
(function(i) {
if(JSON.parse(i).input == "net_radio"){
var trackDataArray = JSON.parse(i).track.split(" - ");
if(trackDataArray.length == 2){
return trackDataArray[trackDataArray.length - 2];
}
return trackDataArray[trackDataArray.length - 1];
}
else{
return JSON.parse(i).artist;
}
})(input)
I have separated “net_radio” input, because in this mode the artist element in the json response is for the radio station.
In most stations that i have listened to, the complete song information is stored in the track element with Artist - Track
Works fine for me for some time now.
getIsxTrack.js is doing nearly the same with different json elements.
And i decided to update my power button too, since the current power state was not set correct all the time.
Switch Yamaha_McRadio_Power "Power [%s]" <switch> (YamahaIsx80McRadio)
{http=
">[ON:GET:http://IPADRESS/YamahaExtendedControl/v1/main/setPower?power=on]
>[OFF:GET:http://IPADRESS/YamahaExtendedControl/v1/main/setPower?power=standby]
<[yamIsx80McRadioStatus:10000:JS(getIsxPowerStatus.js)]"
}
getIsxPowerStatus.js
(function(i) {
if(JSON.parse(i).power == "standby"){
return "OFF";
}
else{
return "ON";
}
})(input)
Yamaha distinguishes between on and standby, so i mapped the state to a OH-switch conform way.
Maybe there is an easier way, but i was dealing with many js files anyway and continued it that way. 
Edit for clarity:
yamIsx80McRadioStatus is just a cached url in my http.cfg
Hi guys,
just put the calls from you listetd here (Power ON, Standby and Volume) in a very very draft binding. So feel free to test on your side. Actual push only, so if ou switch of the MusicCast manually it will be not reflected in the Binding. Also no discovery, you have to put in the IP Adress.
Feel free to play with it. When have more time, i will work on it, feedback welcome
Best Frank
Hey Frank,
Power and Volume work fine for my ISX-80 Radio.
Will test the AV-Receiver this week.
Do you have the source files hosted anywhere?
I am no Java Pro, but maybe i can help out with some simple things already.
Anyway thanks for giving this a start.
Hi Frank,
Power works fine with the WX-10 speaker.
Volume will be tested tomorrow
Thanks a lot!
Hi Frank,
works fine with Yamaha WX-030 
Do you share the source file please ;(
Hey everybody,
Is there a way to configure one of the speakers as “Default Sink” like the Sonos speakers ?
Best regards
I would say not at the current state.
I dont know the exact behaviour, but technically you need to turn in the speaker, set the Input and play the Audio Stream.
The current Binding Supports only Power and mute.
I feared. I have already tried to find he appropriate code site from the Sonos binding , but I have not found so far. Anyone some ideas?