No offense!
We're waiting for Matthew to take a look.
On Sat, Mar 5, 2022 at 11:18 AM jschoonh wrote:
> Hey Tom,
> I don't mean to offend you, but may I ask if anything is known? Or can I
> do something?
>
> Op woensdag 2 maart 2022 om 23:39:31 UTC+3 schreef jschoonh:
>
>> I do understand and
Hey Tom,
I don't mean to offend you, but may I ask if anything is known? Or can I do
something?
Op woensdag 2 maart 2022 om 23:39:31 UTC+3 schreef jschoonh:
> I do understand and I'm happy that there is support. Hope to "speak" to
> you soon
> Op woensdag 2 maart 2022 om 22:40:01 UTC+3 schreef
Hey Ton,
I don't mean to offend you, but may I ask if anything is known? Or can I do
something?
Op woensdag 2 maart 2022 om 23:39:31 UTC+3 schreef jschoonh:
> I do understand and I'm happy that there is support. Hope to "speak" to
> you soon
> Op woensdag 2 maart 2022 om 22:40:01 UTC+3 schreef
I do understand and I'm happy that there is support. Hope to "speak" to you
soon
Op woensdag 2 maart 2022 om 22:40:01 UTC+3 schreef tke...@gmail.com:
> I think we're going to have to wait for Matthew to return. Sorry I
> couldn't be of more help!
>
> On Wed, Mar 2, 2022 at 11:14 AM jschoonh
I think we're going to have to wait for Matthew to return. Sorry I couldn't
be of more help!
On Wed, Mar 2, 2022 at 11:14 AM jschoonh wrote:
> hey tom,
> I quickly made a kind of skin. The first line is from the tmpl file. The 2
> lines below the result before water entered the rain gauge and
I've only just now noticed that the "rainTotal value from
68.116 who changed to 68,272" is the values the "la Crosse"
console declares as Raintotal. Indeed, 682.2 mm of rain has already fallen
this year.
Op woensdag 2 maart 2022 om 22:14:43 UTC+3 schreef jschoonh:
> hey tom,
> I
hey tom,
I quickly made a kind of skin. The first line is from the tmpl file. The 2
lines below the result before water entered the rain gauge and after. The
time is there. According to the console, about 1.5 mm of rain has entered
the rain gauge. all "rain.sum" variants have not changed the
>
> Your workaround to calculate the rain doesn't work. Because there is no
> data to calculate anything. none of the "rain.sum" ($day , $week etc. shows
> new data. The rain data $week, $month, etc, comes from stored data and not
> from new data.
>
How about some more information besides
hey tom,
I've tried a few more things. A think twirl, weewx-csv was installed. I
didn't took any chances and removed all the extras. Of course no
difference. Your reasoning that "historical data" coming in from Lacrosse
gives an accurate rainfall reading is correct. In a "normal" run I kept the
I think I see what's going on. When weewxd first starts up, it goes into a
"catch up" mode, where it downloads all archive records available in the
console. In this case, there may be many records, so the differences
between values of totalRain can be easily calculated.
However, once catch up
wow i feel a bit stupid here. I try to understand what I see. Sorry it took
a little longer I wasn't home and I have to re-plug the configuration every
time. I first let weewx retrieve the history of the ws2359. Then let it run
4 time' s the archive loop (20 min) 4 times. Which gives 4 times a
Run the following:
sudo python3 /usr/share/weewx/weewxd /etc/weewx/weewx.conf
Let it display a few LOOP messages, then hit control-C to stop it.
It should look something like this example:
sudo python3 /usr/share/weewx/weewxd /etc/weewx/weewx.conf
LOOP: 2022-03-01 18:01:11 UTC
Please show what is being printed out: don't summarize. The print out will
show things like rainTotal, which we need to know. Run weewxd directly from
the command line for a few LOOP packets, then post the results.
Sorry i do mis that. I did run weewx a view loops en took the compleet
English is fine! Certainly better than my Dutch!
but as soon as life data is fetched in the main loop, only NULL's appears
> in the column rain, even if rain falls in the rain gauge.
Please show what is being printed out: don't summarize. The print out will
show things like rainTotal, which we
sorry sorry Tom, the terminal file contains two times "wee_device--info"
here's a new attempt with "wee_device--current". But not of the same time
as the log
Using configuration file /etc/weewx/weewx.conf
Using WS23xx driver version 0.41 (weewx.drivers.ws23xx)
Querying the station for the
This is going to be a long post, sorry about that, my english isn't
perfect either.
When I connected my station this afternoon to weewx again and started it
up, I immediately noticed that the historical data that was retrieved from
my station ws2357 seems to be good. In weewx.sdb in the
Much prefer cut and paste to a screenshot. It's easier to read, and can be
searched.
WeeWX has been designed to leave clues in the log. There may not appear to
be much going on, but you'd be surprised. Please post it.
Dropping some water in the rain bucket would definitely be useful!
-tk
On
hey tom,
Glad you want to watch. The wee_device command's output will be a
screenshot of the terminal. Is that a problem or is there another way?
There is currently no message in the log file. There is also no error
message from the rain registration.
Yes weewx has been running for several
We're going to need more information.
First, please cut and paste the results: don't summarize. For example, is
it "raintotal = 63.299" or "rainTotal : 63.299"? This is important because,
in Python, case matters. The driver uses 'rainTotal' (not 'raintotal') to
calculate the field 'rain'.
I am converting to weewx. About 10 years database imported from WU in
weewx.sdb Except for some spikes, this is “healthy data”. Only now it
appears, that the la crosse ws2357 does not generate any rain data.
“wee_device –info” shows all data, “1 hour of rain = 1.55” , “24 hours of
rain =
20 matches
Mail list logo
