Skip to content
Get started

Remote Receiver

The remote_receiver component lets you receive and decode various common remote control signals, such as infrared or 433 MHz radio frequency (RF) signals.

The component is split into two parts:

  • The remote receiver “hub”, which defines the pin and a few additional settings, and…
  • Individual remote receiver binary sensors which will activate when their respective signal is received.

See Setting up IR Devices and Setting up RF Devices for details.

# Example configuration entry
remote_receiver:
pin: GPIOXX
dump: all

Multiple remote receivers can be configured as a list of dict definitions within remote_receiver.

  • pin (Required, Pin): The pin to receive the remote signal on.

  • dump (Optional, list): Decode and dump these remote codes in the logs (at log.level=DEBUG). Set to all to dump all available codecs:

    • abbwelcome: Decode and dump ABB-Welcome codes. Messages are sent via copper wires. See transmitter description for more details.

    • aeha: Decode and dump AEHA infrared codes.

    • aok: Decode and dump A-OK RF codes.

    • beo4: Decode and dump B&O Beo4 infrared codes.

    • brennenstuhl: Decode and dump brennenstuhl RF codes.

    • byronsx: Decode and dump Byron SX doorbell RF codes.

    • canalsat: Decode and dump CanalSat infrared codes.

    • canalsatld: Decode and dump CanalSatLD infrared codes.

    • coolix: Decode and dump Coolix infrared codes.

    • dish: Decode and dump Dish infrared codes.

    • dooya: Decode and dump Dooya RF codes.

    • drayton: Decode and dump Drayton Digistat RF codes.

    • dyson: Decode and dump Dyson Cool AM7 tower fan codes.

    • hob2hood: Decode and dump AEG Hob2Hood infrared codes.

    • jvc: Decode and dump JVC infrared codes.

    • gobox: Decode and dump Go-Box infrared codes.

    • keeloq: Decode and dump KeeLoq RF codes.

    • haier: Decode and dump Haier infrared codes.

    • ira211: Decode and dump Siemens IRA211 infrared codes.

    • lg: Decode and dump LG infrared codes.

    • magiquest: Decode and dump MagiQuest wand infrared codes.

    • midea: Decode and dump Midea infrared codes.

    • nec: Decode and dump NEC infrared codes.

    • nexa: Decode and dump Nexa (RF) codes.

    • nexus: Decode and dump Nexus temperature and humidity sensor (RF) codes.

    • onkyori: Decode and dump Onkyo RI codes. See transmitter description for wiring and voltage-level details.

    • panasonic: Decode and dump Panasonic infrared codes. Both 48-bit and 56-bit codes are decoded. A 56-bit remote that an earlier release showed as a 48-bit code needs a fresh dump.

    • pd_pioneer: Decode and dump PD Pioneer mini-split infrared codes.

    • pioneer: Decode and dump Pioneer infrared codes.

    • pronto: Print remote code in Pronto form. Useful for using arbitrary protocols.

    • raw: Print all remote codes in their raw form. Also useful for using arbitrary protocols.

    • rc5: Decode and dump RC5 IR codes.

    • rc5x: Decode and dump RC5X (Marantz Extended RC5) infrared codes.

    • rc6: Decode and dump RC6 IR codes.

    • rc_switch: Decode and dump RCSwitch RF codes.

    • roomba: Decode and dump Roomba infrared codes.

    • samsung: Decode and dump Samsung infrared codes.

    • samsung36: Decode and dump Samsung36 infrared codes.

    • symphony: Decode and dump Symphony infrared codes.

    • sony: Decode and dump Sony infrared codes.

    • toshiba_ac: Decode and dump Toshiba AC infrared codes.

    • mirage: Decode and dump Mirage infrared codes.

    • toto: Decode and dump Toto infrared codes.

  • tolerance (Optional, int, Time or mapping): The percentage or time that the remote signal lengths can deviate in the decoding process. Defaults to 25%.

    • type (Required, enum): Set the type of the tolerance. Can be percentage or time.
    • value (Required, int or Time): The percentage or time value. Allowed values are in range 0 to 100% or 0 to 4294967295us.
  • buffer_size (Optional, int): The size in bytes of the internal buffer for storing the remote codes. On ESP32 variants with RMT one receive slot is receive_symbols x 4 + 16 bytes (784 bytes at the default 192 symbols); the default is four slots, 3136 bytes, and an explicit value below two slots is raised to two. On other platforms each buffered pulse takes 4 bytes; the default is 4000B, which holds 1000 pulses.

    WARNING

    Before 2026.10.0 the value was applied as a number of pulses on ESP8266, RP2040, LibreTiny, ESP32-C2 and ESP32-C61, four times the bytes requested. Multiply an explicit buffer_size on those platforms by 4 to keep the same capacity. On ESP32 variants with RMT the default was 10kB; an explicit buffer_size: 10kb copied from that can be removed, since the default now follows receive_symbols.

  • filter (Optional, Time): Filter any pulses that are shorter than this. Useful for removing glitches from noisy signals. Allowed values are in range 0 to 4294967295us. Defaults to 50us.

  • idle (Optional, Time): The amount of time that a signal should remain stable/unchanged for it to be considered complete. Defaults to 10ms. The maximum allowable value is:

    • 65536us on the ESP32 and ESP32-S2 variants
    • 32767us on other ESP32 variants with RMT hardware
    • 4294967295us on all other platforms (including ESP32-C2 and ESP32-C61 which use a software implementation)

    Note: The ESP32 RMT values listed above assume the default clock_resolution. If a different clock_resolution is used, the values are scaled by 1000000 / clock_resolution.

  • id (Optional, ID): Manually specify the ID used for code generation. Useful when multiple receivers are configured on a single device.

