I know how can install test wersion thx, but I ask why not showing tag info sun events app, and 2. version is fix this issue? And one more 2. version is test version all released or not ?
Hi, me again @MarcelT .
It is clear to me now that my location has no night at all in the summer, only astronomical dawn, lol. In Spistbergen there are days that don’t see an end - how does your app handle this? (<-- Edit: hmm, they just never do trigger, I guess…)
Anyway, my seasonal flows are working fine now, no more night end problems.
I have another issue though. I am trying to find a trigger point that is around two to two and a half hours after sunrise in the summer. In the winter it is different, but that I can handle.
Sunrise ends plus offset doesn’t get me there, golden hour ends plus offset (especially in summer) doesn’t get me there. I cannot use any delay cards because I need to be able to check for the “seasonal state” and restore it if needed (edit 2: I fixed that by storing states on every change - better that way). I am a bit stuck. So a few questions.
Do you know of any of your events, other app’s events, or other methods I haven’t thought about to get to sunrise +2.5 hours as a trigger?
If I replace the offset with a number variable, can I get beyond 60 minutes?
If not, would you consider extending the offset limit to, say, 3 hours?
Any help would be appreciated! With my thanks in advance.
Alternatively you could use a second flow and something like chronograph app to set a timer to 2.5h and use it to trigger your flow when the timer reaches 0.
Thanks, @sgo that is what I did for a while. It’s like dropping a little ticker to extend a point in time - once you have reached that point. But I have a flow where I want to check the seasonal/astronomical state of shutter, and a few things I have in mind that don’t allow me to wait for x hours
Thinking of that, a card that would give me the time of an event instead of trigger off it when it happens would solve it as well. I could math my own day schedule and completely get away from triggering or comparing against events +nHours. that way. I could then also catch “non-existent” events (the night problem, earlier in this thread) and work around them.
I’ll see first what Marcel has to say when he gets back.