So you are referring to this:
I'm just wondering how are you going to calculate the input values for Azimuth or Altitude. First you would need the raw values, so I don't think even if sunCalc was reversed, you would have the data to input without measuring it from your window. You can get those values from sunCalc, so you don't want to actually reverse it, you just want to know when it happens as an event.
You really just need to know when sunCalc is reporting values within your parameters (since you would need to account for changing Azimuth and Altitude, every day. You are trying to schedule a timed event to happen, when there are already hub events being sent from sunCalc every time it calculates. That like setting up a rule that sets the sunrise time in a hub variable every day at midnight, so that scheduler can use it to trigger a sunrise action. You already have the live event in sunCalc, so this should be an event trigger, not a schedule.
You need a rule trigger that says when Altitude is between such and such, and Azimuth is between such and such (based on the same values you would use for inputs if sunCalc was reversed), then trigger your rule. It would need to use a range with a precision that will not trigger twice, or use a boolean to keep track of when it has already triggered for the day.
I checked, and it is about a 15 degrees per hour change for both altitude and azimuth. So that is 1 degree every four minutes. How accurate were you looking to get with your inputs to a possible reversed sunCalc to determine a scheduling time? If you miss altitude by one degree, it will cause a four minute error in your schedule, and so on.
I don't think that there is a need to schedule another event, when you have event data being sent as it happens from sunCalc that you just need to filter into a trigger.
