Dear Samsung SmartThings Support / Developer Relations Team,
I am writing to report a critical limitation and a conflicting behavior regarding the cloud API implementation for Samsung Air Conditioners (OCF Device Type: oic.d.airconditioner, Model profile family: TP6X_RAC, VID: DA-AC-RAC-100001).
I have read several other topics from users requesting similar fixes, but I would like to provide detailed technical logs to highlight exactly why this breaks third-party integrations.
Issue 1: Missing ‘heat’ mode in supportedAcModes
When querying the device status via the SmartThings Cloud API (e.g., using devices:capability-status from the official CLI), the airConditionerMode capability returns the following array for the supportedAcModes attribute: ["cool", "dry", "wind", "auto"]
The heat mode is completely omitted from this array, despite the physical heat pump hardware fully supporting heating operations (and functioning correctly via the official SmartThings mobile app).
Impact: This acts as a hard blocker for home automation platforms like Home Assistant. When an automation tries to dispatch a heating command, the integration’s schema validation strictly rejects it, returning: HVAC mode heat is not valid. Valid HVAC modes are: off, cool, dry, fan_only, auto.
Issue 2: Conflicting COMPLETED Status via API
Trying to bypass the limitation by sending a direct REST API payload (including locationId, switch, airConditionerMode: heat, and thermostatHeatingSetpoint) results in a formal 200 OK / COMPLETED response from the cloud broker. However, the physical indoor units completely ignore the command.
If we mistakenly send a thermostatCoolingSetpoint alongside the heat mode, the cloud still returns COMPLETED instead of a validation error (422), even though the physical unit drops the conflicting state change entirely.
The Request:
-
Please review the European cloud Device Profiles for Samsung heat pump air conditioners (specifically
DA-AC-RAC-100001) and update thesupportedAcModesattribute to officially include the"heat"string. -
Ensure that API validation correctly rejects conflicting setpoints (e.g., sending a cooling setpoint while requesting heat mode) instead of returning a misleading
COMPLETEDstatus while the physical unit drops the command.
Thank you for your time and for reviewing these technical logs. Fixing the capability array would instantly resolve the integration barrier for thousands of smart home users.
Best regards,