Hallo,
seit dem 08.05.2022 erhalte ich kein Informationen von opendata.de
info aus der wget-dwd.log
"WARNUNG: Zeitstempel funktionieren nicht in Kombination mit der Option
»-O«. Genauere Erläuterungen finden Sie im Handbuch.
--2022-05-09 07:22:00--
Thanks for that, John.
I think we're saying the same thing because a new LOOP request starts with
a wake-up. My intention was to catch the error lower down in the stack,
then restart the loop.
It's good to hear that the strategy works!
-tk
On Sun, May 8, 2022 at 4:30 PM 'John Kline' via
Hi Tom,
You don’t need to restart or try a wake up. You just need to return from
genDavisLoopPackets so another request is made for packets.
Below is what I have been running. You can simplify it as the bad_read
variable is not necessary since it has NEVER occurred that two bad reads
my vp2 (15yo) recently started throwing this error (causing weewx restart)
every few hours. perhaps coincidence, but it started very soon after after id
#2 (a davis temperature station - the ISS has id #1) stopped reporting after
several days of low battery alert on and off (i was travelling),
Thanks, I’ll pop the new code in, a take a look after a bit, and let ya
know.
On Sun, May 8, 2022 at 11:47 Tom Keffer wrote:
> Neither. The push to Weatherlink was just for troubleshooting. The log
> files should look normal.
>
> On Sun, May 8, 2022 at 10:05 AM Rob Cranfill
> wrote:
>
>> Tom,
Tom
It's a USB Data Logger (old type of USB). AC powered with battery backup,
no taught wires and the logger is housed securely.
Just over an hour has gone by with no more errors, as you say, it may just
be the reset/catch up that caused the second issue. I'll have a look again
on the morrow
Now that I think about it, there is an experiment I've been meaning to try.
Right now, the Vantage driver tries 3 times, then gives up and restarts the
program from the top.
The experiment would be to do something not quite so drastic. Rather than
restart the program, try a Vantage "wake up"
The "Expected 99, got 0" error is pretty common, especially after the
logger has done a catch up. I have not noticed any correlation with the age
of the logger.
What kind of connection are you using? USB? Serial? Serial through a USB
converter? The last (converters) are notoriously flaky.
-tk
Spoke too soon. The error appears to back back up, is this a data logger
issue?:
May 8 20:55:18 raspberrypi weewx[8172] INFO weewx.restx: AWEKAS: Published
record 2022-05-08 20:55:00 BST (1652039700)
May 8 20:55:18 raspberrypi weewx[8172] INFO weewx.restx: PWSWeather:
Published record
Just noticed a couple of errors thrown up by WeeWX:
ERROR weewx.drivers.vantage: LOOP try #1; error: Expected to read 99 chars;
got 0 instead.
Having then read through this forum I then reset the data logger in the
Vantage console (removed all power, pulled the data logger out for 20
seconds,
Neither. The push to Weatherlink was just for troubleshooting. The log
files should look normal.
On Sun, May 8, 2022 at 10:05 AM Rob Cranfill wrote:
> Tom,
>
> I'm glad to try out the new code, but I'm not sure what you'd like us to
> do - push data to Weatherlink again? Or just look for
Tom,
I'm glad to try out the new code, but I'm not sure what you'd like us to do
- push data to Weatherlink again? Or just look for something in the log
files?
On Fri, May 6, 2022 at 10:24 AM Tom Keffer wrote:
> Huge thumbs up to Bruce at Davis, who didn't let the ball drop.
>
> While we
Regarding Belchertown skin and Javascript time formatting: This sometimes
depends on the settings of the computer, where the page is displayed. Not
on the settings of the server that hosts the pages or WeeWX.
gjr80 schrieb am Sonntag, 8. Mai 2022 um 01:30:21 UTC+2:
> Barry,
>
> Just a note on
If you're using the new version of the skin Seasons, which auto-configures,
the "N/A"'s will eventually go away. If it hasn't heard from a sensor for a
month, then it figures it doesn't exist.
On Sat, May 7, 2022 at 8:44 PM Gary Strand wrote:
>
> I’ve replaced the vantage.py script and I no
14 matches
Mail list logo
