The device reports airConditionerMode: heat when controlled via IR remote, but the supportedAcModes list incorrectly excludes ‘heat’. This inconsistency prevents any API-based control (SmartThings App/Home Assistant) from switching the device to Heat mode, as the command is rejected by the cloud validation logic.
This is a part of the status api response
“airConditionerMode”: {
“availableAcModes”: {
“value”: null
},
“supportedAcModes”: {
“value”: [
“cool”,
“dry”,
“wind”,
“auto”
],
“timestamp”: “2026-02-06T15:52:33.815Z”
},
“airConditionerMode”: {
“value”: “heat”,
“timestamp”: “2026-02-06T16:50:30.522Z”
}
}
Hi, @dfandrew
Are you trying to control an OCF-type device?
This reminds me to this other case where other developers were trying to control one of these device types through the API.
The Supported Modes doesn’t prevent the usage of certain values through the API, I made a test and the command gets accepted, meaning it doesn’t have a syntax issue. But, here I provided more info on why this happens (for OCF devices specifically):
Thank you for your reply, but I need to clarify two important points:
Non-OCF Device: My device is not an OCF-type device. It is a standard Z-Wave/Zigbee/Matter/Cloud-to-Cloud integration [specifica qui se usi un bridge tipo Sensibo, Broadlink o altro] that has been working perfectly for a long time.
Regression: The “heat” mode was previously available and fully functional via the SmartThings App and API until a few months ago. It hasn’t “never been there”; it has disappeared following a platform update or a driver migration.
The issue isn’t just “syntax.” While the API might technically “accept” the command, the SmartThings UI hides the “Heat” button because it’s missing from supportedAcModes. Furthermore, many third-party integrations (like Home Assistant) strictly follow the supportedAcModes list and will refuse to send a command that the device claims not to support.
The inconsistency is clear in my previous log: the device is currently in “heat” mode, yet the platform claims “heat” is not supported. This is a clear metadata mismatch in the device profile.
Could you please check why the supportedAcModes list was truncated for this specific device profile?
Hi, @dfandrew
Let me investigate further about this change. Cloud-Connected integrations are owned by the Partner, so any changes in the code can only be made by the developer who handles it on their side.
So, I just need to confirm that the logs show a change from their side, or if our Partners team has heard of it.
Do you remember a more approximate time on when you stopped seeing “Heat” as an option in the app? This is to shorten the log search
Can you open support access to your account so I can get information on your instance of this Linked service, please?
Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.