As my English is no longer correct as before, I use an online translator 
with the approximations that this entails. I am sorry for that.

Concerning erratic values.
I actually took the same approach as you recommend, that is to say 
monitoring the graphics of the WU pages which are correct and consistent 
with the values displayed by the console of my PWS. I deduce that the 
values sent by my PWS station are correct and correctly recorded by WU 
since the graphs correspond to reality. Note that I also send my station 
data to weathercloud.net whose graphics are identical to WU.

To import my data, I of course use wee_import in a simple bash script which 
retrieves the last recorded timestamp which is converted into dateTime 
which will serve as a variable for the dateFrom. The date of moment T is 
used for the dateTo variable.
I submit my script on pastbin for your study and the community in case I 
have made a programming error:
https://pastebin.com/biYjHe1E

The strange thing is that the values recorded in mysql for today 11/16/2023 
are correct except from 11:59 p.m. On the other hand, the graph of the 
outTemp column (outside temperature?) of weewx is completely erratic since 
it indicates temperatures of -5°C while the database indicates 8.27°C. Same 
after erasing and importing data.
Is there a problem interpreting the weewx script?
The second strange part is the recording of the outTemp temperature at 
0.32°C and the outHumidity which suddenly dropped from 95% to 79.99% at 
11:59 p.m.
>From a WU quota point of view, my 286 recordings for the day are far from 
1500. I don't understand.

Concerning the units.
Indeed, I use the season skin since I use weewx version 5.0.0b15.
My understanding is that weewx.conf settings take precedence over other 
settings in other files.
I think I understood your advice.
So that you have an overall view you will find my weewx.conf file
https://pastebin.com/BtUtTZzB

I hope it will be more meaningful this way.

Sylvain

Le jeudi 16 novembre 2023 à 00:17:13 UTC+1, gjr80 a écrit :

> My apologies for not replying to your previous post.
>
> I have no knowledge of any changes to the data being provided by WU. In 
> working on some wee_import. change over theist week I have done a number 
> of imports for my station and they have worked without error. I have not 
> checked the veracity of the actual PWS data though. In the past WU has been 
> somewhat flaky/unreliable/hit and miss, call it what you may. However, in 
> recent times they have been more stable. If you are having issues with 
> wildly inaccurate data you might like to do a few checks on your end before 
> taking the issue up with WU. Can you monitor the data that is being 
> uploaded by your station to WU and compare it against what is actually 
> recorded by WU (as opposed to what wee_import obtains via the WU API). If 
> you log onto WU and look at your station towards the bottom of the page you 
> should be able to display your stations historical data either graphically 
> or in tabular form. Does that data  look correct or does it show the 
> non-sense values. If the graphical/tabulated data is correct and 
> wee_import is receiving non-sense values then perhaps it is the WU API or 
> wee_import.
>
> On my diagrams, I no longer have hatched areas but still discontinuous 
> curved lines.
>
>  
> I am not sure what you mean by this, do you mean gaps in plot lines, do 
> you mean something like the second plot in the Line gaps section 
> <http://weewx.com/docs/5.0/custom/image-generator/#line-gaps> of the 
> Customisation Guide? Gaps are typically caused by a lack of data over a 
> period of time. Given you are importing data from WU this could be a lack 
> of data on WU or a problem with your import. It could also be that you have 
> archive records in the WeeWX database that cover that period but those 
> records are missing some data fields. I would suggest identifying the 
> time/period of the gap(s), looking at WU to see if the missing data exists 
> and re-importing if the WU data does exist. If this does not fix the 
> problem I would check your database to see if you do indeed have archive 
> records covering that period, if you do delete those records and then 
> re-import the same period. 
>
> I still can't convert my wind data from m/s to km/h as well as mbar to 
> hPa. However, I have read the documentation and forum threads which for 
> some no longer apply to version 5 of weewx.
> I used the settings recommended in weewx.conf:
> [[Defaults]]
> [[[Units]]]
> [[[Groups]]]]
>                   group_altitude = meter # Options are 'foot' or 'meter'
>                   group_pressure = hPa # Options are 'inHg', 'mmHg', 
> 'mbar', or 'hPa'
>                   group_rain = mm # Options are 'inch', 'cm', or 'mm'
>                   group_rainrate = mm_per_hour # Options are 
> 'inch_per_hour', 'cm_per_hour', or 'mm_per_hour'
>                   group_temperature = degree_C # Options are 'degree_C', 
> 'degree_F', or 'degree_K'
>                   group_speed = km_per_hour # Wind and gust speed
>                   group_speed2 = km_per_hour2
>
>
> Units for plots (among other things) can set in a number of locations 
> within WeeWX. The base default settings are in the weewx.defaults, units 
> can be set by the user/skin developer in the skin config file (skin.conf) 
> [ImageGenerator] stanza, the [StdReport] [[Defaults]] [[[Units]]] 
> [[[[Groups]]]] stanza in weewx.conf or the skin report stanza under 
> [StdReport] in weewx.conf (eg [StdReport] [[SeasonsReport]] for the 
> Seasons skin). If you are using a skin that supports internationalisation 
> the internationalisation settings may also change the plot units. The 
> Processing 
> order section 
> <http://weewx.com/docs/5.0/custom/custom-reports/#processing-order> of 
> the Customization Guide explains the processing order of these 
> locations/options.
>
> Looking at your plots, and given you have an internationalised skin, I 
> suspect that you might find your internationalisation settings are forcing 
> the use of MetricWx units. Under [StdReport] [[SeasonsReport]] I expect 
> you currently have something like:
> [StdReport]
>     ....
>     [[SeasonsReport]]
>         ....
>         lang = fr
>
> Try adding an override for the units you wish to display:
> [StdReport]
>     ....
>     [[SeasonsReport]]
>         ....
>         lang = fr
>         [[[Units]]]
>             [[[[Groups]]]]
>                 group_pressure = hPa
>                 group_speed = km_per_hour
>
> I've not used internationalisation/localisation so I might have the exact 
> overrides wrong, but see how that goes.
>
> Gary
>

-- 
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/8290ac4b-238c-4fd8-b726-f6cd92a5ac29n%40googlegroups.com.

Reply via email to