Generic Controllers can be implemented using only device side code with discovery & capabilities.
Is this also true for ThermostatControllers & other API Controllers or will I need to create a Lambda function/skill to handle these?
Generic Controllers can be implemented using only device side code with discovery & capabilities.
Is this also true for ThermostatControllers & other API Controllers or will I need to create a Lambda function/skill to handle these?
The Generic Controller interfaces are generally for AVS, though smart home skills also use the same ModeController, ToggleController and RangeController interfaces as well.
Regardless of which controller/interface you implement into your device, you either create a smart home skill and publish that to the skill store (which inherently means you create a Lambda function as part of that), or you could play around with AVS and add smart home controls that way (see this video for more).
You may want to check out this Smart Home API forum page for more guides as well to understand how the backend works.
1 Person is following this question.