NOTE

The following options apply only to ESP32 variants with RMT hardware. They are not available on the ESP32-C2 and ESP32-C61, which use a software implementation.

  • rmt_symbols (Optional, int): When use_dma is enabled, this sets the size of the driver’s internal DMA buffer. When DMA is disabled, it specifies how much RMT memory is allocated to the component. RMT memory is shared across all components and should be allocated in multiples of the block size. On the ESP32 and ESP32-S2 variants, RMT memory is shared between RX and TX components. On other variants, RX and TX have their own RMT memory, but a TX component can also use RX memory that no RX component uses.
ESP32 VariantAvailable MemoryBlock Size
ESP32512 symbols64 symbols
ESP32-C396 symbols48 symbols
ESP32-C596 symbols48 symbols
ESP32-C696 symbols48 symbols
ESP32-H296 symbols48 symbols
ESP32-H2196 symbols48 symbols
ESP32-H496 symbols48 symbols
ESP32-P4192 symbols48 symbols
ESP32-S2256 symbols64 symbols
ESP32-S3192 symbols48 symbols
ESP32-S31192 symbols48 symbols

Each component uses its own RMT channel: remote_receiver uses an RX channel, remote_transmitter and esp32_rmt_led_strip use a TX channel. A channel uses at least one block of memory, so the number of channels is the available memory divided by the block size, for example 8 on the ESP32 and 2 on the ESP32-C3. On the ESP32 and ESP32-S2, RX and TX components share these channels. On other variants, RX and TX each have this many channels.

ESPHome checks all esp32_rmt_led_strip, remote_transmitter and remote_receiver components together. Validation fails if:

  • they need more channels than are available
  • more than one RX or more than one TX component sets use_dma, since only one channel per direction supports DMA
  • rmt_symbols is an odd number or smaller than one block
  • without use_dma, rmt_symbols is larger than one channel can use. On the ESP32 and ESP32-S2 that is all the RMT memory; on other variants it is the RX memory for an RX component, or the TX and RX memory together for a TX component

A component with use_dma uses one block. When it compiles, ESPHome also works out which memory each channel gets when the components are set up: by setup_priority, then in the order of the configuration. A component that refers to another component by ID, such as a power_supply, can be set up after the ones that follow it. If a channel does not fit, ESPHome logs a warning that suggests an rmt_symbols value that fits, or a setup_priority that sets up the smaller ones first. esphome config does not show this warning. The order matters because a TX channel can extend into memory that the next one would need: on an ESP32-S3, a 48 symbol strip followed by a 288 symbol strip fits, but not the other way round.

  • receive_symbols (Optional, int): Maximum receive length in symbols. On some variants the maximum receive is limited to rmt_symbols. Defaults to 192 on every variant; the receive slot size follows this value, while the longest frame that can be received is limited by rmt_symbols where that is lower.

  • filter_symbols (Optional, int): Filter out any data received with a length in symbols less than filter_symbols. Useful for filtering out short bursts of noise.

  • clock_resolution (Optional, int): The clock resolution used by the RMT peripheral in Hz. Defaults to 1000000.

  • use_dma (Optional, boolean): Enable DMA on variants that support it. If enabled rmt_symbols controls the DMA buffer size and can be set to a large value.

In rare hardware configurations where the microcontroller will receive modulated signals, the RMT peripheral supports signal demodulation. If you aren’t sure, you probably don’t need this. Infrared remote signals, for example, are typically demodulated by an infrared receiver module (IRM) before reaching the microcontroller.

To enable signal demodulation, configure the signal carrier frequency and duty cycle:

  • carrier_duty_percent (Optional, int): The carrier duty cycle for signal demodulation in the RMT peripheral in Hz. Defaults to 100.

  • carrier_frequency (Optional, int): The carrier frequency for signal demodulation in the RMT peripheral in Hz. Defaults to 0Hz (carrier demodulation disabled).

