Allsky keeps reverting back to an old version of the overlay #4078

NeilAllison147 · 2024-12-18T03:13:39Z

NeilAllison147
Dec 18, 2024

I have updated my overlay layout twice now since upgrading to the latest version.
The 1st time, I thought it must be user error.
But today, it has again reverted back to a previous layout.
The saved image at 13:54 is showing the proper layout (I.E the one I want to keep).
The saved image at 13:55 is showing the old version of the overlay.

Below is an extract of the allsky.log file from that time period.

Any thoughts, anybody?

...
2024-12-18T13:54:28.883385+11:00 hv-allsky allsky[1924]: STARTING EXPOSURE at: 2024-12-18 13:54:28 @ 209 us
2024-12-18T13:54:32.259446+11:00 hv-allsky allsky[1924]: > Saving DAY image 'image-20241218135428.jpg'
2024-12-18T13:54:34.144885+11:00 hv-allsky allsky[188781]: libpng warning: iCCP: known incorrect sRGB profile

2024-12-18T13:55:32.269416+11:00 hv-allsky allsky[1924]: STARTING EXPOSURE at: 2024-12-18 13:55:32   @ 209 us
2024-12-18T13:55:35.664763+11:00 hv-allsky allsky[1924]:   > Saving DAY image 'image-20241218135532.jpg'
2024-12-18T13:55:37.569285+11:00 hv-allsky allsky[188902]: libpng warning: iCCP: known incorrect sRGB profile
2024-12-18T13:55:39.082281+11:00 hv-allsky allsky[188902]: ERROR: No 'Type' defined for '${BRIGHTNESS}'; check in the Variable Manager in the WebUI's Overlay Editor page.  Using '???' instead.
2024-12-18T13:55:39.085518+11:00 hv-allsky allsky[188902]: ERROR: No 'Type' defined for '${AS_MOON_RISE_TIME}'; check in the Variable Manager in the WebUI's Overlay Editor page.  Using '???' instead.
2024-12-18T13:55:39.085660+11:00 hv-allsky allsky[188902]: ERROR: No 'Type' defined for '${AS_MOON_RISE_TIME}'; check in the Variable Manager in the WebUI's Overlay Editor page.  Using '???' instead.

Alex-developer · 2024-12-18T09:09:41Z

Alex-developer
Dec 18, 2024
Maintainer

Can you please provide a little more info

What version of Allsky are you using
Can you please attach the allsky.log file rather than paste it, its easier to read and you can post a lot more of the file
If its v2026 can you attach the ~/allsky/config/settings.json file

Thanks

Alex

0 replies

EricClaeys · 2024-12-18T10:55:13Z

EricClaeys
Dec 18, 2024
Maintainer

@NeilAllison147, in v2024.12.06 the Brightness setting is gone so you'll need to remove ${BRIGHTNESS} from your overlay.
For `${AS_MOON_RISE_TIME}', do as the message says. The variable probably isn't defined in both tabs.

Did you change something between the 13:54 and 13:55 images?

0 replies

NeilAllison147 · 2024-12-18T21:08:06Z

NeilAllison147
Dec 18, 2024
Author

Hi Eric Yeah, that's the problem - I DID remove both of those... and they just reappeared again. Nothing was changed between the 2 images. I just happened to take a look at the camera and noticed that the overlay had reverted back to an old version again. So I looked through the images to find out when it occurred. I suspected that it was during the night to day transition but it was early afternoon.

…

-- Thanks and Best Regards Neil

On Wed, Dec 18, 2024 at 9:55 PM Eric Claeys ***@***.***> wrote: @NeilAllison147 <https://github.com/NeilAllison147>, in v2024.12.06 the Brightness setting is gone so you'll need to remove ${BRIGHTNESS} from your overlay. For `${AS_MOON_RISE_TIME}', do as the message says. The variable probably isn't defined in both tabs. Did you change something between the 13:54 and 13:55 images? — Reply to this email directly, view it on GitHub <#4078 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNGXH6J3OZJ52QXW4CL2GFICNAVCNFSM6AAAAABTZX32RCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRQGQYDSNY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

0 replies

NeilAllison147 · 2025-01-06T23:19:05Z

NeilAllison147
Jan 6, 2025
Author

Just an update on this issue. After rebooting the Pi, this issue has never resurfaced so it can be closed.

…

-- Thanks and Best Regards Neil

