Hi David,
the sentence *"**/It is not necessary to do so if only displaying
current values (ie values from the current archive record)"/* is maybe
a bit trickily phrased - at the time the report is generated weewx
includes values from the database and the current values of all
observations in the current values table, also from those which have not
been archived but are still available in memory from what has been
provided from the driver (here Ecowitt Gateway). That's what you address
by $current.
They will be discarded/replaced by new values coming in - and won't be
accessible later unless also archived by one of the methods described
(new columns/fields or repurposing of existing schema fields) while the
archived values are of course still accessible in the database.
On 27.06.2023 02:16, David Bätge wrote:
Hi Gary and Jon,
I just got some time to look into this (and also made some notes for
myself):
First of all, the GW1000 driver provides a lot of sensor information,
the complete list is:
_Batteries_:
wh31_ch1_batt
wh31_ch2_batt
wh32_batt
wh40_batt
wh41_ch1_batt
wh51_ch1_batt
wh57_batt
ws80_batt
ws90_batt
_Signals_:
wh31_ch1_sig
wh31_ch2_sig
wh32_sig
wh40_sig
wh41_ch1_sig
wh51_ch1_sig
wh57_sig
ws80_sig
ws90_sig
Here is the complete LOOP package with relevant values:
{
'wh31_ch1_batt': '0',
'wh31_ch1_sig': '4',
'wh31_ch2_batt': '0',
'wh31_ch2_sig': '4',
'wh32_batt': '0',
'wh32_sig': '4',
'wh40_batt': '1.39',
'wh40_sig': '4',
'wh41_ch1_batt': '5',
'wh41_ch1_sig': '4',
'wh51_ch1_batt': '1.3',
'wh51_ch1_sig': '4',
'wh57_batt': '4',
'wh57_sig': '4',
'ws80_batt': 'None',
'ws80_sig': '0',
'ws90_batt': '2.86',
'ws90_sig': '4',
}
To be honest, I don't quite understand all of the fields, but I will
try to give an explanation and how to configure these fields in weewx-wdc:
Observations that show something like "Battery OK" or "Battery LOW"
(where 0 is OK and 1 is LOW): `wh31_ch1_batt, wh31_ch2_batt,
wh32_batt`, and `wh41_ch1_batt, wh57_batt` (see
https://github.com/gjr80/weewx-gw1000/wiki/Sensor-battery-states).
This kind of observation needs to be added to
[DisplayOptions]sensor_battery_status in skin.conf.
*Note to me:* wh41_ch1_batt, wh57_batt using another representation of
Battery status, see
https://github.com/gjr80/weewx-gw1000/blob/master/supplementary/skins/Seasons/sensors.inc
and
https://github.com/gjr80/weewx-gw1000/wiki/Adapting-the-Seasons-skin-to-display-battery-states
(There are a few tweaks needed to support these fields)
Signal level observations: All *_sig observations like, wh31_ch1_sig,
wh31_ch2_sig, wh32_sig. I don't understand these: What is the signal
level here? Values seem to be `0` or `4` in that LOOP packet (looks
like battery state fields?).
Battery Voltages observations: wh40_batt, wh51_ch1_batt, ws80_batt,
ws90_batt. These should be added to any of
[DisplayOptions]sensor_stat_tile_observations,
[DisplayOptions]sensor_diagram_observations or
[DisplayOptions]sensor_table_observations in skin.conf.
So the problem with all these observations is basically (as far as I
understand, please correct me if I am wrong): WeeWX does not know
about them and does not save them to the database (but you will need
this data to show plots of the battery voltages for the last week for
example). There should be two ways to overcome this:
1. Add the fields provided by the GW1000 driver to the database, see
http://weewx.com/docs/latest/customizing.htm#Modifying_an_existing_database
2. Map the GW1000 fields to WeeWX schema fields (see
https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py#L16)
I assume that was somehow done for a short period of time because e.g.
rxCheckPercent or consBaterryVoltage are showing/having data for a few
days!?)
@Gary I don't quite understand what you have written about that:
/It is not necessary to do so if only displaying current values (ie
values from the current archive record)/
How would you show fields like wh41_ch1_batt from the current archive
record when the data is not saved? Am I missing something?
gjr80 schrieb am Dienstag, 6. Juni 2023 um 13:32:47 UTC+2:
Jon,
No problems. The console output shows the Ecowitt gateway driver
is populating loop packets with sensor status data, eg ws90_sig,
wh57_batt etc. I assume the sensor data is complete for all
sensors registered with your gateway device (I cannot tell this,
only you can). WeeWX is then accumulating this data and it appears
in WeeWX generated archive records.
Looking at the weewx-wdc GitHub page it appears to use a similar
system to the Seasons skins for displaying sensor status data. The
default fields to be displayed are set in sensor-status.html.tmpl
and these can be overridden in skin.conf. The default appears to
include fields such as rxCheckPercent, consBatteryVoltage,
inTempBatteryStatus, rainBatteryStatus etc. None of the Ecowitt
sensor state fields are included so I expect you need to
override/augment the sensor state fields to be displayed in
skin.conf. How you do this (ie which settings to adjust) is best
discussed with the skin author.
On thing you will need to consider is whether or not to save the
sensor state data to archive. It is not necessary to do so if only
displaying current values (ie values from the current archive
record), but if you wish to display any aggregates based on
historical data you will need to do so. Fortunately it is easy to
do, just modify your database schema using wee_database to include
the desired fields and WeeWX will take care of the rest. Refer to
Modifying an existing database
<http://weewx.com/docs/latest/customizing.htm#Modifying_an_existing_database>
in the Customization Guide.
Gary
On Thursday, 1 June 2023 at 12:54:20 UTC+2 [email protected]
wrote:
Hi Gary
Sorry for the delay, other domestic "priorities" got in the way!
Attached are the files which I hope will help. Dave has now
released the v3.2.0 of the weewx-wdc skin which has the
sensors page. Currently it is not displaying any data. I
suspect this is part of the bigger issue.
Please let me know if you need more information. FYI
wslwx.co.uk <http://wslwx.co.uk> is my site address.
Best wishes
Jon
On Monday, 10 April 2023 at 21:24:59 UTC+1 gjr80 wrote:
Further to what Vince said, if the problem is data not
being saved to database then it will be worth while
running WeeWX directly
<http://weewx.com/docs/usersguide.htm#Running_directly> for
at least two archive intervals to see what data appears in
loop packets and archive records. This will see loop
packet and archive record data sent to the console, take a
(text) copy of this output and post along with your log
extract/wee_debug output.
Gary
On Tuesday, 11 April 2023 at 04:47:02 UTC+10 vince wrote:
One thought would be to read and follow
https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
and
https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem
On Monday, April 10, 2023 at 9:40:25 AM UTC-7 Jon Fear
wrote:
Hi
I am currently working with Dave of the weewx-wdc
skin fame create a sensor stats page for the skin.
Dave has a copy of my db to play with however he
has noticed that the sensor values are not being
recorded frequently. He notes that the values were
recorded for a few days in January and then not
until the end of March, then again only for a few
days.
I do not think I have changed very much at either
time, perhaps a restart here and there and
obviously updated weewx itself but..
Any thoughts?
Thanks
Jon
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/c2ce950d-c9f5-4b3c-8349-f13045679c9fn%40googlegroups.com
<https://groups.google.com/d/msgid/weewx-user/c2ce950d-c9f5-4b3c-8349-f13045679c9fn%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/8a85d5a6-2e8d-f94c-247b-c1f744babfe8%40gmail.com.
