In the last stable release version 0.4, the webserver would trigger/generate events in the log called like:
SamsungTV-OFF
..after sending an HTTP GET to the webserver.
Now, the events are called:
HTTP.SamsungTV-OFF
It's not a big deal, but I have to rename all my webserver events to start with HTTP. if I want to use the new EG beta.
After upgrading to version 0.5.0-rc6 HTTP webserver events need to be renamed
Forum rules
To submit a possible bug report please follow this template
Version: 0.5 beta 2 (the version you are running)
Traceback: Traceback (most recent call last):
File "<SOME_EVENTGHOST_FILE.py>", line 10, in <module>
SOME_FUNCTION()
File "<SOME_EVENTGHOST_FILE.py>", line 4, in SOME_EVENTGHOST_MODULE
SOME_FUNCTION()
copy and past any traceback information from the log if there is no traceback put NONE
Event:
Main.test.0.1.2.3.4.5.6.7.8
1
2
in the Event field you will want to put the event that was triggered just prior to the traceback occurring, if there is personal data put PERSONAL DATA if there was no traceback or no event triggered right before the traceback put NO EVENT
Description: if you have the ability to replicate the issue then put in here a description of what you are doing to create the problem.
Screen Shots: screen shots of the error and any events/macros/acrions that were run before the issue or screen shots of the problem
Files: any files that may be used to isolate where the issue is. something like the log.txt file would go here
if you provide the above information before hand it will greatly speed up the diagnostic process. we will not have to ask for the bits and pieces. And also having a well formatted Bug Report filled out will get answered sooner then the ones that aren't
To submit a possible bug report please follow this template
Version: 0.5 beta 2 (the version you are running)
Traceback: Traceback (most recent call last):
File "<SOME_EVENTGHOST_FILE.py>", line 10, in <module>
SOME_FUNCTION()
File "<SOME_EVENTGHOST_FILE.py>", line 4, in SOME_EVENTGHOST_MODULE
SOME_FUNCTION()
copy and past any traceback information from the log if there is no traceback put NONE
Event:
Main.test.0.1.2.3.4.5.6.7.8
1
2
in the Event field you will want to put the event that was triggered just prior to the traceback occurring, if there is personal data put PERSONAL DATA if there was no traceback or no event triggered right before the traceback put NO EVENT
Description: if you have the ability to replicate the issue then put in here a description of what you are doing to create the problem.
Screen Shots: screen shots of the error and any events/macros/acrions that were run before the issue or screen shots of the problem
Files: any files that may be used to isolate where the issue is. something like the log.txt file would go here
if you provide the above information before hand it will greatly speed up the diagnostic process. we will not have to ask for the bits and pieces. And also having a well formatted Bug Report filled out will get answered sooner then the ones that aren't
Re: After upgrading to version 0.5.0-rc6 HTTP webserver events need to be renamed
Hi mkanet,
That's not a bug, it's a bugfix
No, seriously, when plugins are able to create an event without prefix, multiple plugins could trigger the same event, what may lead to an unexpected behavior in your actions.
That's why with EG 0.5 a mandatory prefix has been added.
It also makes things more structured, so you instantly see where your event it coming from.
That's not a bug, it's a bugfix
No, seriously, when plugins are able to create an event without prefix, multiple plugins could trigger the same event, what may lead to an unexpected behavior in your actions.
That's why with EG 0.5 a mandatory prefix has been added.
It also makes things more structured, so you instantly see where your event it coming from.
If you like my work, 
me a drink 
me a drink -
kgschlosser
- Site Admin
- Posts: 5446
- Joined: Fri Jun 05, 2015 5:43 am
- Location: Rocky Mountains, Colorado USA
Re: After upgrading to version 0.5.0-rc6 HTTP webserver events need to be renamed
@sem;colon is correct.
It helps to minimize the chances of having an event collision between plugins. Because EG has close to 400 plugins available event collisions are a real thing. so when an event comes from a plugin a prefix MUST exist.
Now there is a way you can remove that prefix if you like. If you create a macro and add the event HTTP.* to the macro. Then add a python command action and past in the line of code below into that action it will remove the HTTP. from the beginning of the event.
It helps to minimize the chances of having an event collision between plugins. Because EG has close to 400 plugins available event collisions are a real thing. so when an event comes from a plugin a prefix MUST exist.
Now there is a way you can remove that prefix if you like. If you create a macro and add the event HTTP.* to the macro. Then add a python command action and past in the line of code below into that action it will remove the HTTP. from the beginning of the event.
Code: Select all
eg.TriggerEvent(prefix=eg.event.string.split('.', 1)[-1], payload=eg.event.payload, source=eg.event.source)
If you like the work I have been doing then feel free to 