Hi Tom,

Thanks!  The confusing thing for me is that the database is showing 0.0 for 
the rainRate in those bad intervals.  Wouldn't I expect to see 655.35 in 
those archive intervals instead of 0.0?
On Monday, July 3, 2023 at 3:58:05 PM UTC-4 Tom Keffer wrote:

> I think these are all related.  If your VP2 receives a "dash value", that 
> means the reading from the sensor is bad. The WeeWX Vantage driver detects 
> this, and emits a value of None, which becomes a null value in the 
> database. For whatever reasons, the outside temperature and humidity 
> sensors are emitting dash values, so you're seeing corresponding null 
> values in their database fields.
>
> However, dash values are NOT detected for rain rate, so you'll see 0xFFFF 
> as the value. The documentation does not mention that a dash value is 
> possible for rain rate, but obviously it is. That's a change that needs to 
> be made to the driver.
>
> As for why these sensors are emitting null (aka, "dash") values, I don't 
> know. Something going on with your hardware. Because it is happening to 3 
> different sensors at the same time, it makes me think it must be something 
> they all have in common. Perhaps the battery, perhaps the communications 
> module, perhaps something else. It's worth asking Davis.
>
> Fixed in commit dea4b30 
> <https://github.com/weewx/weewx/commit/dea4b30317fac63428ae47c1b08fe31433d0d232>
> .
>
> -tk
>
> On Mon, Jul 3, 2023 at 4:59 AM Jared <[email protected]> wrote:
>
>> Hi,
>>
>> I'm running a Vantage Pro 2, and there have been four occurrences so far 
>> this year where it has failed to log an outTemp and outHumidity value in 
>> the database for a period of several archive intervals.
>>
>> If I run a query like this:
>>
>> select 
>> dateTime,barometer,inTemp,outTemp,inHumidity,outHumidity,windSpeed,windDir,windGust,windGustDir,rain,rainRate,rxCheckPercent,txBatteryStatus,consBatteryVoltage
>>  
>> from archive where outTemp IS NULL;
>>
>> The station is logging everything normally except outTemp and 
>> outHumidity.  This is going to format terribly but it may help:
>>
>> dateTime    barometer   inTemp      outTemp     inHumidity  outHumidity 
>>  windSpeed   windDir     windGust    windGustDir  rain        rainRate   
>>  rxCheckPercent  txBatteryStatus  consBatteryVoltage
>> ----------  ----------  ----------  ----------  ----------  ----------- 
>>  ----------  ----------  ----------  -----------  ----------  ---------- 
>>  --------------  ---------------  ------------------
>> 1688358000  29.879      76.9                    42.0                     
>> 0.0                     0.0                      0.0         0.0         
>> 99.4375         0.0              4.79
>> 1688358300  29.875      76.7                    42.0                     
>> 0.0                     0.0                      0.0         0.0         
>> 99.4375         0.0              4.79
>> 1688358600  29.873      76.7                    42.0                     
>> 0.0                     0.0                      0.0         0.0         
>> 99.4375         0.0              4.79
>> 1688358900  29.875      76.6                    42.0                     
>> 0.0                     0.0                      0.0         0.0         
>> 100.0           0.0              4.79
>> 1688359200  29.872      76.5                    42.0                     
>> 0.0                     0.0                      0.0         0.0         
>> 99.4375         0.0              4.79
>>
>> First, I wonder if there is a problem with my station's sensor.  I'll 
>> have to investigate that.  Three occurrences of this happened over the 
>> winter, and just last night was the first time it's happened in months.  
>> Any tips here are appreciated, but I know that's well outside the scope of 
>> the forum :)
>>
>> But for whatever reason, this also messes up the rainRate records.  As 
>> you can see there's no strange rain data in the archive, so I'm not sure 
>> how it's causing the rainRate records to have that value (FFFF in hex).  
>> All the other values and tables aside from archive are generated by Weewx, 
>> right?
>>
>> Any help is appreciated.  I've just been deleting these bad records from 
>> archive and rebuilding the daily tables, but let me know if there's 
>> something I else I should be doing.
>>
>> -- 
>> 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/2dbc9618-d9f1-4533-80fc-f642d8e4f5aan%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/2dbc9618-d9f1-4533-80fc-f642d8e4f5aan%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/34dfb434-72ef-4772-8878-15cc11e2e58fn%40googlegroups.com.

Reply via email to