Yes that's exactly what I was missing. I'll dig into database customization tonight. This definitely solves my problem!
On Fri, Oct 29, 2021, 8:10 AM gjr80 <[email protected]> wrote: > Ok, understand. The field map maps GW1000 sourced data to field names that > will appear in loop packets from the driver. WeeWX accumulates data from > those loop packets and synthesises archive records. The archive records > will have the same field names as the loop packets. WeeWX then saves the > archive record data to database, but the only data that is saved is that > which is in fields that are common to the archive record and the database > schema. So if the database schema has a field named outTemp outTemp data > from the archive record will be saved to database. If database schema has > no field named wh57_batt wh57_batt will NOT be saved to database. > > It sounds likes the part you are missing is having the database schema > include the same field names as the additional archive record data fields > you are trying to save. The ‘Customizing the database’ link I provided > should help. > > Gary > > On Friday, 29 October 2021 at 21:29:57 UTC+10 Evan Kimberly wrote: > >> Hi Gary, >> >> Thanks for your answer. I think it has clarified something for me. I >> assumed the field map defined the fields in the archive database, and it >> appears I am wrong. The lightning data I'm missing includes detection time >> and count (not strike count but total), and those fields do not appear in >> the archive. Same with the battery and signal fields. I will try running >> weewx directly to view loop packets and archive records for myself, as well >> as reading up on customizing the database. >> >> Thanks, as always, for the help. I think you have pointed me in the right >> direction. Sorry for my lack of understanding! >> >> On Fri, Oct 29, 2021, 2:09 AM gjr80 <[email protected]> wrote: >> >>> Hi, >>> >>> I am a little perplexed as to what your lightning data problem is. You >>> say you are having no luck in having WeeWX display data from your lightning >>> detector but you then go on to say that the GW1000 driver is displaying >>> lighting data both via --live-data and --test-driver, the lightning >>> data is being populated in your archive and your skin is displaying >>> lightning data. Sounds to me like your lightning data is being processed >>> and displayed as it should. >>> >>> You mention that you have no battery or signal strength fields, is this >>> for your lightning detector? If so when you ran the GW1000 driver directly >>> with --live-data and --test-driver did you see fields wh57_batt and >>> wh57_sig? If so did they contain expected data? Did you run WeeWX >>> directly <http://weewx.com/docs/usersguide.htm#Running_directly> and >>> note if the missing battery and signal data is in the loop packets and >>> archive records? (When running WeeWX directly you will see loop packets and >>> archive records displayed on the console; loop packets indicated by lines >>> starting with LOOP: and archive records on lines starting with REC:). If >>> you are seeing wh57_batt and wh57_sig in archive records then the >>> driver and WeeWX are working as they should. What are your trying to do >>> with the battery and signal data? If you wish to display the current value >>> then there is nothing you need do to WeeWX or the GW1000 driver, though you >>> may need to modify your skin to display the data (I am afraid I cannot help >>> with the Belchertown skin). If you wish to to display historical/aggregate >>> data or plot either/both you will need to have WeeWX store your battery and >>> signal data in your archive.This can be done by altering your database >>> schema to include wh57_batt and wh57_sig (these fields are not included >>> in any of the supplied database schemas, you need to add them yourself - >>> refer to the section Customizing the database >>> <http://weewx.com/docs/customizing.htm#archive_database> in the >>> Customization Guide) or by altering the GW1000 driver mapping to map those >>> fields to appropriate fields that already exist in your database schema. >>> Once you have the data in your archive you then (may) need to alter your >>> skin to display the data. >>> >>> Gary >>> On Friday, 29 October 2021 at 13:31:57 UTC+10 Evan Kimberly wrote: >>> >>>> Hello, >>>> >>>> I have been trying to set up my lightning detector to display data in >>>> weewx and not having any luck. I started digging and it appears that my >>>> archive does not have the appropriate fields populated for the field map. >>>> >>>> When I run the driver with the --default-map command I see the >>>> appropriate field map, as detailed on the driver wiki page. >>>> >>>> When I run the --live-data command, I see my lightning data (plus the >>>> rest of my data) as produced by the GW1000, in ecowitt notation. >>>> >>>> When I run the --test-driver command, I see the same data, now in weewx >>>> notation. >>>> >>>> I thought this might be a version issue, as I had 0.3.1 (or 0.3.2, i >>>> forget which) version of the driver, and just updated to the current >>>> version today with no change. >>>> >>>> For reference, these are the fields I see in my archive, when I export >>>> it to csv: >>>> >>>> *DateTime, usUnits, interval, altimeter, appTemp*, appTemp1, >>>> *barometer*, batteryStatus1, batteryStatus2, batteryStatus3, >>>> batteryStatus4, batteryStatus5, batteryStatus6, batteryStatus7, >>>> batteryStatus8, *cloudbase*, co, co2, consBatteryVoltage, *dewpoint*, >>>> dewpoint1, ET, *extraHumid1, extraHumid2, extraHumid3*, extraHumid4, >>>> extraHumid5, extraHumid6, extraHumid7, extraHumid8, *extraTemp1, >>>> extraTemp2, extraTemp3*, extraTemp4, extraTemp5, extraTemp6, >>>> extraTemp7, extraTemp8, forecast, hail, hailBatteryStatus, hailRate, >>>> *heatindex*, heatindex1, heatingTemp, heatingVoltage, *humidex*, >>>> humidex1, *inDewpoint, inHumidity, inTemp*, inTempBatteryStatus, >>>> leafTemp1, leafTemp2, leafWet1, leafWet2, *lightning_distance,* >>>> lightning_disturber_count, lightning_energy, lightning_noise_count, >>>> *lightning_strike_count,* *luminosity, maxSolarRad*, nh3, no2, noise, >>>> o3, *outHumidity, outTemp,* outTempBatteryStatus, pb, pm10_0, pm1_0, >>>> pm2_5, *pressure, radiation, rain,* rainBatteryStatus, *rainRate*, >>>> referenceVoltage, rxCheckPercent, signal1, signal2, signal3, signal4, >>>> signal5, signal6, signal7, signal8 , snow, snowBatteryStatus, snowDepth, >>>> snowMoisture, snowRate, so2, *soilMoist1*, soilMoist2, soilMoist3, >>>> soilMoist4, soilTemp1, soilTemp2, soilTemp3, soilTemp4, supplyVoltage, >>>> txBatteryStatus, *UV*, uvBatteryStatus, windBatteryStatus, *windchill, >>>> windDir, windGust, windGustDir, windrun, windSpeed* >>>> >>>> Underlined fields are those containing data, which line up with what I >>>> would expect from my station. If I tell weewx Belchertown (my current skin) >>>> to display lightning distance or lightning strike count, it will. I also >>>> noticed I have no battery or signal strength fields here either. >>>> >>>> >>>> I'm not sure if this is a driver issue or something up with weewx, or >>>> some weirdness due to my freebsd system, but starting with the driver >>>> seemed to be the right place. >>>> >>>> Thanks for any help! >>>> >>>> >>>> >>>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "weewx-user" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/weewx-user/OjjpvqJ1850/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/0ce9d30e-232f-471a-b44d-1f9b51ad743fn%40googlegroups.com >>> <https://groups.google.com/d/msgid/weewx-user/0ce9d30e-232f-471a-b44d-1f9b51ad743fn%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "weewx-user" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-user/OjjpvqJ1850/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/27afab10-7468-469e-8550-9e8eee437d64n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/27afab10-7468-469e-8550-9e8eee437d64n%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/CAMTYJPzeUX73Pvo_j%3DkK2g0ZsPTaijJ8PrQSCZf5WJJ4eC3-gQ%40mail.gmail.com.
