If a device reports that it supports a ‘heat’ mode, then it should implement a heatingSetpoint per the spec. If it doesn’t support a ‘heat’ mode, then it should not report ‘heat’ in the supportedThermostatModes.
It sounds like the device is reporting that it supports distinct Heat and Cool modes in addition to an Auto mode. In that case, the device should report a heatingSetpoint and coolingSetpoint attribute, but based on the screenshots above only the coolingSetpoint is available.
We’ve seen this with other non-certified device integrations – the device authors take creative liberties with how they implement the devices and they don’t conform to the platform standards which causes issues.
@Shariff_Attaya can you send a note to support@sharptools.io with the Doc ID so I can take a closer look at the device? As alluded to above, I suspect it’s a flawed integration that would have to be resolved by the manufacturer.