logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

WBR2, WBR3, WBRU, W701-VA2-CG pinout, datasheet, flashing for Home Assistant

p.kaczmarek2 17844 163
ADVERTISEMENT
Report a violation of the law
Reply Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
  • #121 21727461
    p.kaczmarek2
    Moderator Smart Home  
    Nice, it read:

    Code: text Expand Select all Copy to clipboard
    
Backup name has not been set, so output file will only contain flash type/date.
Now is: wtorek, 21 października 2025 21:23:32.
Flasher mode: RTL87X0C
Going to open port: COM15.
Port ready!
Flash ID: 0xEF4015
2MB flash size detected
Starting read...
Read parms: start 0x00 (sector 0), len 0x200000 (512 sectors)
Setting baud rate to 921600
Reading at 0x001000... Reading at 0x002000... Reading at 0x003000... Reading at 0x004000... Reading at 0x005000... Reading at 0x006000... Reading at 0x007000... Reading at 0x008000... Reading at 0x009000... Reading at 0x00A000... Reading at 0x00B000... Reading at 0x00C000... Reading at 0x00D000... Reading at 0x00E000... Reading at 0x00F000... Reading at 0x010000... Reading at 0x011000... Reading at 0x012000... Reading at 0x013000... Reading at 0x014000... Reading at 0x015000... Reading at 0x016000... Reading at 0x017000... Reading at 0x018000... Reading at 0x019000... Reading at 0x01A000... Reading at 0x01B000... Reading at 0x01C000... Reading at 0x01D000... Reading at 0x01E000... Reading at 0x01F000... Reading at 0x020000... Reading at 0x021000... Reading at 0x022000... Reading at 0x023000... Reading at 0x024000... Reading at 0x025000... Reading at 0x026000... Reading at 0x027000... Reading at 0x028000... Reading at 0x029000... Reading at 0x02A000... Reading at 0x02B000... Reading at 0x02C000... Reading at 0x02D000... Reading at 0x02E000... Reading at 0x02F000... Reading at 0x030000... Reading at 0x031000... Reading at 0x032000... Reading at 0x033000... Reading at 0x034000... Reading at 0x035000... Reading at 0x036000... Reading at 0x037000... Reading at 0x038000... Reading at 0x039000... Reading at 0x03A000... Reading at 0x03B000... Reading at 0x03C000... Reading at 0x03D000... Reading at 0x03E000... Reading at 0x03F000... Reading at 0x040000... Reading at 0x041000... Reading at 0x042000... Reading at 0x043000... Reading at 0x044000... Reading at 0x045000... Reading at 0x046000... Reading at 0x047000... Reading at 0x048000... Reading at 0x049000... Reading at 0x04A000... Reading at 0x04B000... Reading at 0x04C000... Reading at 0x04D000... Reading at 0x04E000... Reading at 0x04F000... Reading at 0x050000... Reading at 0x051000... Reading at 0x052000... Reading at 0x053000... Reading at 0x054000... Reading at 0x055000... Reading at 0x056000... Reading at 0x057000... Reading at 0x058000... Reading at 0x059000... Reading at 0x05A000... Reading at 0x05B000... Reading at 0x05C000... Reading at 0x05D000... Reading at 0x05E000... Reading at 0x05F000... Reading at 0x060000... Reading at 0x061000... Reading at 0x062000... Reading at 0x063000... Reading at 0x064000... Reading at 0x065000... Reading at 0x066000... Reading at 0x067000... Reading at 0x068000... Reading at 0x069000... Reading at 0x06A000... Reading at 0x06B000... Reading at 0x06C000... Reading at 0x06D000... Reading at 0x06E000... Reading at 0x06F000... Reading at 0x070000... Reading at 0x071000... Reading at 0x072000... Reading at 0x073000... Reading at 0x074000... Reading at 0x075000... Reading at 0x076000... Reading at 0x077000... Reading at 0x078000... Reading at 0x079000... Reading at 0x07A000... Reading at 0x07B000... Reading at 0x07C000... Reading at 0x07D000... Reading at 0x07E000... Reading at 0x07F000... Reading at 0x080000... Reading at 0x081000... Reading at 0x082000... Reading at 0x083000... Reading at 0x084000... Reading at 0x085000... Reading at 0x086000... Reading at 0x087000... Reading at 0x088000... Reading at 0x089000... Reading at 0x08A000... Reading at 0x08B000... Reading at 0x08C000... Reading at 0x08D000... Reading at 0x08E000... Reading at 0x08F000... Reading at 0x090000... Reading at 0x091000... Reading at 0x092000... Reading at 0x093000... Reading at 0x094000... Reading at 0x095000... Reading at 0x096000... Reading at 0x097000... Reading at 0x098000... Reading at 0x099000... Reading at 0x09A000... Reading at 0x09B000... Reading at 0x09C000... Reading at 0x09D000... Reading at 0x09E000... Reading at 0x09F000... Reading at 0x0A0000... Reading at 0x0A1000... Reading at 0x0A2000... Reading at 0x0A3000... Reading at 0x0A4000... Reading at 0x0A5000... Reading at 0x0A6000... Reading at 0x0A7000... Reading at 0x0A8000... Reading at 0x0A9000... Reading at 0x0AA000... Reading at 0x0AB000... Reading at 0x0AC000... Reading at 0x0AD000... Reading at 0x0AE000... Reading at 0x0AF000... Reading at 0x0B0000... Reading at 0x0B1000... Reading at 0x0B2000... Reading at 0x0B3000... Reading at 0x0B4000... Reading at 0x0B5000... Reading at 0x0B6000... Reading at 0x0B7000... Reading at 0x0B8000... Reading at 0x0B9000... Reading at 0x0BA000... Reading at 0x0BB000... Reading at 0x0BC000... Reading at 0x0BD000... Reading at 0x0BE000... Reading at 0x0BF000... Reading at 0x0C0000... Reading at 0x0C1000... Reading at 0x0C2000... Reading at 0x0C3000... Reading at 0x0C4000... Reading at 0x0C5000... Reading at 0x0C6000... Reading at 0x0C7000... Reading at 0x0C8000... Reading at 0x0C9000... Reading at 0x0CA000... Reading at 0x0CB000... Reading at 0x0CC000... Reading at 0x0CD000... Reading at 0x0CE000... Reading at 0x0CF000... Reading at 0x0D0000... Reading at 0x0D1000... Reading at 0x0D2000... Reading at 0x0D3000... Reading at 0x0D4000... Reading at 0x0D5000... Reading at 0x0D6000... Reading at 0x0D7000... Reading at 0x0D8000... Reading at 0x0D9000... Reading at 0x0DA000... Reading at 0x0DB000... Reading at 0x0DC000... Reading at 0x0DD000... Reading at 0x0DE000... Reading at 0x0DF000... Reading at 0x0E0000... Reading at 0x0E1000... Reading at 0x0E2000... Reading at 0x0E3000... Reading at 0x0E4000... Reading at 0x0E5000... Reading at 0x0E6000... Reading at 0x0E7000... Reading at 0x0E8000... Reading at 0x0E9000... Reading at 0x0EA000... Reading at 0x0EB000... Reading at 0x0EC000... Reading at 0x0ED000... Reading at 0x0EE000... Reading at 0x0EF000... Reading at 0x0F0000... Reading at 0x0F1000... Reading at 0x0F2000... Reading at 0x0F3000... Reading at 0x0F4000... Reading at 0x0F5000... Reading at 0x0F6000... Reading at 0x0F7000... Reading at 0x0F8000... Reading at 0x0F9000... Reading at 0x0FA000... Reading at 0x0FB000... Reading at 0x0FC000... Reading at 0x0FD000... Reading at 0x0FE000... Reading at 0x0FF000... Reading at 0x100000... Reading at 0x101000... Reading at 0x102000... Reading at 0x103000... Reading at 0x104000... Reading at 0x105000... Reading at 0x106000... Reading at 0x107000... Reading at 0x108000... Reading at 0x109000... Reading at 0x10A000... Reading at 0x10B000... Reading at 0x10C000... Reading at 0x10D000... Reading at 0x10E000... Reading at 0x10F000... Reading at 0x110000... Reading at 0x111000... Reading at 0x112000... Reading at 0x113000... Reading at 0x114000... Reading at 0x115000... Reading at 0x116000... Reading at 0x117000... Reading at 0x118000... Reading at 0x119000... Reading at 0x11A000... Reading at 0x11B000... Reading at 0x11C000... Reading at 0x11D000... Reading at 0x11E000... Reading at 0x11F000... Reading at 0x120000... Reading at 0x121000... Reading at 0x122000... Reading at 0x123000... Reading at 0x124000... Reading at 0x125000... Reading at 0x126000... Reading at 0x127000... Reading at 0x128000... Reading at 0x129000... Reading at 0x12A000... Reading at 0x12B000... Reading at 0x12C000... Reading at 0x12D000... Reading at 0x12E000... Reading at 0x12F000... Reading at 0x130000... Reading at 0x131000... Reading at 0x132000... Reading at 0x133000... Reading at 0x134000... Reading at 0x135000... Reading at 0x136000... Reading at 0x137000... Reading at 0x138000... Reading at 0x139000... Reading at 0x13A000... Reading at 0x13B000... Reading at 0x13C000... Reading at 0x13D000... Reading at 0x13E000... Reading at 0x13F000... Reading at 0x140000... Reading at 0x141000... Reading at 0x142000... Reading at 0x143000... Reading at 0x144000... Reading at 0x145000... Reading at 0x146000... Reading at 0x147000... Reading at 0x148000... Reading at 0x149000... Reading at 0x14A000... Reading at 0x14B000... Reading at 0x14C000... Reading at 0x14D000... Reading at 0x14E000... Reading at 0x14F000... Reading at 0x150000... Reading at 0x151000... Reading at 0x152000... Reading at 0x153000... Reading at 0x154000... Reading at 0x155000... Reading at 0x156000... Reading at 0x157000... Reading at 0x158000... Reading at 0x159000... Reading at 0x15A000... Reading at 0x15B000... Reading at 0x15C000... Reading at 0x15D000... Reading at 0x15E000... Reading at 0x15F000... Reading at 0x160000... Reading at 0x161000... Reading at 0x162000... Reading at 0x163000... Reading at 0x164000... Reading at 0x165000... Reading at 0x166000... Reading at 0x167000... Reading at 0x168000... Reading at 0x169000... Reading at 0x16A000... Reading at 0x16B000... Reading at 0x16C000... Reading at 0x16D000... Reading at 0x16E000... Reading at 0x16F000... Reading at 0x170000... Reading at 0x171000... Reading at 0x172000... Reading at 0x173000... Reading at 0x174000... Reading at 0x175000... Reading at 0x176000... Reading at 0x177000... Reading at 0x178000... Reading at 0x179000... Reading at 0x17A000... Reading at 0x17B000... Reading at 0x17C000... Reading at 0x17D000... Reading at 0x17E000... Reading at 0x17F000... Reading at 0x180000... Reading at 0x181000... Reading at 0x182000... Reading at 0x183000... Reading at 0x184000... Reading at 0x185000... Reading at 0x186000... Reading at 0x187000... Reading at 0x188000... Reading at 0x189000... Reading at 0x18A000... Reading at 0x18B000... Reading at 0x18C000... Reading at 0x18D000... Reading at 0x18E000... Reading at 0x18F000... Reading at 0x190000... Reading at 0x191000... Reading at 0x192000... Reading at 0x193000... Reading at 0x194000... Reading at 0x195000... Reading at 0x196000... Reading at 0x197000... Reading at 0x198000... Reading at 0x199000... Reading at 0x19A000... Reading at 0x19B000... Reading at 0x19C000... Reading at 0x19D000... Reading at 0x19E000... Reading at 0x19F000... Reading at 0x1A0000... Reading at 0x1A1000... Reading at 0x1A2000... Reading at 0x1A3000... Reading at 0x1A4000... Reading at 0x1A5000... Reading at 0x1A6000... Reading at 0x1A7000... Reading at 0x1A8000... Reading at 0x1A9000... Reading at 0x1AA000... Reading at 0x1AB000... Reading at 0x1AC000... Reading at 0x1AD000... Reading at 0x1AE000... Reading at 0x1AF000... Reading at 0x1B0000... Reading at 0x1B1000... Reading at 0x1B2000... Reading at 0x1B3000... Reading at 0x1B4000... Reading at 0x1B5000... Reading at 0x1B6000... Reading at 0x1B7000... Reading at 0x1B8000... Reading at 0x1B9000... Reading at 0x1BA000... Reading at 0x1BB000... Reading at 0x1BC000... Reading at 0x1BD000... Reading at 0x1BE000... Reading at 0x1BF000... Reading at 0x1C0000... Reading at 0x1C1000... Reading at 0x1C2000... Reading at 0x1C3000... Reading at 0x1C4000... Reading at 0x1C5000... Reading at 0x1C6000... Reading at 0x1C7000... Reading at 0x1C8000... Reading at 0x1C9000... Reading at 0x1CA000... Reading at 0x1CB000... Reading at 0x1CC000... Reading at 0x1CD000... Reading at 0x1CE000... Reading at 0x1CF000... Reading at 0x1D0000... Reading at 0x1D1000... Reading at 0x1D2000... Reading at 0x1D3000... Reading at 0x1D4000... Reading at 0x1D5000... Reading at 0x1D6000... Reading at 0x1D7000... Reading at 0x1D8000... Reading at 0x1D9000... Reading at 0x1DA000... Reading at 0x1DB000... Reading at 0x1DC000... Reading at 0x1DD000... Reading at 0x1DE000... Reading at 0x1DF000... Reading at 0x1E0000... Reading at 0x1E1000... Reading at 0x1E2000... Reading at 0x1E3000... Reading at 0x1E4000... Reading at 0x1E5000... Reading at 0x1E6000... Reading at 0x1E7000... Reading at 0x1E8000... Reading at 0x1E9000... Reading at 0x1EA000... Reading at 0x1EB000... Reading at 0x1EC000... Reading at 0x1ED000... Reading at 0x1EE000... Reading at 0x1EF000... Reading at 0x1F0000... Reading at 0x1F1000... Reading at 0x1F2000... Reading at 0x1F3000... Reading at 0x1F4000... Reading at 0x1F5000... Reading at 0x1F6000... Reading at 0x1F7000... Reading at 0x1F8000... Reading at 0x1F9000... Reading at 0x1FA000... Reading at 0x1FB000... Reading at 0x1FC000... Reading at 0x1FD000... Reading at 0x1FE000... Reading at 0x1FF000... Reading at 0x200000... 
Getting hash...
Hash matches 7478C689FC87C59CE258D35CBBB6A635CEACE4F2958CC0FA06BD4B34B341326D!
Read complete!
Wrote 2097152 to readResult_RTL87X0C_2025-21-10-21-25-39.bin
Backup created, now will attempt to extract OBK config.
OBK config not found.
Backup created, now will attempt to extract Tuya config.
Tuya config extractor - magic is at 1933312 
WARNING - strange nextblock header 66C3BAF7
WARNING - bad nextblock CRC
WARNING - strange nextblock header 66C3BAF7
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
WARNING - strange nextblock header 346C86F8
WARNING - bad nextblock CRC
Saving debug Tuya decryption data to lastRawDecryptedStrings.bin
Tuya keys extraction has found 1 keys
Tuya config extracted and shown.
MAC seems to be 00:00:00:00:00:00

    Screenshot of BK7231Flasher interface with Tuya config extraction window open
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #122 21750538
    divadiow
    Level 37  
    >>21714597

    interesting. BroadLink app allows you to do a manual firmware update

    Code: Text
    Log in, to see the code



    BroadLink app screen showing firmware is up to date, version v62092
  • #123 21759343
    NODeeJay
    Level 2  
    >>21719359 I would be interested, actually, I would need to remix it to fit on a Proficook kettle with WBR3.
  • #125 21761990
    p.kaczmarek2
    Moderator Smart Home  
    @NODeeJay sure, feel free to remix and let us know - how did it go with your WBR3 Kettle?
    Also, is your kettle similar to my one? https://www.elektroda.com/news/news4147359.html
    Helpful post? Buy me a coffee.
  • #126 21762995
    moviesakbar
    Level 3  
    I have a Daewoo Room heater with same WBR3 , i flashed openbeken which works fine but tuyamcu driver doesnt work, if I declare tuyamcu driver in autoexec.bat or startup command, the device boots into safe mode,

    Here is my config
    Code: JSON
    Log in, to see the code




    This is raw jason fine extracted by tinytuya

    Code: JSON
    Log in, to see the code

    Green PCB with SIM800L module and colored jumper wires attached

    Close-up of green PCB with IC labeled AP2003 and various SMD components

    Close-up of a green circuit board with an IC labeled 5228



    Control panel of a device with both relays off and system status information
  • #127 21763490
    divadiow
    Level 37  
    moviesakbar wrote:
    I have a Daewoo Room heater with same WBR3


    from the Tuya backup you sent me:

    boot log
    Code: Text
    Log in, to see the code


    full dpID
    Code: JSON
    Log in, to see the code
  • ADVERTISEMENT
  • #128 21764279
    divadiow
    Level 37  
    moviesakbar wrote:
    i flashed openbeken which works fine but tuyamcu driver doesnt work, if I declare tuyamcu driver in autoexec.bat or startup command, the device boots into safe mode,


    if you clear your autoexec and startup command, reboot, then run startdriver tuyamcu ad-hoc, does the driver start without rebooting device?

    where did this command come from?

    tuyaMcu_queryAll
  • #129 21764606
    moviesakbar
    Level 3  
    >>21764279

    That's a mistake, instead of tuyaMcu_sendQueryState, I typed tuyaMcu_queryAll
  • #130 21805828
    geniack
    Level 6  
    Hello, I am new here!

    I am trying to flash my cheap RTL8720 based thermostats. I managed to desolder my WBR3 module and was able to get some serial output from the original firmware by wiring it up and using realterm to see the output.

    My problem is, as soon as I am trying to flash with the AmebaZII tool, I see some download progress bars but at some point the application hangs and the download progress will not advance and then the application says "fail" and complains about XMODEM timeouts.

    AmebaZ2 PG Tool 1.2.47 interface showing firmware download failure message

    I am not exactly sure what I am doing wrong, help is highly appreciated. I am using an FTDI232, I just ordered a CH340 because it was mentioned in the instructions, but I dont believe this will change anything.

    That is what my setup looks like right now:

    WBR3 module connected to USB-TTL adapter on a breadboard
  • #131 21806828
    DeDaMrAz
    Level 21  
    Quote:
    IMPORTANT!!! in order to set the WBRG1 module into download/bootloader mode, connect UART (GND, 3V3, Rx and Tx) to P1 , pull ENABLE pin to GND, pull LogTX pin to GND via 2k2-4k7 resistor, disconnect ENABLE pin, then disconnect the resistor from LogTX line - device will be in bootloader mode!!


    This applies to WBR3 module as well just different pin names, did you follow this procedure??

    And you can also use out UART flasher for that - https://github.com/openshwprojects/BK7231GUIFlashTool/releases/tag/v207
  • #132 21806846
    geniack
    Level 6  
    >>21806828
    Hey! Thank you for the quick reply. What is meant by "P1" ?

    I have connected RXD and A_0 to 3,3v (pulling it high?). A_15 to UART TX and RXD to UART RX. UART GND is connected to common GND. EN pin is not connected. I have no resistor in my wiring, should I add one?

    When I boot up this way, I can see this output:

    Screenshot of a console displaying Rt18710c platform boot messages

    If I dont connect RXD and A_0 I will see a lot more output which looks like a tuya device booting up. When shorting EN to GND the device will reboot it seems.
    So for me it looks like I am already getting into bootloader mode. The AmebaZII detects the port and will start to flash but as I said its stopping during download and reports a fail.

    Thank you so much.

    Kind regards

    P.S.: I tried downloading this flashing tool earlier but Windows Defender will remove it immediately and will report a trojan.
  • ADVERTISEMENT
  • #133 21806873
    DeDaMrAz
    Level 21  
    Looks like you are in the download mode already which is perfect, try lowering the baud rate and see what Flash status GET gives you? Some of the USB to UART chips are fussy about certain baud rates so first try with some lower value and see what will work for you. Also double check your wiring just in case - remember Tx from USB goes to RX on the module and Rx from USB goes to TX on the module.

    On the Defender detection, two options, compile it on your own from the source or ignore the warning as the trigger is that we have an option to download latest OBK releases from Github. We had that issue before and I thought it was resolved but it keeps returning unfortunately.
  • #134 21806893
    geniack
    Level 6  
    >>21806873

    This is what Get will result in:

    Software interface showing Unlocked status and connected to COM7 port

    This is right after clicking download again (with 115200, same as I used for Get and same as in RealTerm to see the output) :


    AmebaZ2 PG Tool interface showing firmware download error and failure

    If TX/RX wiring is wrong I wouldn't see output in RealTerm, right?

    You think the other flasher might solve the problem or is it just more convenient? :)

    When the download process starts I can see the LED of the uart converter start flashing, then it stops all of a sudden, thats when the progress bar in the flasher freezes.

    You think using a CH340 based flasher might help?
  • #135 21806899
    DeDaMrAz
    Level 21  
    geniack wrote:
    You think the other flasher might solve the problem or is it just more convenient?


    Well that other flasher is our own development and it will certainly work and solve the problem + it is more convenient :)

    You are right you would not get the RealTerm output so your wiring is right, at least the Rx part. Try CH340 you got nothing to lose.

    You are close and that module is the "worse" to deal with honestly.
  • ADVERTISEMENT
  • #137 21807086
    insmod
    Level 30  
    Increase baud rate to something like 921600 or 1500000.
    And use read only button for now
  • #138 21807095
    geniack
    Level 6  
    Oh! With 150000 I get new errors, this means progress!! :)


    BK7231 Easy UART Flasher window showing flash memory read error
  • #139 21807105
    insmod
    Level 30  
    >>21807095
    Reduce it somewhat. Those errors mean that there is some UART interference.
    Most probable cause - wires are too long.
  • #140 21807117
    geniack
    Level 6  
    I actually tried ALL baud rates and the only one that was giving me at least these kind of errors was 150000. The other ones produced the Length < 16 parts error. I have attached a picture of my setup a few posts above, you think those wires are too long?
  • #142 21807149
    geniack
    Level 6  
    >>21807139
    I am sure I have tried it before but I didn't try it during my recent tests. Is this something that is required?
  • #143 21807156
    insmod
    Level 30  
    From what i see, the problem isn't with wires, but might be with the adapter.
    Those FT232 are often fake.
  • #144 21807157
    DeDaMrAz
    Level 21  
    I have no experience with FTDI, haven't used them since FTDIGate, CP2101 and CH430/1/2 on my end and no problems at all... and also haven't flashed RTL chips in some time now.... I can test more tomorrow as my water heater project is almost complete.
  • #145 21807397
    p.kaczmarek2
    Moderator Smart Home  
    Related (same chip core) guide has been published - flashind MSS810HK-UN V7.0 compatible with Meross app with RTL8710CM.
    https://www.elektroda.com/rtvforum/topic4160849.html

    @divadiow , if you have moment, please make a list of guides that are using obsolete tools, since @insmod did great work with the flasher and send it to me via PM. I will update them later, by adding separate paragraphs saying that new tool is available and preferred. The old guides will stay as reference, but they will also now contain section about Easy Flasher, so people can choose.
    Helpful post? Buy me a coffee.
  • #148 21809020
    insmod
    Level 30  
    >>21809005
    Yes you can. The backup you took is a proper copy of RTL flash, since hash check passed.
    You can flash it now without further problems.

    But considering you already tried to flash it with PG tool, original firmware is probably lost.
  • #149 21809024
    geniack
    Level 6  
    >>21809020

    Thank you for the input!

    Is there anything I would need the original firmware for? I never used the device in it's original form and all I want to do is connect it to home assistant.
