Re: [weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

Thanks again to both, this got me an idea about how things are working! I was asking about testing because my Station/Driver does not provide any "extra-fields" which are not saved, just fields included in the schema. I should have said that I am the Dave from the weewx-wdc Skin, whom John ment

Re: [weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

"Where is this data actually stored if not in the database? Is there any way to test this out, besides actually using the said driver?" The data is not stored on a medium (e.g. disk) but just kept in memory during the runtime of the program - and even there only as long as the program logic al

[weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

Comments below. Gary On Wednesday, 28 June 2023 at 00:19:33 UTC+1 david@gmail.com wrote: Is the $current tag the only tag that provides this access? I assume the $latest tag also does? Under most circumstances $latest will return fields from the current archive record irrespective of w

[weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

Hi Rainer and Gary, thank you both very much for the detailed explanation! I was not aware that the $current tag also provides access to ALL observations of the current record, regardless if they are archived or not. Is the $current tag the only tag that provides this access? I assume the $la

[weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

David, Some answers/comments below. On Tuesday, 27 June 2023 at 01:16:51 UTC+1 david@gmail.com wrote: 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

Re: [weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

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

[weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

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_bat

[weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

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 accum

[weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

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

[weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

Further to what Vince said, if the problem is data not being saved to database then it will be worth while running WeeWX directly for at least two archive intervals to see what data appears in loop packets and archive records. This will se

[weewx-user] Re: GW1000 Gateway - sensor battery stats not entering onto DB

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 s