Daikin AC (ATXC35B/FTXC35B) - Broadlink RM4 & SmartIR: Bip on OFF command but AC doesn't turn off

Configuration
1

Hi everyone,

I’m having trouble getting the “OFF” command to work properly with a Daikin AC (Model ATXC35B / FTXC35B) using SmartIR (climate platform) and a Broadlink RM4 controller.

The Issue:
Whenever the off command is sent via SmartIR, the indoor unit emits a “beep” sound, but the AC does not actually turn off. The temperature/mode commands work fine, but the power off sequence seems incomplete or cut off.

Setup Details:

  • Device: Daikin ATXC35B / FTXC35B
  • Controller: Broadlink RM4 (remote.learn_command used for learning)
  • Integration: SmartIR (codes/climate/1199.json)
  • Reference: A Tuya Smart IR blaster in the same room turns the unit off without any issues.

What we tried so far:

  1. Learned the off command directly from the physical Daikin remote.
  2. Learned the off command from the working Tuya IR blaster emitting the signal.
  3. Extracted the Base64 strings from .storage/broadlink_remote_codes and populated 1199.json.

In both cases, sending the resulting Base64 string via Broadlink results in a beep from the Daikin unit, but no power status change.

Has anyone successfully mapped the full multi-packet Daikin IR payload for this specific model on Broadlink/SmartIR, or is there a known delay/pragmatic fix for Daikin 154-bit IR signals?

Thanks in advance!

2

IR control is terrible. Home Assistant has no idea what the state of the device is. This is well worth the small cost: Need Daikin Wifi? Use the Open-Source Faikin ESP32 Hardware instead of the official wifi Modules

3

Have you considered HAIR?

~ DAB

5

Why on Earth would you when there are vastly superior options?

6

Faikin is a better HVAC control plane if you’re willing to open the indoor unit and hang an ESP32 on the S21 port: real bidirectional state, MQTT climate, no IR. FTXC35B-class units show up on the compatibility list, so that’s a real option here.

That’s a different project from what Vincenzo asked, though.

The beep-without-power-down on an RM4, with a Tuya blaster in the same room that does turn it off, is a Broadlink learn/replay problem on a long Daikin payload (the 154-bit / multi-packet thing). SmartIR is then firing a truncated Base64 as if it were a complete off. Home Assistant has no idea of IR state either way, but the immediate bug is the code, not the philosophy.

If you stay on IR:

  • Don’t re-learn OFF on the RM4. The Tuya shot already works. With Tuya Local, HAIR can pluck those stored codes without blasting them again, then send them through the Tuya emitter (or a cleaned copy through the RM4).
  • Or drop the SmartIR 1199.json into HAIR Closet. AC remotes don’t send a lone “off” button, they send a full state (mode / fan / swing / temp). HAIR treats that as a climate state matrix and transmits the complete cell, which is what the indoor unit actually expects.
  • A cheap power-monitoring plug on the indoor unit is the honest way to know whether it actually went off, if you stay on IR.

Faikin if you want to go inside the unit. HAIR if you want the hardware you already own to send the payload the Tuya is already sending. Both local. Not substitutes.

~ DAB