logo elektroda
logo elektroda
X
logo elektroda

Enhancing OBK Status Page with WiFi Details for OpenBeken Devices

max4elektroda 1821 64
ADVERTISEMENT
  • #61 21603218
    p.kaczmarek2
    Moderator Smart Home
    Well, but no problems on other platforms?

    I guess I will merge it as is.

    Added after 1 [minutes]:

    wait a sec, wlan_sta_ap_info should return 0

    Added after 16 [seconds]:


    Enhancing OBK Status Page with WiFi Details for OpenBeken Devices

    Added after 13 [minutes]:

    added fixes
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #62 21603260
    divadiow
    Level 34  
    XR809 1689_merge_444d39530925
    Code: Text
    Log in, to see the code


    this is the expected mac for bssid
  • ADVERTISEMENT
  • #63 21603304
    p.kaczmarek2
    Moderator Smart Home
    I see.,... so, are you saying it's ready and safe to be merged?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • Helpful post
    #64 21603311
    divadiow
    Level 34  
    not sure if I'm the one to make that call. I've done:
    BL602
    LN882H
    BK7231N
    ESP32
    W600
    W800
    BK7238
    ECR6600
    BK7231T
    RTL8720CF
    XR809
  • Helpful post
    #65 21603333
    p.kaczmarek2
    Moderator Smart Home
    Well, considering the fact that I added BSSID cache within safeMode == 0 block, then I would say that this testing was enough to merge it. In worst case, users can still recover their devices...

    Merged.
    Helpful post? Buy me a coffee.

Topic summary

The discussion centers on enhancing the OpenBeken (OBK) status page to display detailed WiFi information for OpenBeken devices, particularly focusing on LN882H modules. The main goal is to show the connected access point's BSSID, WiFi channel, and PowerSave mode level without relying on serial logs. Initial implementations added WiFi HAL functions to the status page, but concerns arose about cluttering the main page and privacy risks from displaying sensitive data like MAC addresses and SSIDs. Suggestions include making the feature optional via a flag, moving detailed info to a debug page, or integrating it into the JSON API for use in the Web App, similar to Tasmota's approach. Testing on various platforms (W600, W800, XR802, XR809) revealed issues such as truncated SSIDs, invalid channel reporting (e.g., channel 0 on BL602), and inconsistent AP information. The dual SSID logic remains unfinished and complex due to connection failover scenarios and network scanning limitations. The community emphasizes cautious rollout on easily re-flashable devices and prefers exposing PowerSave mode on the main page while relegating other WiFi details to JSON status or tooltips. The discussion also highlights the need for better user guidance on OBK features and the potential to leverage existing APIs to avoid increasing firmware size.
Summary generated by the language model.
ADVERTISEMENT