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 jonfe...@googlemail.com 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 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/3a867f0f-965f-46ec-af72-54e4c80d4488n%40googlegroups.com.
