XIAO_IR_MATE: The example yaml provided doesn't have a climate component or contain the text "platform: gree"

[jjcf89]

wiki-documents/sites/en/docs/Sensor/SeeedStudio_XIAO_Gadgets/XIAO_IR_MATE.md

Line 260 in 6c7cb4f

<summary>seeed-ir-v2.yaml</summary>

The example yaml provided doesn't have a climate component or contain the text "platform: gree".

I'm not sure how to modify the sample config to use the climate component

[github-actions]

👋 @jjcf89

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.

[Lukilyy]

Hi,

Thank you for bringing this to our attention, and we apologize for the confusion caused by the current documentation.

After reviewing the content, we'd like to clarify that the provided YAML example is intended for learning and retransmitting infrared signals, which is the core design of XIAO IR Mate. It does not rely on manufacturer-specific climate integrations such as platform: gree.

We understand that the current wording in the Wiki can make it seem like the example is based on an ESPHome climate component, which may lead to confusion when following the instructions.

We will review and improve the documentation to make the intended workflow and usage clearer.

Thank you again for your feedback and patience.

[jjcf89]

Thanks for looking at this.

the provided YAML example is intended for learning and retransmitting infrared signals

That is a pretty surprising conclusion. I hope what you're saying is this yaml was put in the wrong place and is not the correct yaml for the custom firmware example.

[pb66]

Hi, I've found myself in the same situation. I purchased 2 Xiao smart IR transcievers to controll a couple of non-smart AC units via home assistant after reading the "IR now a first class citizen" release note promoting the Xiao devices as capable of both IR learning AND advanced AC control.

Having gone down the same rabbit hole of the Seeed Studio Wiki documentation for this device not making any sense, I have tried to fathom out A) how to achieve my goal (control 2x AC units via HA & Xiao IR) and b) learn why I cannot make sense of documentation that others apparently followed succesfully before me.

What I have found is that on Feb 3rd Commit d8cb223 titled "fix the XIAO IR Mate yaml file" actually broke the wiki documentation in question!

For example this screenshot shows the climate section with the wiki referenced "platform: gree" etc being removed.

Armed with this new info I came to github issues to report the error and found this issue had been raised and had recieved a less than satisfactory reply, in particular

After reviewing the content, we'd like to clarify that the provided YAML example is intended for learning and retransmitting infrared signals, which is the core design of XIAO IR Mate. It does not rely on manufacturer-specific climate integrations such as platform: gree.

I find it incredibly difficult to believe that the example yaml given in the middle of the "Advanced Usage - Smart Air Conditioner Control" section of the wiki that states in the 2nd paragraph "In this chapter, we will use a Gree air conditioner as a detailed example" is a generic "learning and retransmitting" example yaml given that step 1 includes naming your device eg "xiao-ir-ac-controller", step 2 is to "Delete all default content in the editor" and "Completely copy and paste the code below into the editor:" (the code below being the example yaml) and step 3 directly below that yaml is where the confusion kick in as it refers to all the AC protocol and climate componants that are not there. It even highlights that "This is the most critical step!" and links to the ESPHome Climate Components page to assist with making this critical step, I would say "impossible step" given the wiki and the link are rendered useless by the irrelevent yaml example

We understand that the current wording in the Wiki can make it seem like the example is based on an ESPHome climate component, which may lead to confusion when following the instructions.

The current wording in the wiki does overwhelmingly depend upon the fact the example is based on an ESPHome climate component and can do nothing but cause confusion when following the instructions. It would be far better to have zero info than incorrect info posed as a working example. The changes made to the yaml in commit d8cb223 (whether intended or not) removed an example yaml that was tailored to the "Advanced Usage - Smart Air Conditioner Control" wiki section and replaced it with what you now refer to as a example of "the core design of XIAO IR Mate", that simply highlights the wrong example has been given in the wiki, not that it being misunderstood by the reader.

