SmartIR Devices Codes Files syntax

Disclaimer

I do not provide any support for you to record your own device codes. Please do not create any issues to ask how to do it as it will immediately closed.
You can ask for help at SmartIR Climate (Home Assistant Community).
If you think something is missing or wrong in the docs and you would like to submit PR with docs amendments you are welcome.

Device code JSON file

If you decide to modify or create your own device file you need to do it in the custom_code/[climate|fan|media_player|/ directory. Any changes inside codes directory will be lost upon SmartIR HACS update!

If you need to modify existing file from the code directory please copy it into custom_codes first.
If you need to create new device file please choose free for digit file name (not used by existing json file int the codes/your_class directory) and create json file with given name in the custom_codes/your_class

Each different class (Climate, Fan, Media Player) device file has common part and then class specific part. Please take look to some existing files as examples. It is very easy to make error in JSON file structure when editing. Use any available JSON format checker to validate it after editing - for example JSON Lint

Common declaration part

{
    "manufacturer": "Toyotomi",
    "supportedModels": [
        "AKIRA GAN/GAG-A128 VL"
    ],
    "supportedController": "Broadlink",
    "commandsEncoding": "Base64",

json attribute	mandatory	type	description
`manufacturer`	`yes`	`string`	Manufacturer name of the device you intend to control
`supportedModels`	`yes`	`array of strings`	List of devices names supported by this file
`supportedController`	`yes`	`string`	Controller type used. Can be one of the `Broadlink`, `Xiaomi`, `MQTT`, `LOOKin`, `ESPHome`, `ZHA`, `UFOR11`
`commandsEncoding`	`yes`	`string`	Each controller type supports given type/s of the IR command encodings. For actual supported encodings for your controller refer to the `controller_const.py`

Climate specific

Climate declaration part

    "temperatureUnit": "C",
    "minTemperature": 16,
    "maxTemperature": 30,
    "precision": 1,
    "operationModes": [
        "auto"
        "heat",
        "cool",
        "heat_cool",
        "fan_only",
        "dry"
    ],
    "presetModes": [
        "none",
        "eco",
        "hi_power"
    ],
    "fanModes": [
        "low",
        "mid",
        "high",
        "auto"
    ],
    "swingModes": [
        "off",
        "",
        "high",
        "auto"
    ],

json attribute	mandatory	type	description
`temperatureUnit`	`yes`	`string`	Temperature unit used by you device (this can be different to the HA default temperature unit). Can be one of rhe `C`, `F`, `K`
`minTemperature`	`yes`	`int, float`	Minimum device supported temperature. Can be float or integer depending on the `precision`
`maxTemperature`	`yes`	`int, float`	Maximum device supported temperature. Can be float or integer depending on the `precision`
`precision`	`yes`	`int, float`	This is size of the temperature steps you can set in the target temperature (if you set you temperature in 1 degree steps it will be `1`, if in half degrees it will be `0.5`, etc). Supported precisions are `2`, `1`, `0.5`, `0.1`
`operationModes`	`yes`	`array of strings`	List of the modes your device can operate in. This has to be subset of the HA climate HVAC modes. No customs modes are possible! Do not list `off` mode here it is included by default.
`presetModes`	`no`	`array of strings`	List of the preset modes your device can operate in. Does you device support dirent ways to operate under any given operationMode? For example can your AC units can do `eco` and `hi-power` cooling? Than those shall be listed here. The preset modes names could be freely defined to match naming used by your device.
`fanModes`	`no`	`array of strings`	List of the fan modes your device can operate in. Does you device support fan modes? High, low, auto, etc.? Than those shall be listed here. The fan modes names could be freely defined to match naming used by your device.
`swingModes`	`no`	`array of strings`	List of the fan swing modes your device can operate in. Does you device support different ways how your fan grills move? Than those shall be listed here. The swing modes names could be freely defined to match naming used by your device.

Climate commands

Now when all modes supported by your device (operation, presets, fan, swing) are declared, you need to records IR command for their combination for any target temperature. There may be some tools to help you to help with such process.

Climate `off` commands

Most of the controler devices have single off command, which is used to switch device off. In some more rare cases, there is different command for each operational mode device is currently working in. So for cool operational mode there could be off_cool command, for heat operational mode off_heat, etc. You need to have either off command or off_MODE command for all you operational codes declared.

    "commands": {
        "off": "JgCSAAABKHQKDGgDTFS.............",

or

    "commands": {
        "off_cool": "JgCSAAABKHQKDGgDEht.............",
        "off_heat": "JgCSAAABKHQKDGgDFth.............",
        "off_dry": "JgCSAAABKHQKDGgDFht.............",
        ...

Climate `on` commands

In some cases, controled device have dedicated on command (Otherwise device is switched on by the operation command and dedicated IR code to switch it on is not required). In case your on and off command are same, SmartIR not send on or off command again, if the device is assumed to be already in desired state. As without power sensor devices state is only assumed it is higly suggested to use in this case power sensor feature.

    "commands": {
        "on": "JgCSAAABKHQKDGgHtSq.............",

Climate operation commands

These are command to set controlled device into desired work state. Due to the nature how HVAC units works, all the modes and temperature are contained in single IR command. Therefore you need to records and declare IR commands for the all combinations of the modes and temperatures. The complete structure would look like:

operation mode -> preset mode -> fan mode -> swing mode -> temperature -> recorded IR command

    "commands": {
        "cool": {
            "eco": {
                "low": {
                    "swing": {
                        "16": "JgCSAAABKZIXEBcRFz.............",
                        "17": "JgCSAAABKHQKDGgDHz.............",
                        ...
                    },

If your device doesn't support some of the modes types at all (and you did not declare them in the declaration part - for example presetModes are not supported) then simply skip given level (operation mode -> fan mode -> swing mode -> temperature -> recorded IR command). Only operation mode level is required, all lower levels are optional.

    "commands": {
        "cool": {
            "low": {
                "swing": {
                    "16": "JgCSAAABKZIXEBcRFz.............",
                    "17": "JgCSAAABKHQKDGgDHz.............",
                    ...
                },

If you device doesn't support some mode under given higher level mode (for example temperatures are not supported under fan_only operation mode, or presetModes are not supported under dry operation mode), you have three possibilities how to address this:
1. Use - as 'catch all' mode name/temperature. Using this approach has additional behavior - if you change mode/temperature which to the value covered by - the value will not change in the HA. Example: temperatures are not supported under fan_only operation mode - when you will try to change temperature using - key the temperature in HA stays same:
```
"commands": {
    "fan_only": {
        "-": {
            "low": {
                "swing": {
                    "-": "JgCSAAABKZIXEBcRFz............."
                },
```
1. Define some default mode (i.e. something like none or default but any name will do) as first in the declaration section and use it as default failover mode. Example: if you are running for example in the operation mode cool with preset mode eco and you change operation mode to dry which doesn't support presets, then it will try to select first available preset in the order presets are declared in the presetModes - and it will therefore choose your first one - none:
```
"commands": {
    "cool": {
        "eco": {
            "low": {
                "swing": {
                    "16": "JgCSAAABKZIXEBcRFz............."
                },
        ...
    "dry": {
        "none": {
            "low": {
                "swing": {
                    "16": "JgCSAAABKZIXEBcRFz............."
                },
```
1. Duplicate same IR command to all keys. This approach is not suggested and multiple occurence of the same IR command will be logged by the validator to the HA log. Example: temperature setting is not supported in the fan_only mode and all commands are same:
```
"commands": {
    "fan_only": {
        "normal": {
            "low": {
                "swing": {
                    "16": "JgCSAAABKZIXEBcRFz.............",
                    "17": "JgCSAAABKZIXEBcRFz.............",
                    "18": "JgCSAAABKZIXEBcRFz.............",
                    ...
                },
```

Fan Speficic

TBD

Media Player specific

TBD

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

CODES_SYNTAX.md

CODES_SYNTAX.md

SmartIR Devices Codes Files syntax

Disclaimer

Device code JSON file

Common declaration part

Climate specific

Climate declaration part

Climate commands

Climate `off` commands

Climate `on` commands

Climate operation commands

Fan Speficic

Media Player specific

Files

CODES_SYNTAX.md

Latest commit

History

CODES_SYNTAX.md

File metadata and controls

SmartIR Devices Codes Files syntax

Disclaimer

Device code JSON file

Common declaration part

Climate specific

Climate declaration part

Climate commands

Climate off commands

Climate on commands

Climate operation commands

Fan Speficic

Media Player specific

Climate `off` commands

Climate `on` commands