Reply to thread

Message: <blockquote data-quote="joz" data-source="post: 661539" data-attributes="member: 70244">Re: HTPCInfo plugin for MediaPortal v1.0.7Sure,However the big part (the whole play button handling) is scripted in Eventghost, not really like normal scripting goes but dragged and dropped some stuff (that's how Eventghost works, really powerful), I can share my eventghost xml config file if you'd like (@ work still atm).What I can dig up for you atm is poweroff commands;The last one will only work if you have poweroff running on the NAS (as a service or just the default client GUI is running), you have configured it for remote access (set a pass etc.). You can even change ports, did not need that but you can look that up in poweroff help.Now for the Eventghost part I can describe how I did things;- Both: Setup eventghost on both sides (client + server)- Both: Add the plugins; * network event receiver * network event sender- HTPC: Capture the play button (for me MCERemote.play event)- HTPC: Create a macro with that event (reffered to as IsNasOn)- HTPC: after the event add a network event sender with a variable (I named mine isNasOn)- HTPC: add 2 "jump" commands, the first one to be triggered on success and jumping to some macro which will emulate the "p" press, The second on fail and jump to a macro which will send a WOL packet.- HTPC: For the WOL macro you just add the eventghost WOL command, and add a always jump to IsNasOn macro (to recheck if the NAS is on already, you can add a sleep in between to not have too heavy load)- NAS: Create a macro with the isNasOn event trigger on the server side and send back some value. Which ofcourse will not be send when the NAS is off, so that explains the 2 jump commands (the failure will be triggered within I think 2 sec, so no long waiting. If it receives something from server the success will be triggered instantly so that also introduces a small lag (under a second, need a roundtrip to the server in order to determine server state))Quite a lot, took a while to get right but works pretty solid for me (I left non essential stuff such as sounds out for simplicities sake). If you are really interested in this solution PM me and I'll send you an anonimized version of my eventghost xml definitions</blockquote>

Verification