Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

[Richard Whitcombe]

Just woke up so delayed reply but yep thats exactly the case.

>From index.html.tmpl:

 
#if $current.appTemp.has_data
$obs.label.feels_like: $current.appTemp
#end if


Previously this would display the "feels like" temperature below the 
current temperature.  Now theres simply nothing shown which suggests no 
data.
I cant remember if it appeared on v5 but before i fixed the database by 
adding AppTemp and calc-missing though.

Can see how this could more be a skin problem than weewx related though so 
might not be applicable to this group.
On Sunday 21 January 2024 at 04:06:16 UTC+9 vince wrote:

> In index.html.tmpl..
>
> #if $current.appTemp.has_data
>  $obs.label.feels_like: 
> $current.appTemp
> #end if
>
> So he has no current appTemp value apparently.
>
> On Saturday, January 20, 2024 at 9:29:24 AM UTC-8 Colin Larsen wrote:
>
>> I guess he means this "feels like" which as far as I know is a 
>> derived/calculated field in the skin
>>
>> [image: image.png]
>>
>> On Sun, 21 Jan 2024 at 03:13, Tom Keffer  wrote:
>>
>>> Richard, you're going to have to give us more information than this. The 
>>> only reference to "feels like" that I can find in the Belchertown skin has 
>>> been commented out. Where are you seeing this?
>>>
>>> On Fri, Jan 19, 2024 at 7:25 PM Richard Whitcombe  
>>> wrote:
>>>
>>>> Actually follow up that ive only just noticed.
>>>> Since performing this fix ive lost the "Feels like" temperature display 
>>>> on my skin on all pages.
>>>>
>>>> On Friday 19 January 2024 at 19:47:31 UTC+9 Richard Whitcombe wrote:
>>>>
>>>>> I just did AppTemperature but its working for me.
>>>>> Although i dont think i use any of the other columns as my station 
>>>>> doesnt provide it.
>>>>>
>>>>> Missing data calculations took about 8 minutes for 7 years of data on 
>>>>> a Pi4.
>>>>>
>>>>> On Friday 19 January 2024 at 19:14:09 UTC+9 mh081...@gmail.com wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> as i read in the other posts about this Problem i doing now following.
>>>>>>
>>>>>> weectl database add-column appTemp
>>>>>> weectl database add-column cloudbase
>>>>>> weectl database add-column visibility
>>>>>> weectl database add-column windrun
>>>>>> weectl database add-column cloud_cover
>>>>>> weectl database add-column aqi
>>>>>>
>>>>>> weectl database calc-missing
>>>>>>
>>>>>> Answer all wit 'y'
>>>>>>
>>>>>> Now it seems that the Problem was solved. Belchertown Reports was 
>>>>>> generated in about 6 seconds. Thanks @vince for your right direction.
>>>>>> ##
>>>>>> Jan 19 11:09:50 wetter weewxd[293936]: INFO weewx.engine: Loading 
>>>>>> station type Vantage (weewx.drivers.vantage)
>>>>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: StdConvert 
>>>>>> target unit is 0x1
>>>>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.wxservices: 
>>>>>> StdWXCalculate will use data binding wx_binding
>>>>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Archive 
>>>>>> will use data binding wx_binding
>>>>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Record 
>>>>>> generation will be attempted in 'hardware'
>>>>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Using 
>>>>>> archive interval of 300 seconds (specified by hardware)
>>>>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: 
>>>>>> StationRegistry: Registration not requested.
>>>>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: 
>>>>>> Wunderground-PWS: Data for station IMECKLEN47 will be posted
>>>>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: 
>>>>>> Data for station MHROSTOCK will be posted
>>>>>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: CWOP: 
>>>>>> Posting not enabled.
>>>>>

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

[Richard Whitcombe]

Actually follow up that ive only just noticed.
Since performing this fix ive lost the "Feels like" temperature display on 
my skin on all pages.

On Friday 19 January 2024 at 19:47:31 UTC+9 Richard Whitcombe wrote:

> I just did AppTemperature but its working for me.
> Although i dont think i use any of the other columns as my station doesnt 
> provide it.
>
> Missing data calculations took about 8 minutes for 7 years of data on a 
> Pi4.
>
> On Friday 19 January 2024 at 19:14:09 UTC+9 mh081...@gmail.com wrote:
>
>> Hi,
>>
>> as i read in the other posts about this Problem i doing now following.
>>
>> weectl database add-column appTemp
>> weectl database add-column cloudbase
>> weectl database add-column visibility
>> weectl database add-column windrun
>> weectl database add-column cloud_cover
>> weectl database add-column aqi
>>
>> weectl database calc-missing
>>
>> Answer all wit 'y'
>>
>> Now it seems that the Problem was solved. Belchertown Reports was 
>> generated in about 6 seconds. Thanks @vince for your right direction.
>> ##
>> Jan 19 11:09:50 wetter weewxd[293936]: INFO weewx.engine: Loading station 
>> type Vantage (weewx.drivers.vantage)
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: StdConvert 
>> target unit is 0x1
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.wxservices: 
>> StdWXCalculate will use data binding wx_binding
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Archive will 
>> use data binding wx_binding
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Record 
>> generation will be attempted in 'hardware'
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Using archive 
>> interval of 300 seconds (specified by hardware)
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: StationRegistry: 
>> Registration not requested.
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: 
>> Wunderground-PWS: Data for station IMECKLEN47 will be posted
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: Data 
>> for station MHROSTOCK will be posted
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: CWOP: Posting 
>> not enabled.
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: WOW: Posting not 
>> enabled.
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: AWEKAS: Posting 
>> not enabled.
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: service version is 
>> 0.23
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: binding to 
>> ['archive', 'loop']
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: topic is weather
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: desired unit 
>> system is METRIC
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: data will be 
>> uploaded to mqtt://pi:x...@gw.martenhinrichs.de:8883/ 
>> <http://pi:x...@gw.martenhinrichs.de:8883/>
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: network 
>> encryption/authentication will be attempted
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: 'pyephem' 
>> detected, extended almanac data is available
>> Jan 19 11:09:53 wetter weewxd[293936]: INFO __main__: Starting up weewx 
>> version 5.0.0
>> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Clock error is 
>> 2.69 seconds (positive is fast)
>> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Using binding 
>> 'wx_binding' to database 'weewx.sdb'
>> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Starting 
>> backfill of daily summaries
>> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Daily 
>> summaries up to date
>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.wxxtypes: Type beaufort 
>> has been deprecated. Use unit beaufort instead.
>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
>> 2024-01-19 10:50:00 CET (1705657800) to database 'weewx.sdb'
>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
>> 2024-01-19 10:50:00 CET (1705657800) to daily summary in 'weewx.sdb'
>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
>> 2024-01-19 10:55:00 CET (1705658100) to database 'weewx.sdb'
>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
>> 2024-01-19 10:55:00 CET (1705658100) to daily summary in 'weewx.sdb'
>> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
>> 2024-01-19 11:00:00 CET (1705658400) to da

