I'm not sure what "contains a lot of data" means. Could you be more specific? Many days? Just one? Is it in the archive table as well as the daily summaries? We need to know if this is a one-time thing, or a chronic issue. It would be helpful to see the main archive table. Assuming your database is using US units (the default), then perhaps a query like this:
SELECT dateTime, datetime(dateTime, 'unixepoch', 'localtime'), usUnits, rain, rainRate FROM archive WHERE rainRate > 100.0 LIMIT 100; If the database does contain bad data, then it is a source problem, not a reporting problem. I can't tell you where your log is, because you haven't said what kind of operating system you are running on. See *Where to find things <http://www.weewx.com/docs/usersguide.htm#Where_to_find_things>* for likely locations. On Thu, Feb 24, 2022 at 8:59 AM Luis <luis.ros...@gmail.com> wrote: > I can't my previous question about the log. I have sent the one I thought > was produced by weewx with the debug option. > Which one is the "full log"? > > > On Thursday, February 24, 2022 at 5:06:55 PM UTC+1 tke...@gmail.com wrote: > >> It looks like the log has been filtered to show only debug statements. >> Please post the full log. I need to see version numbers, conversion >> targets, etc. >> >> It's nice to know that the database generally has reasonable rainRate >> values, but the bad value you showed in veleta.png is the highest value >> seen during some unknown day. I don't know which day because you didn't >> show the full plot. What does the database show for that day? If you hover >> a mouse over the value, it will show you the time of that max value. That's >> what we need from the database. >> >> -tk >> >> >> On Thu, Feb 24, 2022 at 7:01 AM Luis <luis....@gmail.com> wrote: >> >>> Now the debug log file (I think this is the one you refer to) >>> >> >>> >>> On Thursday, February 24, 2022 at 3:36:02 PM UTC+1 Luis wrote: >>> >>>> Hi Tom, >>>> I have followed your command on >>>> https://www.mail-archive.com/weewx...@googlegroups.com/msg33396.html >>>> <https://www.mail-archive.com/weewx-user@googlegroups.com/msg33396.html> >>>> and the result is the following: >>>> >>>> $ sqlite3 /var/lib/weewx/weewx.sdb >>>> SQLite version 3.27.2 2019-02-25 16:06:06 >>>> Enter ".help" for usage hints. >>>> sqlite> select >>>> ...> >>>> dateTime,datetime(dateTime,'unixepoch','localtime'),rain,rainRate from >>>> ...> archive where rainRate>0 order by dateTime desc limit 50; >>>> 1641570900|2022-01-07 16:55:00|0.0|0.0393700785 >>>> 1641570600|2022-01-07 16:50:00|0.0|0.0629921256 >>>> 1641570300|2022-01-07 16:45:00|0.0157480314|1.4803149516 >>>> <(480)%20314-9516> >>>> 1641476700|2022-01-06 14:45:00|0.0|0.0314960628 >>>> 1641476400|2022-01-06 14:40:00|0.0|0.0393700785 >>>> 1641476100|2022-01-06 14:35:00|0.0|0.078740157 >>>> 1641475800|2022-01-06 14:30:00|0.0078740157|0.157480314 >>>> 1641475500|2022-01-06 14:25:00|0.0157480314|0.4409448792 >>>> <(440)%20944-8792> >>>> 1641475200|2022-01-06 14:20:00|0.0314960628|2.6220472281 >>>> 1641430800|2022-01-06 02:00:00|0.0|0.0314960628 >>>> 1641430500|2022-01-06 01:55:00|0.0|0.0551181099 >>>> 1641430200|2022-01-06 01:50:00|0.0078740157|0.1181102355 >>>> 1641429900|2022-01-06 01:45:00|0.0078740157|0.0551181099 >>>> 1641429600|2022-01-06 01:40:00|0.0|0.0551181099 >>>> 1641429300|2022-01-06 01:35:00|0.0157480314|0.2519685024 >>>> <(251)%20968-5024> >>>> 1641429000|2022-01-06 01:30:00|0.0078740157|0.2283464553 >>>> <(228)%20346-4553> >>>> 1641428700|2022-01-06 01:25:00|0.0157480314|0.2283464553 >>>> <(228)%20346-4553> >>>> 1641428400|2022-01-06 01:20:00|0.0078740157|0.0944881884 >>>> 1641428100|2022-01-06 01:15:00|0.0078740157|0.1811023611 >>>> 1641427800|2022-01-06 01:10:00|0.0078740157|0.1653543297 >>>> 1641427500|2022-01-06 01:05:00|0.0078740157|0.078740157 >>>> 1641427200|2022-01-06 01:00:00|0.0078740157|0.078740157 >>>> 1641426900|2022-01-06 00:55:00|0.0|0.078740157 >>>> 1641426600|2022-01-06 00:50:00|0.0078740157|0.1181102355 >>>> 1641426300|2022-01-06 00:45:00|0.0078740157|0.0944881884 >>>> 1641426000|2022-01-06 00:40:00|0.0078740157|0.0629921256 >>>> 1641308400|2022-01-04 16:00:00|0.0|0.0314960628 >>>> 1641308100|2022-01-04 15:55:00|0.0|0.0472440942 >>>> 1641307800|2022-01-04 15:50:00|0.0078740157|0.0551181099 >>>> 1641307500|2022-01-04 15:45:00|0.0|0.0551181099 >>>> 1641307200|2022-01-04 15:40:00|0.0236220471|1.6771653441 >>>> 1641306900|2022-01-04 15:35:00|0.0551181099|2.3779527414 >>>> 1640620500|2021-12-27 16:55:00|0.0|0.0314960628 >>>> 1640620200|2021-12-27 16:50:00|0.0|0.0314960628 >>>> 1640619900|2021-12-27 16:45:00|0.0|0.0314960628 >>>> 1640619600|2021-12-27 16:40:00|0.0078740157|0.0314960628 >>>> 1640616300|2021-12-27 15:45:00|0.0|0.0314960628 >>>> 1640616000|2021-12-27 15:40:00|0.0|0.0393700785 >>>> 1640615700|2021-12-27 15:35:00|0.0|0.0393700785 >>>> 1640615400|2021-12-27 15:30:00|0.0078740157|0.0393700785 >>>> 1640611500|2021-12-27 14:25:00|0.0|0.0314960628 >>>> 1640611200|2021-12-27 14:20:00|0.0|0.0472440942 >>>> 1640610900|2021-12-27 14:15:00|0.0078740157|0.0551181099 >>>> 1640610600|2021-12-27 14:10:00|0.0|0.0551181099 >>>> 1640610300|2021-12-27 14:05:00|0.0078740157|0.236220471 >>>> 1640605200|2021-12-27 12:40:00|0.0|0.0314960628 >>>> 1640604900|2021-12-27 12:35:00|0.0|0.0472440942 >>>> 1640604600|2021-12-27 12:30:00|0.0078740157|0.2677165338 >>>> <(267)%20716-5338> >>>> 1640604300|2021-12-27 12:25:00|0.0157480314|0.2283464553 >>>> <(228)%20346-4553> >>>> 1640547900|2021-12-26 20:45:00|0.0|0.0314960628 >>>> >>>> As you can see the database contains normal, acceptable values. >>>> I wonder how the html displayed values are computed/retrieved... >>>> On Wednesday, February 23, 2022 at 9:11:05 PM UTC+1 tke...@gmail.com >>>> wrote: >>>> >>>>> That's certainly an unlikely number. >>>>> >>>>> Are you seeing this all the time? Or, just when it's raining? >>>>> >>>>> In weewx.conf, set debug = 2, then restart weewxd. Please post the log >>>>> from startup through the first reporting cycle. >>>>> >>>>> -tk >>>>> >>>>> >>>>> >>>>> On Wed, Feb 23, 2022 at 11:02 AM Luis <luis....@gmail.com> wrote: >>>>> >>>>>> All is set to prefer_hardware. >>>>>> But then I can't understand why ALL THE REST of values are correct. >>>>>> I moved to WEEWX from VWIEW after several years using wview and there >>>>>> was no problem at all. >>>>>> So my data logger works well. >>>>>> It's just the rain rate which is wrong. >>>>>> >>>>>> Luis >>>>>> On Sunday, November 21, 2021 at 10:43:45 PM UTC+1 tke...@gmail.com >>>>>> wrote: >>>>>> >>>>>>> Two things to check: >>>>>>> >>>>>>> 1. Are you using hardware record generation? This is the default. >>>>>>> Look for option "record_generation" in the stanza [StdArchive]. >>>>>>> >>>>>>> 2. Did you change any values under [StdWXCalculate]? In particular, >>>>>>> make sure the setting for 'rainRate' is "prefer_hardware": >>>>>>> >>>>>>> [StdWXCalculate] >>>>>>> [[Calculations]] >>>>>>> ... >>>>>>> rainRate = prefer_hardware >>>>>>> >>>>>>> Assuming both of these are true, the value you are seeing is coming >>>>>>> straight from the logger in your Vantage Vue. >>>>>>> >>>>>>> -tk >>>>>>> >>>>>>> On Sun, Nov 21, 2021 at 7:03 AM Luis <luis....@gmail.com> wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> I am running a WeeWx server connected to a Vantage Vue station. >>>>>>>> The max rain rate is systematically wrong. >>>>>>>> It always shows 13107.0 mm/hr which is impossible. >>>>>>>> Today's max rain rate reported by the Vantage Vue console is 25.6 >>>>>>>> mm/hr >>>>>>>> Is there an issue with the conversion from inches to mm and with >>>>>>>> the decimal separator (comma vs dot)? >>>>>>>> Thanks >>>>>>>> Luis >>>>>>>> >>>>>>>> -- >>>>>>>> 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+...@googlegroups.com. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/weewx-user/a44a3e2e-7557-48b6-8c5a-a3a7d1607d26n%40googlegroups.com >>>>>>>> <https://groups.google.com/d/msgid/weewx-user/a44a3e2e-7557-48b6-8c5a-a3a7d1607d26n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> >>>>>>> -- >>>>>> 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+...@googlegroups.com. >>>>>> >>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/weewx-user/dcc3ed51-7b11-4739-a4d2-b06d562a7b73n%40googlegroups.com >>>>>> <https://groups.google.com/d/msgid/weewx-user/dcc3ed51-7b11-4739-a4d2-b06d562a7b73n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- >>> 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+...@googlegroups.com. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/d3b6d73a-0918-406e-b2af-1564bb433fd8n%40googlegroups.com >>> <https://groups.google.com/d/msgid/weewx-user/d3b6d73a-0918-406e-b2af-1564bb433fd8n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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/415ff46f-4e77-4781-b97a-e304f3a9f479n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/415ff46f-4e77-4781-b97a-e304f3a9f479n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAPq0zEBf4ZE-W0ETmCCQGH99Abjr%2BY%3D5tnHFkYyZ%3DoizA%3DBjzQ%40mail.gmail.com.