NOTE

The dumped raw code is sequence of pulse widths (durations in microseconds), positive for on-pulses (mark) and negative for off-pulses (space). Usually you can to copy this directly to the configuration or automation to be used later.

  • on_abbwelcome (Optional, Automation): An automation to perform when a ABB-Welcome code has been decoded. A variable x of type API Reference: remote_base::ABBWelcomeData is passed to the automation for use in lambdas.

  • on_aeha (Optional, Automation): An automation to perform when a AEHA remote code has been decoded. A variable x of type API Reference: remote_base::AEHAData is passed to the automation for use in lambdas.

  • on_aok (Optional, Automation): An automation to perform when an A-OK RF remote code has been decoded. A variable x of type API Reference: remote_base::AOKData is passed to the automation for use in lambdas.

  • on_beo4 (Optional, Automation): An automation to perform when a B&O Beo4 infrared remote code has been decoded. A variable x of type API Reference: remote_base::Beo4Data is passed to the automation for use in lambdas.

  • on_brennenstuhl (Optional, Automation): An automation to perform when a brennenstuhl RF code has been decoded. A variable x of type API Reference: remote_base::BrennenstuhlData is passed to the automation for use in lambdas.

  • on_byronsx (Optional, Automation): An automation to perform when a Byron SX doorbell RF code has been decoded. A variable x of type API Reference: remote_base::ByronSXData is passed to the automation for use in lambdas.

  • on_canalsat (Optional, Automation): An automation to perform when a CanalSat remote code has been decoded. A variable x of type API Reference: remote_base::CanalSatData is passed to the automation for use in lambdas.

  • on_canalsatld (Optional, Automation): An automation to perform when a CanalSatLD remote code has been decoded. A variable x of type API Reference: remote_base::CanalSatLDData is passed to the automation for use in lambdas.

  • on_coolix (Optional, Automation): An automation to perform when a Coolix remote code has been decoded. A variable x of type API Reference: remote_base::CoolixData is passed to the automation for use in lambdas.

  • on_dish (Optional, Automation): An automation to perform when a dish network remote code has been decoded. A variable x of type API Reference: remote_base::DishData is passed to the automation for use in lambdas. Beware that Dish remotes use a different carrier frequency (57.6kHz) that many receiver hardware don’t decode.

  • on_dooya (Optional, Automation): An automation to perform when a Dooya RF remote code has been decoded. A variable x of type API Reference: remote_base::DooyaData is passed to the automation for use in lambdas.

  • on_drayton (Optional, Automation): An automation to perform when a Drayton Digistat RF code has been decoded. A variable x of type API Reference: remote_base::DraytonData is passed to the automation for use in lambdas. It has the fields address, data, and the legacy channel and command. Packets that fail the checksum are dropped and do not trigger the automation.

  • on_dyson (Optional, Automation): An automation to perform when a Dyson cool AM07 code has been decoded. A variable x of type API Reference: remote_base::DysonData is passed to the automation for use in lambdas.

  • on_gobox (Optional, Automation): An automation to perform when a Go-Box remote code has been decoded. A variable x of type API Reference: remote_base::GoboxData is passed to the automation for use in lambdas.

  • on_hob2hood (Optional, Automation): An automation to perform when a Hob2Hood remote code has been decoded. A variable x of type

    API Reference: remote_base::Hob2HoodData

    is passed to the automation for use in lambdas.

  • on_jvc (Optional, Automation): An automation to perform when a JVC remote code has been decoded. A variable x of type API Reference: remote_base::JVCData is passed to the automation for use in lambdas.

  • on_keeloq (Optional, Automation): An automation to perform when a KeeLoq RF code has been decoded. A variable x of type API Reference: remote_base::KeeloqData is passed to the automation for use in lambdas. Up to 16 bits that follow the 66-bit HCS301 word are in x.suffix, lowest bit first, and their number is in x.suffix_bits. Both are 0 when these bits do not end at a gap or at the end of the capture, or when there are more than 16; the 66-bit word is still reported. For a 72-bit Jarolift TDEF frame, where x.suffix_bits is 6, x.group() returns its 8 group bits. Check x.suffix_bits first: for other frames x.group() is not a group. The log shows such a frame with group=.

  • on_haier (Optional, Automation): An automation to perform when a Haier remote code has been decoded. A variable x of type API Reference: remote_base::HaierData is passed to the automation for use in lambdas.

  • on_ira211 (Optional, Automation): An automation to perform when a Siemens IRA211 remote code has been decoded. A variable x of type API Reference: remote_base::IRA211Data is passed to the automation for use in lambdas.

  • on_lg (Optional, Automation): An automation to perform when a LG remote code has been decoded. A variable x of type API Reference: remote_base::LGData is passed to the automation for use in lambdas.

  • on_magiquest (Optional, Automation): An automation to perform when a MagiQuest wand remote code has been decoded. A variable x of type API Reference: remote_base::MagiQuestData is passed to the automation for use in lambdas. Since 2026.11, x.wand_id is the wand’s full 31 bit id and x.magnitude its 9 bit magnitude field; earlier versions read both fields at the wrong offsets, so lambdas that compare them need the new values shown by the dumper.

  • on_midea (Optional, Automation): An automation to perform when a Midea remote code has been decoded. A variable x of type API Reference: remote_base::MideaData is passed to the automation for use in lambdas.

  • on_nec (Optional, Automation): An automation to perform when a NEC remote code has been decoded. A variable x of type API Reference: remote_base::NECData is passed to the automation for use in lambdas.

  • on_nexa (Optional, Automation): An automation to perform when a Nexa RF code has been decoded. A variable x of type API Reference: remote_base::NexaData is passed to the automation for use in lambdas.

  • on_nexus (Optional, Automation): An automation to perform when a Nexus RF code has been decoded. A variable x of type API Reference: remote_base::NexusData is passed to the automation for use in lambdas. It carries channel (1 to 4), address, temperature in °C, humidity in %, battery_level (true while the battery is fine) and force_update (true for a transmission started by the sensor’s button). Each sensor repeats its code several times per transmission.

  • on_onkyori (Optional, Automation): An automation to perform when an Onkyo RI code has been decoded. A variable x of type API Reference: remote_base::OnkyoRIData is passed to the automation for use in lambdas.

  • on_panasonic (Optional, Automation): An automation to perform when a Panasonic remote code has been decoded. A variable x of type API Reference: remote_base::PanasonicData is passed to the automation for use in lambdas. Its fields are x.nbits (48 or 56), x.address (16 bits), x.address_2 (8 bits, always 0 for a 48-bit code) and x.command (32 bits).

  • on_pd_pioneer (Optional, Automation): An automation to perform when a PD Pioneer mini-split remote code has been decoded. A variable x of type API Reference: remote_base::PDPioneerData is passed to the automation for use in lambdas.

  • on_pioneer (Optional, Automation): An automation to perform when a pioneer remote code has been decoded. A variable x of type API Reference: remote_base::PioneerData is passed to the automation for use in lambdas.

  • on_pronto (Optional, Automation): An automation to perform when a Pronto remote code has been decoded. A variable x of type API Reference: remote_base::ProntoData is passed to the automation for use in lambdas.

  • on_raw (Optional, Automation): An automation to perform when a raw remote code has been decoded. A variable x of type std::vector<int> is passed to the automation for use in lambdas.

  • on_rc5 (Optional, Automation): An automation to perform when a RC5 remote code has been decoded. A variable x of type API Reference: remote_base::RC5Data is passed to the automation for use in lambdas.

  • on_rc5x (Optional, Automation): An automation to perform when a RC5X (Marantz Extended RC5) remote code has been decoded. A variable x of type API Reference: remote_base::RC5XData is passed to the automation for use in lambdas. It has the fields address, command and extension.

  • on_rc6 (Optional, Automation): An automation to perform when a RC6 remote code has been decoded. A variable x of type API Reference: remote_base::RC6Data is passed to the automation for use in lambdas.

  • on_rc_switch (Optional, Automation): An automation to perform when a RCSwitch RF code has been decoded. A variable x of type API Reference: remote_base::RCSwitchData is passed to the automation for use in lambdas.

  • on_roomba (Optional, Automation): An automation to perform when a Roomba remote code has been decoded. A variable x of type API Reference: remote_base::RoombaData is passed to the automation for use in lambdas.

  • on_samsung (Optional, Automation): An automation to perform when a Samsung remote code has been decoded. A variable x of type API Reference: remote_base::SamsungData is passed to the automation for use in lambdas.

  • on_samsung36 (Optional, Automation): An automation to perform when a Samsung36 remote code has been decoded. A variable x of type API Reference: remote_base::Samsung36Data is passed to the automation for use in lambdas.

  • on_sony (Optional, Automation): An automation to perform when a Sony remote code has been decoded. A variable x of type API Reference: remote_base::SonyData is passed to the automation for use in lambdas.

  • on_symphony (Optional, Automation): An automation to perform when a Symphony remote code has been decoded. A variable x of type API Reference: remote_base::SymphonyData is passed to the automation for use in lambdas.

  • on_toshiba_ac (Optional, Automation): An automation to perform when a Toshiba AC remote code has been decoded. A variable x of type API Reference: remote_base::ToshibaAcData is passed to the automation for use in lambdas.

  • on_mirage (Optional, Automation): An automation to perform when a Mirage remote code has been decoded. A variable x of type API Reference: remote_base::MirageData is passed to the automation for use in lambdas.

  • on_toto (Optional, Automation): An automation to perform when a Toto remote code has been decoded. A variable x of type API Reference: remote_base::TotoData is passed to the automation for use in lambdas.

