[weewx-user] Re: cwxn 0.4 error with weewx 4.2

Ray, I'm successfully using cwxn, but I had problems earlier this year. (but not the problem you're having) Here is a thread discussing cwxn.py. Gary, gjr80 modified the file, you can find it in the fourth post in the following thread: https://groups.google.com/g/weewx-user/c/TUn5ibGr9uo

Re: [weewx-user] Re: Bresser 6in1

Hi Bob All sorted. Downloaded and installed the new driver, added wsType = WS5in1, deleted the UV = None from StdCalibrate/Corrections and restarted weewx. All running as hoped for, no UV output. Have also done the change to "software" for heatindex, rainRate and windchill. Many thanks to

Re: [weewx-user] Re: Bresser 6in1

Hi Paul In your case you need to 1) Either follow steps 2 and 3 of the installation in the readme.txt or if you know where the ws6in1.py is located simply replace it with the updated one from github (location is dependent on how you did the original weewx installation) 2) Update your

Re: [weewx-user] Re: Bresser 6in1

Sorry Bob, could you just walk me through updating the driver to 1.02 Thanks, Paul On Saturday, 28 November 2020 at 14:59:29 UTC Bob Atchley wrote: > Hi Paul, > > I agree with Tom. Using the 'Correction' field is a good work around, but > not really the best long term solution. > So I have

[weewx-user] Re: Belchertown weather pictures does not work after update

Hi Michal, Did you check the differences between the 1.0 and 1.2 skin.conf configuration settings? Are you using Aeris as forecast provider? If that is the case you may be missing this setting in skin.conf: forecast_aeris_use_metar = 1 Regards, Arend Op zaterdag 28 november 2020 om 06:02:47

[weewx-user] Re: Changing my PWS hardware...

http://weewx.com/docs/utilities.htm#wee_config_utility -- 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

Re: [weewx-user] Re: Copy webcam image to /var/www/html/weewx/image.jpg

Duh! There was an extra space between: password=user http://192.168.254.33/jpg/image.jpg?size=3 ^ Thanks everyone for your help. The march forward continues... On Tuesday, November 24, 2020 at

[weewx-user] Changing my PWS hardware...

I've just ordered a new PWS (WS-2902C) and want to switch to that hardware from WeatherFlow. What is the procedure to do that? -- 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,

Re: [weewx-user] Re: Bresser 6in1

Hi Paul, I agree with Tom. Using the 'Correction' field is a good work around, but not really the best long term solution. So I have released 1.02 of the WS6in1 driver. Apart from updating the readme.txt giving updated details of the additional supported weather stations the only other

Re: [weewx-user] Wrong monthly average temperature

Thanks. Somehow, your daily summary shifted from V1.0 to V2.0 behavior starting with the 1605308400 timestamp. Gary: the only thing I can think of that changed in V4.2 is this commit , which was in response to this

Re: [weewx-user] Wrong monthly average temperature

Version 2.0 tke...@gmail.com schrieb am Samstag, 28. November 2020 um 15:00:04 UTC+1: > Michael, > > Can you check what the version number is for your daily summaries? > > *select * from archive_day__metadata;* > > should do it. > > -tk > > On Sat, Nov 28, 2020 at 5:21 AM michael.k...@gmx.at >

Re: [weewx-user] Wrong monthly average temperature

Michael, Can you check what the version number is for your daily summaries? *select * from archive_day__metadata;* should do it. -tk On Sat, Nov 28, 2020 at 5:21 AM michael.k...@gmx.at < michael.kainzba...@gmx.at> wrote: > > I got the point, with the constant archive interval. But why did it

Re: [weewx-user] Wrong monthly average temperature

I got the point, with the constant archive interval. But why did it change from weighted wsum and sumtime values to unweighted when upgrading 4.1.1 => 4.2.0? Did I unintentionally change a config portion when merging the configs? I guess many users aren't aware that this happened to them also.

Re: [weewx-user] Wrong monthly average temperature

Ok, I see the issue now. Whilst changing wsum/sumtime worked in your case it only worked because you have a single constant archive interval in your database. Changing wsum/sumtime to sum/count in a database that has multiple different archive intervals would introduce errors. The correct fix

Re: [weewx-user] Wrong monthly average temperature

I guess the Problem is with the day of the version upgrade only. This day produces values that are off. since the yearly average 2020 and the monthly average 11/2020 is affected, both of these averages are wrong. 12/2020 should have worked. 11/01 til 11/13 worked also, so do 11/15 up until

Re: [weewx-user] Wrong monthly average temperature

I’m not sure I see the problem you are trying to fix, I don’t see anything ‘obviously off’. The ‘weighting’ of archive records was reworked in WeeWX v3.7.0 to properly support multiple different archive intervals in a database. Your data appears to have a constant five minute archive interval,

Re: [weewx-user] Wrong monthly average temperature

Here is what I did and it worked for me :) michael.k...@gmx.at schrieb am Samstag, 28. November 2020 um 10:38:28 UTC+1: > > 1606431600 -2.9 1606461229 6.5 1606483508 90.7493145743143 287 > 90.7493145743143 287 > 1606345200 -1.4 1606376580 5.8 1606396159 208.754783549784 288 > 208.754783549784

Re: [weewx-user] Wrong monthly average temperature

1606431600 -2.9 1606461229 6.5 1606483508 90.7493145743143 287 90.7493145743143 287 1606345200 -1.4 1606376580 5.8 1606396159 208.754783549784 288 208.754783549784 288 1606258800 -2.5 1606290557 5.3 1606310759 71.2823196248196 288 71.2823196248196 288 1606172400 -2.1 1606194900 9.9 1606224600

Re: [weewx-user] Wrong monthly average temperature

I am observing the same situation, as well as other WeeWX users near me. The average is clearly off since the 4.2.0 update. It also affects yearly average since then. So I guess this is something that happened with the 4.2.0 Version. I don't want to rebuild my daily values, how to find the bad