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 > > Syslog extract and debug.txt attached. Output from this is null. Thanks > again. > > > > On Sunday, August 23, 2020 at 3:11:24 PM UTC-6 gjr80 wrote: > >> Please don’t use [[field map]], it is ignored by the GW1000 >> driver/service and will result in the default field map being used which >> will map intemp to inTemp; it definitely will not map intemp to extraTemp2. >> Plus we are left trying to work out if you made a typo or not. >> >> So we know the field map is being read and used (when [[field_map]] is >> used) and the GW1000 is emitting intemp and inhumidity. Now we need to look >> closer at how the data is processed through the GW1000 service. Can you >> please edit weewx.conf, set debug = 2 and make sure the [GW1000] stanza >> has [[field_map]] and that it is set to: >> >> [[field_map]] >> extraTemp2 = intemp >> extraHumid2 = inhumid >> extraTemp1 = temp1 >> extraHumid1 = humid1 >> soilMoist1 = soilmoist1 >> >> Then save weewx.conf and restart WeeWX. Let WeeWX run for 10 minutes then >> take a log extract from when WeeWX was restarted through until 10 minutes >> elapsed and post the extract here. >> >> Can you also run wee_debug >> <http://weewx.com/docs/utilities.htm#wee_debug_utility> and post the >> wee_debug output, do check the wee_debug out for sensitive info such as >> usernames, passwords and api keys etc, wee_debug should obfuscate such >> entries but it is not perfect. >> >> Gary >> On Monday, 24 August 2020 at 05:37:46 UTC+10 [email protected] wrote: >> >>> With bme280wx uninstalled and GW1000 set to [[field_map]], I get all >>> nulls in the database. >>> With bme280wx uninstalled and GW1000 set to [[field map]], I get all GW >>> values, but intemp and inhumid are sent to inTemp and inHumidity. >>> I have switched back and forth repeatedly and this is what I get. >>> With bme280wx installed, I get values from the bme280, but not from >>> GW1000, no matter what settings I use. So it seems that bme280wx and GW1000 >>> are incompatible. But maybe someone who is running a bme280 and GW1000 >>> successfully will chime in here. >>> >>> Timothy >>> >>> On Sunday, August 23, 2020 at 9:54:13 AM UTC-6 [email protected] wrote: >>> >>>> this is still incorrect. it should be [[field_map]] ← note the >>>> underscore >>>> >>>> On 24 Aug 2020, at 1:22 am, Timothy Buchanan <[email protected]> >>>> wrote: >>>> >>>> This morning, I deleted the other service and restarted weewx. GW1000 >>>> not reports intemp and inhumid, but mapped to inTemp and inHumidity. Here >>>> is the field_map: >>>> >>>> [[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/e6a1fb85-900b-4ccf-8435-c9e80c7fbaf7n%40googlegroups.com.