Re: [weewx-user] I'm desperate to fix my NOAA reports. Can I please pay someone to help fix my database and recover this data?

[Richard Whitcombe]

I have an Aercus Weathsleuth so not sure (run via the interceptor driver).  
Backup the DB and theres nothing to lose by trying the solution really.
On Saturday 20 January 2024 at 01:33:14 UTC+9 Michael Sanphillipo wrote:

> Richard, just curious do you have an Acurite weather station and using 
> Belcherstown? I'm just trying to see if we have the same type of setup 
> before going back to V5 and trying your solution. Thanks!
>
> On Friday, January 19, 2024 at 5:49:18 AM UTC-5 Richard Whitcombe wrote:
>
>> FWIW i just needed to add appTemp and its worked - report generation now 
>> takes 3 seconds not 190.
>> I would caveat that by saying im not using the other missing columns at 
>> all as my station doesnt provide the data so maybe if you are they need to 
>> be added too.
>> Missing data calculations took about 8 mins for 2017 - 2024 on a Pi4.
>>
>> On Friday 19 January 2024 at 15:59:15 UTC+9 vince wrote:
>>
>>> Re: the Belchertown issue many seem to be facing, I notice that Blaine's 
>>> db uses the original old wview schema, not the newer bigger 
>>> 'wview_extended' schema that came out a few years ago.  I suspect this is 
>>> the pattern we've missed.  Folks who have the old schema do not have any of 
>>> the elements for many of the Extended Observations in Belchertown's 
>>> skin.conf file. 
>>>
>>> Blaine's db schema misses these items in Belchertown's skin.conf 
>>> extended observations list
>>> appTemp  = Apparent Temperature
>>> cloudbase= Cloud Base
>>> visibility   = Visibility
>>> windrun  = Wind Run
>>> cloud_cover  = Cloud Cover
>>> aqi  = AQI
>>>
>>> The wview_extended schema is missing these, so I'd expect users with 
>>> data in those somehow might have the same slowness issue until they add db 
>>> elements and calc-missing to generate summary tables for them.
>>> visibility   = Visibility
>>> cloud_cover  = Cloud Cover
>>>
>>> Re: Michael's question about what to do about the NOAA files, I'd 
>>> suggest pre-calculating them offline and dropping them into place in his 
>>> NOAA subdirectory with the appropriate owner/group/mode so they don't have 
>>> to be recalculated.  I'd omit the current month+year which should 
>>> regenerate quickly on weewx startup.  That would be a good thing to try. 
>>>  We've verified the db is ok, so it 'should' work on Blaine's system too 
>>> (hopefully).  The test then would be to simply look at the date+time last 
>>> modified for the current month and year NOAA file.  It should change every 
>>> archive period as StdReport runs.
>>>
>>> (reminder - if you have Belchertown 'and' Seasons, you need to drop the 
>>> pre-calculated NOAA files into both places to preseed both skin output 
>>> directories)
>>>
>>> On Thursday, January 18, 2024 at 8:36:20 PM UTC-8 michael.k...@gmx.at 
>>> wrote:
>>>
>>>> Or, to speed things up, do the "calc-missing" on another machine with a 
>>>> more potent CPU.
>>>>
>>>> Back to Blaine's problem: if the NOAA files are generated on other 
>>>> installations with his database, there is obviously another problem with 
>>>> his installation.I don't have an idea what to look for, if deleted NOAA 
>>>> data will be regenerated in the same way, as before.
>>>>
>>>> vince schrieb am Freitag, 19. Januar 2024 um 04:55:13 UTC+1:
>>>>
>>>>> Docs are at https://www.weewx.com/docs/5.0/utilities/weectl-database/ 
>>>>> but what I did for a pip installation using Blaine's db was:
>>>>>
>>>>> source ~/weewx-venv/bin/activate
>>>>> weectl database add-column appTemp
>>>>> weectl calc-missing
>>>>> (answer y when prompted above)
>>>>>
>>>>> If you have a packaged install of weewx you can skip the activate step 
>>>>> above.
>>>>>
>>>>> Note - the calc-missing takes quite a while and will peg your cpu 
>>>>> while working, so if you have a lot of data so you might need to use the 
>>>>> --from and --to options or even the --tranche option to split up the 
>>>>> processing a bit into pieces.  I got lucky with this db on pi3plus with a 
>>>>> bit of patience waiting for calc-missing to comp

