Tonight Allsky thinks it is daytime when it is 2 hours into the evening

[bbillp]

version 2024:12.06
Allsky has worked fine for years suddenly
command line date/time is correct it is now 19:11 Pacific
location is correct: 33.6603N, 118.1W Located near Los Angeles
just to make sure the rest of allsky is working I turned on DAYTime mode, TIME is 19:10 Pacific Time

[bbillp]

After booting a few times all I could think of was to replace 118.1W with -118.1, reboot and it worked. Being the night to SPRING AHEAD something in the 2024.12.06 algorythms didn’t like 118.1W .

[EricClaeys]

Interesting. The sunwait command, which determines if it's daytime or nighttime, requires latitude and longitude to have N, S, E, or W, not + or -.
And Allsky converts + and - numbers to N,S,E,W as needed. Perhaps there is a bug.
Would you please attach /var/log/allsky.log?

[bbillp]

Evening of 3/8/2025 2025-03-08T18:02:52
Search BP in allsky.log.1.txt to find each point in time in the log indicating where I the issue began.
allsky.log.1.log
allsky.log

[EricClaeys]

What is BP ?

[bbillp]

My initials are BP making it easier to use ‘find’ to locate the lines where activity began since there are no error messages in the logs.   Sent from my iPadOn Mar 10, 2025, at 2:31 AM, Eric Claeys ***@***.***> wrote: What is BP ? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[EricClaeys]

Hmmm, I searched for BP in both files and it's not there. Am I doing something wrong?

FYI, the file specified in your Extra Text File setting in the WebUI doesn't exist, so you're getting this message on every image:

*** capture_ZWO: WARNING: Extra Text File Does Not Exist So Ignoring It