# Example automation for decoded signals
remote_receiver:
...
on_samsung:
then:
- if:
condition:
or:
- lambda: 'return (x.data == 0xE0E0E01F);' # VOL+ newer type
- lambda: 'return (x.data == 0xE0E0E01F0);' # VOL+ older type
then:
- ...

The remote_receiver binary sensor lets you track when a button on a remote control is pressed.

Each time the pre-defined signal is received, the binary sensor will briefly go ON and then immediately OFF.

NOTE

For IR Remote Binary Sensors: If you’re using binary sensors to track IR remote button presses and experiencing issues with rapid button presses not being detected (e.g., quick ON→OFF transitions being missed), consider setting batch_delay: 0ms in your API configuration. This will send state changes immediately instead of batching them, ensuring rapid transitions are preserved. However, this increases network traffic and should only be used when necessary.

For new projects, consider using automations with the on_* triggers (described above) instead of binary sensors, as they are better suited for handling momentary button press events.

# Example configuration entry
binary_sensor:
- platform: remote_receiver
name: "Panasonic Remote Input"
panasonic:
address: 0x4004
command: 0x100BCBD
# Example with batch_delay: 0 for rapid button presses
api:
batch_delay: 0ms # Send state changes immediately
remote_receiver:
pin: GPIOXX
dump: all
binary_sensor:
- platform: remote_receiver
name: "TV Remote Power"
nec:
address: 0x1234
command: 0x5678
  • receiver_id (Optional, ID): The remote receiver to receive the remote code with. Required if multiple receivers configured.

  • All other options from Binary Sensor.