Re: [weewx-user] I'm desperate to fix my NOAA reports. Can I please pay someone to help fix my database and recover this data?

[Richard Whitcombe]

'
>>> 2024-01-18T19:45:19.659002-08:00 pi3plus weewxd[1797]: INFO 
>>> weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 3.92 
>>> seconds
>>> 2024-01-18T19:45:20.884377-08:00 pi3plus weewxd[1797]: INFO 
>>> weewx.imagegenerator: Generated 15 images for report SeasonsReport in 1.14 
>>> seconds
>>> 2024-01-18T19:45:20.893901-08:00 pi3plus weewxd[1797]: INFO 
>>> weewx.reportengine: Copied 5 files to /home/pi/weewx-data/public_html
>>> 2024-01-18T19:45:20.967437-08:00 pi3plus weewxd[1797]: INFO 
>>> user.belchertown: version 1.3.1
>>> 2024-01-18T19:45:37.910258-08:00 pi3plus weewxd[1797]: INFO 
>>> weewx.cheetahgenerator: Generated 12 files for report Belchertown in 16.96 
>>> seconds
>>> 2024-01-18T19:45:37.947603-08:00 pi3plus weewxd[1797]: INFO 
>>> weewx.reportengine: Copied 40 files to 
>>> /home/pi/weewx-data/public_html/belchertown
>>>
>>> 2024-01-18T19:50:15.410986-08:00 pi3plus weewxd[1797]: INFO 
>>> weewx.manager: Added record 2024-01-18 19:50:00 PST (1705636200) to 
>>> database 'weewx.sdb'
>>> 2024-01-18T19:50:15.438866-08:00 pi3plus weewxd[1797]: INFO 
>>> weewx.manager: Added record 2024-01-18 19:50:00 PST (1705636200) to daily 
>>> summary in 'weewx.sdb'
>>> 2024-01-18T19:50:18.223483-08:00 pi3plus weewxd[1797]: INFO 
>>> weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 2.65 
>>> seconds
>>> 2024-01-18T19:50:19.311313-08:00 pi3plus weewxd[1797]: INFO 
>>> weewx.imagegenerator: Generated 15 images for report SeasonsReport in 1.08 
>>> seconds
>>> 2024-01-18T19:50:19.313932-08:00 pi3plus weewxd[1797]: INFO 
>>> weewx.reportengine: Copied 0 files to /home/pi/weewx-data/public_html
>>> 2024-01-18T19:50:31.266819-08:00 pi3plus weewxd[1797]: INFO 
>>> weewx.cheetahgenerator: Generated 12 files for report Belchertown in 11.89 
>>> seconds
>>> 2024-01-18T19:50:31.277235-08:00 pi3plus weewxd[1797]: INFO 
>>> weewx.reportengine: Copied 3 files to 
>>> /home/pi/weewx-data/public_html/belchertown
>>>
>>> So the commands above 'did' fix this particular db.
>>> (thanks Tom)
>>>
>>> On Thursday, January 18, 2024 at 6:21:01 PM UTC-8 Richard Whitcombe 
>>> wrote:
>>>
>>>> Can you explain in laymans terms how to do that?
>>>> Do you mean add a new DB field using SQL or similar and leave it blank 
>>>> or something else?
>>>>
>>>> Or outline trouble shooting steps to isolate the cause in simple terms 
>>>> (ie familiar with linux and the basics of weewx but not the core detailed 
>>>> functionality).
>>>>
>>>> On Friday 19 January 2024 at 08:12:14 UTC+9 Tom Keffer wrote:
>>>>
>>>>> Using Blaine's database, I was able to isolate the performance 
>>>>> problems.
>>>>>
>>>>> It's in the template records/index.html.tmpl
>>>>>
>>>>> Specifically, apparent temperature (appTemp). It does not appear in 
>>>>> the database, so a simple tag such as $alltime.appTemp.max requires 
>>>>> searching the engine database, calculating apparent temperature for each 
>>>>> record, then finding the max value.
>>>>>
>>>>> In V4, this would not have even been attempted.
>>>>>
>>>>> The solution is to add appTemp to the database. 
>>>>>
>>>>> On Thu, Jan 18, 2024 at 1:33 PM vince  wrote:
>>>>>
>>>>>> Tom - the NOAA stuff builds from this db ok for me v5 pip on pi3+.  
>>>>>> The Seasons skin NOAA file for 2024-01 'is' being updated every 
>>>>>> archive period.
>>>>>> The historical files dating back to 2014 generated fine.
>>>>>>
>>>>>> Unrelated but interesting.
>>>>>>
>>>>>>- this db shows the Belchertown taking too long issue
>>>>>>- running htop I see it peg two cpus and StdReport aborts due to 
>>>>>>time vs. the Simulator 300 sec on a pi3+
>>>>>>- Belchertown 'always' takes longer than 300 secs and weewx 
>>>>>>always aborts due to StdReport not completing in 300 secs
>>>>>>- yet the same installation with 'my' db works fine with no 
>>>>>>issues, so it 'has' to be content of the db being used doesn't it ?
>>>>>>- I have been unable t

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

[Richard Whitcombe]

I just did AppTemperature but its working for me.
Although i dont think i use any of the other columns as my station doesnt 
provide it.

Missing data calculations took about 8 minutes for 7 years of data on a Pi4.

On Friday 19 January 2024 at 19:14:09 UTC+9 mh081...@gmail.com wrote:

