I have a third party control system (Control4) that I've written a Plex control driver for (actually, really just completed/repaired the work of several others). In any case, it's based on the "HTTP API/Control" section of the wiki and works perfectly.... except with RasPlex.
I suspect this is due to changes in the control protocol - but it's so simple that I'm not at all sure what could have possibly changed (given that the plex iOS control client works just fine for both OSX and RasPlex players)
Note that RasPlex (which is using the version 0.9.9.7 plex stream) reports a bit more information to the server than the current 0.9.5.4 build:
Before I call upon tcpdump to tell me what's different, I thought I'd post here to see if anyone had some guidance.
If RasPlex is based on XBMC 12 (Frodo) or newer (I don't know because I've only done XBMC dev work, not Plex), then the HTTP API would no longer work because it's no longer present. The XBMC developers removed the HTTP API in Frodo, so you have to use the JSON-RPC API instead.
The transition is unfortunately rather jarring, but the JSON-RPC API is pretty well documented. Probably the easiest way to learn to use the API is to download a REST client extension for either Chrome or Firefox and give it a go.
Out of curiousity, how well does Control4 integrate with Plex when it's working? I've been toying around with developing an XBMC addon to eliminate the need for a Crestron or AMX system and allow XBMC to directly control all the room components.
