Paul,
Forgot to say, set debug_parse = 1 in weewx.conf in the Rtldavis section.
Then send both line pairs: received 8-byte hex code and the parsed data.
Luc
Rich,
Please tell me a bit more. json output as standalone function or together with
weewx? What application do you have in mind to use this data?
Luc
Paul,
Can you send me a short list (10-20 different values will do) of the 8-byte
hexcodes of the humidity messages together with the aprox. real humidity values
they should have?
Luc
Luc
Glad to report, after reviewing and correcting my typos in my configuration
(the eyes are going down hill) everything is decoding correctly on my RPI3.
Weewx 3.9.1 with Rtldavis driver 0.10
Just something to think about, would there be a way to add a JSON output?
Again thanks to you and
Tom, can you tell me what WeeWX will do in case it gets a package with the
same unix timestamp a package already had before?
As dateTime is a unique key I'm curious if WeeWX automatically 'filters'
the data/packages or if some kind of exception is thrown (that may have an
impact on system
Luc and Paul
Almost everything for me is decoding properly:
Outside Temperature 46.8°F (Validated against console)
Humidity 59% (Validated against console)
Wind N/A N/A ( N/A) (need to check my sensor map)
Rain Rate 0.00 in/hr (check when raining)
Rain Today 0.00 in (check when raining)
Paul
My Humidity value is being reported correctly. I did not update the
rtldavis file.
LOOP: 2019-03-28 21:35:14 EDT (1553823314) dateTime: 1553823314,
maxSolarRad: 0.0, outHumidity: 59.7, rainRate: 0, usUnits: 1. The issue
I'm having is wind and wind direction is not being decoded.
Luc and Rich
Had been doing the testing on a laptop which didn't have Weewx installed
on. Today I installed everything on my PI3 development machine. I can't
seem to get humidity to report correctly.This message shows in weex log:
Mar 28 19:49:54 pi3-dev weewx[1837]: engine: 2019-03-28
On Wednesday, 27 March 2019 18:27:40 UTC-3, rich T wrote:
>
> Looks like I'm only decoding a couple of the data fields, in which could
> be configuration error on my part. The driver did crash due to a "none
> type" error, again the cause could be configuration error on my part.
>
Rich,
Your
