EventGhost

As contributors to this forum we have no obligations whatsoever, be clear to understand that! Everything provided is by free will & generosity of the community to the community. Also you as consumer has no obligations (besides behaving in a polite manner) and you have to accept this fact since all software related in here is fully free and doesn't cost you any money.

So don't start to indicate what kind of obligations WE have.

If you would buy a product or software, you would be entitled to CLAIM support.

So maybe that is where you went completely wrong from the beginning. EventGhost is free and we try hard to make it as good as possible with limited spare time by many users in here without getting paid.

So this is the message, take it as it is, start to behave polite and make POSITIVE contributions. Or leave.

Aeneas wrote:However, I was able to open a new window which looks like a scheduler
by Right-click on Show Schedulghost and then selecting Execute Item

Great!

Aeneas wrote:this windows Is titled just "SchedulGhost", not "SchedulGhost Manager".

I think it is no problem. There is no rule that the window title exactly match the meaning.

Aeneas wrote:However, the Only Once/Add New/Apply-ed timed event did Not occur --
I set it 2 or 3 minutes ahead of current time
as observed in the bottom right corner of the Windows 7 64 screen.

There are basically two options:
1) This is a bug
2) You're doing something wrong
Given the number of users and the period of use, it can be assumed that the second case is much more likely.
However, I can not advise more. I do not have enough information from you, so I can not know what you're doing wrong.
If you expect help from someone, you should provide as much information as possible.
This means that you would have to do as much work as possible and do not expect that someone will do unnecessary work for you
(for example, creating detailed instructions).

Pako

I returned 9 hours later and noticed that the channel had changed to the one selected.
So it seems that maybe this program just has a time zone bug.
Using the Duplicate feature in that window, I set entries for all 24 hours
and found that here in PST time, 16:40:00 in the program,
equates to 4:40PM or 16:40:00, which is correct
(i.e. the event did indeed toll 4 minutes later at 4:40PM//16:40:00).

So the bug issue is why did it not toll properly, when 1:35:00 or 3:35:00
(I forget which was the last try last night) did not toll until 12:35:00
(using Last Run and other information).
Maybe there is an AM scheduler bug somewhere.

Is there a way to cause this program to generate an audio signal or beep
when the event tolls and changes the channel ?
In addition, I would suggest that the Date/Time be appended to all events
which appear in the eventghost Log.

Aeneas wrote:In addition, I would suggest that the Date/Time be appended to all events
which appear in the eventghost Log.

Why do people not check the options before asking for new features? "EventGhost menu ->View->Log times"

jonib

jonib wrote:

Aeneas wrote:In addition, I would suggest that the Date/Time be appended to all events
which appear in the eventghost Log.

Why do people not check the options before asking for new features? "EventGhost menu ->View->Log times"
jonib

So that is what "Log Times" in the View pull-down menu means.
( About/System Information/Program Version 0.4.1.r1722 ) .
When mouse clicked will display times along with each log line (though not the date).

Of course, the most important program change needed so far is to be
able to select a Macro directly in the schedulghost menu, and have whatever
the Macro is be displayed on each line of the schedulghost event list display.

So far I have gone 4 hours with the scheduler tolling correctly -- in the PM, PST time zone, so far.
1:40AM is still 5 plus hours away.

I should mention at this point that none of the AM items within the 24 events display a "Next Run" time --
only the PM items.
Also, the scheduled events whose PM toll time preceded the time this afternoon when I
set the 24 timers which were typed/mouse-clicked in probably around 4:30PM PST today
(e.g. 12:40:00, 13:40:00, 14:40:00, 15:40:00) also do not state a Next Run time.
Once this bug is crystallized, I hope it will be top priority to fix.

Aeneas wrote:Of course, the most important program change needed so far is to be
able to select a Macro directly in the schedulghost menu, and have whatever
the Macro is be displayed on each line of the schedulghost event list display.

I do not understand, or it sounds like nonsense.
Can you please describe in more detail in other words?
It completely denies the principle EventGhost. For example, are you aware that each event can be used in several macros?

Aeneas wrote:So far I have gone 4 hours with the scheduler tolling correctly -- in the PM, PST time zone, so far.
1:40AM is still 5 plus hours away.

I should mention at this point that none of the AM items within the 24 events display a "Next Run" time --
only the PM items.
Also, the scheduled events whose PM toll time preceded the time this afternoon when I
set the 24 timers which were typed/mouse-clicked in probably around 4:30PM PST today
(e.g. 12:40:00, 13:40:00, 14:40:00, 15:40:00) also do not state a Next Run time.
Once this bug is crystallized, I hope it will be top priority to fix.

1) I can not exclude that for your time zone, it works differently than for my time zone.
What's your time zone?

2) Unfortunately, I do not speak English and I have a big problem understanding your post.
It is for me a very obscure and confused.
Can you please simplify the description so I understand it?
Just one example of a specific problem.
Like this:
Right now is 2016-05-08 08:00.
I create new schedule of type "Only once", that should run at 2016-05-09 07:00, but in the column Next run nothing appears.
(This is hypothetical, for me it works correctly).

