Ad blocker detected:
Our software and support is 100% free. This website is not.
You can donate in 2 ways, by turning off your ad blocker or by pressing the Donate button.
************ NOTICE ************
UPDATE YOUR BOOKMARKS!!!
We have an issue that there is no way around as of yet.
I have done all I can to try and prevent this from happening.
We are going to be losing the .com, .org and .de domains.
We have not been able to contact the original author of EventGhost
(the person that owns those domains) to redirect them to the new web server.
I set in motion when we first moved a redirection from the old server to the new server.
I also put in markers so that search engines would see this change and update any pointers
they have. We still have the .net domain for the production site. and the .rocks for the test site.
For the past few months you have been getting redirected to the .net site if you used one of the 3
domains mentioned above. I just wanted to tell everyone so they can make any changes needed.
I use the logger a lot to keep track of what happens in my system. But there are a few things that I really don't need. Would it be possible to make it optional to show the names of the macros that run and the name of the actions that run inside a macro? An example:
I am looking for some way to reduce log verbosity. I am using EG for home automation and my log gets flooded with various events from sensors just because I have one macro that writes sensors value to a database.
One solution could be to temporarily disable the event. But if I do so, I would no longer get the values written into my database.
It would be nice that next release of EG allows enabling/disabling log of specific sets of events/macros/commands. I see 2 possibilities:
1) a system of log "layers" where we could assign events/macros/commands to named layers of log and then activate any of these layers to be actually displayed. New items would be assigned to Default layer that would correspond to current log
2) an option to enable/disable log of any folder (and the events/macros/commands it contain)
I hope 1) or 2) or both could be implemented in a near future