Gary,
Thanks!
I installed the patch, but it did not help. I also tried to uncomment my
own fix from weeimport.py, (the fix which you don't recommend to do...) but
that returned my first problem back.
My original date.csv has datetime format as in my csv.conf
raw_datetime_format expect. Thanks
Lucky SO(?)!
On Monday, February 21, 2022 at 7:34:25 AM UTC-6 tke...@gmail.com wrote:
> Matthew Wall signed the last couple of releases. He may have used a
> different signature. If he did, I don't have access to it, and he is on a
> small boat in the Caribbean until the end of the month. I'l
Hello
After the update from Weex 4.5.2 to 4.6.2 I only have 2 sensors in the list.
outside temperature and air pressure.
I am using an HP1000 driver.
There are also some error messages in the sys log!
Skin unknown unknown although I specified standard in the config.
Here is an excerpt from the log
Janne,
"It doesn't work" is not very helpful. Please return weeimport.py to it's
original 4.6.2 state, ensure you have the patched weeutil.py and then run
the import again. Please post an exact copy of the console output including
the command issued and responses/error traces.
Gary
On Tuesday
The configuration file (skin.conf) for the Smartphone skin is specifying a
template (iv.html.tmpl), which does not exist. This template is not part of
weewx. If it ever existed, it was supplied by you or someone else.
However, I noticed that the path to the template is non-standard. The log
indica
Gary,
yes, my mistake! I used the wrong version of weeimport.py while I was
returning the original. I have many... Thanks for advising me. Sorry.
Now everything works and I could import data! Your patch was working great.
Thank you! You are really doing a good work!
best regards
Janne
tiist
Hello, I have installed the latest version of
https://github.com/gjr80/weewx-realtime_gauge-data
and the PHP file from
https://github.com/wrybread/weewx-realtime_gauge-data
to create the live_data.json from gauge-data.txt.
The live_data.json will be created but it is empty (only []).
What can I
I have installed your last update, and I will keep an eye on the results
for the next days. Thank you for following up the issue.
However, I performed queries from the accumulator tables for windSpeed,
windDir, windGust and windGustDir. The mintime/maxtime for wind and
direction are unequal bot
The enclosed file was not correct in my last reply.
Please see this new file.
Best Regards, Aslak
On Tuesday, February 22, 2022 at 1:47:36 PM UTC+1 Aslak Vaa wrote:
> I have installed your last update, and I will keep an eye on the results
> for the next days. Thank you for following up the iss
LOL! Well, I guess you could say it's a feature.
max in archive_day_windSpeed is the maximum value seen for 'windSpeed'.
max in archive_day_windGust is the maximum value seen for 'windGust'.
They are not necessarily the same because archived windSpeed is typically
the average wind seen over an ar
Dears,
Currently, i'm working on a Debian server where are running about 7
instances of weewx (7 Davis Vantage meteo stations, six of them are located
in Italy and the last one in Costa Rica).
I use as a driver the wlink - weewx driver that gets data from the
weatherlink web site.
Now, I would
That's quite the setup you have there!
There are several wlink drivers. Which one are you using?
On Tue, Feb 22, 2022 at 7:33 AM 'Sofia_' via weewx-user <
weewx-user@googlegroups.com> wrote:
> Dears,
>
> Currently, i'm working on a Debian server where are running about 7
> instances of weewx (7
Sorry, that was not my intended question.
My issue is that I see wind speed and direction as a pair of values for any
given time. When we speak of max wind, I am interested of the speed of wind
and its direction at that time. The speed is the main issue, and direction
is an attribute to the spee
Thank you for your promptly reply.
I'm using the WLink driver 0.14 (wlink.py 1783 2018-01-29 by mwall), but
mine is for Python 2.7 (I see some modules in the code, such as the urllib2
that is for Python2).
The stations are Vantage Vue Pro equipped with the WeatherLinkIp driver.
I read about th
I am not aware of a Python 3 version of that extension. Matthew is
unavailable until the end of the month. I will try and take a look at it
sometime this week.
On Tue, Feb 22, 2022 at 8:15 AM 'Sofia_' via weewx-user <
weewx-user@googlegroups.com> wrote:
> Thank you for your promptly reply.
>
> I'
Thank you very much, and thanks also for the weewx project that is great.
Have a nice day,
Sofia
Il giorno martedì 22 febbraio 2022 alle 17:30:41 UTC+1 tke...@gmail.com ha
scritto:
> I am not aware of a Python 3 version of that extension. Matthew is
> unavailable until the end of the month.
The accumulators for windDir and windGustDir are useless. If the wind blows
at 359° for an hour, then 1° for an hour, the windDir accumulator would
return 180°. They are there only because it's easiest to just create an
accumulator for everything.
Same with the daily summaries for windDir and wind
Thank you for the clarification.
On Tuesday, February 22, 2022 at 7:43:22 PM UTC+1 tke...@gmail.com wrote:
> The accumulators for windDir and windGustDir are useless. If the wind
> blows at 359° for an hour, then 1° for an hour, the windDir accumulator
> would return 180°. They are there only b
Thanks for the info.
James
On Friday, February 18, 2022 at 10:24:21 PM UTC gjr80 wrote:
> No problems James.
>
> Regards the services, think of the [[Services]] stanza as a matrix. When
> an event occurs (for example the arrival of a new archive record) WeeWX
> works it way down each 'row' (i
19 matches
Mail list logo