We will review and improve the documentation to make the intended workflow and usage clearer.

That would be good, I hope that means the example yaml will be updated to fit the wiki and NOT that the wiki section is simply removed.

This device is clearly capable and has been marketed as able to do this task, plus many other forum posts, esp docs, home assistant docs etc refer to this capability, the device sales page and the wiki directly so there is much to lose if this isn't corrected correctly.

I shall now try and rebuild an old example yaml from deleted code within the git history, hoping to get this working. But I only have so much time (and knowledge) to get this working or give in, maybe send the units back for a refund. Seeed Studio certainly should not be misleading customers by selling devices that are promoted as capable of doing something essentially undocumented or unsupported.

Personally I am a big fan of Seeed Studio and took to this project as I expected to follow a path already laid out and travelled by others, I do not currently have time to "play" with this and suspect, whilst there are many users that are more capable than I, there are also those that are not, and they will not be able to utilise these (potentially) great devices without the help of acurate documentation.

I suspect the currently displayed 'seeed-ir-v2.yaml' was maybe changed to make improvements elsewhere without knowing the resulting changes on this AC specific section of the live wiki page? Perhaps the original AC example had been hand edited without a change of filename and has now been accidently blanket replaced by the AUTO-SYNC START: xiao_smart_ir_mate/xiao_smart_ir_mate.yaml implementation?

In the meantime, if I manage to cobble together a working example, or any further info from git history I shall post it here.

Paul

[pb66]

So the original wiki entry commit is b76d8ce

From that original page I have lifted but not reviewed or tested the following example yaml, it was dated 18th july 2025.

I doubt it will work as is without some work, but it is possibly a better starting point than the live example or at least a good cross reference as this "fits" the current documentation.

substitutions:
  name: "seeed-ir"
  friendly_name: "Gree AC Controller" # You can customize a more friendly name
  version: "v1"

esphome:
  name: "${name}-${version}"
  friendly_name: "${friendly_name}"
  name_add_mac_suffix: True

esp32:
  board: esp32-c3-devkitm-1
  framework:
    type: arduino

globals:
  - id: is_wifi_connected
    type: bool
    initial_value: 'false'
  - id: reset_press_time
    type: uint32_t
    initial_value: '0'
  - id: touch_count
    type: int
    restore_value: no
    initial_value: '0'
  - id: touch_timer
    type: unsigned long
    restore_value: no
    initial_value: '0'

logger:
  level: INFO

api:

ota:
  platform: esphome
  password: "15afb09b5aba7b3d6a6ba01180c60df5"  # Change this to your desired password

wifi:
  # ssid: !secret wifi_ssid
  # password: !secret wifi_password
  on_connect:
    - globals.set: {id: is_wifi_connected, value: 'true'}
    - light.turn_on: rgb_light
  on_disconnect:
    - globals.set: {id: is_wifi_connected, value: 'false'}
  ap:
    password: "12345678"

captive_portal:

remote_transmitter:
  id: default_ir_transmitter
  pin: GPIO3
  carrier_duty_percent: 50%
  rmt_channel: 0

remote_receiver:
  id: default_ir_receiver
  pin:
    number: GPIO4
    inverted: true
  rmt_channel: 2
  dump: raw # Keep for learning or debugging other infrared codes

# Gree Climate Control
climate:
  - platform: gree
    name: "Gree Air Conditioner" # The name displayed in Home Assistant
    id: gree_ac    # Internal ID used by ESPHome, for touch button control
    # --- Required configuration for the gree platform ---
    model: "yan"   # [IMPORTANT] This is a required parameter. Gree has multiple infrared protocols.
                   # You may need to try the following values to find the one that suits your air conditioner:
                   # "generic", "yan", "yaa", "yac", "yac1fb9", "yx1ff", "yag"
                   # "yan" is a common starting point.
    # Optional configuration:
    # sensor: my_temperature_sensor_id # If you have an external temperature sensor
    supports_cool: true
    supports_heat: true # If your Gree AC does not support heating, set to false
    # Note: According to the documentation, the gree platform does not seem to support receiver_id to sync the state from the original remote