> Hi,
>
> as i read in the other posts about this Problem i doing now following.
>
> weectl database add-column appTemp
> weectl database add-column cloudbase
> weectl database add-column visibility
> weectl database add-column windrun
> weectl database add-column cloud_cover
> weectl database add-column aqi
>
> weectl database calc-missing
>
> Answer all wit 'y'
>
> Now it seems that the Problem was solved. Belchertown Reports was 
> generated in about 6 seconds. Thanks @vince for your right direction.
> ##
> Jan 19 11:09:50 wetter weewxd[293936]: INFO weewx.engine: Loading station 
> type Vantage (weewx.drivers.vantage)
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: StdConvert 
> target unit is 0x1
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.wxservices: 
> StdWXCalculate will use data binding wx_binding
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Archive will use 
> data binding wx_binding
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Record 
> generation will be attempted in 'hardware'
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Using archive 
> interval of 300 seconds (specified by hardware)
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: StationRegistry: 
> Registration not requested.
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: Wunderground-PWS: 
> Data for station IMECKLEN47 will be posted
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: Data 
> for station MHROSTOCK will be posted
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: CWOP: Posting not 
> enabled.
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: WOW: Posting not 
> enabled.
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: AWEKAS: Posting 
> not enabled.
> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: service version is 
> 0.23
> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: binding to 
> ['archive', 'loop']
> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: topic is weather
> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: desired unit system 
> is METRIC
> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: data will be 
> uploaded to mqtt://pi:x...@gw.martenhinrichs.de:8883/ 
> 
> Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: network 
> encryption/authentication will be attempted
> Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: 'pyephem' 
> detected, extended almanac data is available
> Jan 19 11:09:53 wetter weewxd[293936]: INFO __main__: Starting up weewx 
> version 5.0.0
> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Clock error is 
> 2.69 seconds (positive is fast)
> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Using binding 
> 'wx_binding' to database 'weewx.sdb'
> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Starting 
> backfill of daily summaries
> Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Daily summaries 
> up to date
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.wxxtypes: Type beaufort 
> has been deprecated. Use unit beaufort instead.
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
> 2024-01-19 10:50:00 CET (1705657800) to database 'weewx.sdb'
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
> 2024-01-19 10:50:00 CET (1705657800) to daily summary in 'weewx.sdb'
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
> 2024-01-19 10:55:00 CET (1705658100) to database 'weewx.sdb'
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
> 2024-01-19 10:55:00 CET (1705658100) to daily summary in 'weewx.sdb'
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
> 2024-01-19 11:00:00 CET (1705658400) to database 'weewx.sdb'
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
> 2024-01-19 11:00:00 CET (1705658400) to daily summary in 'weewx.sdb'
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: 
> Published record 2024-01-19 10:50:00 CET (1705657800)
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
> 2024-01-19 11:05:00 CET (1705658700) to database 'weewx.sdb'
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 
> 2024-01-19 11:05:00 CET (1705658700) to daily summary in 'weewx.sdb'
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.engine: Starting main 
> packet loop.
> Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: 
> Published record 2024-01-19 10:55:00 CET (1705658100)
> Jan 19 11:09:56 wetter 

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

[Richard Whitcombe]

In my case with the same problem, im NOT using the extended schema - it 
returns 52.

On Friday 19 January 2024 at 16:32:51 UTC+9 vince wrote:

> Followup on this one - If the original poster can check to see if their 
> database uses the old original (small) wview schema that would likely help. 
>  Easiest way is to look to see how many elements are in the database. One 
> way to see how many elements you have in your db would be:
>
>- cp weewx.sdb /var/tmp/test.sdb
>- echo "select count(*) from pragma_table_info('archive');" | sqlite3 
>/var/tmp/test.sdb
>   - (my db with the extended schema returns "114" as the count)
>   - (a db with the original wview schema returns "52" as the count)
>
>
> Switching to the extended schema is a bit of work and takes some time. 
>  The details are documented at 
> http://www.weewx.com/docs/5.0/custom/database/ with the procedure for how 
> to switch to the new bigger schema in 
> http://www.weewx.com/docs/5.0/custom/database/#reconfigure-using-new-schema 
> - but be CAREFUL doing this and ALWAYS work off a copy of your db so if 
> anything happens you can revert to a known good db.   I've done it so many 
> years ago at this point that I'll have to defer to others for pitfalls and 
> how they do it, but the links above are how the current docs recommend 
> doing so.
>
> Short description to the original Belchertown problem reporters - check 
> your db schema.  Hopefully that's the pattern of which systems will need to 
> take action.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a9f501bc-35a6-453e-a8ba-a558d7958103n%40googlegroups.com.

Re: [weewx-user] I'm desperate to fix my NOAA reports. Can I please pay someone to help fix my database and recover this data?

[Richard Whitcombe]

Can you explain in laymans terms how to do that?
Do you mean add a new DB field using SQL or similar and leave it blank or 
something else?

Or outline trouble shooting steps to isolate the cause in simple terms (ie 
familiar with linux and the basics of weewx but not the core detailed 
functionality).

On Friday 19 January 2024 at 08:12:14 UTC+9 Tom Keffer wrote:

