What is the Best* Plugin to Forward Events to Another EG?

[justahotbag2]

I've search the forums and found no clear or clarifying answer so I'm posting a new topic, I imagine I'm not the only one looking for this answer.

I'm trying to send events from a netbook running EG 0.5 to a desktop running .4r1722, probably not important details.

Either all events, if that's easiest, or plugin by plugin. I imagine users would find both answers useful.

A forum search netted me this lead "MQTT (mqtt plugin), HTTP (webserver plugin) or TCP (TCP plugin) to get the event transferred to the other PC."
Perhaps there are others, either way no plugin I've tried is plug and play, they seem to require some command be entered.
If you can share that command, perhaps could you also share how you figure these things out, many of these plugins lack instructions.

Also, since I suppose the answer will be it depends.
Which plugin(s) are most efficient?
By efficient I mean least use of resources. Is the file size of the Init.py script even remotely indicative of this?

Also another best* definition could be feature rich, i.e. provide filtering, as in sending only plugin created events and perhaps not things like system idle (might be cluttering I don't know have not gotten this to work, just a layman's assumption.)

Thanks for any advice, in advance.

[kgschlosser]

So if you want to forward all events and payload data then TCP events is the way to go.

If you are running EG 0.5 you can simply achieve this with one macro. You would create a macro to use TCPEvents Send Event action. And in the event field key in {eg.eventString} and in the payload field {eg.event.payload}

Make sure you include the curly braces. Then enter the connection specific information. Then drag and drop any event from the log panel into the macro. Then edit the event and change it to * and nothing else. This will grab every single event and pass it to your other computer. You also have to have the TCP events running on the remote EG as well set with matching passwords

[blaher]

I use a single Python Command of:
import urllib; urllib.urlopen('http://192.168.0.19:8082/?EventName')

where 192.168.0.19:8082 is the IP:Port of the machine you want to send to. Dunno if it's efficient or not.

[kgschlosser]

I use a single Python Command of:
import urllib; urllib.urlopen('http://192.168.0.19:8082/?EventName')

where 192.168.0.19:8082 is the IP:Port of the machine you want to send to. Dunno if it's efficient or not.

and you have the webserver plugin installed on the receiving computer yes?

[Sem;colon]

Well, I did create a plugin that just sends all events from one PC to another, to be able to process them centralized, but in your case the solution kgschlosser suggested with TCP should be the best and easiest.

[blaher]

I use a single Python Command of:
import urllib; urllib.urlopen('http://192.168.0.19:8082/?EventName')

where 192.168.0.19:8082 is the IP:Port of the machine you want to send to. Dunno if it's efficient or not.

and you have the webserver plugin installed on the receiving computer yes?

Yes, kind of an important detail! Whoops

[kgschlosser]

@blaher

OK i just wanted to make sure you could have made something up on thew receiving end. I figured it was important to know.

[justahotbag2]

Nice to "meet" you gentlemen (sem;colon, blaher), (I've been a lurker for many years and quite familiar with your names.)

@kg did you mean TCP Events by miljbee? If so, I have tried 4 versions of it (twice over) under 0.5 and it errors out immediately. My experience watching you work, tells me you probably fixed the darn thing and forgot/skipped along/whistled while you work, that you did? or perhaps you meant the native TCP sender?..

going to try all methods mentioned and watch the netbook memory for a while and post back my results. The whole system has 1GB of memory.
(I have a small bag of so-dimms that I have been hunting for over a year, it's one of those situations; where I could buy a 2GB stick and max it out, but It's the principal that I already hoarded old memory sticks and that hoarding, shall not have been done in vain!)

@Sem;colon what is your plugin called? Pretty sure, you have more than one...

[kgschlosser]

@justahotbag2

I was referring to the one by miljbee. and it works fine for me under EG 0.5 the only thing that is different is how to parses the payload. no need to enter the curly braces {}
prefix = {eg.event.prefix}
suffix = {eg.event.suffix}
payload = eg.event.payload

give it a shot locally. reinstall the thing. pick a port and a password.
then make a new macro and select the Send and Event action. enter the port from above and the password as well.. put in anything you want for the rest of it and click on test

I know there is an issue with android applications and TCPEvents. but the issues are not with TCP events. they are with the application. the applications are only made to work with network event sender and receiver. and not with TCP events. and the way the app handles an additional space before a specific bit of communication is what is causing the issue.

TCPEvents was designed to speak with either it's self or network event sender or receiver. not any other piece of software that uses the protocol. this is due to how the software is designed. if it is designed properly then it can deal with it. as an example of EgiGeoZone app for android. there is an eventghost plugin for that that I helped with and it will work with both TCPEvents and the Network Event Receiver. But for EG to EG network communications. TCPEvents works just fine and is the way to go.

[justahotbag2]

Are you telling me there hasn't been a semi-mass breakage of plugins, due to changes in EG 0.5?
Question #2 Might there be/have you heard of issues with certain plugins if importing a 0.4 egtree into 0.5?

It's 100% of the reason I haven't switched, I was convinced that was the case, when I saw like 20% of my used plugins produce errors/"report unknown" on startup.

[kgschlosser]

The only things I have come across as far as plugin breakage has been with the the dialogs and not the actual functionality of the plugin. there has been one here or there that has had issues not relating to the dialogs but nothing that wasn't fixable.

MCERemoteVista - Dialog
SchedulGhost - Dialog
USB-UIRT - Dialog
StandbyControl - Dialog

Network Broadcaster Asyncore (depreciation warning)
Speech - Dialog/API

And I know there were others. but those were the ones that i recall off the top of my head.

but the only plugin that fully stopped functioning in that list was the Speech plugin. but that has been repaired.

Now i do recall someone having an issue with their tree. But it ended up being something that they did and had nothing to do with the upgrade process.

But in the event you want to make sure simply backup these folders

Program Files (x86)\EventGhost
%appdata%\EventGhost
%programdata%\EventGhost

and if something goes wrong. put them back into place.

[Sem;colon]

@Sem;colon what is your plugin called? Pretty sure, you have more than one...

I was referring to viewtopic.php?f=14&t=9641.
It has a whole bunch of features, that's just one of them...
But it's not even released (still hesitating if I'll even do, as development takes too much time if I can't do it to earn a living), sorry for even mentioning it.