What are the device object interfaces?

[PeterV959 11]

I want to understand what the "interfaces" field in a QA device object is used for. I pasted a screenshot (Figure 1) of the field and its values below. This is the new 5.170.xx version of the hub software. There are more actions available for the auto thermostat device but I don't see that they are used. I have a simple, do-nothing QA that reacts to the UI  The only methods that are called are the setHeatingThermostatSetpoint, setCoolingThermostatSetpoint, and the setThermostatMode. But as you can see (Figure 2), there are quite a few more actions than those. I was hoping maybe there was some way to indicate the QA support for each given interface.

 

Any ideas?

 

Thanks,

 

Peter

 

Please login or register to see this image.

/monthly_2024_12/image.png.d76e83aa7f17a76ce5946507abc2c184.png" />

Figure 1

 

Figure 2

[jgab 2,647]

They signal to the system (HC3) that the device has certain functionality and is then used by the system to annotate the device with that new functionality.
It can be UI elements like the power icon, and/or adding new fields to the device structure (object).
 

@tinman created an explanation and list of interfaces that may be a bit outdated now but the principle remain...

 

Edited December 6, 2024 by jgab

[jgab 2,647]

So, if you have the 'coolingThermostatSetpoint' interface your device object will get som extra properties like 

.coolingThermostatSetpointCapabilitiesMin

.coolingThermostatSetpointCapabilitiesMax

.coolingThermostatSetpoint

.coolingThermostatSetpointFuture

.coolingThermostatSetpointStep

and you will get the action

setCoolingThermostatSetpoint:6

 

So if you take binarySwitch QA and self:addInterfaces({"coolingThermostatSetpoint"})

it will get the properties and the actions.

It also signals to the system that this device can now do setCoolingThermostatSetpoint and could be used 

by scenes etc. to show that option in the UI. I'm not sure this interface alone is enough to make the system treat the QA
as a thermostat - probably needs more interfaces..
It's more useful for a thermostat QA to pick what capabilities it support I guess - heating or auto etc...

Edited December 6, 2024 by jgab