Did you edit the log? There should be a lot more information than that.

On Thu, Jan 9, 2025 at 11:58 AM Francis Perea <[email protected]>
wrote:

> Hi Tom, thanks a lot for your reply.
>
> Here you have my log.
>
> The debug lines regarding the wind speed and vane and the "Discarding
> Observation" lines are mine. I had to find where the code was getting, and
> that's why I think the apply_qc() function is not rejecting the wrong
> observation.
>
> By the moment I'm checking rain, but I've also made some testings with
> rainRate.
>
> Thanks once again for your help.
>
> ene 09 20:52:17 meteopi weewxd[28490]: INFO __main__: Starting up weewx
> version 5.1.0
> ene 09 20:52:17 meteopi weewxd[28490]: DEBUG weewx.engine: Station does
> not support reading the time
> ene 09 20:52:17 meteopi weewxd[28490]: INFO weewx.engine: Using binding
> 'wx_binding' to database 'weewx'
> ene 09 20:52:17 meteopi weewxd[28490]: INFO weewx.manager: Starting
> backfill of daily summaries
> ene 09 20:52:17 meteopi weewxd[28490]: INFO weewx.manager: Daily summaries
> up to date
> ene 09 20:52:17 meteopi weewxd[28490]: INFO weewx.engine: Starting main
> packet loop.
> ene 09 20:52:17 meteopi weewxd[28490]: DEBUG user.byows_rpi: Wind speed:
> 0.0
> ene 09 20:52:17 meteopi weewxd[28490]: DEBUG user.byows_rpi: Read Wind
> Vane value: 0.23
> ene 09 20:52:17 meteopi weewxd[28490]: DEBUG user.byows_rpi: Resolved Wind
> Vane Direction: 225.0
> ene 09 20:52:22 meteopi weewxd[28490]: DEBUG user.byows_rpi: Wind speed:
> 0.0
> ene 09 20:52:22 meteopi weewxd[28490]: DEBUG user.byows_rpi: Read Wind
> Vane value: 0.22
> ene 09 20:52:22 meteopi weewxd[28490]: DEBUG user.byows_rpi: Unknown Wind
> Vane value: 0.22
> ene 09 20:52:27 meteopi weewxd[28490]: DEBUG user.byows_rpi: Wind speed:
> 0.0
> ene 09 20:52:27 meteopi weewxd[28490]: DEBUG user.byows_rpi: Read Wind
> Vane value: 0.23
> ene 09 20:52:27 meteopi weewxd[28490]: DEBUG user.byows_rpi: Resolved Wind
> Vane Direction: 225.0
> ene 09 20:52:32 meteopi weewxd[28490]: DEBUG user.byows_rpi: Wind speed:
> 0.0
> ene 09 20:52:32 meteopi weewxd[28490]: DEBUG user.byows_rpi: Read Wind
> Vane value: 0.23
> ene 09 20:52:32 meteopi weewxd[28490]: DEBUG user.byows_rpi: Resolved Wind
> Vane Direction: 225.0
> ene 09 20:52:37 meteopi weewxd[28490]: DEBUG user.byows_rpi: Wind speed:
> 0.0
> ene 09 20:52:37 meteopi weewxd[28490]: DEBUG user.byows_rpi: Read Wind
> Vane value: 0.22
> ene 09 20:52:37 meteopi weewxd[28490]: DEBUG user.byows_rpi: Unknown Wind
> Vane value: 0.22
> ene 09 20:52:37 meteopi weewxd[28490]: WARNING weewx.qc: 2025-01-09
> 20:52:38 CET (1736452358) LOOP value 'rain' 0.616 outside limits (0.0,
> 0.3937007874015748)
> ene 09 20:52:37 meteopi weewxd[28490]: WARNING weewx.qc: Discarding
> observation
> ene 09 20:52:42 meteopi weewxd[28490]: DEBUG user.byows_rpi: Wind speed:
> 0.0
> ene 09 20:52:42 meteopi weewxd[28490]: DEBUG user.byows_rpi: Read Wind
> Vane value: 0.22
> ene 09 20:52:42 meteopi weewxd[28490]: DEBUG user.byows_rpi: Unknown Wind
> Vane value: 0.22
> ene 09 20:52:47 meteopi weewxd[28490]: DEBUG user.byows_rpi: Wind speed:
> 0.0
> ene 09 20:52:47 meteopi weewxd[28490]: DEBUG user.byows_rpi: Read Wind
> Vane value: 0.22
> ene 09 20:52:47 meteopi weewxd[28490]: DEBUG user.byows_rpi: Unknown Wind
> Vane value: 0.22
> ene 09 20:52:52 meteopi weewxd[28490]: DEBUG user.byows_rpi: Wind speed:
> 0.0
> ene 09 20:52:52 meteopi weewxd[28490]: DEBUG user.byows_rpi: Read Wind
> Vane value: 0.22
> ene 09 20:52:52 meteopi weewxd[28490]: DEBUG user.byows_rpi: Unknown Wind
> Vane value: 0.22
>
> El jueves, 9 de enero de 2025 a las 20:42:24 UTC+1, Tom Keffer escribió:
>
>> We need the log to offer much advice. See *How to get a good, useful log
>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user#how-to-get-a-good-useful-log>*
>>  in
>> the Wiki.
>>
>> Also, what field are you checking in the database? Field "rain"? Or,
>> "rainRate"?
>>
>> On Sun, Jan 5, 2025 at 1:16 PM Francis Perea <[email protected]>
>> wrote:
>>
>>> Hi all,
>>>
>>> I'm having a problem with my rain sensor and I get frequent messages
>>> notifying values outside limits after QC.
>>>
>>> To be exact the function apply_qc in qc.py detects the wrong value and
>>> send a log like this:
>>>
>>> WARNING weewx.qc: 2025-01-05 17:45:00 CET (1736095500) Archive value
>>> 'rainRate' 13.841245901639354 outside limits (0.0, 3.0)
>>>
>>> As I understand the apply_qc function should remove the invalid reading
>>> after detecting it with the instruction
>>>
>>> data_dict[obs_type] = None
>>>
>>> in qc.py line 72, but the wrong value is even so archived.
>>>
>>> Any clue or any other way to remove the wrong observation once it is
>>> detected by apply_qc?
>>>
>>> Thanks a lot in advance.
>>>
>>> --
>>>
>> You received this message because you are subscribed to the Google Groups
>>> "weewx-development" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To view this discussion visit
>>> https://groups.google.com/d/msgid/weewx-development/c37bfae1-5beb-4178-ab1b-69423c008d49n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-development/c37bfae1-5beb-4178-ab1b-69423c008d49n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion visit
> https://groups.google.com/d/msgid/weewx-development/b5977ef9-7181-4ecc-9bf3-b609c4c9324en%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-development/b5977ef9-7181-4ecc-9bf3-b609c4c9324en%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/weewx-development/CAPq0zEDaQS8Uv5VEarWqG0gyYZynUEt6RKJs6V6NJBg0cPuvvQ%40mail.gmail.com.

Reply via email to