You are right. I gave no detailed information:

Vantage Vue
Raspberry Pi + Raspbian Buster

Your query gives no records with rainRate > 100 (and no errors)

sqlite> SELECT dateTime, datetime(dateTime, 'unixepoch', 'localtime'), 
usUnits, rain, rainRate FROM archive WHERE rainRate > 100.0 LIMIT 100; 
sqlite> 

But I executed that query for the archive_day_rainRate table and you can 
see that impossible rainRate value:

sqlite> SELECT dateTime, datetime(dateTime, 'unixepoch', 'localtime'), max 
FROM archive_day_rainRate WHERE max > 100.0 LIMIT 100; 
1588975200|2020-05-09 00:00:00|516.0236188995 
1589148000|2020-05-11 00:00:00|516.0236188995 
1589234400|2020-05-12 00:00:00|516.0236188995 
1589320800|2020-05-13 00:00:00|516.0236188995 
1589407200|2020-05-14 00:00:00|516.0236188995 
1589493600|2020-05-15 00:00:00|516.0236188995 
1589580000|2020-05-16 00:00:00|516.0236188995 
1589752800|2020-05-18 00:00:00|516.0236188995 
1589839200|2020-05-19 00:00:00|516.0236188995 
1589925600|2020-05-20 00:00:00|516.0236188995 
1590012000|2020-05-21 00:00:00|516.0236188995 
1590098400|2020-05-22 00:00:00|516.0236188995 
1590184800|2020-05-23 00:00:00|516.0236188995 
1590357600|2020-05-25 00:00:00|516.0236188995 
1590444000|2020-05-26 00:00:00|516.0236188995 
1590530400|2020-05-27 00:00:00|516.0236188995 
1590616800|2020-05-28 00:00:00|516.0236188995 
1590703200|2020-05-29 00:00:00|516.0236188995 
1590789600|2020-05-30 00:00:00|516.0236188995 
1590876000|2020-05-31 00:00:00|516.0236188995 
1590962400|2020-06-01 00:00:00|516.0236188995 
1591048800|2020-06-02 00:00:00|516.0236188995 
1592863200|2020-06-23 00:00:00|516.0236188995 
1592949600|2020-06-24 00:00:00|516.0236188995 
1594504800|2020-07-12 00:00:00|516.0236188995 
1594591200|2020-07-13 00:00:00|516.0236188995 
1594677600|2020-07-14 00:00:00|516.0236188995 
1594764000|2020-07-15 00:00:00|516.0236188995 
1594850400|2020-07-16 00:00:00|516.0236188995 
1594936800|2020-07-17 00:00:00|516.0236188995 
1595023200|2020-07-18 00:00:00|516.0236188995 
1595109600|2020-07-19 00:00:00|516.0236188995 
1595196000|2020-07-20 00:00:00|516.0236188995 
1595282400|2020-07-21 00:00:00|516.0236188995 
1595368800|2020-07-22 00:00:00|516.0236188995 
1596232800|2020-08-01 00:00:00|516.0236188995 
1596319200|2020-08-02 00:00:00|516.0236188995 
1596405600|2020-08-03 00:00:00|516.0236188995 
1596492000|2020-08-04 00:00:00|516.0236188995 
1596578400|2020-08-05 00:00:00|516.0236188995 
1596664800|2020-08-06 00:00:00|516.0236188995 
1596751200|2020-08-07 00:00:00|516.0236188995 
1596837600|2020-08-08 00:00:00|516.0236188995 
1596924000|2020-08-09 00:00:00|516.0236188995 
1597010400|2020-08-10 00:00:00|516.0236188995 
1598306400|2020-08-25 00:00:00|516.0236188995 
1598392800|2020-08-26 00:00:00|516.0236188995 
1598479200|2020-08-27 00:00:00|516.0236188995 
1598565600|2020-08-28 00:00:00|516.0236188995 
1598652000|2020-08-29 00:00:00|516.0236188995 
1598738400|2020-08-30 00:00:00|516.0236188995 
1598997600|2020-09-02 00:00:00|516.0236188995 
1599084000|2020-09-03 00:00:00|516.0236188995 
1599170400|2020-09-04 00:00:00|516.0236188995 
1599256800|2020-09-05 00:00:00|516.0236188995 
1599343200|2020-09-06 00:00:00|516.0236188995 
1599429600|2020-09-07 00:00:00|516.0236188995 
1599516000|2020-09-08 00:00:00|516.0236188995 
1599602400|2020-09-09 00:00:00|516.0236188995 
1599688800|2020-09-10 00:00:00|516.0236188995 
1599775200|2020-09-11 00:00:00|516.0236188995 
1599861600|2020-09-12 00:00:00|516.0236188995 
1599948000|2020-09-13 00:00:00|516.0236188995 
1600034400|2020-09-14 00:00:00|516.0236188995 
1600120800|2020-09-15 00:00:00|516.0236188995 
1600207200|2020-09-16 00:00:00|516.0236188995 
1600293600|2020-09-17 00:00:00|516.0236188995 
1600380000|2020-09-18 00:00:00|516.0236188995 
1600466400|2020-09-19 00:00:00|516.0236188995 
1600552800|2020-09-20 00:00:00|516.0236188995 
1600725600|2020-09-22 00:00:00|516.0236188995 
1600812000|2020-09-23 00:00:00|516.0236188995 
1600898400|2020-09-24 00:00:00|516.0236188995 
1600984800|2020-09-25 00:00:00|516.0236188995 
1601071200|2020-09-26 00:00:00|516.0236188995 
1601157600|2020-09-27 00:00:00|516.0236188995 
1601244000|2020-09-28 00:00:00|516.0236188995 
1601330400|2020-09-29 00:00:00|516.0236188995 
1601416800|2020-09-30 00:00:00|516.0236188995 
1601503200|2020-10-01 00:00:00|516.0236188995 
1601589600|2020-10-02 00:00:00|516.0236188995 
1601676000|2020-10-03 00:00:00|516.0236188995 
1601762400|2020-10-04 00:00:00|516.0236188995 
1601848800|2020-10-05 00:00:00|516.0236188995 
1601935200|2020-10-06 00:00:00|516.0236188995 
1602021600|2020-10-07 00:00:00|516.0236188995 
1602108000|2020-10-08 00:00:00|516.0236188995 
1602194400|2020-10-09 00:00:00|516.0236188995 
1602280800|2020-10-10 00:00:00|516.0236188995 
1603058400|2020-10-19 00:00:00|516.0236188995 
1603144800|2020-10-20 00:00:00|516.0236188995 
1603231200|2020-10-21 00:00:00|516.0236188995 
1603317600|2020-10-22 00:00:00|516.0236188995 
1603404000|2020-10-23 00:00:00|516.0236188995 
1603753200|2020-10-27 00:00:00|516.0236188995 
1603839600|2020-10-28 00:00:00|516.0236188995 
1603926000|2020-10-29 00:00:00|516.0236188995 
1604012400|2020-10-30 00:00:00|516.0236188995 
1604098800|2020-10-31 00:00:00|516.0236188995 
1604185200|2020-11-01 00:00:00|516.0236188995

The archive table does not contain strange values (result of your query is 
no records and no error is produced).
On the other hand, the archive_day_rainRate table  does contain that error 
for every day at 00:00:00 and only at that hour.

On Thursday, February 24, 2022 at 6:17:47 PM UTC+1 [email protected] wrote:

> 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 <[email protected]> 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 [email protected] 
>> 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 <[email protected]> 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/[email protected]/msg33396.html 
>>>>> <https://www.mail-archive.com/[email protected]/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 [email protected] 
>>>>> 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 <[email protected]> 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 [email protected] 
>>>>>>> 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 <[email protected]> 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 [email protected].
>>>>>>>>> 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 [email protected].
>>>>>>>
>>>>>> 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 [email protected].
>>>>
>>> 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 [email protected].
>>
> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/69f29cd1-273b-475e-a7ff-2203015e1cf1n%40googlegroups.com.

Reply via email to