search

WebThingsIO / schemas

A Web of Things schema repository
https://webthings.io/schemas/
5 stars 8 forks source link

Thermostat Capability - closes #13 #56

Closed benfrancis closed 5 years ago

benfrancis commented 5 years ago

@dhylands wrote:

So this seems to have some notion of heating/cooling, but only seems to have a single target temperature, rather than a separate heating target temperature and cooling target temperature.

Yeah I wasn't exactly sure how to deal with this. My thinking was that you could just have two TargetTemperatureProperty properties in one device.

{
  "properties": {
    "targetCoolingTemperature: {
      "@type": "TargetTemperatureProperty",
      "type": "number",
      "unit": "degree celsius",
      "title": "Target Cooling Temperature"
    },
    "targetHeatingTemperature: {
      "@type": "TargetTemperatureProperty",
      "type": "number",
      "unit": "degree celsius",
      "title": "Target Heating Temperature"
    }
  }
}

Do you think there should be a separate HeatingTargetTemperature and CoolingTargetTemperature property types?

The auto ThermostatModeProperty makes no sense with only a single target temperature.

Are you sure it's definitely not possible to have a thermostat with only a single target temperature, but which does both heating and cooling? I'm sure I've seen this before, and assumed that it just maintains the target temperature within a certain margin.

If this is the case then that would be both a HeatingTargetTemperature CoolingTargetTemperature. Would it be less confusing to just have one or more TargetTemperature properties?

mrstegeman commented 5 years ago

I think it makes the most sense to just have TargetTemperatureProperty, but maybe make a note that a device may include multiple of them to account for different heating/cooling targets.