A HomeKit Heater Cooler service.

The following configuration is available:

{
  "c":{"io":[[[3],2]],"t":3},
  "a":[{
    "t":25,
    "w":3,
    "p":"HPDRAGAAAGCKAE",
    "s":5,
    "g":14,
    "0":{"i":[{"c":"BcAbBaAbBaBbAbAdArAdCdBdAuHaDcDbDaU"}]},
    "1":{"i":[{"c":"BcAbBaAbBaBbAbAdApAbAbAgBdAuFaBaBaGbDaU"}]},
    "2":{"i":[{"c":"BcAbBaAbBaBbAbAdApAaAdCdBdAuFaAaDcDbDaU"}]},
    "3":{"i":[{"c":"BcAbBaAbBaBbAbAdApAbAdBdBdAuFaBaDbDbDaU"}]},
    "4":{"i":[{"c":"BcAbBaAbBaBbAbAdApAaAcBfBdAuFaAaCbFbDaU"}]},
    "5":{"a":0}
  }]
}

This is an example of a Mitsubishi HVAC IrDA Remote HeaterCooler and Humidity sensor ("t":25). The type ("w":3) is a heater & cooler. The HeaterCooler is controlled via a infra-red and the protocol is defined by "p":"HPDRAGAAAGCKAE". A sensor is connected to GPIO 14 ("g":14) and is is the default type 2 ("n":2 not required as the default). Control of the sensor is via actions 0 to 5 and their respective IR strings. The initial state has been set to "last state before restart" ("s":5).

Multiple actions are supported by a HeaterCooler. The Binary Outputs "r": [ ] for each should be configured to attain the desired state.

Sensor GPIO is defined by the "g" key contained within the service object.

Home Accessory Architect only supports one-wire temperature sensors. This is a mandatory option that specifies the GPIO the sensor is attached to e.g. "g": 14

Sensor type is defined by the "n" key contained within the service object.

A variety of one-wire sensors are available and supported by HAA.

Refer to Sensor Type for details of the sensors that are supported.

Sensor polling time is defined by the "j" key contained within the service object.

The HeaterCooler temperature is polled on a regular basis to read the latest values. These values are then posted to HomeKit. If this option is not specified then the sensor will be polled once every 30 seconds.

Temperature offset is defined by the "z" key contained within the service object.

The accuracy of the temperature sensor varies and may sometimes read consistently higher or lower than the actual temperature. The temperature offset option enables calibration of the sensor by specifying a positive or negative offset to apply to the reading.

The option uses is a floating point value, accurate to 1 decimal place e.g. 1.1

Humidity offset is defined by the "k" key contained within the service object.

NOTE: This option is available only for device type 25

The accuracy of the available one-wire sensors varies and may sometimes read consistently higher or lower than the actual humidity. The humidity offset option enables calibration of the sensor by specifying a positive or negative offset to apply to the reading.

The option uses is an integer point value.

HeaterCooler type is defined by the "w" key contained within the service object.

This option is used to select the type of HeaterCooler controlled by the device.

Minimum temperature is defined by the "m" key contained within the service object.

This option is used to set the minimum temperature in °C you can set. The value is a floating point variable accurate to 2 decimal places e.g. 10.04.

Maximum temperature is defined by the "x" key contained within the service object.

This option is used to set the maximum temperature in °C you can set. The value is a floating point variable accurate to 2 decimal places e.g. 10.04.

Target temperature step to use by HomeKit clients.

Deadband temperature is defined by the "d" key contained within the service object.

The "d" option is used to set the temperature deadband in °C to adjust how HeaterCooler works. The value is a floating point variable accurate to 2 decimal places e.g. 10.04.

A HeaterCooler deadband (or hysteresis) is designed to lag the inputs from the environment for the purposes of saving you energy and saving your air conditioner or furnace wear and tear from turning on and off frequently.

The deadband represents a temperature range around the automatic mode set point that is your “comfort zone”. For example, with a 4°C wide deadband ("d": 4.0) and a setpoint of 20°C, the deadband will be 18 - 22°C. This keeps the system from bouncing quickly between heating and cooling when in automatic mode.

When temperatures fall within the deadband, neither heating nor cooling can occur. A larger deadband will have your system run more economically, while a smaller deadband will have your system hold the temperature closer to the setpoint and increase comfort. The deadband does not affect your HeaterCooler's operation when in HEAT or COOL modes.

Example: If you have an 8ºC deadband and you set your desired temperature to 22ºC in AUTO mode, your heating set point will be 18º and your cooling set point will be 26ºC.

Deadband temperature force idle is defined by the "df" key contained within the service object.

Deadband temperature soft on is defined by the "ds" key contained within the service object.

Time to wait until HeaterCooler data in processed. It is used to avoid conflicts when many HomeKit orders are sent at same time.

This service can be part of a HAA iAirZoning service, working as a group in a different way.

The list of notifications "m" supported by this service are as follows:

See the general Service Notifications section for details of how to configure these notifications.

Binary Inputs "b" are supported by this service.

See Binary Inputs for details on how to define this mandatory option.

State inputs "f[n]" & Status Inputs "g[n]" are supported by this service. The supported list is:

NOTE: Fixed states "f5", "f6" & "f7" are only available when HeaterCooler type 3 is selected ("w": 3)

Refer to State Inputs for more detail and examples.

ICMP Ping inputs "p[n]" and "q[n]" are supported by this service. Refer to ICMP Ping Inputs for more detail.

Wildcard Actions "y[n]" are supported by this service. The supported list is:

Refer to Wildcard Actions for more detail.

The Initial Lock State about Service and Physical controls.

The Initial State key is supported by this service. Refer to Initial State for details of the available values.

Initial mode is defined by the "e" key contained within the service object.