Can’t comment on the error when stopping WeeWX, I guess it’s possible something
was messed up that prevented the ‘stop’ script running successfully. I’d give
it the benefit of the doubt for now.
I note from your previous thread I mentioned there was no need for a label map
(field map) as your label names were the same as WeeWX field names. This is not
the case, radiation being a case in hand. That being said fileparse expects a
label map to be under a [label_map] stanza but you have a [Label_Map] stanza.
Case matters here so you might want to change that. This won’t fix your
windGust problem though.
Other than the label map case issue the startup log seems to indicate no config
issues.
The malformed field name could be a sign you still have some issues with your
data.csv. Appreciate the data going into data.csv may be correct but the
fileparse driver uses what is actually in the file; the two could be different.
You might want to try some additional logging in the fileparse driver. Adding a
loginf line like the following in genLoopPackets() will log each line read from
data.csv:
with open(self.path) as f:
for line in f:
loginf(“line=%s” % line)
eq_index = line.find('=')
name = line[:eq_index].strip()
value = line[eq_index + 1:].strip()
It’s going to log a lot but at least we can see the raw data WeeWX is reading
from data.csv.
It’s also interesting that windGust is coming through loop packets as 0.0 but
is accumulated in an archive record as None; I would have expected it to come
through as 0.0.
Gary
--
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/3a37c19d-83a3-4e4b-adf9-302705a47105%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
