Custom capabilities for a driver

[erickv (Erick)]

Hey, @alex.49.98 I’d like to clear up a few points there:

@alex.49.98

6. In the custom-capability sample there is capabilities folder with 2 yaml files, one describing the custom capability and another describing its presentation. It looks like I don’t need that at all. They are not used anywhere, they are not packaged. I wonder why they are in the example at all. Initially I thought that they are somehow processed by smartthings CLI and used as a metadata for the edge driver but eventually it doesn’t look like that.
7. Surprisingly the file from the presentation folder of the custom-capability example, device-config as I understand is not packaged as well. What was the point of creating it if it is not packaged? I don’t understand how and where it is used if it is used.

Unless you use a borrowed namespace that you know it supports the custom capability, yeah, these files won’t be necessary for you, but they’re in there so you can build your own version of the custom capability and make it compatible with the platform (API and SmartThings App).

Also, if you follow the hyperlink that is provided at the README.md file, you’ll notice that it’ll take you to a tutorial on how to set up your custom capability, its presentation and, why a device configuration is needed.

Quoting instructions from SmartThingsDevelopers/SampleDrivers//custom-capability:

This shows an example using a custom capability from within a driver. To get this working you can follow the information found in the community post and linked docs here.

---

@alex.49.98

8. And the last thing. Presentation is not used anywhere in the driver, right? It is needed only for the SmartThings UI to know how to present the capability, so technically, I don’t need any presentation JSONs or YAMLs on the driver side, right?

That’s right, that’s part of the platform setup process.