Lat/Long Changed in weewx.conf but FTP Report does not update on remote Webserver

[Herb Carleton]

I am running weewx 4.10.2 on a Beelink Ubuntu Workstation 22.04 with a Vantage Pro 2. 

It is working great so far. We post to Weather Undergound as well and it has the Updated Lat/Log info . The remote Webserver we FTP to (Seasons Skin 4.10.2) the report web page looks great expect it still shows the old Lat/Long settings. When the weewx.conf settings 

were changed the weewx process's were shut down. Then restarted after LAT/LONG edit was made. I am curious if that the Remote Server has a static data file that was sent once that I need to delete and then wait for next cycle (We send every 5 minutes)  to send fresh file and I am hoping the new correct LAT/LONG info will then appear. I am referring to Lat/Long data in the About this station section. The Server and Weewx uptime in that same section is correct. Any input would be very very appreciated.. Thank you

[gjr80]

Any lat/long info for WU will have been entered when setting up/editing the station on the WU web site - WeeWX does not send lat/long info to WU. There are no static files containing lat/long that are part of the Seasons skin, the Seasons skin html files are generated in their entirety and uploaded each report cycle.

You said "When the weewx.conf settings were changed the weewx process's were shut down." Does that mean you restarted the WeeWX daemon? If you make a change to weewx.conf you must restart WeeWX for the change to take effect. In this case the updated lat/long should appear in the files generated during the first report cycle after the restart. If you didn't restart WeeWX you need to do that. Are your generated files being uploaded to your web server? What does the WeeWX log show? Probably best that you edit weewx.conf again, set debug = 1 (and double check your lat/long entries are correct), save weewx.conf and restart WeeWX. Monitor the WeeWX log. Are your Seasons skin files being generated and uploaded? If you cannot work this out let WeeWX run for at least two report cycles then take an extract of the log showing the full WeeWX startup and the first two report cycles. Post the log extract back here.

The other possibility is you have more than one weewx.conf on your system and are editing the wrong one. Try creating a wee_debug report, the report will contain a copy of the config file actually used by WeeWX. Are the lat/long values in the wee_debug report correct? If you have trouble reading the report, post the report here. If you do post the report be sure to check it for sensitive info such as user names, passwords, API keys etc and obfuscate any such entries before posting the report. wee_debug should obfuscate such information but it is not perfect.

Gary

[Herb Carleton]

Thanks for taking the time to reply to my inquiry . I had a miscomunication with team member who did the initial registration for WU. I did not realize the LAT/LONG was entered during registration process on the WU site. I did the weex.conf site for station id/pw. WeeWX  was restarted and I noticed that locally on the Ubuntu Workstation that the local weewx html page also did not show the updated LAT/LONG settings as specified in the weewx.conf but all other weather data looks good and updates every 5 minutes (300 sec) locally on the Ubuntu PC host and also the remote web site. I set debug to 1. I attached the wee_debug  --output datafile and well as syslog over multiple cycles.  Thanks for any input or recomendations. 

[gjr80]

Thanks.

So the correct lat is 41.63 and long is -74.61?

I'm not seeing anything wrong/inconsistent. Your weewx.conf has lat/log of 41.63N/74.61W. Note these are decimal degrees which is equivalent to 41 degrees 37.80 minute N/74 degrees 36.60W. Your WU page show decimal degrees ie 41.63N/74.61W and your Seasons main page shows the degrees/minutes values of 41 degrees 37.80 minute N/74 degrees 36.60W.

All looks good to me just, same info just different display formats.

Or have I missed something? 

Gary