Comment 13 for bug 1581594

I could sponsor this change for you as it looks sane in this case, but I'm a bit concerned that it's not the right way to go. I think the right way is per what smartmontols-devel reply was, i.e. that we should actually, in case of multiple temperature readings, should prefer the one that's more common - and in that case treat the other attribute as another value. I'm simply worried that this change could affect some of those older HDDs that actually used 231 only to denote temperature. Do we know if those won't get affected?