Bill
About not being able to run the driver directly, If you have python 2 on
your system, but have installed WeeWX to use python 3 you may not have
installed the prerequisites for python 2. If you have a setup.py install
and try to run:
PYTHONPATH=/home/weewx/bin python -m user.gw1000 --test-dr
When running reconfigure with prompts, there are two changes, that occured
in my case without asking:
group_pressure turns to inHg, and group_speed and group_speed2 turn to
mile_per_hour
and ~2 respectively.You better diff old and new version before restarting.
In addition, 'radiation': 'solar_r
Hi All
Have been using the Instromet Stand Alone Sun Duration sensor which if
connected to a Davis Vantage Pro2 system needs to go to a spare rain socket
in the ISS.
Each 0.01 is equivalent to 36 seconds of sunshine and I have converted that
to hours and minutes on my web page.
The next stage
I have a WS6in1 station, and I was wondering if the observation data from
extra sensors could be displayed in the index_hook_after_station_info and
updated with MQTT like the data from the main sensor. At the moment I have
only one extra sensor but I am planning on expanding in the future. I mad
Just as I was going to check the db for the entries you said, my
Weatherflow station started having radiation and windspeed sensor fails.
Now that I have a replacment up and running, I did the db check and I do
have all the parameters in there as well as ET calculations but the result
is so sma
On Sunday, 26 July 2020 00:54:03 UTC+10, Vetti52 wrote:
>
> When running reconfigure with prompts, there are two changes, that
> occured in my case without asking:
> group_pressure turns to inHg, and group_speed and group_speed2 turn to
> mile_per_hour
> and ~2 respectively.You better diff old a
I am not sure if this impacts on the WH65 issue mentioned below but I now
have the driver distinguishing whether there is a WH65 or WH24 connected to
the GW1000. This will (I hope) have a flow on affect on battery status
fields but given the manner in which the API works I don't believe it will
gjr80 writes:
> Some folks derive field radiation from luminosity though I believe the
> relationship is somewhat complex.
I'm not at all clear on what labels the various stations use.
I would use "solar irradiance" or less pedantically "solar radiation".
The term "field radiation" is interesti
Hi,
If I am understanding you correctly you have a field that is being
populated in the WeeWX database. The field data is such that you display
cumulative values or sums (ala rain) rather than point in time values (like
temperature, pressure etc). You have been scaling that field on your web
p
On Sunday, 26 July 2020 08:55:08 UTC+10, Greg Troxel wrote:
>
> gjr80 writes:
>
> > Some folks derive field radiation from luminosity though I believe the
> > relationship is somewhat complex.
>
> I'm not at all clear on what labels the various stations use.
>
> I would use "solar irradiance" o
gjr80 writes:
> You will notice the highlight on the word radiation (but not the word
> field) in my original post, this was in reference to the WeeWX field named
> radiation, not to something known as 'field radiation'.
Sorry, reading in plain text so I did not actually notice that :-)
> I d
Agreed completely :)
Gary
On Sunday, 26 July 2020 09:37:41 UTC+10, Greg Troxel wrote:
>
> gjr80 writes:
>
> > You will notice the highlight on the word radiation (but not the word
> > field) in my original post, this was in reference to the WeeWX field
> named
> > radiation, not to something
Whilst there definitely is nothing in the API for retrieving what WeeWX
knows as 'radiation', there is a calibration setting labelled 'SolarRad
Gain' in the WS View app (interestingly there is no gain setting for
anything to do with 'light', luminosity, illuminance etc so it could be a
mis-labe
It should be numbers like 0.01 or 0.02 inch per hour. I'm just around the
corner in Hood River, and my max value today was 0.024/hr, but it is
probably a bit drier here (RH today was 25%). So, if you have a 5 minute
archive interval, 0.001 sounds about right.
ET is best viewed as summed over a day
Hi Gary
Thanks for your quick response.
You have confirmed the best way is to populate a new field to get the graph
Im looking for.
Im happy with adding a new field to the database
This new field would have the 0.01 * 36 but im not sure how to do that
Is that done in the vantage.py file, and if so
I have been running weewx on a zeropi with wifi connected to my home
network . The zeropi gets the weather station data through a usb connection
to a Acurite 5in 1 PWS and I can access the weewx dashboard from my
browser. The weewx also uploads the data to a PWSWeather.com to allow
viewing on
Is‘t it better to post possible errors on Githup? In addition to Radiation
I‘m also missing rain and current rain rate now.
Will open issues on Github now.
Am Sonntag, 26. Juli 2020 02:13:38 UTC+2 schrieb gjr80:
>
> Whilst there definitely is nothing in the API for retrieving what WeeWX
> knows
Phil,
No need to modify vantage.py, in fact modifying one of the core WeeWX files
is seldom a good solution when others exist. You open yourself up to losing
your changes over an upgrade or if you place your modified file in
/home/weewx/bin/user (or /usr/share/weewx/user) so it is safe from
up
https://github.com/gjr80/weewx-gw1000/issues
Am Sonntag, 26. Juli 2020 08:39:19 UTC+2 schrieb NanoG5Kite:
>
> Is‘t it better to post possible errors on Githup? In addition to Radiation
> I‘m also missing rain and current rain rate now.
> Will open issues on Github now.
>
> Am Sonntag, 26. Juli 2
I don't mind, Github is probably easier for tracking and hopefully keeps
one problem per issue unlike posts here which tend to grow many heads. All
I ask is that some appropriate details of the problem are included (eg an
explanation of the problem and a startup debug log extract - a list of
at
20 matches
Mail list logo