binary_sensor:
  - platform: gpio
    id: touch_pad
    pin:
      number: GPIO5
      mode: INPUT_PULLDOWN
    on_state:
      then:
        - if:
            condition:
              binary_sensor.is_on: touch_pad
            then:
              - script.execute: vibe_short
              - lambda: |-
                  unsigned long current_time = millis();
                  if (current_time - id(touch_timer) < 300) {
                    id(touch_count)++;
                  } else {
                    id(touch_count) = 1;
                  }
                  id(touch_timer) = current_time;
                  ESP_LOGD("touch_pad", "Touch detected. Current count: %d", id(touch_count));
                  if (id(check_touch_actions_script).is_running()) {
                    id(check_touch_actions_script).stop();
                  }
                  id(check_touch_actions_script).execute();

  - platform: gpio
    id: reset_button
    pin:
      number: GPIO9 # Strapping Pin!
      mode: INPUT_PULLUP
    filters:
      - invert
    on_press:
      then:
        - lambda: id(reset_press_time) = millis();
    on_release:
      then:
        - lambda: |-
            uint32_t press_duration = millis() - id(reset_press_time);
            if (press_duration < 5000) {
              id(vibe_short).execute();
              ESP_LOGI("reset_button", "Short press: Restarting device.");
              ESP.restart();
            } else {
              id(vibe_long).execute();
              ESP_LOGI("reset_button", "Long press: Activating factory reset.");
              id(factory_reset_switch).turn_on();
            }

output:
  - platform: gpio
    id: vibration_output
    pin: GPIO6

switch:
  - platform: output
    id: vibration_switch
    name: "Vibration Motor"
    output: vibration_output
  - platform: factory_reset
    id: factory_reset_switch
    name: "Factory Reset"

light:
  - platform: esp32_rmt_led_strip
    rgb_order: GRB
    pin: GPIO7
    num_leds: 1
    rmt_channel: 1
    chipset: ws2812
    name: "RGB Status Light"
    id: rgb_light
    default_transition_length: 0s
    on_turn_on:
      - light.control:
          id: rgb_light
          red: 1.0
          green: 1.0
          blue: 1.0
          brightness: 0.7
    effects:
      - addressable_scan:
      - addressable_rainbow:

