[ST Edge] Google/Alexa integration criteria

Do the ST to Google/Alexa interfaces key off specific ST metadata or are they hardcoded based on default capabilities? For example, could you clone ‘switch’ or ‘switchLevel’ as a custom capability and have them picked up by Google/Alexa?

Custom capabilities are not supported in the integration with Google/Alexa because they need to be mapped to be understandable on their side.
As custom capabilities can have different formats, it’s complex to adapt them.

Note: There may be custom capabilities that exist on the ST platform that may have been already mapped, but newly-created capabilities won’t appear

1 Like