after reading the weewx code i discovered that how the wind values are 
presented in the loop packets matters. i was creating separate loop packets 
for windspeed and winddir, which i think caused weewx to believe that the 
speed is zero when processing the winddir. i changed my driver to deliver a 
single loop packet that includes both windSpeed and windDir. this seems to 
have resolved the issue as i now see windDir values in my archive records.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/651b82f6-5720-418e-9b87-cfd91b1d3154o%40googlegroups.com.

Reply via email to