script:
  - id: vibe_short
    then:
      - switch.turn_on: vibration_switch
      - delay: 100ms
      - switch.turn_off: vibration_switch
  - id: vibe_long
    then:
      - switch.turn_on: vibration_switch
      - delay: 500ms
      - switch.turn_off: vibration_switch

  - id: check_touch_actions_script
    mode: restart
    then:
      - delay: 350ms
      - if: # Single-click action
          condition:
            lambda: 'return id(touch_count) == 1;'
          then:
            - logger.log: "Single Click: Toggling Gree AC Power"
            - lambda: |-
                // [IMPORTANT] Ensure the climate ID used below is gree_ac
                if (id(gree_ac).mode == climate::CLIMATE_MODE_OFF) {
                  ESP_LOGD("touch_action", "Gree AC is OFF, attempting to turn to COOL mode.");
                  auto call = id(gree_ac).make_call();
                  call.set_mode(climate::CLIMATE_MODE_COOL);
                  call.set_target_temperature(25);
                  call.perform();
                } else {
                  ESP_LOGD("touch_action", "Gree AC is ON, attempting to turn OFF.");
                  auto call = id(gree_ac).make_call();
                  call.set_mode(climate::CLIMATE_MODE_OFF);
                  call.perform();
                }
          else: # If not a single click, then check for a double click
            - if:
                condition:
                  lambda: 'return id(touch_count) == 2;'
                then: # Double-click action
                  - logger.log: "Double Click: Gree AC Temperature Up"
                  - lambda: |-
                      // [IMPORTANT] Ensure the climate ID used below is gree_ac
                      if (id(gree_ac).mode != climate::CLIMATE_MODE_OFF) {
                        float current_temp = id(gree_ac).target_temperature;
                        float max_temp = id(gree_ac).get_traits().get_visual_max_temperature();
                        if (current_temp < max_temp) {
                           ESP_LOGD("touch_action", "Increasing Gree AC temp from %.1f to %.1f", current_temp, current_temp + 1.0f);
                           auto call = id(gree_ac).make_call();
                           call.set_target_temperature(current_temp + 1.0f);
                           call.perform();
                        } else {
                          ESP_LOGD("touch_action", "Gree AC already at max temp: %.1f", max_temp);
                        }
                      }
                else: # If not a double click, then check for a triple click
                  - if:
                      condition:
                        lambda: 'return id(touch_count) == 3;'
                      then: # Triple-click action
                        - logger.log: "Triple Click: Gree AC Temperature Down"
                        - lambda: |-
                            // [IMPORTANT] Ensure the climate ID used below is gree_ac
                            if (id(gree_ac).mode != climate::CLIMATE_MODE_OFF) {
                              float current_temp = id(gree_ac).target_temperature;
                              float min_temp = id(gree_ac).get_traits().get_visual_min_temperature();
                              if (current_temp > min_temp) {
                                 ESP_LOGD("touch_action", "Decreasing Gree AC temp from %.1f to %.1f", current_temp, current_temp - 1.0f);
                                 auto call = id(gree_ac).make_call();
                                 call.set_target_temperature(current_temp - 1.0f);
                                 call.perform();
                              } else {
                                ESP_LOGD("touch_action", "Gree AC already at min temp: %.1f", min_temp);
                              }
                            }
                      else: # Other click counts
                        - logger.log:
                            level: WARN
                            format: "Touch Action: No specific action defined for %d clicks."
                            args: ['id(touch_count)']
      # Reset the touch count
      - lambda: 'id(touch_count) = 0; ESP_LOGD("check_touch_actions", "Touch count reset to 0.");'

interval:
  - id: blink_rgb_interval
    interval: 500ms
    then:
      - if:
          condition:
            lambda: 'return !id(is_wifi_connected);'
          then:
            - lambda: |-
                static bool intervalos_led_state = false;
                intervalos_led_state = !intervalos_led_state;
                auto call = id(rgb_light).turn_on();
                if (intervalos_led_state) {
                  call.set_rgb(0, 0, 1);
                  call.set_brightness(0.5);
                } else {
                  call.set_rgb(0, 0, 0); // Off
                }
                call.perform();

[pb66]

Also see #4122

Same issue, similar unhelpful replies.

You nay well have updated the default "factory" example yaml, but it is not a "drop-in" replacement for the AC specific example it has replaced on the live wiki. It should never have been included in the PR and should be restored until someone finds a solution that either offers a yaml that includes the AC parts or the documentation changed to work from a generic "factory" yaml.

[jjcf89]

Thanks @pb66, i couldn't have said it better myself

[grilliiiiii]

Also see #4122

Same issue, similar unhelpful replies.

You nay well have updated the default "factory" example yaml, but it is not a "drop-in" replacement for the AC specific example it has replaced on the live wiki. It should never have been included in the PR and should be restored until someone finds a solution that either offers a yaml that includes the AC parts or the documentation changed to work from a generic "factory" yaml.

Thank you very much for your feedback. We have forwarded your message to our engineering team. They will review it as soon as possible and assess the feasibility of the wiki information. We will contact you here as soon as there are any updates.

[pb66]

Quick update!

I noticed in passing that the wiki has been reverted to previous yaml example 'seeed-ir-v1.yaml' on 2nd of July. Thank you @limengdu 👍

