logo elektroda
logo elektroda
X
logo elektroda

LN882H Firmware on WL2S (BL0937) Outlets: Slow Web Admin, High Ping, Unusual MAC Address

tadeu1 255 7
ADVERTISEMENT
  • #1 21801823
    tadeu1
    Level 5  
    I buy 3 power outlet to check if some I can apply tuya cloud cutter, no success
    2 of them its CB2S and one its WL2S, all of them with BL0973
    I read the tutorial and apply the fw LN882H.
    No MQTT, just standard config
    Code: JSON
    Log in, to see the code


    I have a weird operation with this module.
    its really slow, sometimes the ping its high, I try to change mac adress, because its started with 00:50:xxxxxxx, I never saw something like that.
    But the web admin its quiet slow, sometimes I loose the connection etc.
    I add the mqtt to test, same, i publish and takes time to read, and sometimes did not do.


    Any ideias?
  • ADVERTISEMENT
  • #2 21802010
    divadiow
    Level 37  
    which guide did you follow, which tool did you flash with?

    does the mac at the bottom differ from or match (the latter part) the name at the top?

    User interface of OpenLN882H with configuration buttons and system dataControl panel of OpenLN882H device showing Wi-Fi status and configuration options

    Added after 7 [minutes]:

    sweetlilmre wrote:
    The MAC addresses are generated from random data after a flash erase (1 MAC for AP, 1 for STA).


    I think this is still the case
    https://github.com/NonPIayerCharacter/OpenLN8...6a858301425dc/components/utils/ln_misc.c#L176

    Added after 2 [minutes]:

    as for the poor wifi, this sounds familiar. I feel like there have been reports of such with LN882H for a few months.

    eg https://github.com/openshwprojects/OpenBK7231T_App/issues/1671#issuecomment-2963824624
  • ADVERTISEMENT
  • #3 21802076
    tadeu1
    Level 5  
    >>21802010 W
    I'm not at home right now. I'll do some tests at night

    I use Python to dump and the .exe to write the FW.

    MAC looks like you sent me, the random.
    Mine is a power outlet.
  • ADVERTISEMENT
  • #4 21803035
    tadeu1
    Level 5  
    I changed the MAC to Tuya Athom standard and it's still there

    4C:3A:93:19:38:C3

    Also, look at the ping; it's weird, and when I toggle, I lose the connection. I'm beside the router.


    Ping results to 172.16.0.107 with variable response times and timeouts

    Terminal window showing ping results to 172.16.0.107 with irregular response times

    Added after 1 minute:

    The temperature is not bad.
    Also, I turned the bulb off, and the ping is still bad.


    Screenshot of a metering device showing energy stats and MQTT connection status


    Ping command output with unstable response times for IP 172.16.0.107

    Added after 7 minutes:

    Version build on Jul 28 2024 11:28:41, version 1.17.650. It's better.
    Just when I press toggle, it gets slow right now.

    Terminal window showing ping results to 172.16.0.107 with variable response times

    Added after 2 minutes:

    I did some tests on Home Assistant; still bad with MQTT.


    Terminal window with ping responses from IP address 172.16.0.107
  • #5 21803239
    max4elektroda
    Level 22  
    The last screenshot shows weak signal.
    Do you maybe have more than one access point with the same SSID?
    LN882H is known to sometimes connecting to any AP, not the nearest. It's some time now, I once tried a solution, but didn't succeed, don't remember the last state...
  • ADVERTISEMENT
  • #6 21803316
    tadeu1
    Level 5  
    Yha I have some router with same name.
    Now I get good, I 'm at the version 1.17.650 and I try to run OTA, no sucess, any ideia?:

    Added after 10 [minutes]:

    But with good, I still have issues when I add mqtt and sometimes loose the connection

    Screenshot of a system interface showing Wi-Fi status and MQTT error with pointer on MQTT disconnected.


    Screenshot of ping command with responses and request timeouts



    after mqtt connected

    Ping results to IP address 172.16.0.107 with varying response times and TTL255



    If I toggle at home assistant I loose the connection for a while

    Screen showing ping results to IP 172.16.0.107 with varying response times

    MQTT logs and energy usage data from device “tomada_salao_de_festa_expositor”

    Added after 4 [minutes]:

    I try last fw, last from .17 and I got disconnect when I press start


    Screenshot showing ping to 172.16.0.107 with several requests timing out

    OTA update screen with LN882H chipset and selected file OpenLN882H_1.17.822_OTA.bin

    Added after 2 [hours] 20 [minutes]:

    I give up, I replace with another ESP02S

    attached the config for TNCE to replace LN882H with ESP02S
    {"NAME":"LN822H ESP MOD","GPIO":[0,0,0,32,2720,2656,0,0,2624,576,224,0,0,0],"FLAG":0,"BASE":18}

    VoltageSet 224
    PowerSet 9
    CurrentSet 0.045

    SetOption21 1
  • #7 21803456
    max4elektroda
    Level 22  
    Sorry it didn't work out for you.
    About the "complaints" about some "SENSOR" command: Seems that for LN882H "TEST_COMMANDS" are not enabled (But even if, it would simply ignore any arguments if I'm not mistaken).
    I can try later on my LN882H device if calling unknown commands regularly can lead to the reported problems.
    Because I'm using a smart plug with BL0937 for some time now. There are some issues with selected AP and sometimes ARP seems not to work (device can't be reached, but it's working fine from my router or if I add a static ARP entry for the plugs IP). Beside this I'm quite happy with it...
  • #8 21803642
    tadeu1
    Level 5  
    Good morning! Don't worry.

    It's a lot of issues with this LN882.
    I can buy another power outlet with bl0973 for test proposal if you wanna.

    Just tell me if you wanna something. I wanna help and improve with the OBK.

Topic summary

A user attempted to flash LN882H firmware on three power outlets—two CB2S and one WL2S—all equipped with BL0937 energy monitoring chips, aiming to use Tuya cloud cutter without success. The firmware was applied following a tutorial with a standard configuration excluding MQTT initially. The user reported slow web admin interface performance, high ping times, intermittent connection loss, and an unusual MAC address starting with 00:50, which is uncommon. Attempts to add MQTT did not improve responsiveness, with delayed or failed message publishing. A respondent inquired about the flashing guide and tool used, and whether the MAC address shown matched the device name. They referenced known issues with LN882H firmware causing poor Wi-Fi performance, linking to a GitHub discussion highlighting similar problems. The user confirmed using Python for dumping and an executable for flashing, noting the MAC address appeared random and the device was a power outlet. Further testing was planned.
Summary generated by the language model.
ADVERTISEMENT