On Thu, Dec 19, 2024 at 8:07 AM Neil Allison ***@***.***> wrote: Hi Eric Yeah, that's the problem - I DID remove both of those... and they just reappeared again. Nothing was changed between the 2 images. I just happened to take a look at the camera and noticed that the overlay had reverted back to an old version again. So I looked through the images to find out when it occurred. I suspected that it was during the night to day transition but it was early afternoon. -- Thanks and Best Regards Neil On Wed, Dec 18, 2024 at 9:55 PM Eric Claeys ***@***.***> wrote: > @NeilAllison147 <https://github.com/NeilAllison147>, in v2024.12.06 the > Brightness setting is gone so you'll need to remove ${BRIGHTNESS} from > your overlay. > For `${AS_MOON_RISE_TIME}', do as the message says. The variable probably > isn't defined in both tabs. > > Did you change something between the 13:54 and 13:55 images? > > — > Reply to this email directly, view it on GitHub > <#4078 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/APT5YNGXH6J3OZJ52QXW4CL2GFICNAVCNFSM6AAAAABTZX32RCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRQGQYDSNY> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

0 replies

EricClaeys · 2025-01-06T23:31:13Z

EricClaeys
Jan 6, 2025
Maintainer

Reboots on the Pi are like on Windows. They hide the underlying problem but don’t fix it, so it usually comes back.
If it does, please attach the two files we asked for. We can't do much without them.

0 replies

NeilAllison147 · 2025-01-07T04:37:53Z

NeilAllison147
Jan 7, 2025
Author

Me and my big mouth !!! As soon as I say it's resolved, the overlay data disappears again :( I'm running v2024.12.06 Interestingly, some files mentioned in in the settings.json file: - "extratext": "/home/neil/allsky/config/overlay/config/overlay.json" "daytimeoverlay": "overlay.json", "nighttimeoverlay": "overlay.json", aren't there any longer.

…

-- Thanks and Best Regards Neil

On Wed, Dec 18, 2024 at 8:10 PM Alex ***@***.***> wrote: Can you please provide a little more info - What version of Allsky are you using - Can you please attach the allsky.log file rather than paste it, its easier to read and you can post a lot more of the file - If its v2026 can you attach the ~/allsky/config/settings.json file Thanks Alex — Reply to this email directly, view it on GitHub <#4078 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APT5YNHBY5LKS3SYSEAX7MD2GE3WVAVCNFSM6AAAAABTZX32RCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRQGI4DQNY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

0 replies

EricClaeys · 2025-01-07T04:42:28Z

EricClaeys
Jan 7, 2025
Maintainer

@NeilAllison147, that stinks!
We need the files.

0 replies

NeilAllison147 · 2025-01-07T04:57:32Z

NeilAllison147
Jan 7, 2025
Author

Version is v2024.12.06
I sent them as attachments to the email, but they're also attached here: -

settings.json
allsky.log

0 replies

EricClaeys · 2025-01-07T05:40:39Z

EricClaeys
Jan 7, 2025
Maintainer

@NeilAllison147, thanks. I'll take a look.

GitHub doesn't accept email attachments.

0 replies

EricClaeys · 2025-01-07T06:01:54Z

EricClaeys
Jan 7, 2025
Maintainer

@NeilAllison147,
This error started at 15:23:31 on December 7. Do you remember what you changed?

2025-01-07T15:23:31.910591+11:00 hv-allsky allsky[1998479]: ERROR: Module allsky_overlay.py failed on line 209 - invalid literal for int() with base 10: ''

Please attach ~/allsky/config/overlay/myTemplates/overlay.json. If it's not there, try ~/allsky/config/overlay/config/overlay.json.

Also,
I get a timeout going to your website http://hv-allsky.duckdns.org:22147/allsky/.
Your Remote Website Image URL is incorrect. It should be http://hv-allsky.duckdns.org:22147/image.jpg.

@Alex-developer, Any idea on this error that appears for each image: ~~~ libpng warning: iCCP: known incorrect sRGB profile ~~~

Also, line 209 in allsky_overlay.py is:

Would the error that Neil's getting indicate something strange in the environment?

0 replies

NeilAllison147 · 2025-01-07T06:12:22Z

NeilAllison147
Jan 7, 2025
Author

@EricClaeys Unfortunately, I've slept since then so I haven't got a clue what was changed :(

If I change the image URL to "http://hv-allsky.duckdns.org:22147/image.jpg", I get the error "ERROR: Image URL 'http://hv-allsky.duckdns.org:22147/image.jpg' does not appear to be a valid image."
The image url was previously set to "http://hv-allsky.duckdns.org:22147/current/tmp/image.jpg" and I don't get any errors when using this value.

The attached overlay file is from ~/allsky/config/overlay/myTemplates/overlay.json, and that looks to be the one it should be using.

overlay.json

4 replies

EricClaeys Jan 7, 2025
Maintainer

Sorry, I hadn't realized your "remote Website" is on your Pi. Ignore my comments about the wrong URL.

In the Overlay Editor, delete the Format of the Exp: ${sEXPOSURE} field. It's a string but you are telling the Overlay Editor to format it as a number. That's most likely causing the error and keeping the overlay from appearing.

EricClaeys Jan 7, 2025
Maintainer

I tried setting the format of my Exp: $(sEXPOSURE} to what you have, and it didn't complain, so I'm not sure if removing the Format will work (but please remove it anyhow).

You said earlier:

Interestingly, some files mentioned in in the settings.json file: -
"extratext": "/home/neil/allsky/config/overlay/config/overlay.json"
"daytimeoverlay": "overlay.json",
"nighttimeoverlay": "overlay.json",
aren't there any longer.

What do you mean by "aren't there any longer"?
Because you're using the Overlay Editor, the "extratext" field is ignored.
The "overlay.json" file is in ~/allsky/config/overlay/myTemplates and is the one you attached.

And a few weeks ago you said:

Yeah, that's the problem - I DID remove both of those... and they just reappeared again.
Nothing was changed between the 2 images.
I just happened to take a look at the camera and noticed that the overlay had reverted back to an old version again. So I looked through the images to find out when it occurred.
I suspected that it was during the night to day transition but it was early afternoon.

It's possible to have different overlays for day and night, so I suspect at that point you did have different ones, and one had what you wanted and the other didn't.

NeilAllison147 Jan 7, 2025
Author

Hi Eric
I've removed the formatting of ${EXPOSURE} now.

I wasn't sure where the overlay.json file should live.
I thought it should be in "/home/neil/allsky/config/overlay/config/overlay.json" but it's where it should be, so all good :)

If I look in the Overlay editor > Overlay editor options > Overlays and select the edit option next to Type=User, Name =???, on the Activate tab, both Daytime and Nightime overlay is set to "User - ???"
The overlay data isn't appearing though

EricClaeys Jan 7, 2025
Maintainer

@Alex-developer, can you help?

@NeilAllison147, Alex is the Overlay/Module guru.

NeilAllison147 · 2025-01-07T09:48:24Z

NeilAllison147
Jan 7, 2025
Author

Aaaaannnndddd the overlay data is back :)

0 replies

Alex-developer · 2025-01-08T20:58:57Z

Alex-developer
Jan 8, 2025
Maintainer

This is odd.

The upgrade renames the overlay files and adds meta data to them. The attached overlay.json is in the old format suggesting its not been thru the upgrade process. Using the old format overlays in the new overlay manager will confuse it

@NeilAllison147 Do you still have the installation log? They are in ~/allsky/config/logs its the install.log file that I am initially interested in

Thanks

Alex

0 replies

NeilAllison147 · 2025-01-08T22:29:37Z

NeilAllison147
Jan 8, 2025
Author

install.log is attached, @Alex-developer

This was upgraded, not installed from scratch as my camera is not accessible (and the Pi is housed with the camera).

(Alex) EDIT: I have removed the log as it has some sensitive details in it

1 reply

EricClaeys Jan 9, 2025
Maintainer

FYI, the sensitive data is not added to the log file in the next Allsky release.

NeilAllison147 · 2025-01-08T22:32:49Z

NeilAllison147
Jan 8, 2025
Author

Actually, that's not 100% correct.
I renamed the allsky folder to allsky-OLD and then ran the install.
So it sort of IS a new install but on an SD card that had a previous install on it

0 replies

Alex-developer · 2025-01-08T22:41:04Z

Alex-developer
Jan 8, 2025
Maintainer

Thanks for that

It looks like the install was run twice, once at 10:23 and again at 10:33

In the 10:23 install the installer used a default overlay as no prior allsky was found

Fri 13 Dec 10:23:00 AEDT 2024 * No prior Allsky found at '/home/neil/allsky-OLD'.

Fri 13 Dec 10:29:18 AEDT 2024 * Using overlay 'overlay-RPi_HQ-4056x3040-both.json'.
Fri 13 Dec 10:29:19 AEDT 2024 *     OVERLAY_NAME: daytimeoverlay = overlay-RPi_HQ-4056x3040-both.json, TYPE=text
Fri 13 Dec 10:29:19 AEDT 2024 *     OVERLAY_NAME: nighttimeoverlay = overlay-RPi_HQ-4056x3040-both.json, TYPE=text

Did you copy the overlay.json file from anywhere as it should be using the 'overlay-RPi_HQ-4056x3040-both.json' overlay which is in the myTemplates folder.

You could try editing the settings.json file and change the following two lines to this. It will revert the overlay back to the default one provided by Allsky.

    "daytimeoverlay": "overlay-RPi_HQ-4056x3040-both.json",
    "nighttimeoverlay": "overlay-RPi_HQ-4056x3040-both.json",

Then let Allsky run for a while and if all is ok go into the overlay editor and create a new overlay and add your fields back

I could try and manually convert the overlay.json file you provided if that will help but do the steps above first

0 replies

NeilAllison147 · 2025-01-09T00:06:51Z

NeilAllison147
Jan 9, 2025
Author

Hi Alex

Can you send me the standard overlay-RPi_HQ-4056x3040-both.json file please, Alex?
It seems I've inadvertently made some changes to it as it contains some of my site specific data.

On the plus side, it does seem to be behaving itself now that I've made the changes you suggested.

I have to be honest though, I'm struggling to understand how the whole overlay process works now.
When I go to the overlay editor, it comes up with the message "You are using a default day time overlay. To create a new overlay click here"
So I click to create a new one. Once I've created it, I can't see it anywhere.
What am I missing?

Video is attached.

Overlay.mp4

1 reply

Alex-developer Jan 9, 2025
Maintainer

Hi Alex

Can you send me the standard overlay-RPi_HQ-4056x3040-both.json file please, Alex? It seems I've inadvertently made some changes to it as it contains some of my site specific data.

On the plus side, it does seem to be behaving itself now that I've made the changes you suggested.

I have to be honest though, I'm struggling to understand how the whole overlay process works now. When I go to the overlay editor, it comes up with the message "You are using a default day time overlay. To create a new overlay click here" So I click to create a new one. Once I've created it, I can't see it anywhere. What am I missing?

Video is attached.

Overlay.mp4

Thanks for the video that help a lot and I see whats going on.

There is no need to change the filename under the advance tab just leave it as it is
You overlay is there its the one with the ??? as the details are derived from the filename which you changed

So Do exactly what you did in the vide but leave the advanced tab alone. The overlay will then show up

Hope that helps

Alex

EricClaeys · 2025-01-09T00:46:31Z

EricClaeys
Jan 9, 2025
Maintainer

@NeilAllison147,
All the original files are inder ~/allsky/config_repo.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Allsky keeps reverting back to an old version of the overlay #4078

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 18 comments 6 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Allsky keeps reverting back to an old version of the overlay #4078

NeilAllison147 Dec 18, 2024

Replies: 18 comments · 6 replies

Alex-developer Dec 18, 2024 Maintainer

EricClaeys Dec 18, 2024 Maintainer

NeilAllison147 Dec 18, 2024 Author

NeilAllison147 Jan 6, 2025 Author

EricClaeys Jan 6, 2025 Maintainer

NeilAllison147 Jan 7, 2025 Author

EricClaeys Jan 7, 2025 Maintainer

NeilAllison147 Jan 7, 2025 Author

EricClaeys Jan 7, 2025 Maintainer

EricClaeys Jan 7, 2025 Maintainer

NeilAllison147 Jan 7, 2025 Author

EricClaeys Jan 7, 2025 Maintainer

EricClaeys Jan 7, 2025 Maintainer

NeilAllison147 Jan 7, 2025 Author

EricClaeys Jan 7, 2025 Maintainer

NeilAllison147 Jan 7, 2025 Author

Alex-developer Jan 8, 2025 Maintainer

NeilAllison147 Jan 8, 2025 Author

EricClaeys Jan 9, 2025 Maintainer

NeilAllison147 Jan 8, 2025 Author

Alex-developer Jan 8, 2025 Maintainer

NeilAllison147 Jan 9, 2025 Author

Alex-developer Jan 9, 2025 Maintainer

EricClaeys Jan 9, 2025 Maintainer

NeilAllison147
Dec 18, 2024

Replies: 18 comments 6 replies

Alex-developer
Dec 18, 2024
Maintainer

EricClaeys
Dec 18, 2024
Maintainer

NeilAllison147
Dec 18, 2024
Author

NeilAllison147
Jan 6, 2025
Author

EricClaeys
Jan 6, 2025
Maintainer

NeilAllison147
Jan 7, 2025
Author

EricClaeys
Jan 7, 2025
Maintainer

NeilAllison147
Jan 7, 2025
Author

EricClaeys
Jan 7, 2025
Maintainer

EricClaeys
Jan 7, 2025
Maintainer

NeilAllison147
Jan 7, 2025
Author

EricClaeys Jan 7, 2025
Maintainer

EricClaeys Jan 7, 2025
Maintainer

NeilAllison147 Jan 7, 2025
Author

EricClaeys Jan 7, 2025
Maintainer

NeilAllison147
Jan 7, 2025
Author

Alex-developer
Jan 8, 2025
Maintainer

NeilAllison147
Jan 8, 2025
Author

EricClaeys Jan 9, 2025
Maintainer

NeilAllison147
Jan 8, 2025
Author

Alex-developer
Jan 8, 2025
Maintainer

NeilAllison147
Jan 9, 2025
Author

Alex-developer Jan 9, 2025
Maintainer

EricClaeys
Jan 9, 2025
Maintainer