The guide should now make sense at least, however I have not yet tried it and have since learnt the factory default yaml was updated in-line with on going changes to the device firmware (and esphome?) so there maybe issues running old yaml with new firmware, but hopefully not. If/when I can test I will post here.

[RuedigerMueller]

I used the YAML from the wiki and faced one issue: the light and remote_transmitter were interfering. Light was working but the remote_transmitter showed an error when starting the device. I was not able to get to work both of them so I removed the light. I also removed the script that allows you to control the AC via the touch pad oft e XIAO_IR_MATE as I did not like that feature (but I can confirm it is working).

If anyone has an idea to get the light to work: please share.

I am not yet convinced that the remote_receiver is working as it should. This requires some more testing.

Here is my YAML (adjusted for a Toshiba AC).

substitutions:
  name: "seeed-ir"
  friendly_name: "Toshiba AC Controller" # You can customize a more friendly name
  version: "v1"

esphome:
  name: "${name}-${version}"
  friendly_name: "${friendly_name}"
  name_add_mac_suffix: True

esp32:
  board: esp32-c3-devkitm-1
  framework:
    type: arduino

globals:
  - id: is_wifi_connected
    type: bool
    initial_value: 'false'
  - id: reset_press_time
    type: uint32_t
    initial_value: '0'
  - id: touch_count
    type: int
    restore_value: no
    initial_value: '0'
  - id: touch_timer
    type: unsigned long
    restore_value: no
    initial_value: '0'

logger:
  level: INFO

api:

ota:
  platform: esphome
  password: "15afb09b5aba7b3d6a6ba01180c60df5"  # Change this to your desired password

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  on_connect:
    - globals.set: {id: is_wifi_connected, value: 'true'}
  on_disconnect:
    - globals.set: {id: is_wifi_connected, value: 'false'}
  ap:
    password: "12345678"

captive_portal:

remote_transmitter:
  id: default_ir_transmitter
  pin:
    number: GPIO3
  carrier_duty_percent: 50
  rmt_symbols: 48

remote_receiver:
  id: default_ir_receiver
  pin:
    number: GPIO4
    inverted: true
  dump: raw # Keep for learning or debugging other infrared codes

# Toshiba Climate Control
climate:
  - platform: toshiba
    name: "Toshiba AC" # The name displayed in Home Assistant
    id: toshiba_ac    # Internal ID used by ESPHome, for touch button control
    model: "GENERIC"  
    # Optional configuration:
    supports_cool: true
    supports_heat: true # If your Toshiba AC does not support heating, set to false
    icon: "mdi:air-conditioner"
    receiver_id: default_ir_receiver
    transmitter_id: default_ir_transmitter

binary_sensor:
  - platform: gpio
    id: reset_button
    pin:
      number: GPIO9 # Strapping Pin!
      mode: INPUT_PULLUP
    filters:
      - invert
    on_press:
      then:
        - lambda: id(reset_press_time) = millis();
    on_release:
      then:
        - lambda: |-
            uint32_t press_duration = millis() - id(reset_press_time);
            if (press_duration < 5000) {
              id(vibe_short).execute();
              ESP_LOGI("reset_button", "Short press: Restarting device.");
              ESP.restart();
            } else {
              id(vibe_long).execute();
              ESP_LOGI("reset_button", "Long press: Activating factory reset.");
              id(factory_reset_switch).turn_on();
            }

output:
  - platform: gpio
    id: vibration_output
    pin: GPIO6

switch:
  - platform: output
    id: vibration_switch
    name: "Vibration Motor"
    output: vibration_output
  - platform: factory_reset
    id: factory_reset_switch
    name: "Factory Reset"
    
script:
  - id: vibe_short
    then:
      - switch.turn_on: vibration_switch
      - delay: 100ms
      - switch.turn_off: vibration_switch
  - id: vibe_long
    then:
      - switch.turn_on: vibration_switch
      - delay: 500ms
      - switch.turn_off: vibration_switch