Coverage remained the same when pulling b438d7d on qedi-r:pending_events into 691f3b7 on cantino:master.

Interesting! So the idea is that an Agent can schedule Events that will "appear" in the future. What are some example use cases?

My driving motivation for this currently is an astronomy agent, which I will submit a pull request for once this is done. It checks weather underground automatically whenever the date changes and determines the sunrise and sunset times and schedules events for them so I trigger things based on those times.

It feels like a better model would be to have either

1. an Agent that outputs arbitrary events at very specific times
2. an Agent that delays input events until very specific times
   or
3. a general system to schedule exactly when agents will run

being able to emit "future events" strikes me as a bit odd, although I understand that it completely meets your needs in this case. Would 1-3 work for you as well?

I'll take a crack at trying 2. It's probably the most flexible approach.

Hey @qedi-r, did you make any progress on this?

Also, I'm curious to know more about how you're using Huginn. You said it's for astronomy?

Hadn't had too much time to work in it as of late. I expect to have an agent tomorrow, though. The idea for this feature is for an agent that uses the wunderground astronomy API, ie an agent that can generate events at sunrise and sundown. This in turn triggers a Philips Hue Agent I have written that turns my porch lights on and off.

I'm using this trial as an experiment to see if huginn can be the flexible master control I desire for my home.

See pull request #197