Your monthly summary is in mm and the daily details are in cm. What
exactily is your problem?
Have you been making changes to the NOAA reports??
On Friday, 24 July 2020 07:30:34 UTC+3, Olivier GARNIER wrote:
>
> How is it possible... Look at the total rain of mars...
>
>
> The
How is it possible... Look at the total rain of mars...
The NOAA-2020-03.txt file :
MONTHLY CLIMATOLOGICAL SUMMARY for mars 2020
NAME: Le Plessis Placy, France
ELEV: 130 mtresLAT: 49-03.48 NLONG: 002-59.22 E
TEMPERATURE (C), RAIN (cm), WIND
I couldn't get it to run from the command line.
When I did python -m user.gw1000 --help
I get /usr/bin/python: No module named user.gw1000
But I have it up and running, everything looks good on my Seasons page.
I'll give the data a closer look tomorrow.
But I'm scratching my head trying to
I have it up and running, everything looks good on my Seasons page.
I'll give the data a closer look tomorrow.
But I'm scratching my head trying to find how to specify the IP address in
weewx.conf
I have three GW1000s here, I have no idea which one is being used..
On Thursday, July 23, 2020 at
This link
works:
https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/gw1000-0.1.0b4.tar.gz
On Thursday, July 23, 2020 at 8:57:49 PM UTC-5 Bill Arthur wrote:
> FYI:
> wget -P /var/tmp
> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
>
FYI:
wget -P /var/tmp
https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
gives me an Error 404
On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:
> There is a thread in the developer section where some questions were asked
> that were not
You are getting ahead of yourself worrying about Ecowitt.net not having the
data and WeeWX skins for the WH40...etc.
WS View needs to be happy first. Once everything is showing up correctly in
WS View then you can move on to the other things...which you'll likely then
see that these other
Hello all.
For many many years, I've been pushing my Acurite 5n1/01035 data to WUND
using VIS software running on a nettop pc. It's been working fine except
my system hangs whenever VIS pushes an update.
Because of the hanging problem, and the desire to host my station on my
AREDN node, last
There is a thread in the developer section where some questions were asked
that were not directly related to development. This thread is good. I'm
just inviting people to ask their questions here in this thread rather than
in the developer section.
On Thursday, July 23, 2020 at 2:56:51 PM
Well, I had to wait for some wind first. Now, after sunset, wind seems to
be growing. And this is the latest archive record:
REC:2020-07-23 20:50:00 CEST (1595530200) altimeter: 29.94844953418796,
appTemp: 64.63492618774067, barometer: 29.8973336, beaufort:
0.,
???
On Thu, 23 Jul 2020 at 19:39, galfert wrote:
> For anyone discussing this new GW1000 API driver in the WeeWX development
> section STOP. Use this user section instead to discuss its use.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user"
For anyone discussing this new GW1000 API driver in the WeeWX development
section STOP. Use this user section instead to discuss its use.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails
thank you Matthias, I already did, she told me I should remove the 5 all in
1 sensor unit from WS view. Then I should be able to get the rain data from
the new raingauge. I will loose all the other sensor data then though, as:
- external temp
- solar
- uv
- hum
- wind directory and wind speed
Just recocnized the very promising announcement in the developer forum...:
https://groups.google.com/forum/#!topic/weewx-development/bhtsW6WWtvQ
On Github:
https://github.com/gjr80/weewx-gw1000
Will test this API driven driver certainly during the weekend.
Matthias
--
You received this
thank you
On Wednesday, July 22, 2020 at 2:01:16 PM UTC-4, Jamie Stephens wrote:
>
> new user
>
> saw this in my logs today, anything i need to worry about?
>
> Jul 22 09:25:19 weewx systemd[1]: Starting Cleanup of Temporary
>>> Directories...
>>
>> Jul 22 09:25:20 weewx
If you have beaufort in the loop packets then you should end up with
beaufort in archive records. Does it work now? If not $current.x tags
come from the archive record hence the suggestion to run WeeWX directly for
at least a full archive period to confirm that beaufort is appearing in
Hi, Gary!
Thanks for the hints. In deed, there is a value for beaufort in the loop:
LOOP: 2020-07-23 14:16:36 CEST (1595506596) altimeter:
30.065488730750573, appTemp: 69.20122805363343, barometer: 30.014,
beaufort: 1, cloudbase: 3824.7354273385445, dateTime: 1595506596, dewpoint:
>
> Thank you for the detailed explanation Gary! I have added the
> [Accumulator] section to my weewx.conf for lightning_strike_count ->
> extractor = sum and lightning_distance -> extractor = min. Now to wait for
> another storm.
-Troy
--
You received this message because you are
For questions regarding WS View and shown or not shown data you might
contact Lucy from the Ecowitt support by mail. In general she answers your
questions within 24 hours.
Email: ecowittweat...@outlook.com
Regards,
Matthias
Am Mittwoch, 22. Juli 2020 15:56:42 UTC+2 schrieb RMiles:
>
> Hi,
>
Hi,
A little background as to how WeeWX takes loop data and generates archive
records to save to database. WeeWX accumulates the loop data seen during an
archive interval and when using software record generation (as you are) WeeWX
synthesises an archive record from the accumulated loop data
20 matches
Mail list logo