> Using Blaine's database, I was able to isolate the performance problems.
>
> It's in the template records/index.html.tmpl
>
> Specifically, apparent temperature (appTemp). It does not appear in the 
> database, so a simple tag such as $alltime.appTemp.max requires searching 
> the engine database, calculating apparent temperature for each record, then 
> finding the max value.
>
> In V4, this would not have even been attempted.
>
> The solution is to add appTemp to the database. 
>
> On Thu, Jan 18, 2024 at 1:33 PM vince  wrote:
>
>> Tom - the NOAA stuff builds from this db ok for me v5 pip on pi3+.  
>> The Seasons skin NOAA file for 2024-01 'is' being updated every archive 
>> period.
>> The historical files dating back to 2014 generated fine.
>>
>> Unrelated but interesting.
>>
>>- this db shows the Belchertown taking too long issue
>>- running htop I see it peg two cpus and StdReport aborts due to time 
>>vs. the Simulator 300 sec on a pi3+
>>- Belchertown 'always' takes longer than 300 secs and weewx always 
>>aborts due to StdReport not completing in 300 secs
>>- yet the same installation with 'my' db works fine with no issues, 
>>so it 'has' to be content of the db being used doesn't it ?
>>- I have been unable to get Belchertown to succeed even at 600 secs 
>>archive period.
>>
>> Question - why would the db be 'locked' if a skin is reading it in order 
>> to process its contents ??
>>
>> last restart/failure...
>>
>> Jan 18 13:15:10 pi3plus weewxd[1756]: INFO __main__: Starting up weewx 
>> version 5.0.0
>> Jan 18 13:15:10 pi3plus weewxd[1756]: INFO weewx.engine: Clock error is 
>> -0.21 seconds (positive is fast)
>> Jan 18 13:15:10 pi3plus weewxd[1756]: INFO weewx.engine: Using binding 
>> 'wx_binding' to database 'weewx.sdb'
>> Jan 18 13:15:10 pi3plus weewxd[1756]: INFO weewx.manager: Starting 
>> backfill of daily summaries
>> Jan 18 13:15:10 pi3plus weewxd[1756]: INFO weewx.manager: Daily summaries 
>> up to date
>> Jan 18 13:15:10 pi3plus weewxd[1756]: INFO weewx.engine: Starting main 
>> packet loop.
>> Jan 18 13:20:15 pi3plus weewxd[1756]: INFO weewx.manager: Added record 
>> 2024-01-18 13:20:00 PST (1705612800) to database 'weewx.sdb'
>> Jan 18 13:20:15 pi3plus weewxd[1756]: INFO weewx.manager: Added record 
>> 2024-01-18 13:20:00 PST (1705612800) to daily summary in 'weewx.sdb'
>> Jan 18 13:20:19 pi3plus weewxd[1756]: INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 3.96 seconds
>> Jan 18 13:20:24 pi3plus weewxd[1756]: INFO weewx.imagegenerator: 
>> Generated 30 images for report SeasonsReport in 4.80 seconds
>> Jan 18 13:20:24 pi3plus weewxd[1756]: INFO weewx.reportengine: Copied 5 
>> files to /home/pi/weewx-data/public_html
>> Jan 18 13:20:24 pi3plus weewxd[1756]: INFO user.belchertown: version 1.3.1
>> Jan 18 13:30:15 pi3plus weewxd[1756]: INFO weewx.manager: Added record 
>> 2024-01-18 13:30:00 PST (1705613400) to database 'weewx.sdb'
>> Jan 18 13:30:15 pi3plus weewxd[1756]: INFO weewx.manager: Added record 
>> 2024-01-18 13:30:00 PST (1705613400) to daily summary in 'weewx.sdb'
>> Jan 18 13:30:20 pi3plus weewxd[1756]: INFO weewx.engine: Main loop 
>> exiting. Shutting engine down.
>> Jan 18 13:30:20 pi3plus weewxd[1756]: INFO weewx.engine: Shutting down 
>> StdReport thread
>> Jan 18 13:30:40 pi3plus weewxd[1756]: ERROR weewx.engine: Unable to shut 
>> down StdReport thread
>> Jan 18 13:30:40 pi3plus weewxd[1756]: CRITICAL __main__: Database 
>> OperationalError exception: database is locked
>> Jan 18 13:30:40 pi3plus weewxd[1756]: CRITICAL __main__:  
>>  Waiting 2 minutes then retrying...
>> Jan 18 13:30:42 pi3plus weewxd[1756]: INFO weewx.cheetahgenerator: 
>> Generated 12 files for report Belchertown in 617.64 seconds
>> Jan 18 13:30:42 pi3plus weewxd[1756]: INFO weewx.reportengine: Copied 40 
>> files to /home/pi/weewx-data/public_html/belchertown
>>
>>
>> weewx related open files:
>>
>> pi@pi3plus:~/weewx-data $ lsof|grep weew
>> python3   1633pi  mem   REG  179,2   
>>  217360 272588 
>> /home/pi/weewx-data/skins/Seasons/font/OpenSans-Regular.ttf
>> python3   1633pi  mem   REG  179,2   
>>  224592 272587 /home/pi/weewx-data/skins/Seasons/font/OpenSans-Bold.ttf
>> python3   1633pi  mem   REG  179,2   
>> 1630340 271670 /home/pi/weewx-venv/lib/python3.11/site-packages/PIL/_
>> imaging.cpython-311-arm-linux-gnueabihf.so
>> python3   1633pi  mem   REG  179,2   
>> 2528660 271317 

[weewx-user] Re: v5.0 main loop exiting/restarting constantly and very slow/misses readings

[Richard Whitcombe]

Should add yes, to confirm i see 2 threads of weewxd.py at 100% CPU at this 
point.

On Friday 19 January 2024 at 11:14:09 UTC+9 Richard Whitcombe wrote:

