List of compatible categories/ocfDeviceType used by SmartThings Skill

In my tests, it seems SmartThings Skill uses ocfDeviceType field that is present at metadata block of device profiles to make devices visible/controllable by Alexa.

I would like to know whether my suspicious is confirmed or not.
If so, what is the acceptable values that we should use when creating profiles to make device compatible with Alexa?

This is what I have so far… but none relate anything with SmartThings Skill.

I haven’t used Alexa for a while, but a quick sample of various of my devices doesn’t reveal any that have ocfDeviceType in the profile, and it doesn’t seem to be used in the profiles for any stock Edge drivers.

So they have some kind of precedence.
What do you think they use to distinguish device types ?

In my case, I had the declaration below and wasn’t being recognized:

  deviceType: PresenceSensor
  deviceTypeId: PresenceSensor
  mnmn: SmartThingsCommunity

Then I changed to oic.d.switch and it showed as a switch.

I would have been looking to the categories of the main component first.

1 Like

Here is a sample of the OCF device types that I see in my Z-Wave, LAN, OCF, Matter, and VIPER devices:


1 Like

I want to revisit that statement to make it clear that I was talking specifically about the device profiles. Apart from some special cases like the device objects for device groups and ‘mobile as a thing’ devices, all of my device objects have an ocfDeviceType.

So I wouldn’t want to question the significance of ocfDeviceType to Alexa, only to note that it seems that it is ‘normally’ a derived value.


1 Like

Hi, @w35l3y
I checked with the internal team and they mentioned that custom integrations are not officially supported to be discovered by Alexa.
There are several check-ups to verify if a device is ok to be discovered to ensure that the integration will work as expected on both sides. The metadata like ocfDeviceType is only one of them.