(4th Jun, 2013 08:44 AM)zilexa Wrote: [ -> ]I was actually just looking for a solution to get this working without installing anything extra... and I think the wget solution is the way to do it since it works via SSH after I login in the RPi! It only does not work when the script is executed via Transmission 
yes, sorry, I was so lazy open ssh terminal that I did it from macosx terminal. and there telnet still is.
why I chosen telnet is the fact, that all three (telnet | curl | wget ) are providing you the same. connecting to port 8080 (xbmc) and running while running html get command (what on xbmc side will run the update process). from the tree is telnet the simplest desto minimum possibilities to get the command wrong specially when passed through more shells and command line preprocessors. if the curl (wget) command works for one path (from shell directly) but doesn't when calling from scripts from transmission that means exactly why I chosen (as demonstration) the telnet way.
i mean, the only problem must be nessed all the {}[]"'\%#$ in the command, what will cause different interpretation at xbmc.
btw: I know you don't ant to install anything else, but XBMC supports receiving remote events directly on port 9777. There is nice and small (in perl written) toolchain - it's by default supplied in binary for MacOsx, for linux you can get it at
http://wiki.xbmc.org/?title=EventServer (point 9.1) at the bottom.
it's few kb, doesn't need nothing else as standard perl / python (no extra modules or other shits) and as a result, you will have one .py script which works like:
Code:
xbmc-send [OPTION] --action=ACTION
Example
xbmc-send --host=192.168.0.1 --port=9777 --action="XBMC.Quit"
Options
-?, --help Will bring up this message
--host=HOST Choose what HOST to connect to (default=localhost)
--port=PORT Choose what PORT to connect to (default=9777)
--action=ACTION Sends an action to XBMC, this option can be added multiple times to create a macro
you can't go wrong with that.
and going back to your
http://forum.xbian.org/thread-479-post-9990.html#pid9990 post, the easy to remember solution how to get all the parameters, but we don't know syntax/names is to temporarily call such script as a hook to transmission:
echo $(env) >> /tmp/list.environment.txt
then you would just look into the file and you will see all the variables which transmission is passing to your scripts ...
)