Remote code selection (exactly one of these has to be included):

  • abbwelcome: Trigger on a decoded ABB-Welcome code with the given data, see the transmitter description for more info.

    • source_address (Required, int): The source address to trigger on.

    • destination_address (Required, int): The destination address to trigger on.

    • three_byte_address (Optional, boolean): The length of the source and destination address. false means two bytes and true means three bytes. Defaults to false.

    • retransmission (Optional, boolean): true if the message was re-transmitted. Defaults to false.

    • message_type (Required, int): The message type to trigger on.

    • message_id (Optional, int): The random message ID to trigger on, see dumper output for more info. Defaults to any ID.

    • data (Optional, 0-7 bytes list): The code to listen for. Usually you only need to copy this directly from the dumper output. Defaults to []

  • aeha: Trigger on a decoded AEHA remote code with the given data.

    • address (Required, int): The address to trigger on, see dumper output for more info.
    • data (Required, 3-35 bytes list): The code to listen for, see transmitter description for more info. Usually you only need to copy this directly from the dumper output.
  • aok: Trigger on a decoded A-OK RF remote code with the given data.

    • remote_id (Required, int): The 24-bit ID of the remote. Range is 0 to 0xFFFFFF.
    • channels (Required, int): The 16-bit channel mask. Each of the 16 channels on the remote corresponds to one bit of the mask.
    • command (Required, int): The 1-byte command code. Range is 0 to 0xFF.
  • beo4: Trigger on a decoded B&O Beo4 infrared remote code with the given data.

    • source (Required, int): The 8-bit source to trigger on, e.g. 0x00=video, 0x01=audio,…, see dumper output for more info.
    • command (Required, int): The 8-bit command to listen for, e.g. 0x00=number0, 0x0C=standby,…, see dumper output for more info.
  • brennenstuhl: Trigger on a decoded brennenstuhl RF code with the given data.

    • code (Required, int): The 24-bit code to trigger on, see dumper output for more info.
  • byronsx: Trigger on a decoded Byron SX Doorbell RF remote code with the given data.

    • address (Required, int): The 8-bit ID code to trigger on, see dumper output for more info.
    • command (Optional, int): The 4-bit command to listen for. If omitted, will match on any command.
  • canalsat: Trigger on a decoded CanalSat remote code with the given data.

    • device (Required, int): The device to trigger on, see dumper output for more info.

    • address (Optional, int): The address (or subdevice) to trigger on, see dumper output for more info. Defaults to 0.

    • command (Required, int): The command to listen for.

  • canalsatld: Trigger on a decoded CanalSatLD remote code with the given data.

    • device (Required, int): The device to trigger on, see dumper output for more info.

    • address (Optional, int): The address (or subdevice) to trigger on, see dumper output for more info. Defaults to 0.

    • command (Required, int): The command to listen for.

  • coolix: Trigger on a decoded Coolix remote code with the given data. It is possible to directly specify a 24-bit code, it will be checked for a match to at least one of the two received packets. The main configuration scheme is below.

    • first (Required, uint32_t): The first 24-bit Coolix code to trigger on, see dumper output for more info.
    • second (Optional, uint32_t): The second 24-bit Coolix code to trigger on, see dumper output for more info. If not set, trigger on only single non-strict packet, specified by the first parameter.
  • dish: Trigger on a decoded Dish Network remote code with the given data. Beware that Dish remotes use a different carrier frequency (57.6kHz) that many receiver hardware don’t decode.

    • address (Optional, int): The number of the receiver to target, between 1 and 16 inclusive. Defaults to 1.
    • command (Required, int): The Dish command to listen for, between 0 and 63 inclusive.
  • dooya: Trigger on a decoded Dooya RF remote code with the given data.

    • id (Required, int): The 24-bit ID code to trigger on.
    • channel (Required, int): The 8-bit channel to listen for.
    • button (Required, int): The 4-bit button to listen for.
    • check (Required, int): The 4-bit check to listen for. Includes an indication that a button is being held down.
  • drayton: Trigger on a decoded Drayton Digistat RF remote code with the given data. Set address and either data or both channel and command. Packets that fail the checksum are dropped and never trigger.

    • address (Required, int): The 16-bit address to trigger on, see dumper output for more info. It is the 12-bit thermostat ID followed by a 4-bit pairing field. The pairing field is normally 0; a thermostat sets bit 0 in the first packets after its batteries are inserted, so a receiver in pairing mode can learn its ID.
    • data (Optional, int): The 4-bit data value to trigger on. Range is 0 to 0xF. Bit 0x8 means the thermostat calls for heat and bit 0x2 means low battery, so 0x8 is On with the battery OK and 0x0 is Off. The other two bits have not been seen set. Cannot be used with channel and command.
    • channel (Optional, int): The legacy 5-bit channel, the low 5 checksum bits. Range is 0 to 0x1F. Must be used together with command; kept for configurations written for the first Drayton release. It is not compared when matching, since the checksum is verified before a packet gets this far.
    • command (Optional, int): The legacy 7-bit command, the 4 data bits followed by the top 3 checksum bits. Range is 0 to 0x7F. Must be used together with channel. Only its 4 data bits are compared with the received packet.
  • dyson: Trigger on a decoded dyson cool AM07 infrared remote code with the given data.

    • code (Required, int): The 16-bit code to trigger on, e.g. 0x1200=power, 0x1215=fan++,0x122a=swing…, see dumper output for more info.
    • index (Optional, int): The 8-bit rolling index [0..3], to be increased with every transmit, see dumper output for more info.
  • gobox: Trigger on a decoded Go-Box remote code with the given data.

    • code (Required, int): The Go-Box code to trigger on, see dumper output for more info.
  • hob2hood: Trigger on a decoded Hob2Hood remote code with the given data.

    • command (Required, enum): The Hob2Hood command to trigger on, see dumper output for more info.
      • light_off
      • light_on
      • fan_off
      • fan_low
      • fan_medium
      • fan_high
      • fan_max
  • jvc: Trigger on a decoded JVC remote code with the given data.

    • data (Required, int): The JVC code to trigger on, see dumper output for more info.
  • keeloq: Trigger on a decoded KeeLoq RF remote code with the given data. Suffix bits after the 66-bit word are not compared.

    • address (Required, int): The 28-bit ID code to trigger on, see dumper output for more info.
    • command (Optional, int): The 4-bit switch/command to listen for. If omitted, will match on any command/button.
  • haier: Trigger on a Haier remote code with the given code.

    • code (Required, 8 or 13-bytes list): The code to listen for, see transmitter description for more info. Usually you only need to copy this directly from the dumper output.
  • ira211: Trigger on a decoded Siemens IRA211 remote code with the given data. SYNC and POWER carry the full state (temperature, mode and fan), TEMP_UP and TEMP_DOWN carry only the temperature, MODE only the mode and FAN only the fan speed; a frame matches when its command and the fields it carries match.

    • command (Required, string): The command to trigger on. One of TEMP_UP, TEMP_DOWN, MODE, FAN, POWER or SYNC.
    • temperature (Optional, float): The target temperature in °C, from 5 to 35 in 0.5 steps. Defaults to 20.
    • mode (Optional, string): The operating mode. One of PROTECTION, TIMER or COMFORT. Defaults to COMFORT.
    • fan_mode (Optional, string): The fan speed. One of AUTO, LOW, MEDIUM or HIGH. Defaults to AUTO.
  • lg: Trigger on a decoded LG remote code with the given data.

    • data (Required, int): The LG code to trigger on, see dumper output for more info.
    • nbits (Optional, int): The number of bits of the remote code. Defaults to 28.
  • magiquest: Trigger on a decoded MagiQuest wand remote code, optionally limited to one wand ID.

    • wand_id (Optional, int): The MagiQuest wand ID to trigger on, see dumper output for more info. If omitted, any wand triggers the sensor. Ids written down with ESPHome versions before 2026.11 keep working: they are the new id without its five lowest bits, and both forms are matched. Because of that, an id below 0x04000000 also matches the 32 wands whose full id shortens to it; a full id from a current dump is unambiguous above that value.
    • magnitude (Optional, int): Accepted for compatibility but ignored; the magnitude field encodes the kind of cast rather than a strength, so every activation of the wand matches.
  • midea: Trigger on a Midea remote code with the given code.

    • code (Required, 5-bytes list): The code to listen for, see transmitter description for more info. Usually you only need to copy first 5 bytes directly from the dumper output.
  • nec: Trigger on a decoded NEC remote code with the given data.

    • address (Required, int): The address to trigger on, see dumper output for more info.
    • command (Required, int): The NEC command to listen for.
  • nexa: Trigger on a decoded Nexa RF code with the given data.

    • device (Required, int): The Nexa device code to trigger on, see dumper output for more info.
    • group (Required, int): The Nexa group code to trigger on, see dumper output for more info.
    • state (Required, int): The Nexa state code to trigger on, see dumper output for more info.
    • channel (Required, int): The Nexa channel code to trigger on, see dumper output for more info.
    • level (Required, int): The Nexa level code to trigger on, see dumper output for more info.
  • nexus: Trigger on any decoded Nexus RF code from the given sensor, whatever it reports.

    • channel (Required, int): The channel (1 to 4) to trigger on, see dumper output for more info.
    • address (Required, int): The address (sensor ID) to trigger on, see dumper output for more info.
  • onkyori: Trigger on a decoded Onkyo RI code with the given data.

    • data (Required, int): The Onkyo RI code to trigger on, in the range 0x000 to 0xFFF, see dumper output for more info.
  • panasonic: Trigger on a decoded Panasonic remote code with the given data. A 56-bit remote that an earlier release showed as a 48-bit code needs a fresh dump; its nbits, address_2 and command change.

    • address (Required, int): The 16-bit address to trigger on, see dumper output for more info.
    • address_2 (Optional, int): The extra 8-bit address byte of a 56-bit code, see dumper output for more info. Only allowed with nbits: 56. Defaults to 0.
    • command (Required, int): The 32-bit command.
    • nbits (Optional, int): The number of bits of the remote code, 48 or 56. Defaults to 48.
  • pd_pioneer: Trigger on a decoded PD Pioneer mini-split remote code with the given data.

    • code (Required, 13- or 14-byte list): The code to listen for, see transmitter description for more info. Usually you only need to copy this directly from the dumper output.
  • pioneer: Trigger on a decoded Pioneer remote code with the given data.

    • rc_code_1 (Required, int): The remote control code to trigger on, see dumper output for more details.
  • pronto: Trigger on a Pronto remote code with the given code.

    • data (Required, string): The code to listen for, see transmitter description for more info. Usually you only need to copy this directly from the dumper output.

    • delta (Optional, integer): This parameter allows you to manually specify the allowed difference between what Pronto code is specified, and what IR signal has been sent by the remote control.

  • raw: Trigger on a raw remote code with the given code.

    • code (Required, list): The code to listen for, see transmitter description for more info. Usually you only need to copy this directly from the dumper output.
  • rc5: Trigger on a decoded RC5 remote code with the given data.

    • address (Required, int): The address to trigger on, see dumper output for more info.
    • command (Required, int): The RC5 command to listen for.
  • rc5x: Trigger on a decoded RC5X (Marantz Extended RC5) remote code with the given data.

    • address (Required, int): The address to trigger on, see dumper output for more info. Range is 0 to 0x1F.
    • command (Required, int): The RC5X command to listen for. Range is 0 to 0x7F.
    • extension (Required, int): The RC5X extension field to listen for. Range is 0 to 0x3F.
  • rc6: Trigger on a decoded RC6 remote code with the given data.

    • address (Required, int): The address to trigger on, see dumper output for more info.
    • command (Required, int): The RC6 command to listen for.
  • rc_switch_raw: Trigger on a decoded RC Switch raw remote code with the given data.

    • code (Required, string): The remote code to listen for, copy this from the dumper output. To ignore a bit in the received data, use x at that place in the code.

    • protocol (Optional): The RC Switch protocol to use, see RC Switch Protocol for more info.

  • rc_switch_type_a: Trigger on a decoded RC Switch Type A remote code with the given data.

    • group (Required, string): The group, binary string.
    • device (Required, string): The device in the group, binary string.
    • state (Required, boolean): The on/off state to trigger on.
    • protocol (Optional): The RC Switch protocol to use, see RC Switch Protocol for more info.
  • rc_switch_type_b: Trigger on a decoded RC Switch Type B remote code with the given data.

    • address (Required, int): The address, int from 1 to 4.
    • channel (Required, int): The channel, int from 1 to 4.
    • state (Required, boolean): The on/off state to trigger on.
    • protocol (Optional): The RC Switch protocol to use, see RC Switch Protocol for more info.
  • rc_switch_type_c: Trigger on a decoded RC Switch Type C remote code with the given data.

    • family (Required, string): The family. Range is a to p.
    • group (Required, int): The group. Range is 1 to 4.
    • device (Required, int): The device. Range is 1 to 4.
    • state (Required, boolean): The on/off state to trigger on.
    • protocol (Optional): The RC Switch protocol to use, see RC Switch Protocol for more info.
  • rc_switch_type_d: Trigger on a decoded RC Switch Type D remote code with the given data.

    • group (Required, int): The group. Range is 1 to 4.
    • device (Required, int): The device. Range is 1 to 3.
    • state (Required, boolean): The on/off state to trigger on.
    • protocol (Optional): The RC Switch protocol to use, see RC Switch Protocol for more info.
  • roomba: Trigger on a decoded Roomba remote code with the given data.

    • data (Required, int): The Roomba code to trigger on, see dumper output for more info.
  • samsung: Trigger on a decoded Samsung remote code with the given data.

    • data (Required, int): The data to trigger on, see dumper output for more info.
    • nbits (Optional, int): The number of bits of the remote code. Defaults to 32.
  • samsung36: Trigger on a decoded Samsung36 remote code with the given data.

    • address (Required, int): The address to trigger on, see dumper output for more info.
    • command (Required, int): The command.
  • sony: Trigger on a decoded Sony remote code with the given data.

    • data (Required, int): The Sony code to trigger on, see dumper output for more info.
    • nbits (Optional, int): The number of bits of the remote code. Defaults to 12.
  • symphony: Trigger on a decoded Symphony remote code with the given data.

    • data (Required, int): The Symphony code to trigger on, see dumper output for more info.
    • nbits (Required, int): The number of bits of the remote code. Typical values: 8, 12, or 16.
  • toshiba_ac: Trigger on a decoded Toshiba AC remote code with the given data.

    • rc_code_1 (Required, int): The remote control code to trigger on, see dumper output for more details.
    • rc_code_2 (Optional, int): The second part of the remote control code to trigger on, see dumper output for more details.
  • mirage: Trigger on a Mirage remote code with the given code.

    • code (Required, 14-bytes list): The code to listen for, see transmitter description for more info. Usually you only need to copy this directly from the dumper output.
  • toto: Trigger on a decoded Toto remote code with the given data.

    • command (Required, int): The 1-byte Toto command code to trigger on. Range is 0 to 0xFF.
    • rc_code_1 (Optional, int): The first 4-bit Toto code (usually a command parameter) to trigger on. Range is 0 to 0xF.
    • rc_code_2 (Optional, int): The second 4-bit Toto code (usually a command parameter) to trigger on. Range is 0 to 0xF.

