Bug: Retrieve Custom Capabilities Files

[nayelyz (SmartThings Developer Support)]

@samuelspagl

Because there obviously still exists a way, as the SmartThings App is still retrieving the status of all of those values.

The communication of OCF devices works differently, in this post I included some details:

Get info from API

Welcome to the SmartThings Community, @Sdahl1234! This is the information we have so far by analyzing Jacob’s case. The team checked the profile assigned to the device (list of capabilities used), and they noticed the temperature and the other values are not available. They’re trying to investigate more about the root cause. More details To attempt to shed light on why some capabilities might show up in the ST app but not on the API side, the team shared these details: The phone client (ST app) uses OCF’s COAP protocol, which allows the physical device to define its resources (such as the temperature values). So, these values can be written there by the device and as a result, they can be displayed by the app. The APIs do not work via OCF, but, the profile is the manifest of what val…

Basically, the communication happens between the app and the device and this information is not required to go through the public API
So, that’s why the app can still see those values, I’ll ask the engineering team if there’s another option but I can’t make any promises.
Also, I’ll confirm if the attribute data won’t be used any more to request its removal from the capability.