I can confirm this is a bug. Had to rollback firmware upgrade on a couple of them today because of this. One of them was the only device in the rack in a 68F room. At least on 2.5.0.83.
This seems to be a bug in the 2.5.x code line. I had the same issue after upgrading from the 2.4 code line. Rolling back to the 2.4 line made everything happy again.