logo elektroda
logo elektroda
X
logo elektroda

Flashing and Configuring Micro IR Blaster (Ali 1005006823624599) with BK7231N

bkespoke 1419 7
ADVERTISEMENT
  • BK7231N pinout and flashing notes for micro IR blaster

    #1 21573835
    bkespoke
    Level 5  
    Posts: 14
    Help: 1
    Rate: 3
    Similar to many others, here is a small IR receiver/transmitter courtesy of atc1441 (though the one he posted about looks different).
    I bought this one in late 2024, seems to be still available for $7 on Ali, 1005006823624599
    The whole device is just 38 mm diameter, 15 mm thick.

    It has a BK7231N on the common CBU board. Four IR leds on top, and a receiver. Blue status LED and a button on the bottom.
    Trivial to flash with a USB-serial device, the pins are labelled underneath the board. I usually solder some 30 gauge wires to them.

    A black, round electronic gadget connected by cable lies on a ruler with a millimeter scale.
    Close-up of a circuit board with a Bekin BK7231N chip and 26 MHz quartz resonator.
    PCB with LED electronics and a controlling module in a round housing.

    Config:
    Code: JSON
    Log in, to see the code
  • ADVERTISEMENT
  • AC remote still decodes as unknown pulse-distance code

    #2 21574510
    bkespoke
    Level 5  
    Posts: 14
    Help: 1
    Rate: 3
    >>21573835
    Now I'd like to ask for some help... the remote blaster above is working fine for my TV remote decoding various codes. But for my AC remote it simply doesn't work.
    Summary of my frustrating questions in this AI discussion though I think the AI is dreaming up the build v1.18.130 and probably some other things.

    I've tried turning on all the IR flags. Commands like set IRdebug 1 are not supported. Roughly the same messages come out on MQTT. All the forum posts on IR are quite old. I would be happy with some sort of RAW capture - I only want to send three commands for the AC (on-cool-lowfan-16C ; on-fan-lowfan ; off)

    Is the (raw) buffer too small for this remote? Is there a nightly/alpha build that has the latest IR in it, or can you recommend a modification that I can build, that will receive this remote control?

    Thank you!

    With v1.18.110 the remote produces codes like this in the log:
    Debug:IR:IR decode returned true, protocol 1
    Debug:IR: Raw-Data=0x0
    Debug:IR: 48 bits
    Debug:IR: LSB first
    Debug:IR:IR decode returned true, protocol PulseDistance (1)
    Info:IR:IR IR_PulseDistance 0xD20 0xD0A 0 (48 bits)
    Debug:IR:IR fire event took 0ms
    Debug:IR:IR decode returned true, protocol 0
    Debug:IR: Hash=0x0
    Debug:IR:0 bits (incl. gap and start) received
    Debug:IR:IR decode returned true, protocol UNKNOWN (0)
    Info:IR:IR IR_UNKNOWN 0x0 0


    My autoexec.bat:
    startDriver SSDP
    startDriver NTP
    startDriver IR


    My config:
    {
      "vendor": "Tuya",
      "bDetailed": "0",
      "name": "Full Device Name Here",
      "model": "enter short model name here",
      "chip": "BK7231N",
      "board": "TODO",
      "flags": "32768",
      "keywords": [
        "TODO",
        "TODO",
        "TODO"
      ],
      "pins": {
        "7": "IRSend;0",
        "8": "IRRecv;0",
        "24": "WifiLED;0",
        "26": "Btn;0"
      },
      "command": "",
      "image": "https://obrazki.elektroda.pl/YOUR_IMAGE.jpg",
      "wiki": "https://www.elektroda.com/rtvforum/topic_YOUR_TOPIC.html"
    }
  • ADVERTISEMENT
  • ADVERTISEMENT
  • Intermittent KELON168 decode with bad CRC

    #4 21574572
    bkespoke
    Level 5  
    Posts: 14
    Help: 1
    Rate: 3
    Thanks - that is quite different.
    Now I get something on every remote press.

    Unfortunately the data is different every time:
    info:ir:ir unknown ffffffff,0xf3963672,172
    info:ir:ir unknown ffffffff,0x8301fb23,172
    info:ir:ir unknown ffffffff,0x928f624f,172
    info:ir:ir unknown ffffffff,0xbeb94b2f,172
    info:ir:ir unknown ffffffff,0xc21ea93,172
    info:ir:ir unknown ffffffff,0xa620bed1,172
    info:ir:ir unknown ffffffff,0xc0311423,172
    info:ir:ir unknown ffffffff,0xf187fb6b,172
    info:ir:ir unknown ffffffff,0x981bd6be,172
    info:ir:ir unknown ffffffff,0x5019b230,172
    info:ir:ir unknown ffffffff,0xea55b743,172
    info:ir:ir unknown ffffffff,0xf561a712,172
    info:ir:ir unknown ffffffff,0x9b520955,172
    info:ir:ir unknown ffffffff,0x821ba9ff,172

    Occasionally when the signal is strong it will decode it as KELON168? but then the debug doesn't print out the decoded result (bad CRC?).


    Info:IR:Received AC code:KELON168
    Debug:IR:IR fire event took 0ms
    Info:IR:IR Unknown ffffffff,0x6CA9AFD2,172
    Info:IR:Received AC code:KELON168
    Debug:IR:IR fire event took 0ms
    Info:IR:IR Unknown ffffffff,0x41E59780,172
    Info:IR:Received AC code:KELON168
    Debug:IR:IR fire event took 0ms
    Info:IR:Received AC code:KELON168
    Debug:IR:IR fire event took 0ms
    Info:IR:IR Unknown ffffffff,0x7771B42A,172

    Turning on flag 14, I get this on MQTT
    70,0x83060302000080000000000000810002000008000A
    Corresponding to this in the log:
    Info:IR:Received AC code:KELON168
    Info:IR:IR MQTT publish �A took 2ms
    Debug:IR:IR fire event took 0ms

    Could you suggest the next steps please?
  • #5 21580579
    divadiow
    Level 38  
    Posts: 5152
    Help: 442
    Rate: 906
    bkespoke wrote:
    Could you suggest the next steps please?

    hmm, not really sure what next. I have not had any experience with the irRemoteESP version.

    I wonder if powersave can have an effect on it like with standard ir version. Do you have powersave 1 set?
  • Occasional KELON168 decodes suggest accidental IR detection

    #6 21581354
    bkespoke
    Level 5  
    Posts: 14
    Help: 1
    Rate: 3
    Thanks again. Powersave does seem to have an impact but it was off.

    I have powersave 0 (I tried powersave 1, then the powersave messages appear everywhere in the logs, which I haven't seen before. Powersave 1 also causes a known-good remote to read garbage, while powersave 0 it decodes something most of the time.

    Interesting, the odd times it fails to decode the working remote, the hex values are just garbage.

    Hex values from my AC remote are always garbage, no pattern.

    But asking about the very occasional successful decodes, they all say:
    Info:IR:Received AC code:KELON168
    for any button on the remote. Whereas with the working TV remote I get various codes.
    Does this mean it's just an accidental decode?
  • #7 21581356
    divadiow
    Level 38  
    Posts: 5152
    Help: 442
    Rate: 906
    hmm. not sure.
    poking @p.kaczmarek2 and @DeDaMrAz who I think co-authored the irESP variant
  • ADVERTISEMENT

Topic summary

✨ A small AliExpress IR blaster/receiver module based on BK7231N and a CBU board was flashed over UART and configured with IRSend, IRRecv, WifiLED, and Btn pins. It worked well for TV remote decoding, but AC remote decoding was unreliable: standard firmware produced mostly garbage or empty IR data, while the irRemoteESP firmware enabled reception of some signals but often decoded them as random unknown values. Occasional successful decodes reported KELON168, suggesting either protocol mismatch, CRC issues, or limitations in the IR capture/decoding implementation. Powersave settings affected IR behavior, and a forum link was provided for additional IR context and known issues.
Summary generated by AI based on the discussion content.
ADVERTISEMENT