> Disabling Belchertown or selecting Standard/Sofaskin and it all appears 
> normal - report generation is 3 seconds or so as it used to be.
> Re-enabling Belchertown and problem returns - 3+ minutes, pegged out 
> performance, main loop crashing.
> FWIW whatever causes this is new in 5.0 as its been fine on all previous 
> versions.
>
> Its running on a Pi4 / 2gb under Raspbian.
>
> On Friday 19 January 2024 at 03:24:52 UTC+9 vince wrote:
>
>> On Thursday, January 18, 2024 at 2:14:23 AM UTC-8 Richard Whitcombe wrote:
>>
>> What im seeing now is the service seems to start fine, but after each 5 
>> min cycle the entire thread seems to kill itself and reload/reinitialise 
>> from scratch.
>>
>> INFO weewx.cheetahgenerator: Generated 12 files for report StandardReport 
>> in 188.04 seconds
>> Jan 18 10:03:28  weewxd[420]: INFO weewx.reportengine: Copied 39 
>> files to /var/www/html/weewx
>> Jan 18 10:05:24  weewxd[420]: INFO weewx.manager: Added record 
>> 2024-01-18 10:05:00 GMT (1705572300) to database 'weewx.sdb'
>> Jan 18 10:05:24  weewxd[420]: INFO weewx.manager: Added record 
>> 2024-01-18 10:05:00 GMT (1705572300) to daily summary in 'weewx.sdb'
>> Jan 18 10:05:29  weewxd[420]: INFO weewx.engine: Main loop 
>> exiting. Shutting engine down.
>> Jan 18 10:05:29  weewxd[420]: INFO weewx.engine: Shutting down 
>> StdReport thread
>> Jan 18 10:05:49  weewxd[420]: INFO user.interceptor: shutting 
>> down server thread
>> Jan 18 10:05:50  weewxd[420]: INFO weewx.cheetahgenerator: 
>> Generated 12 files for report Belchertown in 136.37 seconds
>>
>>
>> Looks like the same thing one or two others have reported. Try 
>> temporarily setting enabled=false for Belchertown, restart weewx, and see 
>> if the problem goes away.
>>
>> If you run 'htop' you will likely see two threads running and the cpu 
>> pegged for both.
>>
>> What model pi are you running on ?
>>
>>  
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b6ee92fa-9dfc-4ccb-86c0-2241c16b61ccn%40googlegroups.com.

[weewx-user] Re: v5.0 main loop exiting/restarting constantly and very slow/misses readings

[Richard Whitcombe]

Disabling Belchertown or selecting Standard/Sofaskin and it all appears 
normal - report generation is 3 seconds or so as it used to be.
Re-enabling Belchertown and problem returns - 3+ minutes, pegged out 
performance, main loop crashing.
FWIW whatever causes this is new in 5.0 as its been fine on all previous 
versions.

Its running on a Pi4 / 2gb under Raspbian.

On Friday 19 January 2024 at 03:24:52 UTC+9 vince wrote:

> On Thursday, January 18, 2024 at 2:14:23 AM UTC-8 Richard Whitcombe wrote:
>
> What im seeing now is the service seems to start fine, but after each 5 
> min cycle the entire thread seems to kill itself and reload/reinitialise 
> from scratch.
>
> INFO weewx.cheetahgenerator: Generated 12 files for report StandardReport 
> in 188.04 seconds
> Jan 18 10:03:28  weewxd[420]: INFO weewx.reportengine: Copied 39 
> files to /var/www/html/weewx
> Jan 18 10:05:24  weewxd[420]: INFO weewx.manager: Added record 
> 2024-01-18 10:05:00 GMT (1705572300) to database 'weewx.sdb'
> Jan 18 10:05:24  weewxd[420]: INFO weewx.manager: Added record 
> 2024-01-18 10:05:00 GMT (1705572300) to daily summary in 'weewx.sdb'
> Jan 18 10:05:29  weewxd[420]: INFO weewx.engine: Main loop 
> exiting. Shutting engine down.
> Jan 18 10:05:29  weewxd[420]: INFO weewx.engine: Shutting down 
> StdReport thread
> Jan 18 10:05:49  weewxd[420]: INFO user.interceptor: shutting down 
> server thread
> Jan 18 10:05:50  weewxd[420]: INFO weewx.cheetahgenerator: 
> Generated 12 files for report Belchertown in 136.37 seconds
>
>
> Looks like the same thing one or two others have reported. Try temporarily 
> setting enabled=false for Belchertown, restart weewx, and see if the 
> problem goes away.
>
> If you run 'htop' you will likely see two threads running and the cpu 
> pegged for both.
>
> What model pi are you running on ?
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5d2ff79c-7ae8-4291-af56-31c15f359e5bn%40googlegroups.com.

[weewx-user] v5.0 main loop exiting/restarting constantly and very slow/misses readings

[Richard Whitcombe]

I accidentally updated to v5.0 (Debian apt update) and since then my 
install has basically been broken and i cant seem to work out why.

Running on a RaPi for years with no issue, using Belchertown skin.

What im seeing now is the service seems to start fine, but after each 5 min 
cycle the entire thread seems to kill itself and reload/reinitialise from 
scratch.

In logs:

INFO weewx.cheetahgenerator: Generated 12 files for report StandardReport 
in 188.04 seconds
Jan 18 10:03:28  weewxd[420]: INFO weewx.reportengine: Copied 39 
files to /var/www/html/weewx
Jan 18 10:05:24  weewxd[420]: INFO weewx.manager: Added record 
2024-01-18 10:05:00 GMT (1705572300) to database 'weewx.sdb'
Jan 18 10:05:24  weewxd[420]: INFO weewx.manager: Added record 
2024-01-18 10:05:00 GMT (1705572300) to daily summary in 'weewx.sdb'
Jan 18 10:05:29  weewxd[420]: INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Jan 18 10:05:29  weewxd[420]: INFO weewx.engine: Shutting down 
StdReport thread
Jan 18 10:05:49  weewxd[420]: INFO user.interceptor: shutting down 
server thread
Jan 18 10:05:50  weewxd[420]: INFO weewx.cheetahgenerator: 
Generated 12 files for report Belchertown in 136.37 seconds


