Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Short answer: this is a hardware transplant, not a normal firmware upgrade. You remove the Broadlink 3323 module from a compatible RM Mini 3 PCB, install an ESP-12E or ESP-12F ESP8266, reconnect the board’s power, serial and IR circuits, then flash local firmware such as Tasmota.
The best-documented example uses an RM Mini 3 PCB revision 1.5 and an ESP-12E. Its GPIO assignments are useful starting points, but they are not universal: verify the IR receiver and transmitter traces on your own board before soldering.
What the conversion changes
The RM Mini 3 is the complete IR hub. The Broadlink 3323 is its original wireless/control module; it is not simply an ESP8266 waiting for a different firmware image. The documented modification removes that module and reuses the RM Mini PCB’s enclosure, power section, IR receiver, IR LEDs, button and indicator.
- Removed: Broadlink 3323 module.
- Added: ESP8266 ESP-12E (ESP-12F can be considered after checking fit and wiring).
- Retained: RM Mini PCB, IR hardware and enclosure.
- Firmware: Tasmota’s IR build, or a separately configured ESPHome/custom firmware installation.
See the original RM Mini 3 transplant report for the revision-specific build that this guide discusses.
#1 Best Overall
- Not only it is easy to program for this controller by using the CP2102-USB interface,but also unnecessary to press the flash and reset buttons before each flash operation.
- NodeMcu is an open source Lua based firmware for the ESP8266, ultra low cost wireless modules, development boards for rapid prototyping, integrated with ESP8266 chips.
- The ESP8266 has powerful on-board processing and storage capabilities, and can be integrated with sensors and other application-specific devices through its GPIOs.
- It is compatible with Arduino IDE,works great with the latest Mongoose IoT/Micropython.
- Modern Internet development tools can use the built-in API to instantly put your idea on the fast track.
Is your RM Mini a good donor?
Open the unit only when it is unplugged. Photograph both sides of the PCB, record its revision marking and identify the module actually fitted. The published wiring applies to an RM Mini 3 PCB V1.5; other revisions can move pads, change the regulator or use a different circuit.
Before committing to soldering, check:
- There is room for the ESP module and its antenna.
- The board has a clean, regulated 3.3-V rail.
- The regulator and wiring can handle ESP8266 peaks. ESP8266 guidance recommends at least 250 mA, with practical margin above that.
- You can trace the original module’s VCC, GND, TX, RX, IR-input and IR-output connections.
- The IR receiver, LED and transistor driver are still functional.
A continuity tester is more reliable than an Internet pinout. The Tasmota template database lists another RM Mini mapping—GPIO5 for receive and GPIO14 for send—showing why one template cannot be assumed for every board (template reference).
Tools and parts
| Required | Useful additions |
|---|---|
| RM Mini 3 donor; ESP-12E or ESP-12F; fine wire; fine-tip iron; flux; solder; multimeter; 3.3-V USB-to-UART adapter | Magnification; oscilloscope or logic analyzer; programmer fixture; spare resistors and capacitors; Kapton or insulating tape |
Use a genuine 3.3-V UART. TX and RX must be 3.3-V logic, grounds must be common, and an adapter’s 3.3-V pin may not supply enough current. ESPHome’s physical connection guide specifically warns that some adapters expose 5 V; applying it to an ESP8266 can destroy the module.
Map the board before removing the 3323
- Disconnect the power adapter and open the enclosure without losing the button or light pipe.
- Photograph the original module and every pad.
- Mark VCC, GND, TX and RX, then trace the receiver signal and the transistor/LED driver input.
- Measure the regulated rail with the board powered from its normal isolated low-voltage adapter.
- Check for shorts between 3.3 V and ground before attaching the ESP.
- Plan an accessible GPIO0 connection for programming.
Do not work on an exposed board connected to mains or an unisolated supply. The Broadlink adapter may be low voltage, but the safe practice is still to unplug before soldering and use an isolated source for tests.
Rank #2
- ESP8266 Breakout Board GPIO 1 into 2 Terminal Screw Board is Fully Compatible with ESP8266 ESP-12E
- GPIO 1 into 2: ESP8266 Breakout Board Can Expand 1 GPIO Pin to 2, Which is Convenient for Users to Reuse Pins for Large-Scale Smart Home Projects
- Double-Layer PCB: ESP8266 Breakout Board is a Double-Layer Board. One Pin is Wired On Both Sides. Therefore, the Circuit is Stable and Highly Reliable
- 2 Type Connections:ESP8266 Breakout Board Designed with Two Connection Methods: Pin Header Connector & Screw Terminal. Just Select Connection According to Your Need
- Convenient to USE: Compared with the Previous Version, Updated Version ESP8266 Breakout Board Has Been Soldered Completely. No Need to Solder Parts,Very Convenient to Use
ESP8266 minimum circuit
An ESP-12 module needs a stable 3.3-V supply, ground, and the normal boot straps. Provide pull-ups for GPIO0, GPIO2 and EN/CH_PD, a pull-down for GPIO15, and a reset pull-up as required by your module. Keep a decoupling capacitor close to the ESP. The RM Mini’s existing resistors may not provide every connection the ESP-12 requires, so verify them rather than assuming they are present.
Documented RM Mini V1.5 wiring
The Hackster build reports this arrangement:
| ESP8266 connection | RM Mini connection |
|---|---|
| VCC | Verified board 3.3-V rail |
| GND | Board ground |
| TX/RX | Corresponding original module serial pads |
| GPIO4 | Pad traced as IR signal input |
| GPIO5 | Pad traced as IR signal output |
| GPIO0 | Accessible programming pad, pulled to ground during boot |
This is a project-specific map, not a universal RM Mini pinout. Do not connect GPIO4/GPIO5—or GPIO14 from another template—without confirming which physical trace reaches the IR receiver and which drives the IR LED circuit. Also distinguish raw GPIO numbers from development-board labels such as D1 and D2.
Flash the replacement module
With power disconnected, wire the UART as follows:
- Adapter 3V3 → ESP VCC
- Adapter GND → ESP GND
- Adapter TX → ESP RX
- Adapter RX → ESP TX
- GPIO0 → GND while powering or resetting for flash mode
After installing the ESP and checking for shorts, test serial access before writing firmware:
esptool.py --port COM5 read_mac
esptool.py --port COM5 flash_idReplace COM5 with your port, such as /dev/ttyUSB0. Tasmota’s Getting Started guide covers current esptool usage and troubleshooting.
Rank #3
- Built-in Micro-USB, with flash and reset switches, easy to program
- Arduino compatible, works great with the latest Arduino IDE/Mongoose IoT/Micropython
- Data download access to the website: http://www;nodemcu;com
Backup and erase
If the module already contains ESP firmware, an optional backup is:
esptool.py --port COM5 read_flash 0x00000 0x100000 fwbackup.binThe 0x100000 size is only Tasmota’s example; determine the actual flash size first. It may not be useful for the original Broadlink 3323, which may not be an ESP8266 and may not respond to esptool at all. Do not promise that the original Broadlink firmware can be restored.
For a replacement module, erase only after you have confirmed communication:
Recommended Free Tools
esptool.py --port COM5 erase_flashFlash the current official Tasmota IR binary from Tasmota’s release sources. The tasmota-ir.bin build includes almost all protocols from the IRremoteESP8266 library. Remove the GPIO0-to-ground bridge and power-cycle for normal boot.
Rank #4
- NodeMCU GPIO expansion board
- NodeMCU can be connected through by Pin Header & Screw Terminal
- GPIO 1 INTO 2
Configure Tasmota IR
Connect to the device’s temporary Wi-Fi setup, configure your network and open the Tasmota web console. The historical project used:
{"NAME":"CCXX-IR","GPIO":[1,1,1,1,1056,1088,1,1,1,1,1,1,1,1],"FLAG":0,"BASE":18}Treat that JSON as a compatibility reference for the documented build, not a guaranteed current template. In the current web UI, assign the GPIO function for IR receive to the pin connected to your traced receiver signal and IR send to the pin connected to the LED-driver input. Save, reboot and inspect the resulting template.
The separate RM Mini template entry shows an older mapping with GPIO5 as IRrecv and GPIO14 as IRsend. Different PCB revisions, signal polarity, module wiring and template conventions explain such differences.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchTest receive and transmit separately
Receive
- Boot normally and open the Tasmota console.
- Point a known-good remote at the receiver.
- Press a simple button and confirm a decoded protocol or raw message appears.
- Save a known-good sample before changing wiring.
Successful decoding proves the receiver path, not the transmitter.
Best Value
- ESP8266 NodeMCU Lua ESP-12E CP2102 Development Board Module with USB C Type-C Interface, has a wider range of applications.
- Adopting the original brand new CP2102 chip with powerful functions, developing a complete set of tools for ESP8266.
- Built in Tensilica L106 ultra low power 32-bit micro MCU, with main frequency support of 80 MHz and 160 MHz
- Supports RTOS.
- Support many kinds of working modes like STAAP/STA+AP etc, support AT remote upgrade and cloud OTA , and upgrade for Smart Config function etc.
Transmit
- Place the RM Mini in line of sight of the target device.
- Start with power or volume using a known command.
- Try several distances and angles.
- If nothing happens, trace the transistor input through the IR LED driver and check polarity.
The documented builder received IR correctly but initially could not transmit. Back-tracing the LED path revealed the output connection error. A wrong GPIO, active-low/active-high assumption, damaged transistor or LED, or an incorrect Tasmota function can produce exactly this symptom. Air-conditioner remotes also send long, stateful messages, so a decoded signal does not guarantee reliable control of every AC.
MQTT and Home Assistant
Set a unique Tasmota device name and topic, then use the command topic shown by the device’s current configuration. The original project reported a working example of:
tasmota/gateway_ir/cmnd/IRHVACDo not copy that topic blindly: device name, topic settings and Tasmota version determine the actual path. Verify it in the console and use Home Assistant’s MQTT integration or Tasmota discovery after receive and transmit work locally. Tasmota can operate locally over MQTT, HTTP and its web interface, but your broker or Home Assistant installation can still introduce network dependencies.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →ESPHome alternative
ESPHome is a good Home Assistant-first option because configuration is declarative and OTA updates are available after the first serial installation. It is not a drop-in continuation of the Tasmota template: define the receiver and transmitter pins again, account for the RM Mini’s transistor polarity and test both directions. Follow ESPHome’s 3.3-V and serial guidance.
Custom Arduino firmware is appropriate only when you need unusual timing or a proprietary API. OpenBeken is relevant to Beken/Tuya hardware, not to the genuine ESP8266 transplant described here.
Troubleshooting decision tree
- No serial output: check crossed TX/RX, common ground, 3.3-V logic, GPIO0 low at boot, port selection and solder joints.
- Boot loops or brownouts: use a stronger 3.3-V regulator, shorter power wires and local decoupling; adapter power is often inadequate.
- Wi-Fi works, no receive: verify the receiver trace, GPIO function, receiver supply and electrical noise.
- Receive works, transmit fails: identify the LED-driver input, check active polarity and test the transistor/LED path independently.
- MQTT command fails: confirm the actual topic and payload in Tasmota rather than relying on an old example.
- AC control is inconsistent: capture complete stateful messages and use the correct protocol rather than treating AC remotes like simple toggle remotes.
When not to do this
This modification makes sense when the RM Mini is already stranded, its IR hardware is good and you are comfortable with fine soldering. It is a poor choice when the device still works, the revision is unknown, you lack a reliable 3.3-V supply, or a modern local IR bridge costs less than your time and tools. A development board or programmer fixture can reduce debugging risk, but a NodeMCU carrier is usually too large for the original enclosure.
Once the transplant works, insulate exposed joints, confirm Wi-Fi range and temperature, and close the case only after repeated receive/transmit tests. The modification may be permanent, and failure can leave the original Broadlink functionality unrecoverable.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
