It appears that it did, although that was unintentional. If you use the functions we provide for parsing temperature it is handled either way so I didn’t catch this in testing. I will dig a little deeper to make sure that there wasn’t something else related to temperature that I missed, but otherwise I should be able to have a fix out for this in the next couple of days.