I purchased the Multicolour LED Light Bar with BK7231N inside today from Action. Seemed like a simple topic, all pads beautifully described, but when uploading the UART with Flasher I get this message: Using hack to write QIO - just skip bootloader.... ... so bootloader will not be overwritten!...

this message is normal if you do not have overwrite bootloader selected what logs do you see on TX2 when powering the device?

There should be a log from TX2. This is not a bootloader flashing error. It's a message that you're not overwriting it because you don't need to: Code: text Expand Select all Copy to clipboard Encryption key: 510fb093 ... Reading file firmwares/OpenBK7231N_QIO_1.18.135.bin... Loaded 1220464 bytes from firmwares/OpenBK7231N_QIO_1.18.135.bin... Using hack to write QIO - just skip bootloader... ... so bootloader will not be overwritten! Preparing to write data file to chip - resetting bus and baud... Getting bus... (now, please do reboot by CEN or by power off/on) Getting bus success! The factory bootloader remains. To overwrite it, you need to select the overwrite bootloader option, only this is generally not needed. If you have a factory backup, you could try enabling this and see if the chip then boots and there is something on TX2.

However, it must have corrupted during the flashing, because after uploading OpenBeken with the bootloader overwrite option and OBK data, the strip got up and connected to the indicated wifi network After selecting the Sky-lighting RGB Light Bar configuration, from the web I can turn the strip on, all animations work, but the IR remote does not work. I see that pin 26 is indicated as IRRecv, so I assume it should, the question is whether rightly

And have you mapped the pilot codes to actions in autoexec.bat? Tutorial: Tutorial/presentation on using the NiceMCU BK7238/T1 IR remote control - Home Assistant Does the Web App log see codes when you press buttons on the remote control?

The actions were already mapped in the finished config, along with animations, etc. Well that's exactly what it doesn't see, I started with that too. I tried GPIO Finder to move IRRecv to other free ports, but no change Trying to pull ports from the original config shows that IR is on 26

