logo elektroda
logo elektroda
X
logo elektroda

[BK7231T] device that is far from wifi lose connectivity and became not available, openbeken restart

jbrande 1407 8
ADVERTISEMENT
  • #1 20567878
    jbrande
    Level 3  
    Does anyone experience the same, that a device that does not have a good connection became unavailable and have to do a hard reset each time that happens? Is there any way to make a hard reset like once a day so if that happens the device will reset alone and don't have to take it out and hard reset it?
  • ADVERTISEMENT
  • #2 20570125
    p.kaczmarek2
    Moderator Smart Home
    I haven't heard about it, but you could use a ping watchdog mechanism. I think we've had an example somewhere.

    Search for "ping watchdog" on that page:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/autoexecExamples.md

    PS: Here are OpenBeken docs:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/README.md
    Helpful post? Buy me a coffee.
  • #3 20590612
    jbrande
    Level 3  
    Is there any way to share uptime with Home Assistant to see if any device rebooted?
  • ADVERTISEMENT
  • #4 20590829
    p.kaczmarek2
    Moderator Smart Home
    Yes, you can check our docs:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/mqttTopics.md
    If you enable "broadcast self state" flag, you will get uptime broadcasts over MQTT.
    Helpful post? Buy me a coffee.
  • #5 20593421
    jbrande
    Level 3  
    I activate the flag, but it does not show the info on the device page of Home Assistant
  • #6 21113214
    vincenzoernst1
    Level 8  

    I see some similar behavior on a BK7231N. It has weak connection "Wifi RSSI: Weak (-85dBm)" and loses connection after some days and never connects back. I needs to be power cycled and after it connects to the AP within seconds. Why doesn't OpenBeken reconnect correctly?
  • ADVERTISEMENT
  • #7 21536875
    Zorlak
    Level 2  
    Hello everyone.
    I have SM-028_V1.3. OpenBL602. Flashed OpenBeken release 1.18.94. Set up Ping watchdog with an interval of 20 seconds.
    My router reboots every night. This is necessary because my Internet disappears every night when the provider reboots its equipment. And the Internet does not work until you reboot the router. After flashing SM-028_V1.3, my WiFi connection disappears every night. After rebooting the router at night SM-028_V1.3, it does not connect to WiFi until you unplug it and plug it back in again. Then it connects quickly and without problems. Sorry if I wrote in the wrong topic.
  • ADVERTISEMENT
  • #8 21537100
    p.kaczmarek2
    Moderator Smart Home
    We've updated BL602 SDK today, please try the new version.
    View of a GitHub repository section showing a warning about the main branch not being protected, with a file and folder list below.
    Helpful post? Buy me a coffee.
  • #9 21537530
    Zorlak
    Level 2  
    p.kaczmarek2 wrote:
    We've updated BL602 SDK today, please try the new version.
    View of a GitHub repository section showing a warning about the main branch not being protected, with a file and folder list below.


    Good morning. Yesterday I installed OpenBeken release 1.18.96. Everything is working fine this morning. I’ll wonder how it will turn out.

Topic summary

Devices based on BK7231T and related chips experience WiFi connectivity loss when located far from the access point, often requiring a hard reset or power cycle to restore connection. A ping watchdog mechanism is suggested as a potential solution to automatically reset the device upon connectivity failure. Enabling the "broadcast self state" flag allows uptime monitoring via MQTT, which can be integrated with Home Assistant to track device reboots, although some users report issues with visibility in Home Assistant's device page. Similar issues are reported on BK7231N devices with weak WiFi RSSI, where the device fails to reconnect after losing connection and requires power cycling. For OpenBL602-based devices like SM-028_V1.3 running OpenBeken firmware, WiFi disconnection occurs after router reboots, necessitating manual unplugging and replugging to reconnect. Updating to the latest OpenBeken releases and BL602 SDK versions has shown improvements in stability and connectivity recovery.
Summary generated by the language model.
ADVERTISEMENT