New Transmission add-on thread

DiWa wrote:

I also take this opportunity to submit another improvement on these scripts: automatically pickup host, port, user and password from settings.json This will ease deployment and avoid issues because one has forgotten to update these files with the right user, port and password. The port is already retrieved in the TRANSMISSION startup script. The only issue I see is when the password is encrypted in settings.json, can we pass the encrypted version to transmission-remote ? Thanks

This is what I've setup (only the encrypted password is not working :( ):
File include-connect.sh

#!/bin/sh
# *************
# transmission connect
# *************
# Variables
#
# Path to transmission-remote
REMOTE="/usr/local/bin/transmission-remote"

# Port to acces transmission-remote
TRANSM_PORT=`cat /c/addons-config/Transmission/transmission-daemon/settings.json | grep "rpc-port" | awk -F " " '{ print $2 }' |  awk -F "," '{ print $1 }'`
# User to acces transmission-remote
TRANSM_USER=`cat /c/addons-config/Transmission/transmission-daemon/settings.json | grep "rpc-username" | awk -F ": \"" '{ print $2 }' |  awk -F "\"," '{ print $1 }'`
# pwd to acces transmission-remote
TRANSM_PWD=`cat /c/addons-config/Transmission/transmission-daemon/settings.json | grep "rpc-password" | awk -F ": \"" '{ print $2 }' |  awk -F "\"," '{ print $1 }'`

# Options to be passed to transmission-remote
TRANSOPT="localhost:$TRANSM_PORT -n $TRANSM_USER:$TRANSM_PWD"

Then in transtart.sh

#!/bin/sh
# *************
# transmission start  by super-poussin
# *************
#
. ./include-connect.sh
# *************
LIST=`cat /c/addons-config/Transmission/downloading.txt`
for ID in $LIST; do
    $REMOTE $TRANSOPT --torrent $ID --start > /dev/null
done

If someone have an idea for the encrypted password it would be great

Thanks