Thank you very much for contributing in the investigation!
I use a small proprietary computer in my KNX home automation system that has a built-in feature to send UDP commands.
I can program this proprietary computer (the EIBPC by Enertex
http://www.enertex.de/e-eibpc.html) in such a way that when I press a switch in my house, an UDP command is sent on my LAN network.
The following program syntax is programmed in the proprietary computer for issuing the UDP command on the LAN network:
sendudp(33333u16,192.168.1.16,$sbwoonkuit$)
Some explanation of the command:
The u16 behind the port number is used to define the datatype of the port numberr (a normal necessity in the ETSsoftware for the KNX domotica world).
The IP address is the IP of the receiving computer on which Eventghost is running.
The letters between the dollar signs are the UDP command that actually gets sent. Like for the port number, text strings for ETS/KNX purposes must be between dollar signs. As you can see, the command itself only contains normal letters.
With the command programmed in the EIBPC and then when I press the programmed switch in my house, the UDP commands is sent by the EIBPC, which is received in Eventghost without a problem.
The event I receive in the log of Eventghost is the following:
01:50:57 Broadcast.sbwoonkuit
This is exactly what I would expect.
If I then don't do anything else but just receive the UDP event in the log, save and exit Eventghost, I can then re-open Eventghost without a problem.
I can also drag the UDP event to a Macro and it will trigger the Macro when I press the switch.
That is exactly what I would expect.
However, if I NOW save and exit Eventghost, Eventghost can NOT be re-opened normally again. When I try to restart, it takes a bit longer and then the only information in the log I get are the error messages (new log after just trying again just now):
02:18:16 ---> Welcome to EventGhost <---
02:18:22 Unhandled exception in WorkerThread <EventThread>:
02:18:22 Callers stack:
02:18:22 File "wx\_core.pyc", line 8010, in MainLoop
02:18:22 File "wx\_core.pyc", line 7306, in MainLoop
02:18:22 File "wx\_core.pyc", line 14669, in <lambda>
02:18:22 Traceback (most recent call last) (1700):
02:18:22 File "C:\Program Files\EventGhost\eg\Classes\ThreadWorker.py", line 326, in __DoOneEvent
02:18:22 self.HandleAction(action)
02:18:22 File "C:\Program Files\EventGhost\eg\Classes\ThreadWorker.py", line 289, in HandleAction
02:18:22 action()
02:18:22 File "C:\Program Files\EventGhost\eg\Classes\ThreadWorker.py", line 62, in __call__
02:18:22 self.returnValue = self.func(*self.args, **self.kwargs)
02:18:22 File "C:\Program Files\EventGhost\eg\Classes\EventThread.py", line 142, in StartSession
02:18:22 actionThread.Func(actionThread.StartSession, 120)(filename)
02:18:22 File "C:\Program Files\EventGhost\eg\Classes\ThreadWorker.py", line 62, in __call__
02:18:22 self.returnValue = self.func(*self.args, **self.kwargs)
02:18:22 File "C:\Program Files\EventGhost\eg\Classes\ActionThread.py", line 39, in StartSession
02:18:22 eg.document.Load(filename)
02:18:22 File "C:\Program Files\EventGhost\eg\Classes\Document.py", line 143, in Load
02:18:22 xmlTree = ElementTree.parse(filePath)
02:18:22 File "<string>", line 45, in parse
02:18:22 File "<string>", line 32, in parse
02:18:22 SyntaxError: not well-formed (invalid token): line 280, column 45
That is the only thing that is in the Eventghost log. On the right hand side, nothing happens (i.e. the Autostart does not come up, plugins are not loaded, etc.).
The only things that add to the Eventghost log are the 'idle', 'unidle' messages that you always get when you check every once in while to look at the Eventghost window.
I am using Windows 7 for the Eventghost machine and I run Eventghost 'as administrator' at each start.
I am just clueless about what the issue could be here.
I really appreciate your feedback and input!
Let me know if you need me to check/try something else.
Thanks again,
Perry