Vince, Now Vince, I could have said Google 'outTempDay' and take the 1st result.... :)
Seriously, are you running weeWX-WD or some derivative by chance? outTempDay (along with outTempNight ) is a field added to loop packets and archive records by weeWX-WD for the purposes of calculating (month, year, all time) max/min day time and night time temperatures. If the time is between 6am and 6pm then outTempDay = outTemp and outTempNight = None and if the time is between 6pm and 6am then outTempDay = None and outTempNight = outTemp . WeeWX may be doing something to omit outTempNight since (in the case you cited) it will be None, or it may be there if you look again. I thought weeWX-WD was well behaved (well behaved in this regard anyway) and should have converted outTempDay and outTempNight to the appropriate units before adding it to the packet/record, trust me it is not some sort of metric conspiracy. Mind you, that functionality goes back to 2014 so who knows, but I am almost certain that code has always respected the packet/record units. In any case you have your hint on where to look. Gary On Saturday, 27 January 2018 10:02:34 UTC+10, vince wrote: > > I'm fiddling with the weewx-mqtt extension Matthew wrote to export weewx > data to MQTT topics and notice a 'outTempDay' item in there with a value of > 4.8333 here, but I can't figure out what that means or where it comes from. > > Weather here is miserable at about 40.8 F which is pretty close to that > value 'if' it is degrees C, but that might be a coincidence. It might be > the high or current temperature for the day, but that seems odd since I'm > running weewx in US units. > > Ideas ? > > -- 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.