Reply Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
Report a violation of the law

Topic summary

The discussion centers on flashing and integrating Tuya modules based on the RTL8720CF chip (W701-VA2-CG), including WBR1, WBR2, WBR3, WBR2L, WBR3L, and WBRU, for cloud-free operation with Home Assistant (HA) using the AmebaZ2 PG Tool and OpenBK7231T (OBK) firmware. Detailed pinouts, flashing jigs, and boot logs are shared, highlighting the need to access specific pins (A0, A15, A16) often located on the PCB underside, sometimes requiring desoldering. Users report successful flashing on devices like Kasa HS200, Gosund SP1 (BL097), and Tapo P110, with calibration support for BL0937 power monitoring chips. Challenges include reading and backing up firmware, especially system and calibration data, which may be stored in efuse or inaccessible flash areas. The community collaborates on templates for device configuration, MQTT integration, and HA discovery, including channel type mappings (e.g., OpenStopClose, LowMidHigh, dimmer) for TuyaMCU protocols. OTA updates and UART communication are tested, with ongoing development of tools and firmware support for these Realtek-based modules. Additional discussion covers the similarity between WBR3 and WBRU modules for firmware transplantation and the presence of Tuya config partitions. The thread also touches on related devices like thermostats (WT50-WH-3A, WT100-WH-3A, WT200-16A-W, HY609-WE) and the FR8016HA MCU in some modules. Overall, the topic provides a comprehensive guide and collaborative troubleshooting for flashing, configuring, and integrating RTL8720CF-based Tuya modules with open-source firmware and Home Assistant.
Summary generated by the language model.
Today's popular
ADVERTISEMENT