New Device Metadata for OCF Standard

At SmartThings, we continue to review emerging open standards in the IoT space. The Open Connectivity Framework (OCF) defines an open standard for IoT resource types, similar to the SmartThings Capabilities model. This specification is referred to as the Open Interconnect Consortium (OIC) Resource Type specification, and is available for download on the OCF Specifications page.

As a first step towards supporting OIC Resource Types, we will be adding metadata to several of our Device Handlers. You will see these changes being made in the coming days in our public repository of SmartApps and Device Handlers.

This metadata specifies the OIC Resource Type of the device, and will look something like this:

metadata {
  definition(name: 'device-name', namespace: 'my-namespace', 
             author: 'smartthings', ocfDeviceType: 'oic.r.button')

This allows the device to explicitly declare its OCF Resource Type. This is a first step towards supporting this new standard; we will continue to add support in an iterative way.

This change has no behavioral impact on your SmartThings-connected devices or automations, nor on any custom Device Handlers. It is, however, an important first step towards supporting an exciting new open IoT standard.


Should I update my custom Device Handlers with this new ocfDeviceType metadata?

No. At this point there is no behavioral impact of this field. The ocfDeviceType metadata is only used for specific devices that are targeting initial OCF support, and only in cases where we cannot correctly determine the best OIC Resource Type to use from the device’s defined capabilities.

Will this impact any of my SmartThings-connected devices or automations?

No. There will be no behavioral impact on any SmartThings-connected device or automation.

When will SmartThings fully support the OCF standard?

There is no specific date targeted for full OCF support, but we are taking initial steps towards supporting it.

Where can I learn more about OCF? is the best resource to learn more about OCF. There you will find the various specifications, developer resources, and latest news.


Love this step toward OCF. Huge applause.

This might be premature, but are you only considering OCF from a consumption/client point of view? Ie, only consume OCF devices? Or are you also considering exposing SmartThing’s own devices as OCF via the hub - in essence acting as an OCF Bridge for other clients to build on?

We are not at this time exposing OCF from the hub in the way you are talking about. The SamsungConnect app does interact with ST devices via ocf, but they are not exposed over hub.


@Jim or @beckje01 it looks like the SmartThings (Samsung Connect) app uses the ocfDeviceType metadata to determine the icon used for a device in the list view. Is there an ocf type for fan that works with STSC? I tried with no success. oic.d.swtch does work and displays the switch icon.


@Jim Any official answers on this or how to update third party DTH’s without having to go through github and guess?

1 Like

You can certainly go to the OCF page and use their IDs. So far I got good results doing so.

Tried that for a garage door opener and couldn’t get it to work. Well should say works fine in classic, doesn’t in “new” app. I’ll keep playing with it but it would be nice to have something official.

Have you checked the DTH code of Z-Wave Garage Door Opener?
This the one used by my Iris opener and it works fine in the new app.

I did and it doesn’t have a ofc or vid code in it so back to my original statement “without having to go through github and guess?”

There’s is no official documentation yet on getting custom handlers to work in the new app

I have been editing my DTHs to make my devices appear and be operational in the new app (and my 2018 TV).
These are the OCF device types that work and have an icon appear in the device:


@Jim - DTHs with child devices do not seem to work in the new app. Does it have anything to do with the new Device Metadata for OCF not being present and/or correct? In this particular instance I have several multi outlet devices that do not work - just the parent works, the others say “Can’t connect”.

I’m not sure about the status or roadmap for DTH’s with child devices in OneApp. I wish I could give some more info, but your best bet is to get in touch with Developer Support.