Sorry, but you did not answer my question.
I am reading the CCDTemperature property, but I am also reading the HeatSinkTemperature property to allow me to control how the camera temperature is warmed up, since I don't want to continue to try to warm up the sensor above the HeatSinkTemperature.
I would expect that reading the HeatSinkTemperature would throw an exception if it is not supported, rather than to always return the same, unreasonable value.
Per the ASCOM Developers Help documentation, the driver should throw a NotConnectedException when a client app attempts to read the HeatSinkTemperature property value and the data is unavailable.
As it is, I have a hack in my code to ignore the HeatSinkTemperature, specifically for ZWO hardware.