Feature Requests

[jay (support)]

As far as I can tell, there isn't enough in your included documentation snippit to determine if that's even going to work. It seems to imply that there is some kind of setup step (the one shown) then some kind of repeated event query (not shown). But I'm just guessing based on the limited information.

If the status API call is made, with the proper header, every 10 minutes, then the Yamaha unit unicast a UDP "status change" packet that I am receiving in my code. I've tested this functionality, but would like to use the GhostXML to make it easier to implement and maintain. I'd need to more or less duplicate GhostXML, and I'm not a plugin developer.

The status API call looks like this:
http://musiccast-zone1.example.com/Yama ... /getStatus

GhostXML is sending this and receiving the device status presently. If it could send this API call with the additional header:
{'X-AppName':'MusicCast/1.71', 'X-AppPort':'41100'}

then this would enable the UDP status unicast I need.

The full spec can be seen by Googling "Yamaha Extended Control API Specification (Basic)". I can't attach the PDF here.

It's a 2 line embedded Python script. How is using the plugin going to be easier than that?

Actually quite a bit more complicated, as the code would need to monitor state on all the returned data, which is what GhostXML does nicely. Receipt of the UDP change update packet triggers a GhostXML refresh. GhostXML maintains all the device state information.

We're back from our week-before-Memorial Day vacation and I've had a little bit of time to think about this.

You might be able to do this now using a custom raw CURL command like this (obviously untested):

Code: Select all

curl -X GET \
  -H "X-AppName: MusicCast/1.71" \
  -H "X-AppPort: 41100"


Or something in that neighborhood. See this page for a known-to-work example.

Initial testing looks good! Thanks! I should have read the raw curl docs, sorry. I was focused on the requests code and went right past it.

Good news. The GhostXML plugin was a collaboration and I think this particular tool was developed by @GlennNZ.