I have a sensor that's reporting bad temperatures. It's outdoors in northern Vermont but reported the temperature this afternoon as 85°F. That's just wrong. The probe is buried in the garden (to be ready to monitor soil temperatures in the spring), and the ground is frozen hard. It's nothing like 85°. The air temperature on the other side of the garden (above ground!) was 27°. I've been thinking that the sensor was dying and was reporting nonsense.
But I realized today that 27°C is something like 83°F. So now I'm thinking the scale is getting messed up somewhere along the line. Something is getting Fahrenheit when it expects Celsius, and converts it an extra timr. 85°F is 29°C, and 29°F sounds about right. Has anyone seen this kind of error before? Does it sound like I'm on the right track? Weewx isn't the source of the problem. The bad number (complete with °F) shows on the monitor on my Meade TE923W. All of my other readings are in Fahrenheit and seem reasonable in relation to each other. But this sensor is kind of inaccessible for the winter, so I'm thinking of using weewx to fix it for now. I'll deal with the sensor in the spring. Am I right that this sounds like a use for [[Corrections]]? I just create a line like extraTemp1 = (extraTemp1 - 32) * 5/9 and then the corrected reading will be saved in the database? Is there a way to adjust the existing values in the reports? Or can I fix the existing records in the database? Thanks a lot. Lynda -- 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]. For more options, visit https://groups.google.com/d/optout.
