logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

BK7238 MultiAHTX_493371f360d3 Module Ignores Static IP, Shows wlan0 Net Name

taggbricka 705 7
ADVERTISEMENT
Report a violation of the law
Reply | New topic

  • MultiAHTX module ignores static IP and uses wlan0 name

    #1 21593212
    taggbricka
    Level 7  
    Posts: 48
    Help: 1
    Rate: 4
    I am using the new module for BK7238 with two AHT30 sensors.

    There is a small quirk with this module that is not present in the vanilla "OpenBK7238_1.18.124"
    The setting of static IP is not honored.
    The device comes up with a DHCP assigned IP and a funny net name "wlan0" where "OpenBekenX_92D994" would be expected.
    The difference in behaviour is repeatable when I OTA switch between the two load modules.

    This is the setup that works with OpenBK7238_1.18.124 but not with multiAHTX_493371f360d3
    BK7238 MultiAHTX_493371f360d3 Module Ignores Static IP, Shows wlan0 Net Name
    eufyMake E1 - łatwa personalizacja za pomocą druku UV [sponsorowany]
  • ADVERTISEMENT
  • #2 21593477
    max4elektroda
    Level 24  
    Posts: 758
    Help: 49
    Rate: 189
    Just to verify or rule out my change is the cause of that issue:
    Could you please try latest release (1.18.127)?
    If it's present there, try the releases in between to find the one breaking the function.
  • ADVERTISEMENT
  • #3 21851252
    gotvmodding
    Level 2  
    Posts: 3
    I am having the same issue with an LSC Smart Plug running on a BK7238, OBK version 1.18.266.
    When I set a static IP and reboot (both powering the device off and restarting from the interface), the IP won't stick. How did you solve your issue?

    EDIT: When running version 1.18.124 as the original poster said, the IP seems to stick. Something must have happened in between these updates.
  • ADVERTISEMENT
  • #5 21859260
    gotvmodding
    Level 2  
    Posts: 3
    >>21851416 Sorry for the late reply. No, it doesn't seem to work on .254 either. No point in trying .255. I'll be installing .124 on this other new plug I got in the meantime.

    EDIT: Another thing I tried was setting the IP on .124, then reverting to .270. It went back to the original DHCP IP.
  • #6 21877835
    gotvmodding
    Level 2  
    Posts: 3
    >>21859260 another issue I've found is that after a couple of days connected to the Wi-Fi, the smart plugs disconnect, but the Status LED is still lit up. This is just on the smart plugs that are running firmware .124 (chip type BK7238), the BK7231 doesn't seem to have the same issue.
  • ADVERTISEMENT
  • #7 21877852
    divadiow
    Level 38  
    Posts: 5216
    Help: 448
    Rate: 917
    do your devices have different mac addresses? did you flash them with Easy Flasher read/write combo button or purposefully restore RF from factory backup when you converted them, if at al?
Reply | New topic
Report a violation of the law

Topic summary

LABEL_AI_GENERATED
A BK7238-based OpenBeken module with dual AHT30 sensors shows a regression in newer firmware builds: static IP settings are ignored, the device boots with a DHCP-assigned address, and the network name appears as “wlan0” instead of the expected OpenBeken hostname. The issue is repeatable when OTA-switching between the working OpenBK7238_1.18.124 build and the multiAHTX_493371f360d3 module. Later replies confirm the same static-IP problem on BK7238 smart plugs in versions 1.18.266 and 1.18.270, while 1.18.124 still preserves the configured IP. Troubleshooting suggests testing intermediate releases, with suspicion around a merge in PR #1969 and later references to issue #2075 and PR #2079. Additional notes mention possible differences in MAC address or RF backup restoration, and a separate observation that some BK7238 smart plugs disconnect after days on firmware .124.
AI summary based on the discussion. May contain errors.
Today's popular
ADVERTISEMENT