Sunset / Sunrise Times Not Correct

[cgmiller76]

Is there something specific that I have to run to ensure these times are updating correctly on my Overlay?

I use the Overlay Module and have Sun enabled, but the times for the sunset & sunrise are not correct and are different between 2 different allsky installations. The image timestamps are correct and in sync on the 2 different machines. Both are on the latest version of AllSky with the AllSky-Modules installed as well.

Sunrise is almost 30 minutes off on one of the machines, with sunset just being a few minutes off on that same one:

On the other rpi the times appear to be closer to accurate, just off by maybe a minute or two - if that:

BTW - Location is Louisville KY USA

I know it's minor - but just something that I can't figure out and want to get right. Thanks in advance!

[Alex-developer]

Is there something specific that I have to run to ensure these times are updating correctly on my Overlay?

I use the Overlay Module and have Sun enabled, but the times for the sunset & sunrise are not correct and are different between 2 different allsky installations. The image timestamps are correct and in sync on the 2 different machines. Both are on the latest version of AllSky with the AllSky-Modules installed as well.

Sunrise is almost 30 minutes off on one of the machines, with sunset just being a few minutes off on that same one:

On the other rpi the times appear to be closer to accurate, just off by maybe a minute or two - if that:

BTW - Location is Louisville KY USA

I know it's minor - but just something that I can't figure out and want to get right. Thanks in advance!

Can you let me have your approximate lat/lon and I will check for you

Thanks

Alex

[cgmiller76]

Thank you Alex: 38.24, -85.58

Appreciate the help!

[nofootprintz]

Has this been adressed somewhere? The sunset and sunrise times are all over the place and have not changed for a few days. I only now became aware of this issue? I am running the latest version of AllSky on bookworm.

[EricClaeys]

Actual sunrise and sunset times are based on your latitude and longitude and have nothing to do with Allsky.
I assume you mean the times when Allsky considers nighttime and daytime to begin, and not the sunrise and sunset times? Can you give some examples of "all over the place"? Allsky's nighttime begins at 6pm one day, then 8pm the next day, then 4am after that?
Run allsky-config show_start_times to see when nighttime and daytime are today. The times will change about 30 seconds a day, but some days won't change due to rounding - we only look at the minute.

Try running grep endOfNight.sh /var/log/allsky.log* to see when Allsky's daytime began. It should also change a little bit each day, but shouldn't be "all over the place". If it is, follow the instructions on the WebUI's "Getting Support " page and post the support log.

[EricClaeys]

Oh, and I suggest looking at the "Explanations -> Angle..." documentation page.

[nofootprintz]

Thank you for coming back so quickly! Let me try to clarify:

I mean the actual sunrise and sunset times. "end of day" and "end of night" seem to be correct.
For example todays sunset time ${SUN_SUNSET} shows 13:11, yesterday was the same, the day before that it was at 13:10, before that it was at 14:10 for 4 days, before that 15:10 and so on. It doesn't really make any sense. The sunset and sunrise times change rapidly now here. My coordinates are 68.34N and 18.82E. Further i noticed, that the ${SUN_ELEVATION} shows the correct angle and triggers day and night transitions correctly. This is the output of the commad you sugested running and it looks fine:

admin@allsky:~ $ allsky-config  show_start_times
Daytime start    Nighttime start     Angle   Latitude    Longitude
06:28            16:28               -8.00   68.34N      18.82E
admin@allsky:~ $

grep endOfNight.sh /var/log/allsky.log* outputs:

admin@allsky:~ $ grep endOfNight.sh /var/log/allsky.log*
/var/log/allsky.log:2025-11-02T06:29:00.524251+01:00 allsky allsky[915334]: endOfNight.sh: ===== Posting twilight data
/var/log/allsky.log:2025-11-02T06:29:02.003458+01:00 allsky allsky[915334]: endOfNight.sh: ===== Generating Keogram for 20251101
/var/log/allsky.log:2025-11-02T06:29:13.205966+01:00 allsky allsky[915334]: endOfNight.sh: ===== Keogram completed successfully
/var/log/allsky.log:2025-11-02T06:29:13.515219+01:00 allsky allsky[915334]: endOfNight.sh: ===== Generating Timelapse for 20251101
/var/log/allsky.log:2025-11-02T06:32:42.205515+01:00 allsky allsky[915334]: endOfNight.sh: ===== Timelapse completed successfully
/var/log/allsky.log.1:2025-10-26T05:05:22.169400+01:00 allsky allsky[1946446]: endOfNight.sh: ===== Posting twilight data
/var/log/allsky.log.1:2025-10-26T05:05:23.652594+01:00 allsky allsky[1946446]: endOfNight.sh: ===== Generating Keogram for 20251025
/var/log/allsky.log.1:2025-10-26T05:05:34.189875+01:00 allsky allsky[1946446]: endOfNight.sh: ===== Keogram completed successfully
/var/log/allsky.log.1:2025-10-26T05:05:34.497135+01:00 allsky allsky[1946446]: endOfNight.sh: ===== Generating Timelapse for 20251025
/var/log/allsky.log.1:2025-10-26T05:08:25.290795+01:00 allsky allsky[1946446]: endOfNight.sh: ===== Timelapse completed successfully
grep: /var/log/allsky.log.1: binary file matches
admin@allsky:~ $

[EricClaeys]

Allsky itself is working fine, changing between daytime and nighttime correctly.
The problem is with the ${SUN_SUNSET} and related variables which only determine what goes on the overlay; those variables aren't used for anything.

If you are in the US remember that our time just changed to standard time.

@Alex-developer,
any ideas on why the ${SUN_*} variables vary?

[nofootprintz]

I just started a new discussion with logs attached. Maybe I shoudn't have. Sorry, for the mess. I can attach it all here and delete the other post. Just say the word.

[EricClaeys]

Let's only use this GitHub item, not the other one.

[nofootprintz]

I moved this commend over from a duplicate thread:

support-ASM-discussion-4921-20250926205624.zip

Hi AllSky team.

First of all. Thank you for this great piece of software! It's just way too much fun.
Now, to the problem I am encountering: I use the overlay manager to display the sunset and sunrise times as well as the current angle of the sun. The sun angle is behaving alright, but the times for sunset and sunrise don't seem to. For the for weeks I have been running the camera this aurora season it never display the correct times and I cannot figure out why that is. Somtimes it is stuck on on (incorrect) value for up many days and then would change by an hours. I hope you can point me in the right direction with this, since I am clueless. Last season I didn't have this problem. But I wiped the whole system and did a fresh install (OS and Allsky) this autumn. If it helps, there are 28 days worth of timelapses and images on my website. Just use the date picker on this site: https://fabianwimmer.com/abisko-allsky-webcam-live-northern-lights-weather/

I thank you in advance for taking a look at this.

Cheers, Fabian

[EricClaeys]

@Alex-developer, v2025.xx.xx_01 ?

[Alex-developer]

@Alex-developer, v2025.xx.xx_01 ?

Yes will be in _01 or later

[Jovax2025]

Dear Alex,

Is there any possibility to add a module or create a variable that allows us to set the Astronomical Night times?
For example, in Tenerife the Astronomical Night begins at 19:36 and ends at 06:24.

Currently, the available variables only provide sunset and sunrise, and the closest values we have are:

AS_SUN_DUSK: 18:37:25

AS_SUN_DAWN: 07:21

This results in a difference of about one hour.
Is there any way to either add new variables for Astronomical Night or adjust the existing SUN_DUSK and SUN_DAWN variables (e.g., SUN_DUSK + one hour and SUN_DAWN - one hour)?

Thank you.

[Alex-developer]

Dear Alex,

Is there any possibility to add a module or create a variable that allows us to set the Astronomical Night times? For example, in Tenerife the Astronomical Night begins at 19:36 and ends at 06:24.

Currently, the available variables only provide sunset and sunrise, and the closest values we have are:

AS_SUN_DUSK: 18:37:25

AS_SUN_DAWN: 07:21

This results in a difference of about one hour. Is there any way to either add new variables for Astronomical Night or adjust the existing SUN_DUSK and SUN_DAWN variables (e.g., SUN_DUSK + one hour and SUN_DAWN - one hour)?

Thank you.

Yes we can, it wont be until the next release which is in testing and being documented though

Thanks

Alex

[Jovax2025]

Thanks, cheers