And do you have a copy of the factory batch (from before the pairing, so that the WiFi data isn't there) from which you could try to extract the GPIO data? The remote obviously has a battery?

Trying to pull the ports from the original config shows that IR is on 26 even blinks suspiciously through the camera EDIT: By default from the config the IR driver was not enabled, but after the command startDriver IR it is in the active list, but still in the logs silence

Can you see on the main OBK panel that there is an IR in the drivers? I.e. whether the IR driver is enabled. Are there any messages from the IR driver in the Web App log? Do you have PowerSave enabled? It messes up the IR - remove PowerSave from the command line.

YES: 5 drivers active (PixelAnim, NTP, SM16703P, IR, DDP), total: 33 Total silence By the logs from MQTT there was powersave, I put PowerSave 0 and it's gone, but still silence

Show a photo of the board where the IR sensor is and/or test with a multimeter (with the device switched off) whether it is physically connected to the Beken pin, or perhaps via some transistor? Alternatively, also check from Github the IRRemoteESP variant, this is the other library for IR, another implementation of the

Action Multicolor LED Light Bar with BK7231N - no WiFi after flashing OpenBK7231N

Mad_Maxs 573 21

Treść została przetłumaczona

Zobacz oryginalną wersję tematu

Report a violation of the law

Reply | New topic

#1 21805082 10 Jan 2026 22:05

Mad_Maxs Mad_Maxs

Level 12

» | Topic author

Post #1
21805082 10 Jan 2026 22:05

I purchased the Multicolour LED Light Bar with BK7231N inside today from Action.

Seemed like a simple topic, all pads beautifully described, but when uploading the UART with Flasher I get this message:
Quote:
Using hack to write QIO - just skip bootloader....
... so bootloader will not be overwritten!

The whole thing ends with the message Write success! but the chip doesn't boot, no default WIFI network is visible, when I push the WIFI config to it from the flasher it doesn't connect either

Full log from flasher:
Quote:
Starting flash new (no backup)!
Now is: Saturday, 10 January 2026 22:44:00.
Flasher mode: BK7231N
Going to open port: COM3.
Serial port open!
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Chip ID: 0x7231c
Will try to read device flash MID (for unprotect N):
Flash MID loaded: 1560EB
Will now search for Flash def in out database...
Flash def found! For: 1560EB
Flash information: mid: 1560EB, icName: TH25Q16HB, manufacturer: TH, szMem: 200000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-FF-FF-FF
Flash size is 2MB
Entering SetProtectState(True)...
sr: 0
sr: 0
final sr: 0
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
SetProtectState(True) success!
Going to read encryption key...
Encryption key read done!
Encryption key: 510fb093 ...
Reading file firmwares/OpenBK7231N_QIO_1.18.135.bin...
Loaded 1220464 bytes from firmwares/OpenBK7231N_QIO_1.18.135.bin...
Using hack to write QIO - just skip bootloader....
... so bootloader will not be overwritten!
Preparing to write data file to chip - resetting bus and baud...
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Will try to read device flash MID (for unprotect N):
Flash MID loaded: 1560EB
Will now search for Flash def in out database...
Flash def found! For: 1560EB
Flash information: mid: 1560EB, icName: TH25Q16HB, manufacturer: TH, szMem: 200000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-FF-FF-FF
Flash size is 2MB
Entering SetProtectState(True)...
sr: 0
sr: 0
final sr: 0
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
SetProtectState(True) success!
Going to do erase, start 0x11000, sec count 281!
Erasing sector 0x11000... ok! Erasing sector 0x12000... ok! Erasing sector 0x13000... ok! Erasing sector 0x14000... ok! Erasing sector 0x15000... ok! Erasing sector 0x16000... ok! Erasing sector 0x17000... ok! Erasing sector 0x18000... ok! Erasing sector 0x19000... ok! Erasing sector 0x1A000... ok! Erasing sector 0x1B000... ok! Erasing sector 0x1C000... oK! Erasing sector 0x1D000... oK! Erasing sector 0x1E000... oK! Erasing sector 0x1F000... ok! Erasing block 0x20000... ok! Erasing block 0x30000... ok! Erasing block 0x40000... ok! Erasing block 0x50000... ok! Erasing block 0x60000... ok! Erasing block 0x70000... ok! Erasing block 0x80000... ok! Erasing block 0x90000... ok! Erasing block 0xA0000... ok! Erasing block 0xB0000... ok! Erasing block 0xC0000... ok! Erasing block 0xD0000... ok! Erasing block 0xE0000... ok! Erasing block 0xF0000... ok! Erasing block 0x100000... ok! Erasing block 0x110000... ok! Erasing sector 0x120000... ok! Erasing sector 0x121000... ok! Erasing sector 0x122000 ... ok! Erasing sector 0x123000 ... ok! Erasing sector 0x124000... ok! Erasing sector 0x125000... ok! Erasing sector 0x126000... ok! Erasing sector 0x127000... ok! Erasing sector 0x128000... ok! Erasing sector 0x129000... ok!
All selected sectors erased!
Writing sector 0x11000... ok! Writing sector 0x12000... ok! Writing sector 0x13000... ok! Writing sector 0x14000... ok! Writing sector 0x15000... ok! Writing sector 0x16000... ok! Writing sector 0x17000... ok! Writing sector 0x18000... ok! Writing sector 0x19000... ok! Writing sector 0x1A000... ok! Writing sector 0x1B000... ok! Writing sector 0x1C000... ok! Writing sector 0x1D000... ok! Writing sector 0x1E000... ok! Writing sector 0x1F000... ok! Writing sector 0x20000... ok! Writing sector 0x21000... ok! Writing sector 0x22000... ok! Writing sector 0x23000... ok! Writing sector 0x24000... ok! Writing sector 0x25000... ok! Writing sector 0x26000... ok! Writing sector 0x27000... ok! Writing sector 0x28000... ok! Writing sector 0x29000... ok! Writing sector 0x2A000... ok! Writing sector 0x2B000... ok! Writing sector 0x2C000... ok! Writing sector 0x2D000... ok! Writing sector 0x2E000... ok! Writing sector 0x2F000... oK! Writing sector 0x30000... ok! Writing sector 0x31000... ok! Writing sector 0x32000... ok! Writing sector 0x33000... ok! Writing sector 0x34000... ok! Writing sector 0x35000... ok! Writing sector 0x36000... ok! Writing sector 0x37000... ok! Writing sector 0x38000... ok! Writing sector 0x39000... ok! Writing sector 0x3A000... ok! Writing sector 0x3B000... ok! Writing sector 0x3C000... ok! Writing sector 0x3D000... ok! Writing sector 0x3E000... ok! Writing sector 0x3F000... ok! Writing sector 0x40000... ok! Writing sector 0x41000... ok! Writing sector 0x42000... ok! Writing sector 0x43000... ok! Writing sector 0x44000... ok! Writing sector 0x45000... ok! Writing sector 0x46000... ok! Writing sector 0x47000... ok! Writing sector 0x48000... ok! Writing sector 0x49000... ok! Writing sector 0x4A000... ok! Writing sector 0x4B000... ok! Writing sector 0x4C000... ok! Writing sector 0x4D000... ok! Writing sector 0x4E000... ok! Writing sector 0x4F000... ok! Writing sector 0x50000... ok! Writing sector 0x51000... ok! Writing sector 0x52000... ok! Writing sector 0x53000... ok! Writing sector 0x54000... ok! Writing sector 0x55000... ok! Writing sector 0x56000... ok! Writing sector 0x57000... ok! Writing sector 0x58000... ok! Writing sector 0x59000... ok! Writing sector 0x5A000... ok! Writing sector 0x5B000... ok! Writing sector 0x5C000... ok! Writing sector 0x5D000... ok! Writing sector 0x5E000... ok! Writing sector 0x5F000... ok! Writing sector 0x60000... ok! Writing sector 0x61000... ok! Writing sector 0x62000... ok! Writing sector 0x63000... ok! Writing sector 0x64000... ok! Writing sector 0x65000... ok! Writing sector 0x66000... ok! Writing sector 0x67000... ok! Writing sector 0x68000... ok! Writing sector 0x69000... ok! Writing sector 0x6A000... ok! Writing sector 0x6B000... ok! Writing sector 0x6C000... ok! Writing sector 0x6D000... ok! Writing sector 0x6E000... ok! Writing sector 0x6F000... ok! Writing sector 0x70000... ok! Writing sector 0x71000... ok! Writing sector 0x72000... ok! Writing sector 0x73000... ok! Writing sector 0x74000... ok! Writing sector 0x75000... ok! Writing sector 0x76000... ok! Writing sector 0x77000... ok! Writing sector 0x78000... ok! Writing sector 0x79000... ok! Writing sector 0x7A000... ok! Writing sector 0x7B000... ok! Writing sector 0x7C000... ok! Writing sector 0x7D000 ... ok! Writing sector 0x7E000 ... ok! Writing sector 0x7F000... ok! Writing sector 0x80000... ok! Writing sector 0x81000... ok! Writing sector 0x82000... ok! Writing sector 0x83000... ok! Writing sector 0x84000... ok! Writing sector 0x85000... ok! Writing sector 0x86000... ok! Writing sector 0x87000... ok! Writing sector 0x88000... ok! Writing sector 0x89000... ok! Writing sector 0x8A000... ok! Writing sector 0x8B000... ok! Writing sector 0x8C000... ok! Writing sector 0x8D000... ok! Writing sector 0x8E000... ok! Writing sector 0x8F000... ok! Writing sector 0x90000... ok! Writing sector 0x91000... ok! Writing sector 0x92000... ok! Writing sector 0x93000... ok! Writing sector 0x94000... ok! Writing sector 0x95000... ok! Writing sector 0x96000... ok! Writing sector 0x97000... ok! Writing sector 0x98000... ok! Writing sector 0x99000... ok! Writing sector 0x9A000... ok! Writing sector 0x9B000... ok! Writing sector 0x9C000... ok! Writing sector 0x9D000... ok! Writing sector 0x9E000... ok! Writing sector 0x9F000... ok! Writing sector 0xA0000... ok! Writing sector 0xA1000... ok! Writing sector 0xA2000... ok! Writing sector 0xA3000... ok! Writing sector 0xA4000... ok! Writing sector 0xA5000... ok! Writing sector 0xA6000... ok! Writing sector 0xA7000... ok! Writing sector 0xA8000... ok! Writing sector 0xA9000... ok! Writing sector 0xAA000... ok! Writing sector 0xAB000... ok! Writing sector 0xAC000... ok! Writing sector 0xAD000... ok! Writing sector 0xAE000... ok! Writing sector 0xAF000... ok! Writing sector 0xB0000... ok! Writing sector 0xB1000... ok! Writing sector 0xB2000... ok! Writing sector 0xB3000... ok! Writing sector 0xB4000... ok! Writing sector 0xB5000... ok! Writing sector 0xB6000... ok! Writing sector 0xB7000... ok! Writing sector 0xB8000... ok! Writing sector 0xB9000... ok! Writing sector 0xBA000... ok! Writing sector 0xBB000... ok! Writing sector 0xBC000... ok! Writing sector 0xBD000... ok! Writing sector 0xBE000... ok! Writing sector 0xBF000... ok! Writing sector 0xC0000... ok! Writing sector 0xC1000... ok! Writing sector 0xC2000... ok! Writing sector 0xC3000... ok! Writing sector 0xC4000... ok! Writing sector 0xC5000... ok! Writing sector 0xC6000... ok! Writing sector 0xC7000... ok! Writing sector 0xC8000... ok! Writing sector 0xC9000... ok! Writing sector 0xCA000... ok! Writing sector 0xCB000... ok! Writing sector 0xCC000... ok! Writing sector 0xCD000... ok! Writing sector 0xCE000... ok! Writing sector 0xCF000... ok! Writing sector 0xD0000... ok! Writing sector 0xD1000... ok! Writing sector 0xD2000... ok! Writing sector 0xD3000... ok! Writing sector 0xD4000... ok! Writing sector 0xD5000... ok! Writing sector 0xD6000... ok! Writing sector 0xD7000... ok! Writing sector 0xD8000... ok! Writing sector 0xD9000... ok! Writing sector 0xDA000... ok! Writing sector 0xDB000... ok! Writing sector 0xDC000... ok! Writing sector 0xDD000... ok! Writing sector 0xDE000... ok! Writing sector 0xDF000... ok! Writing sector 0xE0000... ok! Writing sector 0xE1000... ok! Writing sector 0xE2000... ok! Writing sector 0xE3000... ok! Writing sector 0xE4000... ok! Writing sector 0xE5000... ok! Writing sector 0xE6000... ok! Writing sector 0xE7000... ok! Writing sector 0xE8000... ok! Writing sector 0xE9000... ok! Writing sector 0xEA000... ok! Writing sector 0xEB000... ok! Writing sector 0xEC000... ok! Writing sector 0xED000... ok! Writing sector 0xEE000... ok! Writing sector 0xEF000... ok! Writing sector 0xF0000... ok! Writing sector 0xF1000... ok! Writing sector 0xF2000 ... ok! Writing sector 0xF3000 ... ok! Writing sector 0xF4000... ok! Writing sector 0xF5000... ok! Writing sector 0xF6000... ok! Writing sector 0xF7000... ok! Writing sector 0xF8000... ok! Writing sector 0xF9000... ok! Writing sector 0xFA000... ok! Writing sector 0xFB000... ok! Writing sector 0xFC000... ok! Writing sector 0xFD000... ok! Writing sector 0xFE000... ok! Writing sector 0xFF000... ok! Writing sector 0x100000... ok! Writing sector 0x101000... ok! Writing sector 0x102000... ok! Writing sector 0x103000... ok! Writing sector 0x104000... ok! Writing sector 0x105000... ok! Writing sector 0x106000... ok! Writing sector 0x107000... ok! Writing sector 0x108000... ok! Writing sector 0x109000... ok! Writing sector 0x10A000... ok! Writing sector 0x10B000... ok! Writing sector 0x10C000... ok! Writing sector 0x10D000... ok! Writing sector 0x10E000... ok! Writing sector 0x10F000... ok! Writing sector 0x110000... ok! Writing sector 0x111000... ok! Writing sector 0x112000... ok! Writing sector 0x113000... ok! Writing sector 0x114000... ok! Writing sector 0x115000... ok! Writing sector 0x116000... ok! Writing sector 0x117000... ok! Writing sector 0x118000... ok! Writing sector 0x119000... ok! Writing sector 0x11A000... ok! Writing sector 0x11B000... ok! Writing sector 0x11C000... ok! Writing sector 0x11D000... ok! Writing sector 0x11E000... ok! Writing sector 0x11F000... ok! Writing sector 0x120000... ok! Writing sector 0x121000... ok! Writing sector 0x122000... ok! Writing sector 0x123000... ok! Writing sector 0x124000... ok! Writing sector 0x125000... ok! Writing sector 0x126000... ok! Writing sector 0x127000... ok! Writing sector 0x128000... ok! Writing sector 0x129000... ok! Starting CRC check for 281 sectors, starting at offset 0x11000
CRC matches 0x157DCAEE!

NOTE: the OBK config writing is disabled, so not writing anything extra.
Writing file data to chip successs.

I'm assuming it's due to this bootloader flashing bug, the question is how to get around it, because even when I restore the flash backup, it doesn't get up

When I give Read OBK, I get a reading of the data I put in there, including the ones from Wifi:
Quote:
Starting read!
Read parms: start 0x1D1000 (sector 465), len 0x1000 (1904640 sectors)
Now is: Saturday, 10 January 2026 22:56:37.
Flasher mode: BK7231N
Going to open port: COM3.
Serial port open!
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Chip ID: 0x7231c
Will try to read device flash MID (for unprotect N):
Flash MID loaded: 1560EB
Will now search for Flash def in out database...
Flash def found! For: 1560EB
Flash information: mid: 1560EB, icName: TH25Q16HB, manufacturer: TH, szMem: 200000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-FF-FF-FF
Flash size is 2MB
Entering SetProtectState(True)...
sr: 0
sr: 0
final sr: 0
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
SetProtectState(True) success!
Going to read encryption key...
Encryption key read done!
Encryption key: 510fb093 ....
Going to start reading at offset 0x1D1000...
Reading 0x1D1000... Ok!
Basic read operation finished, but now it's time to verify...
Starting CRC check for 1 sectors, starting at offset 0x1D1000
CRC matches 0x7C0936F!
All read!
Loaded total 0x1000 bytes
OBK config loaded. You can now view it by clicking 'Change OBK settings' button.
You can also edit it however you want.
You can also use 'Write OBK config' button to write it back with your changes.

EDIT:
I found something like this, but I don't know if it can help anything in my case, because even uploading the original flash, doesn't restore basic functionality:
https://www.elektroda.pl/rtvforum/topic4131054.html

I have also seen a similar problem to mine with a suggestion to collect the log from the TX2, the question is how? I've tried reading it via putty on COM3 and 115200, but I only get single bushes. The same thing with the rest falling on TX0
ADVERTISEMENT
#2 21805951 11 Jan 2026 21:19

divadiow divadiow

Level 38

Helpful post? (0)

Post #2
21805951 11 Jan 2026 21:19

Mad_Maxs wrote:
Using hack to write QIO - just skip bootloader....
... so bootloader will not be overwritten!

this message is normal if you do not have "overwrite bootloader" selected

what logs do you see on TX2 when powering the device?
ADVERTISEMENT
#3 21805955 11 Jan 2026 21:21

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home
» | Helpful post? (0)

Post #3
21805955 11 Jan 2026 21:21

There should be a log from TX2.

This is not a bootloader flashing error. It's a message that you're not overwriting it because you don't need to:
Code: text Expand Select all Copy to clipboard
Encryption key: 510fb093 ... Reading file firmwares/OpenBK7231N_QIO_1.18.135.bin... Loaded 1220464 bytes from firmwares/OpenBK7231N_QIO_1.18.135.bin... Using hack to write QIO - just skip bootloader... ... so bootloader will not be overwritten! Preparing to write data file to chip - resetting bus and baud... Getting bus... (now, please do reboot by CEN or by power off/on) Getting bus success!

The factory bootloader remains. To overwrite it, you need to select the "overwrite bootloader" option, only this is generally not needed. If you have a factory backup, you could try enabling this and see if the chip then boots and there is something on TX2.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
ADVERTISEMENT
#4 21806212 12 Jan 2026 08:34

Mad_Maxs Mad_Maxs

Level 12

» | Topic author Helpful post? (0)

Post #4
21806212 12 Jan 2026 08:34

p.kaczmarek2 wrote:
This is not a bootloader flashing error. It's a message that you don't overwrite it because you don't need to

However, it must have corrupted during the flashing, because after uploading OpenBeken with the bootloader overwrite option and OBK data, the strip got up and connected to the indicated wifi network

After selecting the Sky-lighting RGB Light Bar configuration, from the web I can turn the strip on, all animations work, but the IR remote does not work. I see that pin 26 is indicated as IRRecv, so I assume it should, the question is whether rightly
#5 21806326 12 Jan 2026 11:08

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #5
21806326 12 Jan 2026 11:08

And have you mapped the pilot codes to actions in autoexec.bat? Tutorial:
Tutorial/presentation on using the NiceMCU BK7238/T1 IR remote control - Home Assistant
Does the Web App log see codes when you press buttons on the remote control?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#6 21806332 12 Jan 2026 11:16

Mad_Maxs Mad_Maxs

Level 12

» | Topic author Helpful post? (0)

Post #6
21806332 12 Jan 2026 11:16

p.kaczmarek2 wrote:
And did you map the pilot codes to actions in autoexec.bat?

The actions were already mapped in the finished config, along with animations, etc.
p.kaczmarek2 wrote:
Does the Web App log see the codes when you press the buttons on the remote control?

Well that's exactly what it doesn't see, I started with that too. I tried GPIO Finder to move IRRecv to other free ports, but no change
Trying to pull ports from the original config shows that IR is on 26
#7 21806339 12 Jan 2026 11:22

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #7
21806339 12 Jan 2026 11:22

And do you have a copy of the factory batch (from before the pairing, so that the WiFi data isn't there) from which you could try to extract the GPIO data?

The remote obviously has a battery?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
ADVERTISEMENT
#8 21806347 12 Jan 2026 11:27

Mad_Maxs Mad_Maxs

Level 12

» | Topic author Helpful post? (0)

Post #8
21806347 12 Jan 2026 11:27

p.kaczmarek2 wrote:
And do you have a copy of the factory batch (from before the pairing, so that the WiFi data isn't there) from which you could try to pull the GPIO data?

Trying to pull the ports from the original config shows that IR is on 26
p.kaczmarek2 wrote:
Pilot obviously has battery power?

even blinks suspiciously through the camera

EDIT:
By default from the config the IR driver was not enabled, but after the command "startDriver IR" it is in the active list, but still in the logs silence
#9 21806363 12 Jan 2026 11:37

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #9
21806363 12 Jan 2026 11:37

Can you see on the main OBK panel that there is an IR in the drivers? I.e. whether the IR driver is enabled.

Are there any messages from the IR driver in the Web App log?

Do you have PowerSave enabled? It messes up the IR - remove PowerSave from the command line.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#10 21806393 12 Jan 2026 11:59

Mad_Maxs Mad_Maxs

Level 12

» | Topic author Helpful post? (0)

Post #10
21806393 12 Jan 2026 11:59

p.kaczmarek2 wrote:
Does the OBK main panel show that there is an IR in the drivers? I.e. is the IR driver enabled.

YES: 5 drivers active (PixelAnim, NTP, SM16703P, IR, DDP), total: 33
p.kaczmarek2 wrote:
Are there any messages from the IR driver in the Web App log?

Total silence
p.kaczmarek2 wrote:
Do you have PowerSave enabled? It messes up IR - remove PowerSave from the command line.

By the logs from MQTT there was powersave, I put PowerSave 0 and it's gone, but still silence
#11 21806444 12 Jan 2026 12:53

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #11
21806444 12 Jan 2026 12:53

Show a photo of the board where the IR sensor is and/or test with a multimeter (with the device switched off) whether it is physically connected to the Beken pin, or perhaps via some transistor?

Alternatively, also check from Github the IRRemoteESP variant, this is the other library for IR, another implementation of the

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#12 21806527 12 Jan 2026 14:04

Mad_Maxs Mad_Maxs

Level 12

» | Topic author Helpful post? (0)

Post #12
21806527 12 Jan 2026 14:04

>>21806444

The IR diode is at the end of this short cable, at the bottom is the blue IR, which goes via a capacitor to the 23rd pin of the chip, and with a second capacitor to the 17th
#13 21806662 12 Jan 2026 15:51

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #13
21806662 12 Jan 2026 15:51

And what is the tuya config from this device?

Does the IR receiver, when you power the strip normally from the power supply, have 3.3V on one of its pins?

I'm starting to wonder if it's that one of the GPIO pins on this device is just switching on the power to the IR receiver, but I don't know, I'm guessing.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#14 21806906 12 Jan 2026 20:33

Mad_Maxs Mad_Maxs

Level 12

» | Topic author Helpful post? (0)

Post #14
21806906 12 Jan 2026 20:33

p.kaczmarek2 wrote:
And what does the tuya config look like with this device?

I used the predefined setting for the Sky-Lighting RGB lighting bar , ready-made templates. The only thing I changed is that I switch on the IR controller by hand.
p.kaczmarek2 wrote:
Does the IR receiver, when you power the bar normally from the power supply, have 3.3V on one of its pins?

Yes, I have 3.3V on IR+ and 2.12V on the blue IR

Added after 13 [minutes]:

It's always darkest under the lantern....
Instead of IRRec I had RCRec selected. In the template curiously it is correct and several times I set it up and it didn't go in.
Anyway, after changing it and adding it to the startDriver autostart, IR works just fine 😀
#15 21807170 13 Jan 2026 04:21

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #15
21807170 13 Jan 2026 04:21

Where did RCRecv come from? That would clarify things. For future reference I guess I need to ask for config screenshots straight away, that would speed things up. So now everything works as it should?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#16 21807202 13 Jan 2026 07:31

Mad_Maxs Mad_Maxs

Level 12

» | Topic author Helpful post? (0)

Post #16
21807202 13 Jan 2026 07:31

p.kaczmarek2 wrote:
Why RCRecv? That would explain things.

This is a great question. I've been fiddling with transferring this to other pins and then probably chose RCRec instead of IRRec in error
p.kaczmarek2 wrote:
So now everything works as it should?

Yes, everything is currently working as it should.
#17 21807207 13 Jan 2026 07:55

divadiow divadiow

Level 38

Helpful post? (0)

Post #17
21807207 13 Jan 2026 07:55

for the record, just confirming extracted config from the backup you sent:

Code: Text
Log in, to see the code

boot log:
Code: Text
Log in, to see the code
#18 21807327 13 Jan 2026 10:22

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #18
21807327 13 Jan 2026 10:22

@Mad_Maxs now all it asks is to make a modification and add some kind of temperature and humidity sensor.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#19 21807451 13 Jan 2026 13:01

Mad_Maxs Mad_Maxs

Level 12

» | Topic author Helpful post? (0)

Post #19
21807451 13 Jan 2026 13:01

>>21807327
Only it would need to be moved outside the housing, as the chip gets quite hot during lamp operation.
Alternatively, glue some small heatsink to it (there is some space on the chip side).
#20 21807476 13 Jan 2026 13:32

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #20
21807476 13 Jan 2026 13:32

Outside the enclosure is best. Or the DS18B20 the one on the cable, which is easy to buy. @max4electrode keeps a driver for it (thank you!). This is an LED controller, there is 12V there, you can boldly lead outside the housing, even if someone were to break the sensor.

The only thing is not to lead anything outside the casing in the case of devices powered from 230 V and having a non-isolated inverter, as a rule such are on BP2525. Then there is a risk of shock.

Was the other LED controller repaired successfully?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#21 21807539 13 Jan 2026 21:51

Mad_Maxs Mad_Maxs

Level 12

» | Topic author Helpful post? (0)

Post #21
21807539 13 Jan 2026 21:51

p.kaczmarek2 wrote:
Beyond the housing it is best to lead. Or the DS18B20 the one on the cable

The DS18B20 is just a temperature measurement and you wrote about humidity, this confused me
p.kaczmarek2 wrote:
This second LED controller has been repaired?

The other one? I ran the other thread on the socket topic, but the LED controller I have is one

Added after 6 [hours] 58 [minutes]:

It is worth adding that you have to add Powersave 0 to autoexec.bat, otherwise the infrared doesn't actually work.

I discovered today after work that the remote is again unresponsive, but after punching in the execute command, the remote caught on immediately
#22 21808306 14 Jan 2026 09:14

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #22
21808306 14 Jan 2026 09:14

Lots of sensors are supported, it depends what you need. DS18B20 is just temperature.

PowerSave doesn't turn itself on, if you have it turned on it has to be entered somewhere.

IR events have to be in autoexec.bat, otherwise the device will not set them after a reboot.

I'll have a look at the thread about your other device soon.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
Create an account, log in here. You will receive points by participating in discussions.
Join this discussion.

Install Elektroda application

Reply | New topic

Report a violation of the law

FAQ

TL;DR: If your Action BK7231N light bar loses Wi‑Fi after flashing, this 2 MB device may need a bootloader overwrite; “This is not a bootloader flashing error.” Enable the IR driver and disable PowerSave to regain remote control. [Elektroda, p.kaczmarek2, post #21805955]

Why it matters: It speeds up recovery when OpenBeken flashes succeed but the device won’t boot or the IR remote stays silent, saving hours of trial and error.

Quick Facts

Flash memory: 2 MB (TH25Q16HB; MID 1560EB) detected during flashing. [Elektroda, Mad_Maxs, post #21805082]
OpenBK7231N_QIO_1.18.135.bin image size loaded: 1,220,464 bytes. [Elektroda, Mad_Maxs, post #21805082]
“Skip bootloader” message is normal unless you explicitly choose overwrite. [Elektroda, p.kaczmarek2, post #21805955]
Overwriting bootloader and writing OBK config restored Wi‑Fi and normal boot. [Elektroda, Mad_Maxs, post #21806212]
IR receive is on GPIO26 in the original config; ensure the IR driver is enabled. [Elektroda, Mad_Maxs, post #21806347]

How do I fix no Wi‑Fi after flashing OpenBK7231N?

Reflash with the “overwrite bootloader” option enabled, then write back your OBK config. After reboot, the bar should join your Wi‑Fi and operate normally. Selecting the Sky‑lighting RGB Light Bar profile afterward restored full control for the user who reported this. [Elektroda, Mad_Maxs, post #21806212]

What does “Using hack to write QIO – just skip bootloader…” mean?

It indicates the tool will not overwrite the factory bootloader. That state is normal when the overwrite option is not selected. As the maintainer said, “This is not a bootloader flashing error.” If recovery fails, try enabling overwrite on the next flash. [Elektroda, p.kaczmarek2, post #21805955]

Should I overwrite the bootloader on BK7231N?

Usually no. The factory bootloader remains by default. If your device won’t boot or logs are missing on TX2, you can retry flashing with the overwrite option to restore the loader and test again. [Elektroda, p.kaczmarek2, post #21805955]

How do I enable the IR driver in OpenBeken?

From the console, run: startDriver IR. Confirm IR appears in the active drivers list on the main panel. If absent, add the command to startup so it loads on every boot. [Elektroda, Mad_Maxs, post #21806347]

Why does my IR remote show nothing in the Web App log?

Map remote codes to actions in autoexec.bat and watch the Web App log while pressing buttons. If no codes appear, the driver, pin mapping, or power-saving may be blocking reception. [Elektroda, p.kaczmarek2, post #21806326]

Which GPIO is the IR receiver on for this Action light bar?

GPIO26, according to the original configuration extracted by the user. If you moved IRRecv elsewhere with GPIO Finder, revert to 26 and retest. [Elektroda, Mad_Maxs, post #21806332]

Does PowerSave break IR reception, and how do I disable it?

Yes. PowerSave can interfere with IR. Disable it from the console with: PowerSave 0. Recheck the Web App log for IR messages after disabling. [Elektroda, p.kaczmarek2, post #21806363]

How do I capture device logs (TX2) for troubleshooting?

Connect to the TX2 pin to view boot/runtime logs, as the platform emits serial output there. If you still see nothing, reflash with bootloader overwrite and test again. [Elektroda, p.kaczmarek2, post #21805955]

How can I verify the IR hardware is actually wired to BK7231N?

Open the case and photograph the IR receiver area. With power off, use a multimeter to trace the IR output pin to the BK7231N GPIO or any intermediary transistor. Fix wiring before retesting software. [Elektroda, p.kaczmarek2, post #21806444]

What is OpenBeken (OpenBK7231N) in this context?

It’s the firmware image targeting BK7231N chips, such as OpenBK7231N_QIO_1.18.135.bin, which you flash over UART to replace stock software and gain web control. [Elektroda, Mad_Maxs, post #21805082]

How do I restore or reuse the factory backup if the device won’t boot?

If a simple restore fails, reflash while enabling bootloader overwrite using your factory backup. This can revive boot and re-enable TX2 logging for further checks. [Elektroda, p.kaczmarek2, post #21805955]

What baud rate and port settings worked during flashing?

The session used COM3 at 115200 baud during flash and verification. Match these when reproducing the procedure, then adjust only if your adapter requires it. [Elektroda, Mad_Maxs, post #21805082]

How large is the flash, and does erase count matter?

This device reports a 2 MB TH25Q16HB flash. The tool erased 281 sectors before writing, then verified with a CRC match. Those stats confirm full image coverage during the session. [Elektroda, Mad_Maxs, post #21805082]

How do I map IR buttons to actions quickly?

Use the autoexec.bat mapping approach demonstrated by the maintainer and confirm button presses appear in the Web App log. “Map pilot codes to actions,” then test each function. [Elektroda, p.kaczmarek2, post #21806326]

Recovery steps after a bad flash (3‑step How‑To)

Reflash OpenBK7231N with “overwrite bootloader” enabled.
Write your OBK config and reboot; join Wi‑Fi.
Select the Sky‑lighting RGB Light Bar profile and verify control.
[Elektroda, Mad_Maxs, post #21806212]