Jan 18 10:07:49  weewxd[420]: INFO __main__: retrying...
Jan 18 10:07:49  weewxd[420]: INFO weewx.engine: Loading station 
type Interceptor (user.interceptor)
Jan 18 10:07:49  weewxd[420]: INFO user.interceptor: driver version 
is 0.60
Jan 18 10:07:49  weewxd[420]: INFO user.interceptor: device type: 
observer
Jan 18 10:07:49  weewxd[420]: INFO user.interceptor: hardware name: 
weatherstation via interceptor
Jan 18 10:07:49  weewxd[420]: INFO user.interceptor: mode is listen
Jan 18 10:07:49  weewxd[420]: INFO user.interceptor: listen on :8090
Jan 18 10:07:49  weewxd[420]: INFO user.interceptor: sensor map: 
{'pressure': 'pressure', 'barometer': 'barometer', 'outHumidity': 
'humidity_out', 'inHumidity': 'humidity_in', 'outTemp': 'temperature_out', 
'inTemp': 'temperature_in', 'windSpeed': 'wind_speed', 'windGust': 
'wind_gust', 'windDir': 'wind_dir', 'windGustDir': 'wind_gust_dir', 
'radiation': 'solar_radiation', 'dewpoint': 'dewpoint', 'windchill': 
'windchill', 'rain': 'rain', 'rainRate': 'rain_rate', 'UV': 'uv', 
'txBatteryStatus': 'battery', 'extraTemp1': 'temperature_1', 'extraTemp2': 
'temperature_2', 'extraTemp3': 'temperature_3', 'extraHumid1': 
'humidity_1', 'extraHumid2': 'humidity_2', 'soilTemp1': 
'soil_temperature_1', 'soilTemp2': 'soil_temperature_2', 'soilMoist1': 
'soil_moisture_1', 'soilMoist2': 'soil_moisture_2', 'soilMoist3': 
'soil_moisture_3', 'soilMoist4': 'soil_moisture_4', 'leafWet1': 
'leafwetness_1', 'leafWet2': 'leafwetness_2', 'pm2_5': 'pm2_5', 
'extraTemp4': 'temperature_4', 'extraTemp5': 'temperature_5', 'extraTemp6': 
'temperature_6', 'extraTemp7': 'temperature_7', 'extraTemp8': 
'temperature_8', 'extraHumid3': 'humidity_3', 'extraHumid4': 'humidity_4', 
'extraHumid5': 'humidity_5', 'extraHumid6': 'humidity_6', 'extraHumid7': 
'humidity_7', 'extraHumid8': 'humidity_8', 'soilTemp3': 
'soil_temperature_3', 'soilTemp4': 'soil_temperature_4'}
Jan 18 10:07:49  weewxd[420]: INFO weewx.engine: StdConvert target 
unit is 0x1
Jan 18 10:07:49  weewxd[420]: INFO weewx.wxservices: StdWXCalculate 
will use data binding wx_binding
Jan 18 10:07:49  weewxd[420]: INFO weewx.engine: Archive will use 
data binding wx_binding
Jan 18 10:07:49  weewxd[420]: INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Jan 18 10:07:49  weewxd[420]: INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Jan 18 10:07:49  weewxd[420]: INFO weewx.restx: StationRegistry: 
Station will be registered.
Jan 18 10:07:49  weewxd[420]: INFO weewx.restx: Wunderground-PWS: 
Data for station  will be posted
Jan 18 10:07:49  weewxd[420]: INFO weewx.restx: PWSweather: No 
config info. Skipped.
Jan 18 10:07:49  weewxd[420]: INFO weewx.restx: CWOP: Posting not 
enabled.
Jan 18 10:07:49  weewxd[420]: INFO weewx.restx: WOW: Data for 
station XX will be posted
Jan 18 10:07:49  weewxd[420]: INFO weewx.restx: AWEKAS: Posting not 
enabled.
Jan 18 10:07:49  weewxd[420]: INFO user.windy: version is 0.7
Jan 18 10:07:49  weewxd[420]: INFO user.windy: Data will be 
uploaded to https://stations.windy.com/pws/update
Jan 18 10:07:49  weewxd[420]: INFO weewx.engine: 'pyephem' 
detected, extended almanac data is available
Jan 18 10:07:49  weewxd[420]: INFO __main__: Starting up weewx 
version 5.0.0


The end result of this is it isnt getting regular, reliable data at all, 
the graphs have huge gaps and rsync to the server hosting the external 
webpage only seem to work sporadically (every 15 mins or so)

One other thing that stands out is the huge is the time to create 
StandardReport - near 3minutes.
This effectively means it takes most of the 5 minute cycle after reloading 
itself doing this and then crashes and repeats again.

Any idea whats broken, how to fix this or how i can go back 

Re: [weewx-user] Re: Belchertown - Charts suddenly disappeared

[Richard Whitcombe]

Thanks to all that replied - my initial search was in the area of 
"Charts not rendering" and "No graphs" so didn't find the posts.


Im using the workaround to specify 10.3 in the template and will keep 
that until i suspect the best way is to just store everything locally.


Problem solved - thanks to all.



On 27/04/2023 16:31, Rick M0LEP wrote:

On Thu 27 Apr m...@erwinheger.de wrote:

Have you seen this discussion?

The useful link from that "Belchertown graphs stopped working" thread is
probably this one:

https://github.com/poblabs/weewx-belchertown/issues/881



--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/08aafcc0-91c4-1786-e93d-28d9b6fa8b8a%40gmail.com.

[weewx-user] Re: Belchertown - Charts suddenly disappeared

[Richard Whitcombe]

Further to that, on the site itself my Console logs show this error:

