Open Kosygor opened 1 year ago
Dziękuję, thank you, for the report.
So basically this one single device has problems with WiFi and others work?
Would you be able to submit a full 2MB flash dump of that device for analysis?
I suspect that it may be possible to fix by clearing the BK7231 RF section, but it's a risky operation, don't try doing it yourself, I will give specific instructions when ready.
Btw, @btsimonh , thoughts on that?
Well I have to admit that yesterday update of BK7231 GUI Flash Tool let me read that without an isse. Before I had to use python uartprogram and there was no go without using CEN or RST, on controary what manuals said (pretty usefull to have reminder now in Flash Tool while getting serial). I am not sure if FW dump containts any credentials (probably not but ... ) so I just have sent it directly to Your email. I am really proud to see Elektroda's (so I assume Polish) fighting with China's pursuance to wrap everyone in their Tuya world ;)
Obviously FW dump contains SSID and password, it has too, as it's the full memory of the device.
We're from Elektroda and you can contribute as well by creating a teardown or a review for us: https://openbekeniot.github.io/webapp/devicesList.html As long as you are from within Poland, you can also get a free SD card for submitting a teardown (status of shipping outside of PL is not clear yet): https://www.elektroda.pl/rtvforum/topic3550170.html
Your case seems very rare for me and I really flashed lots of devices. Currently I can only suggest you one risky operation:
Restore RF Config
You can also download it first, but the whole operation is up to you, I am not sure yet if it can help or worsen the issue.
Try that now, but only if you are willing to take small risk.
The another way to fix it might be to just copy whole flash dump from another BK and just change mac, again, don't try it yourself yet because there is a risk of overwriting the bootloader.
Ok I got it, thanks for clarification about FW.
I can share teardown of course, but shouldn't I wait for it to be working like it should ? Yep I am from Poland I can make PL and EN teardown`s ( but I am laking writng skill in both - so do not expect much).
About my problem I think it is worth to notice that I have counted it took about 20 min for device to connect and this is exactly what Online for
filed said in http://IP/index
Webui. So device seems to start without an issue.
Sure I have tried it, whole HA journey is trial and error. After resetting Restore RF Config It did not make much change it took 5 min to reconnect. It seems like these re-connection times are random 5-20 min. Only diffrence that I have noticed is that after this operation device sends less data trough mqtt. I have sent You before and after RF blocks.
One Idea that I have is because of that particular bulb RF antenna is on the level of aluminium plate with LED`s so I think that maybe rising whole WB2l can help. Is it worth giving a try ? I may fail because I have damaged few pads on first and second bulb but I will try to make one for teardown from both of them. Edit: I have tried moving antenna up. first startup was promising and took approx. 10 seconds. But another one was slow.
Describe the bug Hello, Device is slowly reconnecting to WiFi after swtching it on by Zigbee switch. It takes about 3-5 min to reconnect. When I pulled BK outside and connected it to serial terminal it reconnects to WiFi in acceptable 12s. WiFi Signal should not be an issue since router is 3 m and 1 25cm wall from both of them. I have two Spectrum Smart E27 1500 lm 13 W with Is thare any way to save log when BK is inside the bulb ? Can reason of this can be that I have Loaded configuration for BK7231N instead of T ? It seems like this is only responsible for Pinout mapping. I just assume that W2BL is BK7231T because i was not able to read chip marks after removing putty. Firmware:
To Reproduce Well apparently no other devices have problems.
Screenshots
Ripped one pad so had to solder wires directly to one of bulbs chips.
![IMG_20230106_202941](https://user-images.githubusercontent.com/61921662/211085828-9dc03939-3b2c-43a2-a6b4-eb986b0ff905.jpg)
Additional context Log - not sure where it starts and i do not want to cut it.: