logo elektroda
logo elektroda
X
logo elektroda

Smart Power Plug LCS Action Shop 2578685 970766 firmware upload

The_Wrecker 7383 28
ADVERTISEMENT
  • Hi,

    new time user here, but just wanted to let you know my experience with flashing to OpenBKT7231. First of all thank you for the work done on the firmware and the investigation.

    I bought a couple (5 of them) "Smart Plugs" from the Action in the Netherlands:
    Brand: LSC (Smart Connect)
    Product: Smart Power Plug
    Art. No. 2578685
    Art. No. 970766
    Both Art. No. (as listed above) were on the box, right below each other, I believe the bottom might be the more typical known in the Tuya brand, the first might be from the LSC brand (but I am not 100% sure).

    On the plug itself:
    970766 Max 16A 3680W μ T35
    220-240V~ 50/60Hz
    AL M21167 Made in P.R.C.

    Basically Tuya rebranded. The Tuya app saw the plugs.

    I used the Python script https://github.com/OpenBekenIOT/hid_download_py (under Ubuntu 22.04) to upload the firmware with a ftdi TTL 3v3 cable. Soldered some jumper wires to the TX, RX and GND. With a bit of timing, got the flashing started (this took a couple of tries to get the timing down), trick was to start the python command right before the plug got power.
    I was confident about my method here, but dealing with 230v this way, might not be the best for everyone. Plus, I kept my hand away from the plug itself (used a separate switch). Caution advised when dealing with mains.

    All 5 bought plugs have been successfully flashed. So, a 100% success rate (very nice!).

    I used to the template included in the firmware version 1.12.66 to get started:
    [BK7231N][CB2S] LSC Smart Connect Plug
    P6 LED 1 <- blue
    P7 Btn 1
    P8 LED 0 <- red (WIFILED_N)
    P26 Rel 1

    But, after some investigation, it was not 100% correct. The button worked, and you could trigger the relay, but something was off when playing with the channel and LED control. Perhaps another model? I was not sure if P8 was in the template, it might not be there.

    I traced the PCB a bit and got to the following config (which is working great up till now):
    P6 - Rel 1
    p7 - Btn 1
    P8 - Wifiled_N 0
    P26 - LED 1

    P26 == Blue LED
    P8 == Red LED

    Wifi LED (P8) just blinks when starting up searching for the network. Because it is negated, It'll be off by default. You can just set it to LED, to have it on all the time. I just left it like this, since I'd rather have it off by default. As you can see, the config is very similar to the template that was already in the firmware.

    Hope this helps someone.

    Br,

    The Wrecker

    Some pics:
    Smart Power Plug LCS Action Shop 2578685 970766 firmware upload
    Smart Power Plug LCS Action Shop 2578685 970766 firmware upload
    Smart Power Plug LCS Action Shop 2578685 970766 firmware upload
    Smart Power Plug LCS Action Shop 2578685 970766 firmware upload
    Smart Power Plug LCS Action Shop 2578685 970766 firmware upload

    Cool? Ranking DIY
    About Author
    The_Wrecker
    Level 2  
    Offline 
    The_Wrecker wrote 2 posts with rating 7. Been with us since 2022 year.
  • ADVERTISEMENT
  • #2 20219393
    p.kaczmarek2
    Moderator Smart Home
    Thank you for your feedback. Your opinion is very valuable, we have separated your post into a standalone topic.

    Tuya tends to change device internals without changing the device model number, so it's very possible that pins order was changed.

    Have you done a firmware backup/dump for tuya-cloudcutter?
    Helpful post? Buy me a coffee.
  • #3 20220178
    The_Wrecker
    Level 2  
    p.kaczmarek2 wrote:
    Thank you for your feedback. Your opinion is very valuable, we have separated your post into a standalone topic.

    Tuya tends to change device internals without changing the device model number, so it's very possible that pins order was changed.

    Have you done a firmware backup/dump for tuya-cloudcutter?


    Hi, p.kczmarek2,

    I was not aware of the change of internals under the same model, but it is indeed plausible. I think the brand of caps might've been different on some as well, but that should not be an issue, construction was otherwise the same across all of them.

    Unfortunately I did not make a dump of the original firmware. While I was playing around with the first device I did not create a dummy WiFi beforehand for it. In case I get another of these plugs (the store was sold out), I'll make sure to create a couple of dumps of said firmware.
  • #4 20220359
    p.kaczmarek2
    Moderator Smart Home
    They can change device internals very much. I have seen cases of ESP8266 module to Beken swap without device model change. For example Zmai 90. My Zmai 90 has WB3S.
    I also saw WB2S to CB2S and BL0937 to BL0942 change. That was in LSPA9 power metering socket. No differences from the outside.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #5 20334120
    blowagie
    Level 6  
    Hi,

    I also bought the LSC Power Plug but with Art. nr 2578677.

    I flashed it succesfully with OpenBK7231N_QIO_1.15.180 using Beken Writer v1.60. But when powering on, there is no Wifi (2.4GHz)/no LED.

    Smart Power Plug LCS Action Shop 2578685 970766 firmware upload

    Also tried the old version OpenBK7231N_QIO_1.12.66.

    I could restore the original firmware.

    What can I do to get the power plug working?

    Tx

    Bart
  • #6 20334170
    p.kaczmarek2
    Moderator Smart Home
    You have flashed the firmware to offset 0x11000, which is incorrect in case of BK7231N.
    You have used settings for BK7231T.


    For BK7231N, you should flash the QIO image to the offset 0, so use:
    The_Wrecker wrote:

    I used the Python script https://github.com/OpenBekenIOT/hid_download_py (under Ubuntu 22.04) to upload the firmware with a ftdi TTL 3v3 cable. Soldered some jumper wires to the TX, RX and GND. With a bit of timing, got the flashing started (this took a couple of tries to get the timing down), trick was to start the python command right before the plug got power.

    python uartprogram ./OpenBK7231N_QIO_1.15.140.bin --unprotect -d com15 -w --startaddr 0x0
    pause


    You could also TRY using bkWriter 1.60, but in BK7231N mode (not BK7231, which is used for BK7231T). And make sure that offset is 0x0, not 0x11000.
    Helpful post? Buy me a coffee.
  • #7 20334298
    blowagie
    Level 6  
    Thank you for your quick reply.

    I used python now but I'm facing another problem now.. The FW was flashing but I received Read CRC Failed after flashing.

    Plug seems to be dead now. Retrying to flash results in 'cannot get bus'
    Smart Power Plug LCS Action Shop 2578685 970766 firmware upload

    I'm using the 3.3V of the UART (CH340).

    Bart
  • ADVERTISEMENT
  • #8 20334348
    p.kaczmarek2
    Moderator Smart Home
    The command below (with unprotect):
    
    python uartprogram ./OpenBK7231N_QIO_1.15.140.bin --unprotect -d com15 -w --startaddr 0x0
    pause
    

    Is 100% correct, I flashed many devices that way.

    You might have issues with device because of the previous misguided flash attempt, but it's hard to tell, because I never tried flashing QIO to 0x11000 offset.

    Are you sure there is no Access Point?

    I hope that bootloader is OK, and if not, there is always a Recovery method in SPI mode: https://www.elektroda.com/rtvforum/topic3931424.html

    Please triple check everything, device should respond to flashing, but getting CEN reset takes several tries.
    Helpful post? Buy me a coffee.
  • #9 20334358
    blowagie
    Level 6  
    There is no AP.

    Ok I'll check the bootloader. FUN hahaha.

    I'll come back to it.

    Thanks a lot.
  • #10 20334408
    p.kaczmarek2
    Moderator Smart Home
    Are you 100% sure that device does not respond any more?

    I'd also, just to be sure, redo all connections and check again.
    Helpful post? Buy me a coffee.
  • #11 20334763
    blowagie
    Level 6  
    No,

    Is there a way to have a console output? Are that RX2 & TX2?

    I've started reading the SPI flash method, that will be tough.

    Bart
  • #12 20334773
    p.kaczmarek2
    Moderator Smart Home
    How good are your soldering skills? Maybe if you desolder whole CB2S out of the board.... it's easy if you know soldering, just some flux, solder wire...

    TX2 is a debug console output. You can read it with USB to UART converter. This might tell you what goes wrong, but I'd guess that device does not even boot.
    Helpful post? Buy me a coffee.
  • #13 20335315
    blowagie
    Level 6  
    Hi,

    I was able to desolder the board.

    I took a close pic
    ture of the board. To my suprise I see the chip is BK7231TQN32

    Bart Smart Power Plug LCS Action Shop 2578685 970766 firmware upload
  • #14 20339883
    nielspiersma
    Level 9  
    @blowagie , You're not alone :).

    I have 20 of these babies, now all updated. It seems that Tuya is shipping incorrectly labeled PCB's.

    https://github.com/tuya-cloudcutter/tuya-cloudcutter/issues/210

    You can safely use the tuya cloud cutter, and if you flash the latest firmware, you can directly configure the LEDs and relays by executing the following URL when in AP mode;

    http://192.168.4.1/cm?cmnd=backlog+SetPinRole...207,1;SetPinChannel%206,1;SetPinChannel%208,1


    Niels
  • #15 20339983
    blowagie
    Level 6  
    Thank you for this information.

    In mean time I could recover the flash using SPI. I could connect to Wifi AP. In the web interface I configured my Wifi settings SSID & PWD. But now the chip is in a loop rebooting. Log file of the console output is in the attachment.

    Pffff :evil:

    Bart
  • #17 20340057
    blowagie
    Level 6  
    I think it was OpenBK7231T_QIO_1.15.197.bin with SPI
  • #18 20340720
    blowagie
    Level 6  
    Could it be a problem with the bootloader?

    Other FW also don't work (UART, not SPI).
  • #19 20340731
    btsimonh
    Level 11  
    in user_main.c, comment out
    extended_app_waiting_for_launch()

    as a test, and try.

    (your log never sees bk_printf("\r\nMain_Init_Delay done\r\n") - so it never gets there....)

    seems maybe something is broken in the beken wait....

    Simon
  • #20 20340906
    p.kaczmarek2
    Moderator Smart Home
    @blowagie did you just restore bootloader and still have further partitions overwritten with bk7231N data, or have you restored everything from factory backup, including RF partition?
    Helpful post? Buy me a coffee.
  • #21 20340946
    blowagie
    Level 6  
    @p.kaczmarek2

    That's what I have executed:
    def WriteImage(startaddr,filename, maxSize):
    print("WriteImage "+filename)
    statinfo = os.stat(filename)
    # size = statinfo.st_size
    # size = (size+255)//256*256
    size = maxSize;

    count = 0
    addr = startaddr
    f = open(filename, "rb")

    while count < size:
    print("count "+str(count) +"/"+str(size))
    if 1:
    if 0 == (addr & 0xfff):
    CHIP_ENABLE_Command()
    send_buf = bytearray(4)
    send_buf[0] = SPI_SECTRO_ERASE_CMD
    send_buf[1] = (addr & 0xFF0000) >> 16
    send_buf[2] = (addr & 0xFF00) >> 8
    send_buf[3] = addr & 0xFF
    spi.xfer(send_buf)
    Wait_Busy_Down()

    buf = f.read(256)
    if buf:
    CHIP_ENABLE_Command()
    send_buf = bytearray(4+256)
    send_buf[0] = SPI_WRITE_PAGE_CMD
    send_buf[1] = (addr & 0xFF0000) >> 16
    send_buf[2] = (addr & 0xFF00) >> 8
    send_buf[3] = addr & 0xFF
    send_buf[4:4+256] = buf
    spi.xfer(send_buf)
    count += 256
    addr += 256

    f.close()

    return True

    WriteImage(0,"OpenBK7231T_QIO_1.15.197.bin", 0x200000)
  • ADVERTISEMENT
  • #22 20343005
    blowagie
    Level 6  
    Hi,

    At a certain point I was able to configure the pins of the power plug and put it in AP.
    The led is blinking when no device is connected to the Wifi AP. When I try to connect to de Wifi AP, the led is going off and the W2BS is rebooting. It seems more like a HW fault to me (not enough power).

    I suppose there are no settings in the bootloader regarding power settings?

    Bart
  • #23 20343246
    p.kaczmarek2
    Moderator Smart Home
    I'd restore it like that:
    Code: Python
    Log in, to see the code

    where "REST.bin" is a bkWriter 1.60 flash dump which starts at 0x11000 offset and QIO is just the bootloader source.

    This is because here "REST.bin" is not just the application - it also contains data partitions used by BK, including RF calibration

    If you need to get "REST.bin" file, here it is:


    NOTE: now that you have bootloader running, you could flash REST.bin to offset 0x11000 directly, but use hid_download_py for that and not bkWriter 1.60 because as far as I remember there is a little issue on bkWriter 1.60 which rolls around the addresses and giving 2MB file at 0x11000 offset can overwrite the 0x0 - 0x11000 sections and break bootloader again. Also try to keep flash length to 2MB - 0x11000
    Helpful post? Buy me a coffee.
  • #24 20436074
    frankvanginkel
    Level 2  
    Hoi,

    Recently I bought an LSC powerplug. After opening I found out that it contained the BK7231T with a CB2S label and was very happy to have found your project!
    After desoldering (looking back, not needed?) I flashed the firmware. Worked like a charm!!!!
    I've flashed the UA version.

    And now comes the great BUT.... After something like 8 hours the http interface stops working, so the http api is not working anymore.
    MQTT and the raw interface are still working,
    When looking at the log before http goes down I see the reported "free" value steadily going down. It starts around 88000, after 6 to 7 hours it's around 30000. And I think at around 20000 http stops.
    Disabling all flags except the raw interface.
    But I can still connect using the raw interface at port 100 and control the device!

    I have tried not to enable mqtt after a clean restart, setting loglevel to zero but to no avail.
    The device has been upgraded to the latest release, but even older relases (going back to 1.15.206 I saw that's wahet Niels Piersma used) show the same behaviour!

    What more can I do? Should I flash the UG version (cloudcutter) first? Or am I too late for that?

    Groeten,
    Frank.
  • #25 20436088
    p.kaczmarek2
    Moderator Smart Home
    The issue must be within the firmare, so flashing UG won't change anything, also it won't be possible if device already has OpenBK.

    Can you provide more information how to reproduce the issue? I can add a free memory count watchdog mechanism for you that will just restart device when in need, but that's not a correct solution.

    How do you manage to get memory leaks, what kind of browser are you using, maybe your browser is somehow not closing connection after doing HTTP request and the sockets are left open?

    Have you tried another browser?

    Can you observe the log and determine when the leak happens?

    Or maybe... maybe you can try going to Web App -> Flash -> Restore RF Partition (as a last resort), reboot, reconnect to the device (it will have new MAC) and tell me if it helped.
    Helpful post? Buy me a coffee.
  • #26 20436660
    frankvanginkel
    Level 2  
    Well, reproducing is quite simple :)
    Just start the thing with or without any configuration, open the log in the webapp and look at the lines:
    Info:MAIN:Time 1122, idle 246618/s, free 84328, MQTT 0(70), bWifi 1, secondsWithNoPing -1, socks 2/38
    Time goes up (duh :) ) and free goes down. Socks is always 2 or 3
    No need to do anything.
    The free value will decrease every now and then and restore itself to value it had before.
    Info:MAIN:Time 1662, idle 253592/s, free 84328, MQTT 0(104), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 1663, idle 248137/s, free 84328, MQTT 0(104), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 1664, idle 252916/s, free 84328, MQTT 0(104), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 1665, idle 247087/s, free 84112, MQTT 0(104), bWifi 1, secondsWithNoPing -1, socks 3/38
    Info:MAIN:Time 1666, idle 252356/s, free 84328, MQTT 0(104), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 1667, idle 250078/s, free 84328, MQTT 0(104), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 1668, idle 255938/s, free 75720, MQTT 0(104), bWifi 1, secondsWithNoPing -1, socks 3/38
    Info:MAIN:Time 1669, idle 251079/s, free 84328, MQTT 0(104), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 1670, idle 249954/s, free 84328, MQTT 0(104), bWifi 1, secondsWithNoPing -1, socks 2/38

    After some time the free value decreases:
    Info:GEN:sta:rssi=-70,ssid=zbcint1,bssid=00:25:9c:13:aa:f0 ,channel=11,cipher_type:CCMP
    Info:MAIN:Time 1781, idle 252271/s, free 83296, MQTT 0(111), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 1782, idle 255931/s, free 83296, MQTT 0(111), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 1783, idle 247360/s, free 83296, MQTT 0(111), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 1784, idle 250093/s, free 83296, MQTT 0(111), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MQTT:mqtt_host empty, not starting mqtt
    Info:MAIN:Time 1785, idle 250306/s, free 83296, MQTT 0(112), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 1786, idle 255120/s, free 83296, MQTT 0(112), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 1787, idle 249050/s, free 83296, MQTT 0(112), bWifi 1, secondsWithNoPing -1, socks 2/38

    As you can see I have not configured MQTT. Is there a way to completely disable MQTT and Homeassistent stuff?

    I am using Firefox on both Linux and Windows. I''ve also tried Chrome on Windows. No difference.
    Waiting for the HTTP server to go down, I have nothing connected. Goto bed and look the next morning.
    I have not tried to use Chrome with a suspected dead http server. Will do the tomorrow morning.

    I have restored the RF partition (indeed a different MAC address) but to no avail.

    Added after 9 [hours] 35 [minutes]:

    And these are the last signs of life:

    Info:GEN:dhcp=0 ip=10.0.0.95 gate=10.0.0.138 mask=255.255.255.0 mac=84:e3:42:d8:e0:e9
    Info:GEN:sta: 1, softap: 0, b/g/n
    Info:GEN:sta:rssi=-73,ssid=zbcint1,bssid=00:25:9c:13:aa:f0 ,channel=11,cipher_type:CCMP
    Info:MAIN:Time 14661, idle 247003/s, free 8648, MQTT 0(916), bWifi 1, secondsWithNoPing -1, socks 3/38
    Info:MAIN:Time 14662, idle 244235/s, free 20344, MQTT 0(916), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14663, idle 249624/s, free 20344, MQTT 0(916), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14664, idle 251875/s, free 20344, MQTT 0(916), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MQTT:mqtt_host empty, not starting mqtt
    Info:MAIN:Time 14665, idle 247526/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14666, idle 250670/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14667, idle 248103/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14668, idle 256052/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14669, idle 247646/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14670, idle 250249/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:GEN:dhcp=0 ip=10.0.0.95 gate=10.0.0.138 mask=255.255.255.0 mac=84:e3:42:d8:e0:e9
    Info:GEN:sta: 1, softap: 0, b/g/n
    Info:GEN:sta:rssi=-74,ssid=zbcint1,bssid=00:25:9c:13:aa:f0 ,channel=11,cipher_type:CCMP
    Info:MAIN:Time 14671, idle 247287/s, free 8632, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 3/38
    Info:MAIN:Time 14672, idle 246022/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14673, idle 265446/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14674, idle 248115/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14675, idle 244160/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14676, idle 249781/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14677, idle 248023/s, free 8632, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 3/38
    Info:MAIN:Time 14678, idle 244365/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14679, idle 246130/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14680, idle 247726/s, free 20344, MQTT 0(917), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:GEN:dhcp=0 ip=10.0.0.95 gate=10.0.0.138 mask=255.255.255.0 mac=84:e3:42:d8:e0:e9
    Info:GEN:sta: 1, softap: 0, b/g/n
    Info:GEN:sta:rssi=-73,ssid=zbcint1,bssid=00:25:9c:13:aa:f0 ,channel=11,cipher_type:CCMP
    Info:MQTT:mqtt_host empty, not starting mqtt
    Info:MAIN:Time 14681, idle 254037/s, free 8640, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 3/38
    Info:MAIN:Time 14682, idle 244935/s, free 20336, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14683, idle 248425/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14684, idle 244568/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14685, idle 249010/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14686, idle 259250/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14687, idle 250737/s, free 8648, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 3/38
    Info:MAIN:Time 14688, idle 248418/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14689, idle 245723/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14690, idle 244894/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:GEN:dhcp=0 ip=10.0.0.95 gate=10.0.0.138 mask=255.255.255.0 mac=84:e3:42:d8:e0:e9
    Info:GEN:sta: 1, softap: 0, b/g/n
    Info:GEN:sta:rssi=-74,ssid=zbcint1,bssid=00:25:9c:13:aa:f0 ,channel=11,cipher_type:CCMP
    Info:MAIN:Time 14691, idle 246107/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14692, idle 245355/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14693, idle 279938/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14694, idle 250073/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14695, idle 251128/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14696, idle 252604/s, free 20344, MQTT 0(918), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MQTT:mqtt_host empty, not starting mqtt
    Info:MAIN:Time 14697, idle 249395/s, free 20344, MQTT 0(919), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14698, idle 246990/s, free 20344, MQTT 0(919), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14699, idle 249933/s, free 20344, MQTT 0(919), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14700, idle 251242/s, free 20344, MQTT 0(919), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:GEN:dhcp=0 ip=10.0.0.95 gate=10.0.0.138 mask=255.255.255.0 mac=84:e3:42:d8:e0:e9
    Info:GEN:sta: 1, softap: 0, b/g/n
    Info:GEN:sta:rssi=-74,ssid=zbcint1,bssid=00:25:9c:13:aa:f0 ,channel=11,cipher_type:CCMP
    Info:MAIN:Time 14701, idle 253927/s, free 20344, MQTT 0(919), bWifi 1, secondsWithNoPing -1, socks 2/38
    Info:MAIN:Time 14702, idle 246297/s, free 20344, MQTT 0(919), bWifi 1, secondsWithNoPing -1, socks 2/38

    And the logging stops.
    The raw port doesn't work. I forgot to switch it on........

    Just to exclude a hardware issue, I'll buy a new plug.
  • #27 20439102
    frankvanginkel
    Level 2  
    Yesterday I bought a new device, same specs as before. CB2S with a BK7231T on the PCB.
    This time a flashed it using the tuya cloud cutter and used that to flash your latest version. No soldering/serial etc. required!
    The tuya cloudcutter needs a firmware version and name which, in this case was: 1.1.8 - BK7231T / oem_bk7231s_rnd_switch
    with Aoycocr as the brandname and X5P Smart Plug as the model.

    Now it works the same as the old plug, including the memory leak! :( That's a pity.

    So it comes down that it's somewhere in the firmware. I hope to find some time to help debug. Might take a while.
  • #28 20439131
    p.kaczmarek2
    Moderator Smart Home
    @frankvanginkel are you 100% sure that doing "restore RF partition" does not fix the behaviour?

    That bulb, for example, is for 81 days online and still works for me...
    Smart Power Plug LCS Action Shop 2578685 970766 firmware upload
    Helpful post? Buy me a coffee.
  • #29 20439322
    frankvanginkel
    Level 2  
    I assume that I am just one of the very few to experience this problem, otherwise the forum would be full of memory leak comments.

    As it is already surprising that a plug with the same article number comes in at least two flavors, I would not be surprised if there was some more awfullness embedded. The shop where I bought the plugs is not exactly known for selling the best electronics :)
    I should have looked first at your website and Tasmota for device compatibility.

    Yes I did an RF restore on both plugs, restarted them and got new MAC addresses.

Topic summary

The discussion revolves around the flashing of firmware onto LSC Smart Power Plugs (Art. No. 2578685 and 970766) using OpenBKT7231 firmware. Users share their experiences with flashing processes, including issues with device internals potentially changing without model number updates, leading to complications during firmware uploads. One user successfully flashed their device but encountered a reboot loop and connectivity issues, suggesting possible hardware faults or bootloader problems. Others discussed the use of Tuya Cloud Cutter for flashing and the persistence of memory leaks in the firmware. Solutions and troubleshooting steps, including checking connections, using specific offsets for flashing, and restoring RF partitions, were also shared.
Summary generated by the language model.
ADVERTISEMENT