After quite a lot of work (always more than you think) I have updated the SunEvents app from SDK 2 to SDK 3 to make sure it will work after 01.01.2023. I have also restructured it to make it easier to maintain.
You can find here the test release:
Please be sure that you are aware that this app can be buggy and can interrupt your workflows related to SunEvents.
Thank you @MarcelT for update to the SDK3, it wasn’t for sure late
So far testing but it looks like the memory footprint is a little bit higher ~10% - but not significantly and most important, it’s so far stable.
If I install the test app, will this affect the existing flows based on the “old” sun events app? Since about 2 weekd (when wintertime/DST came into effect), sun events triggers (start of night, sundown) do not trigger anymore. Reading the above, the test version could possibly correct this, but if it means having to redo all flows with sun events in them, I rather wait until the regular app is updated.
Do you use an offset other than 0 ?
I had this issue (it only triggered with offset 0 ), but it’s fixed in the test version.
Maybe you know alr, but nonetheless, you can view and check the available events of today via app settings. As you can see, a few of my custom events aren’t available outside the summer season.
You can add a few check flows to compare your flow triggers
That can be possible, which app version do you run?
How does the event timetable look? Do the times correspond with the real sun events, or are those an hour off as well?
Which trigger do you use? Which event do you use? Do you use an offset? Does this happen for all events? What means “more or less accurate”? 1 minute deviation? 30 minutes deviation? Have you downgraded to the stable version v0.8.4 and checked if the same problem is present?