sorry, my touchpad has caused early posting!
To continue,
5. Edit the import file to include the field names.
6. run wee-import --test only
7. evaluate results, make corrections
8. run final import
9. restart weewx
any way to verify success?
On Monday, February 22, 2021 at 10:27:44 PM UTC-8
I'm trying to import (wee_import) two weeks of data from my tempest
repository held at Weatherflow. The API page example of my data shows no
header in the csv file. How should i handle this import? should i edit the
file by adding the first reacord and inserting the proper field names?
i assume
This is a link to my current weather site.
http://nevsweather.duckdns.org:8048/weather/belchertown/index.html
I have updated my link to this site on my weewx Wiki page entry (pi weather
with i2C sensors).
The skin now has two extra pages, one for a colour history chart (code by
Nick Dajda used
That seems to be it... not sure what happened.
On Tuesday, February 23, 2021 at 9:41:41 AM UTC+10 Neville Davis wrote:
> I seemed to be unable to post, found not linked to my google account..
> this is to see if this works.
>
> Neville
>
--
You received this message because you are subscribed
I seemed to be unable to post, found not linked to my google account.. this
is to see if this works.
Neville
--
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
Here's the problem: when a browser renders a document, it needs to know
what encoding it is in. For HTML documents, this is specified by a meta tag
However, with a plain text document, there is no way to specify the
encoding, so, instead, browsers must use a default. From what I can tell,
Hi Tom
At #1 you wrote:
NOAA reports now use a 'utf8' encoding instead of 'strict_ascii'. This will
only
affect new installations. Fixes issue #644.
When I look at the skin.conf, utf8 has disappeared as a choice:
# Possible encodings include 'html_entities', 'strict_ascii',
the Klimalogg Pro database consists of two databases (default names:
weewx.sdb and weewx-kl.sdb) - they will have of course be located in a
different directory from your standard weewx installation if you keep
the database names.
The installation will not run with the weewx-kl.sdb only - even
Hi all,
I have weewx 4.4.0 already running with a Fine Offset Station and it works
fine. I also have a TFA Klimalogg station with two external sensors. I've
read out that it is possible to get data with a weewx Klimalogg driver and
that it is also possible two run two stations in one weewx
Then I just wait until the latest version of python 3.7
Ton
Op zondag 21 februari 2021 om 22:26:20 UTC+1 schreef gjr80:
> The following error strongly suggests a python 2 only extension being run
> under python 3:
>
> File "/var/tmp/fuzzy-archer-2.26/install.py", line 84
> print ""
>
You did not restart weewx, so the log does not show the startup sequence.
There could be another problem, but, at the minimum, it appears that the
memory in your logger is corrupt. See the section *WeeWX generates HTML
pages, but it does not update them
OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I am
told they behave just like a console. First thing I would do is test
connectivity from your RPi to the Envoy. Any chance the Envoy is now on a
different USB port? Not sure if you remember the Establishing connectivity
Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather system...
Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing weewx
version 4.4.0
Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 2.7.13
(default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
Hi,
About 30 min log is attached
I see a lot of these errors:
Feb 22 09:06:04 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage:
LOOP try #1; error: Expected to read 99 chars; got 0 instead
Feb 22 09:06:08 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage:
LOOP try #2; error:
Hi,
We need to see the log from when you try starting WeeWX. Restart WeeWX and
let it run for an archive period or two, then goto the log and take an
extract from when WeeWX was restarted through until the two archive periods
have passed. Post the log back here without alteration. It’s
My Davis system has been running really well for the last 2 years. Needed
no maintenance from me etc. Then the Envoy started tripping the circuit
fuse (I think it was the Envoy rather than the power chord as I replaced
with new Envoy and tripping stopped). I directly changed out the Envoy and
16 matches
Mail list logo