Pako

i know what this is...


it's a PEBKAC problem

that's what it is

I have no idea what the English-to-other-language translator you are using
is doing with these phrases and words.

The user is forced to engage in a circuitous path to establish an Event-name
which is then assigned to the Macro-name which I have assigned
to a sequence of smaller single-digit infrared Macros I have pasted together.

Why should that Event-name be necessary in the schedulghost syntax ?
The Event-name in this particular scenario is superfluous and should be eliminated.
The Macros I have created contain the channel number infrared commands I care about
and confusing the user (and wasting the user's time) with Event-names here is unnecessary.

Are you saying that it is random whether or not the schedulghost Next Run column will display
an intent and time to perform the action/event on that line ?

Needed bug fixes and changes:
1) fix whatever is the bug which sometimes does not perform the action at the selected time,
2) modify schedulghost window to allow each entry to select a Macro directly,
without the Event wrapper,
3) modify the schedulghost window to display the Macro name
associated with each line-event, clearly on each line
4) display on each schedulghost event line the "schedule type" selection for that event
5) allow user to select an audio sound/beep when scheduled event occurs on a per-line basis.
6) allow user to enter a short comment on each line-entry -- e.g. the name of the show
necessitating this channel change.

And, as I suspected, the 00:42:00 channel change event did Not occur.
Maybe there is some sort of AM bug here.
This is a high priority Bug, which needs to be fixed as soon as possible.
I doubt that Pacific Standard Time (PST) is causing this bug.

well we will make sure to get right on that for you being that you did invest a whole lot of money for this software and plugin.

you really need to go and find some other program to use. the problem isn't the program or the plugin, it's your understanding of how it works and what it is supposed to do.

and the simple fact is that if there is a problem with it you are not going to get it fixed by demanding that it be done right now. i am not sure who pissed in your cheerios but go take it somewhere else.

and ya know it's probably a DST bug and the plugin is probably using epoch time which doesn't account for use of DST so now you know where to look go demand it of yourself to fix it

kgschlosser wrote:and ya know it's probably a DST bug and the plugin is probably using epoch time which doesn't account for use of DST so now you know where to look go demand it of yourself to fix it

Are you saying that the schedulghost plugin was written by someone
outside the core team of eventghost developers ?
01:42:00 event also did not occur, so I think we are definitely onto some sort of bug here.

kgschlosser wrote:well we will make sure to get right on that for you being that you did invest a whole lot of money for this software and plugin.
you really need to go and find some other program to use. the problem isn't the program or the plugin, it's your understanding of how it works and what it is supposed to do.
and the simple fact is that if there is a problem with it you are not going to get it fixed by demanding that it be done right now. i am not sure who pissed in your cheerios but go take it somewhere else.

I did ask what other programs are available which could schedule USB-UIRT events here,
but have not received a response to that question yet.

Aeneas wrote:When mouse clicked will display times along with each log line (though not the date).

For date in the log you can use Log redirector plugin, That gives date for the log entries but only in a text file.

jonib

there should be more than the one plugin available for scheduling if you dislike the way it functions.

you have to search the forums


(right back to square one again)

Aeneas wrote:
The user is forced to engage in a circuitous path to establish an Event-name
which is then assigned to the Macro-name which I have assigned
to a sequence of smaller single-digit infrared Macros I have pasted together.

Why should that Event-name be necessary in the schedulghost syntax ?
The Event-name in this particular scenario is superfluous and should be eliminated.
The Macros I have created contain the channel number infrared commands I care about
and confusing the user (and wasting the user's time) with Event-names here is unnecessary.

and the Event Name is why it's called EventGhost

the Event is what tells EventGhost what to do. you can have duplicates of everything in the tree (except some plugins)

makes it nice and easy to replicate things.

so if you have 2 macros with the same name but do different things then that would be a problem. and tracking that in a complex nested tree is very difficult, now with the events if you just double click on the event in the log it brings you right to the macro that got triggered

but on the other hand if you have 2 macros that do different things but want both of them to occur with the same event, you can drag and drop the event into each one of the macros

see how that works???

one of the things you will also have to remember with a different schedule plugin you may have to load the scheduled tasks into the plugin at eventghost boot time.

so if you start eventghost you will notice an event called

Main.OnInit

so you would creat a macro and add that event to it then add the actions for the scheduler plugin you want to use to that same macro. so it will load the tasks into the schedule plugin that you decide to use (i do not use a schedule plugin so i am not 100% familiar with how they function as far as adding tasks)

eventghost is all about if "If this happens, then do this"

that's essentially the core of it (with a lot of nice fluff added) once you get familiar with using it there is not a single electronic device that can't be controlled from it (obviously with python knowledge)

there is not a single home automation platform that is able to do what eventghost does

it actually can make home automation automatic