NOTE

The CanalSat and CanalSatLD protocols use a higher carrier frequency (56kHz) and are very similar. Depending on the hardware used they may interfere with each other when enabled simultaneously.

NOTE

NEC codes: In version 2021.12, the order of transferring bits was corrected from MSB to LSB in accordance with the NEC standard. Therefore, if the configuration file has come from an earlier version of ESPhome, it is necessary to reverse the order of the address and command bits when moving to 2021.12 or above. For example, address: 0x84ED, command: 0x13EC becomes 0xB721 and 0x37C8, respectively.

NOTE

Some receivers, such as the TSOP38238, may require the use of a pull-up resistor. You can enable this as follows:

remote_receiver:
pin:
number: GPIOXX
inverted: true
mode:
input: true
pullup: true
dump: all

NOTE

For the black Sonoff RF Bridge, you can bypass the EFM8BB1 microcontroller handling RF signals with this hack created by the GitHub user wildwiz. Then use this configuration for the remote receiver/transmitter hubs:

remote_receiver:
pin: 4
dump: all
remote_transmitter:
pin: 5
carrier_duty_percent: 100%

There’s also a software “hack” that allows the radio chip to mirror all the voltages to the ESP to do the decoding, rendering the hardware hack unnecessary. This software passthrough mode can be used for the OB38S003 (white) and EFM8BB1 (black) sonoff RF bridge. Then use this configuration for the remote receiver/transmitter hubs:

remote_receiver:
pin:
# sonoff and wemos board
number: GPIO3
mode:
input: true
pullup: false
tolerance: 60%
filter: 4us
idle: 4ms
remote_transmitter:
pin: 1
carrier_duty_percent: 100%