How I hate Google Groups. It looks like I answer only to you Michael. To be short - your explanation helps me a lot. Thank you.
I have one more question. Here is how I do it now when I want to change something manually (for example the rain rate - which is quite often a problem). 1. Stop service on Raspberry PI. 2. Copy WEEWX.SBD to my PC and open it with DB Browser for SQLite. 3. Using the website https://www.epochconverter.com/ find the approximate dateTime to find the position in the database and change the number in the table "archive". 4. After your explanation from yesterday change the number in the table "archive_day_rainRate". 5. Write the changes to the file and copy it back to Raspberry PI. 6. Start the Weewx service. Is there any better way? On Tuesday, 25 July 2023 at 07:45:43 UTC+2 [email protected] wrote: > The values are in the "archive_day_*" tables in the database. These tables > contain a dateTime values, min and max values as well as their exact time > (depending on the source), sum and weighted sum values and a count. When > you change a value in the archive table by hand, it won't show up there, > thus not show up in any statistics in the front end, as long as you don't > fix this in the proper way. > See https://weewx.com/docs/latest/utilities.htm#wee_database_utility for > a description of a tool that does it the proper way. Be aware, that some > actions might lead to loss in precision. For instance, the "exact time" I > mentioned before is then changed to the dateTime of the archive value, e.g. > when you maximum gust occurred at 8:33pm using a 5 min archive_interval, it > might happen, that after running the tool you maximum gust will be shown at > 8:35pm. Or, if your maximum temp was at 4:32pm showing 30,1°C with a single > loop value of 30,1°C, and all other loop values were 30,0°C in that > archive_interval, after running the tool, it might be, that your maximum > will read as 30,0°C at 1:15pm, if that was the first interval that day, > that had 30,0°C. > > [email protected] schrieb am Dienstag, 25. Juli 2023 um 06:37:12 UTC+2: > >> I had some problems with connections and also physical shocks on sensors. >> So, I stopped the Weewx service, copy the file /var/lib/weewx/weewx.sdb >> to my PC. I opened it with SQLiteDatabaseBrowser and change some extreme >> (unreal) results. For example wind and also rainRate which was caused by >> the son's ball :-) >> After that, I copy the file back onto my server and start the Weewx >> service again. >> Now some changes are properly shown (for example in graphs), but the max >> results are old (unreal). I don't understand how this is calculated. I even >> tried "xstats" and it also shows old (unreal) max results. I checked again >> in the database and there are no old results there. >> >> Any idea how to get rid of "unreal" results which should not apear in the >> database (and AFAIK they are not there anymore)? >> >> Here is the monthly graph where (for example) where we can see wind >> (VETER) max on the 18th and 19th of July. It was 65 km/h: >> https://izo.amebis.si/belchertown/graphs/?graph=month >> >> Here is a summary where the max wind for July 2023 is 50 km/h: >> https://izo.amebis.si/belchertown/ >> >> It is similar to the rain rate. Max is 13107.0 mm/hr (unreal and I can't >> find this result in the database (I sorted the rain rate column, tried to >> check for the particular time ... there is no such data anymore). >> >> Regards. > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/20beccae-a7c5-402e-8e10-305ac9abb425n%40googlegroups.com.
