Actually, looking at the code I can see that timestamps of the GW1000 data are handled differently when operated as a driver and as a service. In this case adding dateTime = datetime to [[field_map]] will get things operating as expected.
I need to revisit the handling of GW1000 data timestamps, the need for dateTime = datetime may or may not be the final solution. Either way the final version will be backwards compatible with a dateTime = datetime entry in the field map.This issue has also highlighted the need for some better debug output around the processing of loop packets. Gary On Tuesday, 25 August 2020 at 16:34:25 UTC+10 [email protected] wrote: > add ‘dateTime = datetime’ back to field_map. > worth a go while gary works on it > > On 25 Aug 2020, at 8:37 am, Timothy Buchanan <[email protected]> > wrote: > > How would I add dateTime to the field_map? > > On Monday, August 24, 2020 at 9:59:17 AM UTC-6 [email protected] wrote: > >> try adding ‘dateTime’ to the field_map. i think augmentations are skipped >> (gw1000 fields are not added) because on its absence the service assumes >> the offered data is infinitely old >> >> On 25 Aug 2020, at 12:47 am, Graham Eddy <[email protected]> wrote: >> >> it will be interesting to see what gary concludes. >> it looks to me like the fields are correctly identified and mapped (i >> presume; the data is there but i don't see the mapped result) but not >> inserted into packet by augmentation. one reason for not inserting the data >> would be if it is stale - do the timestamps of the weatherflowudp driver >> (datetime in packet) line up with the gw1000 service (datetime in >> mapped_data) within age toleration? >> >> On 24 Aug 2020, at 11:48 pm, Timothy Buchanan <[email protected]> >> wrote: >> >> field_map used with debug 3. >> >> On Sunday, August 23, 2020 at 6:07:35 PM UTC-6 gjr80 wrote: >> >>> Thanks, from the log it looks like the GW1000 service thread has >>> silently died (which it shouldn't, it should die loudly if it dies!). Let's >>> step the debug level up, leaving everything else as it is edit >>> weewx.conf and set debug = 3, save weewx.conf and restart WeeWX. Let >>> WeeWX run for about five minutes and again take a log extract from when you >>> just started WeeWX. Post the log here. >>> >>> Gary >>> >>> On Monday, 24 August 2020 at 09:55:21 UTC+10 [email protected] >>> wrote: >>> >>>> debug=2 GW options so (pasted): >>>> >>>> # Options for extension 'GW1000' >>>> [GW1000] >>>> driver = user.gw1000 >>>> [[field_map]] >>>> extraTemp2 = intemp >>>> extraHumid2 = inhumid >>>> extraTemp1 = temp1 >>>> extraHumid1 = humid1 >>>> soilMoist1 = soilmoist1 >>>> >>> >> >> > -- > 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/fb279140-dd76-4767-92b8-1cdb780a2e30n%40googlegroups.com > > <https://groups.google.com/d/msgid/weewx-user/fb279140-dd76-4767-92b8-1cdb780a2e30n%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/93bf281c-5681-432d-a41c-1bab61e71147n%40googlegroups.com.
