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
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
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
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
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
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.
this is still incorrect. it should be [[field_map]] ← note the underscore
> On 24 Aug 2020, at 1:22 am, Timothy Buchanan
> 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
>
Here is live data:
GW1000 live sensor data: absbarometer: 753.4, datetime: 1598189179, humid1:
42, inhumid: 30, intemp: 21.7,
relbarometer: 753.4, soilmoist1: 26, temp1: 12.8, wh31_ch1_batt: 0,
wh51_ch1_batt: 0
This morning, I deleted the other service and restarted weewx. GW1000 not
reports
The GW1000 data is being picked up every 60 seconds as it should but it is
sans extraHumid2/extraTemp2. Time to look a little closer at what the
GW1000 is picking up. Can you run the GW1000 driver directly with the
--live-data command line option. For a setup.py install something like:
$
Here is the output from one archive period; the REC loop is near the end.
Timothy
On Friday, August 21, 2020 at 11:51:41 PM UTC-6 gjr80 wrote:
> Actually, now that we have the GW1000 field mapping set I suspect the
> answer may be in the loop packets. Tim has three sources contributing to
>
Actually, now that we have the GW1000 field mapping set I suspect the
answer may be in the loop packets. Tim has three sources contributing to
loop packets, and on top of that I believe the Weatherflow driver emits
partial packets which further complicates the process. that being said it
when you run weewx in foreground (not as daemon) so you can see the weewx
records, looking at the REC records (not LOOP records), what are the fields
being offered to archive service? then looking in weewx db, which of these
fields are actally being populated in db?
> On 22 Aug 2020, at 12:24
I think you're being helpful, not harping, and I appreciate it. I just
restarted weewx with [[field_map]] and found the following line in syslog:
Aug 21 19:51:10 raspberrypi weewx[22309] INFO gw1000: user.gw1000: field
map is {'extraHumid1': 'humid1', 'extraHumid2': 'inhumid',
'extraTemp1':
Sorry if you think I am harping on the [[field_map]] issue but I need to
understand if we are trying to track down a field map issue or something
else. Is the log extract you just posted with [[field map]] or
[[field_map]]? because again it shows the setting was ignored.
The reason that
Yes, the GW1000 disconnected and I moved it close to the router for
testing, where I can see it. the router reserves an ip for it. I decided to
start over. I uninstalled the extension, went back to an earlier weewx.conf
then reinstalled the extension. I modified weewx.conf as shown in the
The highlighted line tells me the default field map is being used and not
[[field_map]]:
Aug 20 20:01:29 raspberrypi weewx[31556] DEBUG weewx.engine: Loading
service user.gw1000.Gw1000Service
Aug 20 20:01:32 raspberrypi weewx[31556] INFO gw1000: user.gw1000: GW1000
was found at
[[field_map]] makes all values null, including the ones that worked before.
Syslog follows
--
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
try [[field_map]] instead of [[field map]]. If that does not work edit
weewx.conf, set debug = 1, save weewx.conf and then restart WeeWX. Let
WeeWX run for five minutes or so then post a log extract from when you
restarted WeeWX through until the five minutes elapsed. post the log
extract
OK, I placed this at the end of weewx.conf:
# Options for extension 'GW1000'
[GW1000]
driver = user.gw1000
[[field map]]
extraTemp2 = intemp
extraHumid2 = inhumid
extraTemp1 = temp1
extraHumid1 = humid1
soilMoist1 = soilmoist1
Result is the same as before; the first two lines produce null
Thanks, now I understand. You have the right approach but unfortunately the
execution is not quite correct. Did you run the driver directly with the
—live-data command line option? The output will detail all of the available
GW1000 ‘fields’ and their current values. Those field names are what
Thanks for the detailed reply; I'll try to be more clear. I have two
services running, as indicated by this line:
data_services = user.bme280wx.Bme280wx, user.gw1000.Gw1000Service
The first service is an i2c sensor providing temp/humidity at the raspberry
pi. It's options are so:
[Bme280wx]
Hi,
I think we might need a bit of clarification as to what it is you are
trying to do. You say "inTemp is being used by another service", do you
mean that WeeWX field inTemp is being *provided* by another service/driver
(which has consequences for running the GW1000 driver as as service) or
22 matches
Mail list logo
