Yes, I could, however, I didn't do it because if you can access EventGhost you should be trusted already.kalia wrote:Could you make the password text box hidden (masked with asterisks)?
me a drink 
The plugin is designed the way that you first create a host (e.g. in autostart) and send commands when you need to.Luca Brasi wrote:I was wondering how you guys run things.
Do you add the host in your Autostart and have it run/connected all the time or do you add and delete the host for any command you issue to the ssh box?
You should split your macro in two:Luca Brasi wrote:If so how do you handle the timing? I had to put in some serious waits to get it working like that.
It should reconnect when it's kicked, doesn't it?Luca Brasi wrote:Without that I guess the server would kick the connection after its default timeout.
Hmm... No, I don't see the benefit of creating another GUI action for that.Luca Brasi wrote:Oh and if I might add something to the wishlist... it'd be cool to be able to send a series of commands from an action. Maybe a number of commands set in the actions config or from a file. I tried to do it like 'command a; command b; ...' to no avail.
Code: Select all
commandList=["command a","command b"]
for item in commandList:
eg.plugins.SSH.RunCommand(item, u'host1', False, False, False)After setting it up like this I saw how nice it works that way. As my target is a 24/7 rpi I don't even have to think about reconnects but I am sure it'd handle those as well.The plugin is designed the way that you first create a host (e.g. in autostart) and send commands when you need to.
Of course this leads to an always open ssh session, but that shouldn't be an issue.
The Plugin recognises if the host is not available and reconnects as soon as it becomes active again.
The big advantages of keeping the session open are:
-You can pass a series of commands within one session
-It's much faster, as the session doesn't need to be started again
-It has a lot less communication overhead while processing commands, as the session doesn't need to be started every singel time
I've put the create host action in the start action for my htpc.You should split your macro in two:
macro 1: is triggered by your event and only Creates the ssh host
macro 2: is triggered by the "connected" event from the ssh plugin and contains all your ssh commands.
Funny, I should have checked that. I went straight ahead and disabled the timeout on the rpi.It should reconnect when it's kicked, doesn't it?
Oh yeah, thanks, that comes in handyHmm... No, I don't see the benefit of creating another GUI action for that.
You can write a script that does that very easy:
Code: Select all
commandList=["command a","command b"]
for item in commandList:
eg.plugins.SSH.RunCommand(item, u'host1', False, False, False)
me a drink me a drink me a drink me a drink