BK7231N: received IR codes are not published via mqtt

[MaxRower]

When an IR code is received, I can see it in the log, but the code is not published via mqtt, so there is no way, to get it in Home Assistant. Only sending IR code via Home Assistant is possible.

OpenBK7231N_QIO_1.18.287.bin
Built on Apr 11 2026 22:23:06 version 1.18.287
Nivian NVS-SMARTIR-W2
BK7231N on Tuya CB3S

"pins": {
"7": "WifiLED_n;0",
"8": "IRSend;0",
"9": "IRRecv;0",
"26": "Btn;0"
},

[divadiow]

have you tried flag 22?

[MaxRower]

Ooops, completely missed those flags. IR gets published now.
But the log shows different values get published.

Info:IR:IR IR_Samsung 0x2C2C 0x41 0 (32 bits)
Info:MQTT:Publishing val {"IrReceived":{"Protocol":"Samsung","Bits":32,"Data":"0xBE412C2C"}} to BK7231N_301B000DB/RESULT retain=0
Info:IR:IR IR_RC6 0x10 0xC 1 (36 bits)
Info:MQTT:Publishing val {"IrReceived":{"Protocol":"RC6","Bits":36,"Data":"0x8052900C"}} to BK7231N_301B000DB/RESULT retain=0

And RC6 is inconsistently detected, it often varies, e.g. 0x8052900C and 0x8052100C for a VU+ STB on/off remote code. And sending those two does not do anything on the device. Other codes for a Hisense TV and LG sound system do work fine.
Any clues what could be wrong with RC6? Should I create another issue for this?

[MaxRower]

Tasmota does list RC6 codes for VU+ here https://tasmota.github.io/docs/Codes-for-IR-Remotes/#vu-duo2
But those don't work either when I send them.

[openshwprojects]

Hey, have you tried also alternate IR library build?

[MaxRower]

I did try OpenBK7231N_1.18.287_irRemoteESP, but when I started to configure the pins, it somehow did not respond anymore, so I had to reflash it via UART. Would this be the correct build? The pins looked different, for the same device, can this be possible?

[openshwprojects]

It should behave 100% the same, just OTA to irRemoteESP and it should use same pin as main release. Can you retry? If this really crashes, then we need to investiage.

[divadiow]

I've done a basic check from 1.18.287 -> 1.18.287_irremotesp8266 and was able to configure pins and stuff without a crash. assignments stayed present after OTA. I did no ir tests.

[MaxRower]

Successfully flashed OpenBK7231N_1.18.287_irRemoteESP.rbl via OTA to the second device, the other still running the regular version. Booting seems to take much longer, maybe this is why I gave up on my first attempt?
Did a few IR tests, very strange. Receive is very erratic, codes the regular firmware detects are logged as "Received Unknown IR". When I send those code with the regular firmware (which will actually turn on the TV), still the same "Received Unknown IR".
RC6 is receiving codes very seldom. Sometimes it does not react to any IR codes by any remote. But I managed to turn the STB on and off by doing "irsend RC6,36,0xC8052100C". Apperently, both firmware variants use different syntax for RC6?. On the regular firmware I have to "IRsend RC6 0xC8052900C (36 bits)", but the STB is not reacting at all.
It seems the alternate firmware could be used to sucessfully send IR codes to all three devices (VU+ STB, Hisense TV, LG 5.1 sound system) here in the living room. But learning all the codes is PITA. I still have to test a Sony 5.1 AMP and a Sony TV on another location.

On my third device (got a triple pack), I installed ESPHome with IR proxy, to test the new feature from Home Assistant 2026.4. But I could not really test it, maybe it will work with a very old LG TV. The only integration that curently supports IR proxy is for LG TVs. I don't see any other way or found any docs how to interact with that proxy. HA seems to do IR proxy transmit only, no receive control shown in the device view.