The wh23xx error message seems to be from the wh23xx driver. I'd understand
it in a way that there seem to be inconsistencies/errors in the stations
hardware memory.
Günther Wrana schrieb am Donnerstag, 20. März 2025 um 21:42:08 UTC+1:
> Thank you very much, I imported an old database and now
Correct, but I was hoping that by routing the TCP transmission to the
Raspberry with Weewx on board I would cause the packets to be captured by
Weewx.
poniedziałek, 31 marca 2025 o 06:57:56 UTC+2 Cameron D napisał(a):
> sorry, I did not read your post thoroughly enough.
> You have told the Garn
Thank you Ian,
I have a working version running on a system at home. It needs some tidying
up plus the backfill via device history files needs a touchup after the
v1.0.4 firmware release. The absence of any complete and reliable local
device HTTP API documentation is not helping. I am away on h
One thing I’ve found is that some devices only query dns and especially ntp
when they power up, so it is easy to miss those if you run tcpdump after
the console is already running. You might have more luck if you start
tcpdump then power the console down/up.
SDR should likely see something if
I'm trying to get a template modified to pull data from essentially
$span(week_delta=1). There's two sections in the template, one a
valuesCard(), the other is chartCard(). The logic of the template goes
like this:
#for $x in $Extras.Appearance.values_order
#if $x == "ET
Thanks for your reply. I know about that option, but it is a bit more
complicated for my setup. Instead, I have used great weewx documentation
and examples and customized the FileParse example driver which reads from
the file. I could extend it to get data from the ecowitt cloud directly but
fo
