logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

ISPTEC Tuya Smart Socket OpenLN882H v1.18.165 Not Sending Pings After BK7231Flasher

bendezar12a 387 7
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Report a violation of the law
Reply | New topic
  • #1 21653819
    bendezar12a
    Level 2  
    Device: ISPTEC Tuya Smart Socket - OpenLN882H
    Software: version 1.18.165
    Device IP: 192.168.2.222
    Firmware uploaded using: BK7231Flasher

    pinghost 8.8.8.8 (or any address)
    >Info:CMD:[WebApp Cmd 'pinghost 8.8.8.8' Result] OK
    Did not send a ping - deceives that it arrived

    pinghost from autostart.bat or from Ping watchdog there is always a message:
    >Info:MAIN:Time 328, idle 0/s, free 77288, MQTT 0(21), bWifi 1, secondsWithNoPing 263, socks 0/0
    Does not send a ping.

    I checked in Wireshark and the device never sent any ping, even to a computer on the local network.

    AI: Are the other network functions of the socket (e.g. app control, MQTT) working correctly, or are there any problems with them? .
    Other functions are working correctly.
    AI: Has the device been reset to factory settings or was there an attempt to update/change the firmware before the ping problem occurred? .
    Resetting does not change anything.
  • ADVERTISEMENT
  • #2 21654657
    divadiow
    Level 36  
    I've done some testing with BK7231N. With 1.18.15 Ping watchdog is counting down on GUI page

    Text “Ping watchdog (192.168.137.1) – will start in 8!” on dark background

    and wireshark logs ICMP

    List of ICMP packets between IP addresses 192.168.137.1 and 192.168.137.16

    it stops working in 1.18.16 where a lot of changes were made to reduce built file size - no GUI countdown and no wireshark logs

    https://github.com/openshwprojects/OpenBK7231T_App/releases/tag/1.18.16

    https://github.com/openshwprojects/OpenBK7231T_App/pull/1500

    try 1.18.15 - does it work for you?
    IoT device status panel showing ping connection info and weak Wi-Fi signal

    @p.kaczmarek2

    Added after 10 [minutes]:

    might just be disabled
    https://github.com/divadiow/OpenBK7231T_App/actions/runs/17512141840
  • ADVERTISEMENT
  • #3 21654671
    p.kaczmarek2
    Moderator Smart Home  
    Strange, if that's disabled, then commands should be also not available, so we don't confuse users. I'll look into it.
    Helpful post? Buy me a coffee.
  • #4 21654675
    divadiow
    Level 36  
    with
    Code: Text
    Log in, to see the code


    PW works again
    Device control panel with buttons: Config, Restart, Launch Web Application, and About

    Added after 30 [minutes]:

    +496 bytes
  • ADVERTISEMENT
  • #5 21654701
    p.kaczmarek2
    Moderator Smart Home  
    I pushed change to hide ping watchdog commands if it's not enabled in build:
    https://github.com/openshwprojects/OpenBK7231...mmit/9cc5519b7ce7c65e9e348b8b57e0ff7ded47b71b

    I also checked obk_config.h - it seems disabled on all platforms. Shall we enable it on every one?
    Helpful post? Buy me a coffee.
  • #6 21654710
    divadiow
    Level 36  
    p.kaczmarek2 wrote:
    Shall we enable it on every one?


    yes? dunno. it's quite small.

    tbh I thought it was, like MQTT, one of those things that forms the base of OBK - always there.
  • ADVERTISEMENT
  • #7 21655159
    bendezar12a
    Level 2  
    >>21654657 .
    Thank you very much for your help. Checked on 1.18.15; ping works>>21654657 .
Reply | New topic
Report a violation of the law

Topic summary

The ISPTEC Tuya Smart Socket running OpenLN882H firmware version 1.18.165, flashed using BK7231Flasher, exhibits an issue where ping commands (e.g., pinghost 8.8.8.8) report success but do not actually send ICMP echo requests, as confirmed by Wireshark analysis. Despite this, other network functionalities such as MQTT and app control operate normally. Attempts to resolve the issue by resetting the device to factory settings have no effect. The problem persists both when ping commands are issued manually and when triggered automatically via autostart scripts or ping watchdog processes. The device maintains network connectivity, but the ping mechanism fails to generate network traffic, indicating a possible firmware or network stack anomaly specific to the ping implementation in this firmware version.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT