EventGhost

Posted: **Thu Sep 21, 2017 3:54 pm**

Yes the listening PCs MAC address, this is hard coded in the plugin:
CODE: SELECT ALL
34:E6:AD:0E:43:13
I assume this is the PCs MAC address?

jonib

Yes that is the listening PC's Mac address.
Maby a provision could be made into the plugin to type in the mac address, or pick up the mac address automatically(same as it picks up the ip address).

Posted: **Thu Sep 21, 2017 3:56 pm**

yup I know this is hard coded to his computers mac address at the moment. But the use of it can go beyond waking a computer up. and I will be setting this thing up to grab the mac address of the selected interface on the computer. I didn't know if it would be able to trigger events properly. and i guess it does.

Posted: **Thu Sep 21, 2017 4:30 pm**

ok so here goes a version that should automatically detect the mac addresses. and also listens on the 3 standard ports.

let me know if it works please

Posted: **Thu Sep 21, 2017 7:48 pm**

I ran the plugin and got this error

Code: Select all

error: uncaptured python exception, closing channel <eg.UserPluginModule.WOL.Server connected 192.168.0.163:9 at 0x4eb15f8> (<type 'exceptions.UnicodeDecodeError'>:'ascii' codec can't decode byte 0xff in position 0: ordinal not in range(128) [asyncore.pyc|read|76] [asyncore.pyc|handle_read_event|414] [C:\ProgramData\EventGhost\plugins\WOL\__init__.py|handle_read|100])

Personally, I think its better if given the option to chose the UDP port as there are many users choose different ports for WoL signals.

Posted: **Fri Sep 22, 2017 3:03 am**

WOL packets only get sent on 3 different UDP ports... 0, 7, and 9. this monitors all 3. and if for some reason it cannot listen on one of the ports because it is in use then the plugin just doesn't listen on that one.

But here is the newest version.

Posted: **Fri Sep 22, 2017 11:26 am**

I ran the plugin and there was no reaction at all.
When I hit 'Add Plugin' and whose the WoL plugin, this screen pops up.

After hitting Ok, and sending the WoL packet, no reaction.

The reason I was suggesting to allow users to pick the UDP port, cuz there are software that allow the user to configure which port they want to send the WoL signal (For example Yatse remote), in case any of the commonly used ports for WoL commands are already in use.

Posted: **Sun Sep 24, 2017 12:47 pm**

Oh good the forum is back up

Posted: **Sun Sep 24, 2017 4:09 pm**

that it is. sorry for it being down. we had a slight issue with our web hosting provider and it was causing an issue with forum attachments. and when i was working on this with you i kept on hitting the file cap and couldn't attach anything. it's a real headache. and over the past few months I had been working on writing a program to move the website. so i finished it up and yesterday i moved the site. I still have a couple of things to fix with it and then i will get right back onto working on this with you.

Posted: **Mon Sep 25, 2017 6:39 pm**

Oh, dont mind me

Take your time. Do what it is that you need to do.
I already appreciate all the time and effort that you have put into helping me. So prioritize the website/forum. There are others who depend on it too.

Posted: **Fri Sep 29, 2017 5:23 am**

give this a try. I am having a memory issue over here. I can't seem to remember the conversion from the returned data into int. I think I may have it this time tho. but if not I am going to have it print out the data that has come in.

I also added the ip address of the computer sending the wol packet as a payload. this way you can use that to tell the computer what to do. so if you wanted to send a wol packet from one device it can do something different then another

Posted: **Fri Sep 29, 2017 11:27 pm**

Thanks for coming back. Thought you had almost forgotten about lil ol me

How things with the site now? All sorted?

Ok so I ran the plugin and I got the following:

Here's the output

Code: Select all

data: [255, 255, 255, 255, 255, 255, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19, 52, 230, 173, 14, 67, 19]

Code: Select all

wol_packet: [255, 255, 255, 255, 255, 255, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171, 80, 199, 191, 23, 68, 171]

Posted: **Fri Sep 29, 2017 11:33 pm**

ok i need you to tell me what these 2 mac address are from

34:E6:AD:E:43:13
50:C7:BF:17:44:AB

I am not sure as to why there are 2 different ones

Posted: **Fri Sep 29, 2017 11:55 pm**

scratch that last post. I found the problem. (i think)

give this one a shot

Posted: **Sat Sep 30, 2017 10:10 am**

Ok. Ran the plugin and got this

Error code:

Code: Select all

error: uncaptured python exception, closing channel <eg.UserPluginModule.WOL.Server connected 192.168.0.163:9 at 0x56b7300> (<type 'exceptions.TypeError'>:TriggerEvent() takes at least 2 non-keyword arguments (1 given) [asyncore.pyc|read|76] [asyncore.pyc|handle_read_event|414] [C:\ProgramData\EventGhost\plugins\WOL\__init__.py|handle_read|114])

Posted: **Sat Sep 30, 2017 1:51 pm**

YAY! I fixed it. but found another dumbass mistake.

EventGhost

Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster

Re: Help With Broadcaster