Uncaught TypeError: Highcharts.chart is not a constructor
showChart http://192.168.1.2/weewx/js/belchertown.js?1682562025:1198
each jQuery
showChart http://192.168.1.2/weewx/js/belchertown.js?1682562025:488
jQuery 8
c
fireWith
l
o
send
ajax
i
getJSON
showChart http://192.168.1.2/weewx/js/belchertown.js?1682562025:485
 http://192.168.1.2/weewx/:134
jQuery 13
belchertown.js:1198:25
showChart http://192.168.1.2/weewx/js/belchertown.js?1682562025:1198
each jQuery
showChart http://192.168.1.2/weewx/js/belchertown.js?1682562025:488
jQuery 8
c
fireWith
l
o
(Async: EventHandlerNonNull)
send
ajax
i
getJSON
showChart http://192.168.1.2/weewx/js/belchertown.js?1682562025:485
 http://192.168.1.2/weewx/:134
jQuery 13


On Thursday, 27 April 2023 at 11:02:01 UTC+9 Richard Whitcombe wrote:

> Im running the latest WeeWx (  4.10.2) and Belchertown 1.3 skin.
>
> This setup has been running perfectly for several months on an RaPi4.
>
> As of last night it seems to have stopped displaying any charts at all 
> despite me changing nothing in the setup.
> They've just vanished off the home/daily screen and the graph screen.
>
> The logs (set to debug) are showing no errors but nothing at all seems to 
> be displayed any more - just they dont show at all (not frozen, vanished).
>
> I don't see any log errors:-
>
> Apr 27 02:50:32 pi4-logger weewx[9704] DEBUG weewx.reportengine: Running 
> report 'Belchertown'
> Apr 27 02:50:32 pi4-logger weewx[9704] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Belchertown/skin.conf for report 
> 'Belchertown'
> Apr 27 02:50:32 pi4-logger weewx[9704] DEBUG weewx.cheetahgenerator: Using 
> search list ['user.belchertown.getData', 'weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions', 
> 'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
> 'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 
> 'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
> Apr 27 02:50:32 pi4-logger weewx[9704] DEBUG weewx.manager: Daily summary 
> version is 4.0
> Apr 27 02:50:33 pi4-logger weewx[9704] INFO weewx.restx: WOW: Published 
> record 2023-04-27 02:50:00 BST (1682560200)
> Apr 27 02:50:34 pi4-logger weewx[9704] INFO weewx.cheetahgenerator: 
> Generated 12 files for report Belchertown in 2.12 seconds
> Apr 27 02:50:34 pi4-logger weewx[9704] INFO weewx.reportengine: Copied 3 
> files to /var/www/html/weewx
> Apr 27 02:50:34 pi4-logger weewx[9704] DEBUG weewx.manager: Daily summary 
> version is 4.0
> Apr 27 02:50:35 pi4-logger weewx[9704] DEBUG user.interceptor: empty queue
>
> Only 3 files copied is suspicious though - from memory it was a lot more 
> than that.
>
> Live data is still coming in, reports and records are updated just no 
> graphs.
>
> Highcharts = 1 are still enabled in the skin and so on.  Ive manually 
> checked the skin and weewx configs and ensured everything still works.
>
> If it helps the site is public accessible at 
> http://weather.whitcombe.org.uk .  The graphs should appear below the 
> Windy embed.
>
> Any help here appreciated - been tearing my hair out here and just cant 
> see why charts have vanished.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/608d0add-6f0d-4050-a663-3d1a36a9c16en%40googlegroups.com.

[weewx-user] Belchertown - Charts suddenly disappeared

[Richard Whitcombe]

Im running the latest WeeWx (  4.10.2) and Belchertown 1.3 skin.

This setup has been running perfectly for several months on an RaPi4.

As of last night it seems to have stopped displaying any charts at all 
despite me changing nothing in the setup.
They've just vanished off the home/daily screen and the graph screen.

The logs (set to debug) are showing no errors but nothing at all seems to 
be displayed any more - just they dont show at all (not frozen, vanished).

I don't see any log errors:-

Apr 27 02:50:32 pi4-logger weewx[9704] DEBUG weewx.reportengine: Running 
report 'Belchertown'
Apr 27 02:50:32 pi4-logger weewx[9704] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Belchertown/skin.conf for report 
'Belchertown'
Apr 27 02:50:32 pi4-logger weewx[9704] DEBUG weewx.cheetahgenerator: Using 
search list ['user.belchertown.getData', 'weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions', 
'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 
'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
Apr 27 02:50:32 pi4-logger weewx[9704] DEBUG weewx.manager: Daily summary 
version is 4.0
Apr 27 02:50:33 pi4-logger weewx[9704] INFO weewx.restx: WOW: Published 
record 2023-04-27 02:50:00 BST (1682560200)
Apr 27 02:50:34 pi4-logger weewx[9704] INFO weewx.cheetahgenerator: 
Generated 12 files for report Belchertown in 2.12 seconds
Apr 27 02:50:34 pi4-logger weewx[9704] INFO weewx.reportengine: Copied 3 
files to /var/www/html/weewx
Apr 27 02:50:34 pi4-logger weewx[9704] DEBUG weewx.manager: Daily summary 
version is 4.0
Apr 27 02:50:35 pi4-logger weewx[9704] DEBUG user.interceptor: empty queue

Only 3 files copied is suspicious though - from memory it was a lot more 
than that.

Live data is still coming in, reports and records are updated just no 
graphs.

Highcharts = 1 are still enabled in the skin and so on.  Ive manually 
checked the skin and weewx configs and ensured everything still works.

If it helps the site is public accessible at 
http://weather.whitcombe.org.uk .  The graphs should appear below the Windy 
embed.

Any help here appreciated - been tearing my hair out here and just cant see 
why charts have vanished.


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/cde0c591-b603-4215-862b-2cbe259556ebn%40googlegroups.com.