This is a result of using ThermostatSetpoint:DualSetpoint. Since there are two set point temperatures, one for cooling and one for heating, the choice of which of those temperatures to use for reporting was never included (coded) such that this specific table had non-zero values. Change to the single cooling and heating set point (or cooling or heating only) type and you should see the non-zero data.

Here's a view of the table after correcting the problem: C:\fakepath\CorrectedZoneTempSP_HVACSumaryTable.jpg