D'oh ... sorry. Stupid me. TIL: There is configuration menu for startup, Thanks.
But: The relais switches of for about half a second when the socket restarts. I guess, that is unavoidable?!
I have a PC plugged into the socket ...
You could add a capacitor between base and GND of the driver transistor.
The draw from the base and the 10K resistor in conjunction with the capacitor form a simple time delay
.
Thanks guys for the idea with modifying the relais or adding a delay. I will look into that. It would be a very good modification for a lot of my smart plugs, because I use them for all my PCs to track the power consumption. The plugs with Beken chips almost never reboot. But it could happen. BL602 and LN chips ... it happens.
I just registered because of this post.
I didn't know until now of how to flash this chips.
Thank you all for your effort.
You mention
"Easy to open with pliers. "
I bought a pack of 4 pcs of this.
I destroyed one if this unit while trying to open.
Completely destroyed the plastic.
Can you or someone do a video or something of how to open this?
Because to me it seemed, when trying to open, that was glued or plastic soldered, I couldn't easily opened.
I have more units waiting for this treatement...
Many LSPA9 pieces varies a lot in the terms on the physical connection strength/glue. I had some LSPA9s that were very hard to open, and, on the other hand, I had LSPA9s that were very easy to open, they were almost like no glued at all.
I see, but just to be sure, was this plug marked as Zigbee? Maybe somewhere on the case? If not, that is something we certainly need to watch for in the future.
THIS ISN'T A CASE OF A BAD MARKED ITEM that the community must be aware.
I have both zigbee and wifi plugs in my network. Mainly zigbee.
I am experienced in both, know perfetly the difference.
It was just a stupid mistake of getting the first one BEING SURE it was an wifi tuya plug and it WASN'T.
Completely my mistake, nevermind and thank you for your help!!!
Added after 44 [minutes]:
Well it is a AWOW EU3S.
I can't find the brand and model as a profile in tuya cloud cutter.
How can I know which is the compatible profile when not appearing in the tuya cloud cutter app?
I tried pairing in the tuya app and it gives am an error when trying to pair in slow blinking mode, and it appears an Wifi hotpot.
is when tryign to connect to hotspot that gives the error.
Well, I managed to pair it in fast mode and not in slow mode. It said v1.0.0
I tried all the 1.0.0 versions in tuya cloud cutter with no success.
Then I went to see the one tat is open and broken, and it is an ESP8.... I though it wasn't
It doesn't work with tuya convert, I nought this back in 2020 and tried that method, and it couldn't because the exploit was patched.
I assumed it was because it was a different chip, but no.
What are my options to take if off the cloud and an open source firmware? I am talking without opening and flashing it... OTA...
>>21027185 Hi, i'm new here. I managed to flash the bl602 chip but i'm stuck, because all my values are 0. I see yours is quite working. can you give a hint please?
Update: After OTA "OpenBL602_1.17.756_OTA.bin.xz.ota" the values are ok, but the physical button is not working. ( "17": "Btn;1", )
Update: physical button on my plug tuya plug is "22": "Btn;1" not "17": "Btn;1".
I have firmware 1.3.18 on wifi socket 16A and can't change firmware on it by wifi, no profiles for this firmware. No software updates in SmartLife.
It BL0937 and T34. Can you help me to cut it from cloud?
The discussion centers on a Smart Plug purchased from AliExpress, identified as an Aubess device with an SM-028_V1.3 board featuring a BL602L02 chip and BL0937 energy metering IC. Users successfully opened and flashed the device using FTDI232L and Bouffalo Lab Dev Cube tools. Challenges include incomplete BL0937 interrupt counter support, pin mapping uncertainties, and unstable OTA firmware updates on the BL602 platform. Various firmware builds and pull requests were tested to improve OTA reliability, including reducing binary size and modifying flash erase procedures. Watchdog timer implementation was a major focus to address device freezes and unresponsiveness, with a watchdog driver added and tested to enable automatic reboot on crashes. Some users reported inconsistent device freezes, sometimes with partial functionality (e.g., button still working), suggesting possible TCP socket or memory leaks. Discussions also covered relay default state on power-up, with solutions involving startup commands or hardware modifications to maintain relay state through reboots. WiFi reception issues were noted, attributed to channel congestion rather than hardware faults. Additional topics included difficulties opening the device casing without damage, and clarifications on device identification to avoid confusion with Zigbee models. The thread also references related devices and firmware versions, with community contributions to device templates and driver improvements. Overall, the conversation highlights ongoing development and troubleshooting efforts to stabilize BL602-based smart sockets with BL0937 metering, improve OTA updates, implement watchdog recovery, and enhance user experience with relay control and device reliability. Summary generated by the language model.
