New installation - initially no forecast icons

[swfrx]

I set up a new instance of WeeWx in a Debian 12 virtual machine. I installed the latest WeeWx and Belchertown skin, and edited the forecast section of weewx.conf to include my API key etc. and restarted WeeWx.

Initially I had the Forecast .... Forecast Interval hours line with no forecast images or summary below - see image, they are circled in red.

I clicked '1' and they appeared. This is on a Windows 11 PC using the latest Edge browser. They are there if I use Chrome or my Android phone, but I didn't try those when they weren't appearing.

This seems to be because 'forecast.json' isn't initially created even though '24' shows as selected - clicking a forrecast interval creates it.

I can't give you a link as the VM isn't exposed to the outside world, and I'm currently not FTPing it to somewhere that is.

Please don't delete these questions! They are asked almost with every issue - answering them as below saves us time from asking them!

First step
Try to debug the skin yourself. If you can't figure it out, please include the debug information (text, screenshots, etc.). See this guide on debugging the skin. https://github.com/poblabs/weewx-belchertown#how-to-use-debug

Describe the bug
A clear and concise description of what the bug is.

Link to your website (IMPORTANT)

Version of the skin you're using

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Device Information (please complete the following information):

• Device: [e.g. desktop, iPhone6]
• OS: [e.g. Windows, Android, iOS]
• Browser [e.g. Chrome, Safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here. Maybe a potential fix?

HELP WANTED
If you have a fix for this, please submit a pull request against the development branch!

[uajqq]

Does this problem only happen on the very first time the skin is run? It might be a manifestation of #959, which I opened a pull request to fix.