EventGhost

So what was it??

It was the way I was obtaining the mac address. you can't ping yourself and then lookup the mac of the computer in the arp tables. So i opted to grab it from ipconfig instead


here is the version that fixes the traceback.

Ok I ran the plugin and got these results:



The iOS Remotes ran fine with no errors.

The Android remotes however had an issue.
Yatze remote, gave some error/data.
Kore remote gave an instant double WoL
'
Here's the data from Yatze.
However, in all instances, they have a proper WoL signal

do me a favor. turn on your log time stamping and then send the WOL packets. I probably just have to tweak the timing. Or put in place a thread lock (the latter probably being the case) the thread lock will not allow another thread to process the same code simultaneously. thus allowing the first one that is running to set up the timer and the flag to not process the second before it actually does. but if the 2 are running almost at the exact same time then the second packet is making it past the flag before the first even sets it.. That is why the log times will help me out. it will let me know how close they come in to one another.

as far as the "error data" this is not of concern. i am going to be removing that error printout when this is buttoned up.

Well, both the signals are almost instantaneous, just a few milliseconds apart I would say.
Your idea would be nice as it would stop WoL spam on network, or atleast prevent 2 remotes sending a signal simultaneously.

yeah it is as i thought. let me institute the threading lock and go from there. that will take care of the problem. tho i may use threading events as the flag this will allow me to bump out the second one since they are back to back like they are.

ok i think i got this right. it's early I haven't fully woken up. what i did is this. I am thinking that the double events might be coming from the fact that the plugin is listening on 3 different ports. so I added the port the WOL comes in on to the even. but I also made the lock and the timer for the double WOL packet span all 3 instances of the socket. so if a packet comes in on port 0 as an example and another comes in on port 9 because whatever program it is that is sending the WOL packet might send it to 0 and 9 automatically to try and cover it's bases we don't want to get the double event. I am going to refine this a bit to do actual IP checking so it will only stop them from being a double if it is the same IP but lets make sure this works first.

Sorry I was unable to post any results.
I installed the plugin, but when I tried to 'Add' the plugin, EG hanged.

I thought that might happen. so give this a try I remove the use of wx to handle the timer bits. I created my own thread for it and i also instituted the ip address checking. so if you have a WOL come in from different IP addresses it will not block them. it will only block them if the WOL comes in from the same IP address more then one time per second.

Same thing again. EG hanged

ok last time.

LOL

Ok I ran the plugin successfully.
As you can see from the picture below, there were no errors, or data popups from both iOS (1,2) and Android (3,4).
I will test it a bit more, and if I run into anything, I will let you know.



But so far it seems to be very successful.

Ok,
I have ran the plugin multiple times and have no problems so far.

Thank you so much kgschlosser for the time and effort you put into this.

Now to see what possibilities this plugin opens up

no worries m8. thats why i am here