BK7231T RGB Bulb Connects to OpenWRT but No IP Communication, Static IP Issue?

Hi,

I'm struggling with BK7231T (from RGB Bulb) to connect to my WLAN.

I successfully managed to flash and connect to the device AP. There I configured Wifi credentials (several different modes) and set static IP (as all of my mainly Tasmota devices have).
The device then connects to my OpenWRT router like this:


I see that the device is connected to OpenWRT in the Wifi tab.

But I cannot ping it - even not from OpenWrt console.
In the OpenWrt Console I see this. The IP is the one I assigned to the device.


nslookup does not find the device.

Most of the tests & configurations were done using a USB TTL (gold version) which usually has no issue to provide the needed power...
The device has also been powered by an external power supply as this is mentioned to be critical.

The OpenWrt AccessPoint has been configured as
- WPA PSK
- WPA2 PSK
- WPA/WPA2 mixed mode
- WMM deactivated
- Country Code = DE

Could it be that fixed IP assignment does not work properly?
Unfortunately DHCP is not stable enough in my environment (for an unknown reason) so I'm configuring static IPs for *all* devices since years.

During the device AP phase, it is completely stable and I can click around and configure without issues.
The connection to the OpenWRT router seems to work - only IP connection cannot be established.

P.S.: I also tried to connect to an old Fritzbox 7170 (original firmware). Connection also works there but I also don't see an IP address.

P.P.S.:
Just struggling with the safe mode of the device. It worked dozens of times before but not anymore.
I wanted to check DHCP against FB 7170 with an external power supply and now the local AP does not show up anymore...
I reflashed with backup - no change.

Any ideas?

Thanks in advance
Eva

That's strange, I'm sure that I had static IP set on some BK7231T devices and they worked well... I will take a moment and try again, btw, @DeDaMrAz @divadiow do you have any T's to test?


Would you be able to try with other router?

>>21104601
At the moment I only have this one ready for testing and it is not opening the AP... Flashing and backup works well.
Did you see such a behavior before?

ok I have idea - what is your device MAC? Maybe you have erased your RF partition, so your MAC ends with 00 00, so you have MAC conflict?

hmmm... what I did:

WebUI presented my a valid MAC shown in the first code section of my initial post.
50:8a:06:75:e4:50
This MAC is in my WHITELIST of OpenWRT Access Point and OpenWRT let the device in.
In ARP there is 00:00:00:00:00:00 for unknown reason.
To eliminate any doubt I actively reassigned the MAC be WebUI. First changed one digit 50:8a:06:75:e4:51 and then changed back to 50:8a:06:75:e4:50

At that point in time I still was able to communicate and configure the device without any issue using the device AP.

I searched around for this ARP 00:00:00:00:00:00 thing but did not find an explanation nor an idea whether this is related to my issues.
Unfortunately OpenWRT can only show ARP table. The arp command has no parameters, expecially no remove or flush or clear...

Probably there are 2 main differences in the way of dealing with devices at my home compared to other users:
- OpenWRT as main router for local devices with MAC whitelisting
- fixed IPs

As the test with a stock Fritzbox failed I focus now on IP issue.

But I'm open for every idea!

Or did you mean that having erased some important portion of the device is the root cause of not having AP anymore?
Is there a way to solve it with the flashing tool BK7231 Easy UART flasher?

Hinzugefügt nach 1 [Stunden] 41 [Minuten]:

p.kaczmarek2 wrote:

Maybe you have erased your RF partition, so your MAC ends with 00 00, so you have MAC conflict?

I probably found what you meant. There is an option in the flasher tool "show advanced options" -> "Restore RF part"
The explanation shown after clicking on the button sound similar to what you wrote.

I did a restore but the situation remains the same => no access point coming up

ok let me check this. My settings:

after reboot:

Well, it clearly works on my side...


Ok, regaring your router - are you sure that the problem is static IP? Maybe OBK device fails to connect to your router in general?

p.kaczmarek2 wrote:

Maybe OBK device fails to connect to your router in general?

Device is shown in the list of connected devices with connection speed, ...
In router's log I see that connection was successful. Log looks like other logs of successfully connected devices. (see log section in my first post).
But for sure it did not work completely correct because IP connection is not established.

Unfortunately I'm not able to do further checks right now as the device access point does not start up anymore.
Am about to reflash it and restoring RF part and so on....

Hinzugefügt nach 5 [Minuten]:

one more question:
Do you feel it could help to restore the original backup to the device and afterwards reflash with OpenBeken?
The backup is QIO while OpenBeken is UA.
If I understand it correctly QIO is a full backup of the whole chip while UA is only the firmware section.
Can I simply select the original firmware from drop down and the flasher UI knows that flashing needs to start at another address (0x0 instead of the address of firmware)?

I don't want to brick it even more

You can easily restore your backup with our flasher, backups are always QIO. Give it a go.

If you didn't break your RF, then original RF is better than the one created by "RF restore"

thanks a lot.

I finally managed to get it into my local network.

To be honest: I don't know what I did differently.

I right now did:
- flash config several times using Flasher
- restored original backup file
- reflashed OpenBeken
- configured Wifi using Flasher (yesterday I configured only using devices AP)
- tested against Fritzbox 7170 (no success)
- configured to connect to OpenWRT with DHCP
- suddenly the device was shown with the IP I configured in OpenWRT's DHCP configuration file
- then configured this IP as fixed IP using Flasher

The final configuration of the device should be equal to my configuration of yesterday. But today I did a lot with the Flasher instead of using my Smartphone and use devices AP...

Anyway: thanks a lot for your hints!!! I learned a lot and hopefully don't need to bother you that much again.

Please ask as much as you like, you're welcome here, that's what the forum is for.

I honestly don't know myself why it wasn't working before, so I won't close this topic now, let's just watch and observe, maybe there is something else at play.