You need a newer FW for this sensor. Go to "Launch web application" → "OTA" → "Select remote OTA file to download to PC", rip the latest 1.17.10.rbl and load it to your device (Drop OTA here). Then there will be an option with IP and other things needed for this sensor to work as it should.
You need to update the firmware. In addition, from the description of your problem, I'm beginning to suspect that you may have performed an operation in the flasher Clear all , i.e. you have removed the entire Flash memory, as a result of which the MAC address has changed to the default one, ending with 0x00 characters. Now if you have another same device, you will have two devices with the same MAC, which will result in problems connecting them.
The normal OpenBeken upload operation does not clear the entire memory, only its beginning, and leaves the MAC sections unchanged.
If your MAC address ends in 0x00, there are two solutions: 1. via UART, in our flasher, do Restore RF partition: https://github.com/openshwprojects/BK7231GUIFlashTool 2. In our Web Application, in the Flash Memory tab, press the Restore RF partition button
The Restore RF Partition operation will assign a new random MAC address to your device and solve WiFi connection issues.
You have indeed removed the RF partition, as evidenced by the device name ending in zeros. This name comes by default from the MAC, which also ends with zeros, which means that during flashing you had to overwrite the RF section or perform Clear All (the entire 2MB flash).
There should be a big "Exit safe mode" button in the main menu, but the Web App downloads from the web, so it may not open for you. I have separate wifi and separate internet connected by cable, so it works for me. Try the Web App anyway.
If it doesn't go, disconnect the device with the same MAC from the router (I guess it is, because this problem has already appeared on the forum), or fix the RF partition on that device, and then fix it on the other one, it was written in like previous post.
As a last resort, you can also simply repair the RF partition via UART.
Now I see it's finally there the restore RF partition option would be very useful in the firmware itself (not WebApp), but at the moment it is not there, we did not expect such problems with it. I think I will modify the firmware so that from the next versions, as soon as it detects a clean MAC, it will fix it itself ...
Fixed IP: 192.168.2.44, 255.255.255.0, 8.8.8.8, 192.168.2.1 2.4GHz WiFi network Unfortunately, there is still no IP and no access to the device, DHCP does not assign an address for this device, and somehow setting the IP to a fixed one also does not change anything
The situation becomes very mysterious. To sum up - you wiped 2MB flash, lost the RF partition, then restored it, and the device still won't connect to your WiFi?
On which BK are your devices, on which is the strip, and on which door sensor?
I have two dev boards with BK7231T and BK7231N, just to be sure, I will clean their flash at home and check if they connect ....
The discussion revolves around using the CH341A programmer to interface with the BK7231N/CB3S door/window sensor (PB-69W VER 1.3) and the OpenBK7231N_QIO firmware. Users report issues with the sensor not waking up from deep sleep when the reed switch is closed, despite various firmware updates and configurations. Solutions proposed include adjusting GPIO settings, using different firmware versions, and implementing specific commands like "DSEdge" to manage wake-up behavior. The conversation highlights the importance of correctly configuring pull-up and pull-down resistors and the need for firmware modifications to ensure proper functionality. Users also discuss the challenges of MQTT connectivity and the timing of state changes after waking from sleep. Summary generated by the language model.