Tuya LSPA9 smart socket - teardown, OpenBeken flashing guide for CB2S, BL0942

Just received some LSPA9's but they come along now with WL2S (Lightning LN882HK) wifi/ble modules.
See also Support for WL2S module (Lightning LN882HK chip)

Dears,
Long time ago I bought 3 pieces of Tuya plugs (NEO NAS-WR01W) which I supposed to be easy to tasmotize - I already had same one tasmotized. What was a surprise, when I got Beken7231T ones They were working via LocalTuya integration, and one day one of them stopped to work (no wifi connection, no reaction on button). I supposed it to be dead, but I found your thread about OpenBeken, so decided to give it a try. Soldered wires, updated firmware and voila, it is alive again
As I was able to recover it to same functionality as LocalTuya had (no power readings), I played with settings, succesfully configured BL0942, configured it to work with Home Assistant, but now there is an issue with voltage sensor.
Here is what I see in Home Assistant:


In MQTT info I see following:


Looks like something is mixed in MQTT data, voltage readings with signal strength, but I wonder where I did somthing wrong. I reloaded MQTT integration, removed and rediscovered device again, and no clue what's the point.
Any ideas?
By the way, thanks for everything what you're doing here, great job!

Update to the above - what I wrote about occurred on version 1.17.286. I changed it to 1.17.289, but with no result, the signal strength is still converted into voltage:

.

Sometimes the "voltage" value is displayed as the actual signal strength, e.g. "-47 dBm". I have no idea what it depends on.

I'll find a moment and check it out. If necessary, you can temporarily revert to the version before RSSI was added, which was relatively recently. I can find which one it is.

Added after 2 [hours] 32 [minutes]:

@maczekg I found the problem, it already works for me:


I'm uploading the fix to Github.

Works! Thanks a lot!

Please, if you have any other suggestions or ideas on what to do, let me know.

p.kaczmarek2 wrote:

I will have two LSPA9 clones on Tuesday, I will program them for the reader, I will try to check them. Remind me if anything happens.

Do we know?

@skupu I didn't check it, but then it turned out that it was impossible to remove the PCB and I chose the route of "cutting the corner of the housing" to get to the pads:

You have to wait for another opportunity. And why do you need this resistor value?

And the BL0937 or BL0942 application diagrams will not help?

>>20785282

Hi,
There will always be suggestions Today's topic - I noticed that after restarting HA (or reloading the MQTT integration), the "buttons" connected to the dashboard via OpenBeken sockets do not work. You can click as much as you want, it does not turn on the relay. After entering MQTT integration and displaying the properties, switching on the relay looks like this:



Only clicking on the uncrossed/crossed out lightning bolt (if the socket is off/on) turns on and "unblocks" the whole thing and changes to a regular switch:



The buttons on the dashboard then start working. The situation is similar when you press the button on the socket itself - the lightning disappears and the switch appears. I have never noticed similar behavior on sockets or relays with Tasmota, ESPHome or Zigbee, so it is probably not a matter of HA itself.
I wonder if the flags might have an impact on this - I have them set to 10, 27 and 40. Flag 10 probably not, I tried unchecking it and it doesn't change anything. Any suggestions?

I saw two solutions for this, you can:
- turn on flag 2 so that the socket refreshes its status from time to time
- in HA in yaml, force refresh with a simple script after restart, see topic: https://www.elektroda.com/rtvforum/topic4001877.html#20761607

Well, thanks again I chose script and automation.
Three sockets have already been removed from LocalTuya and are running on OpenBeken.

@p.kaczmarek2

>>20787417
I think this resistor went bad and it has some strange strip markings on it, so I'm not sure what to replace it with.

I don't know if the value is given in the diagrams because I didn't find them.

As for disassembly, the board can be removed by unscrewing the screws inside the L/N pins or by unscrewing the screw in the board - at least that was the case in the products I had.

Hi,
I have a LSPA9 clone called Chigoods with CBS2 wifi module and BL0937, successfully installed the latest OpenBK firmware and everything works fine except the voltage, current and power report. Did the calibration as instructed and with that particular lightbulb plugged in the values are ok. As soon as I change and plug in another device the values are off see attached image. I get 89,3 V instead of 218V. What could be the problem?

Hello, can you do Tuya config extraction and post here JSON?

Ok, so is your GPIO correctly configured?
Here is template importer:
https://openbekeniot.github.io/webapp/templateImporter.html
You can also import it directly in the OBK...

It seems the GPIO was not configured correctly. PIN 6 and 7 assignment was switched. I used the BK7231 Easy flasher built in autoconfig from tuya backup but it seems that has a bug and assigned wrongly PIN 6 and 7. The online tool you provided showed the correct assignment and after I changed it, everything is working fine.
Thanks for the help.

Wow, this is a nice find! I will fix flasher now.

maczekg wrote:

They were working via LocalTuya integration, and one day one of them stopped to work (no wifi connection, no reaction on button). I supposed it to be dead, but I found your thread about OpenBeken, so decided to give it a try. Soldered wires, updated firmware and voila, it is alive again

Exactly the same thing happened to me a couple of days ago with BL0937 version. This was really strange because when I did try to read it with BK7231Flasher I got CRC mismatch error and also was unable to read OBK configuration. But flashing with OB was without any problems and after some setup troubles, it is now fully functional again.

I have also some questions to p.kaczmarek2 if he happens to read this.
Is it still needed to "to save your BL0942 init and calibration constant setting commands in LittleFS or startup command " as described in the first post?
Can I save the button state after a power outage? I have not found any settings for that. Maybe I missed something.

minusync wrote:

maczekg wrote:

They were working via LocalTuya integration, and one day one of them stopped to work (no wifi connection, no reaction on button). I supposed it to be dead, but I found your thread about OpenBeken, so decided to give it a try. Soldered wires, updated firmware and voila, it is alive again

Exactly the same thing happened to me a couple of days ago with BL0937 version. This was really strange because when I did try to read it with BK7231Flasher I got CRC mismatch error and also was unable to read OBK configuration. But flashing with OB was without any problems and after some setup troubles, it is now fully functional again.

That\s good to hear, however, I have never heard yet about CRC error in BK7231 GUI flasher. It happens in HID_download_py because of the wrong algorithm implementation, but not in my flasher. Did it happen every time you read?
Can you read device configuration with the Web App method? The one from our YT video?
https://www.youtube.com/watch?v=WunlqIMAdgw

minusync wrote:

I have also some questions to p.kaczmarek2 if he happens to read this.
Is it still needed to "to save your BL0942 init and calibration constant setting commands in LittleFS or startup command " as described in the first post?

You can use our docs to check the latest state of c ommands:

https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/commands.md

minusync wrote:

Can I save the button state after a power outage? I have not found any settings for that. Maybe I missed something.

Do you mean relay state?

It can be also done via WWW GUI with "Configure Startup" menu

p.kaczmarek2 wrote:

I have never heard yet about CRC error in BK7231 GUI flasher. It happens in HID_download_py because of the wrong algorithm implementation, but not in my flasher. Did it happen every time you read?

I didn't try that hard because the Tuya software didn't seem to work anyway. I first tried to just read for backup and then also the OBK settings just in case. The weirder thing is that the OB software worked. I think the memory was somehow corrupted?? because initially OB also had almost similar constant reboot problem. At one point, however, all the settings disappeared by themselves - even wifi and MQTT. After setting everything up again, suddenly everything started working.

p.kaczmarek2 wrote:

You can use our docs to check the latest state of c ommands:

Since it is obviously now possible to perform calibration in the webapp, c commands are not directly necessary for this. The point of the question was rather whether the calibration made in the web app is preserved after the device restart?

minusync wrote:

Since it is obviously now possible to perform calibration in the webapp, c commands are not directly necessary for this. The point of the question was rather whether the calibration made in the web app is preserved after the device restart?

Yes, I answered you in the previous post. Please open this screenshot from the documentation:

The text on screenshot reads:

Quote:

Measure the real voltage with an external, reliable power meter and enter this voltage via this command to calibrate. The calibration is automatically saved in the flash memory.

The calibration is saved in flash memory, which means, it's kept forever stored in the device. In general, it's worth to check the docs often, both our commands list and FAQ:
https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/faq.md

p.kaczmarek2 wrote:

Yes, I answered you in the previous post. Please open this screenshot from the documentation:

Nice to know, but there was a little bit of contradiction between the first post of the thread and the current situation. That is why I always promote whenever it is possible to keep the first post with actual instructions up to date. This is the place where most of the users will look for actual setups. Especially since the device database literally points to the forum thread of each device. So users should by design get most if not all of the necessary information for setup from there.
The best example of a great (in my opinion) , clear structure and instructions for users is XDA forums like for example this one: https://xdaforums.com/t/guide-magisk-unlock-root-keep-root-oos-13-1-0-591.4252373/
thanks

Hallo,

I flashed a LSPA9 plug successfully with tuya-cloudcutter.
Everything is working well except when I'm switching the plug on or off manually with the button the state will not transferred via MQTT.

When I switch this plug remotely via MQTT everything is working well.

Is there any workaround or a fix for this problem?

Have you followed our HASS discovery guide? What is your device config?
Easy Home Assistant Discovery Pairing for BK7231T, BK7231N, BL602, XR3, W800, W600, etc. - OpenBeken

Thank you for your feedback.

I don't use HA. I'm happy with FHEM...

I followed this guide an this fixed my problem.

I made some typos in my mqtt config.

Hello,

I purchased a smart plug on AliExpress: https://fr.aliexpress.com/item/1005005725291219.html It had CB2S and BL0937 as chipsets with Tuya version 1.1.15, making it flashable with Tuyacutter. Through the exchanges in this conversation, I managed to flash the smart plug with OpenBK 1.17.389 (had to desolder the CB2S chip to do so, as the flash wouldn't start on bk7231flasher_1.1.6 otherwise).



The smart plug is discovered by Home Assistant, but some elements are missing, which are available on MQTT Explorer. I can retrieve "energycounter" and "energycount_last_hour," but not "energycounter_last_hour," "energycounter_today," and "energycounter_clear_date."



This issue occurs on both smart plugs I flashed with OpenBK. I thought of bypassing the problem through the configuration.yaml and creating the sensor manually, but that doesn't work either. Any ideas?



Thank you very much.

Do you have set a SetupEnergyStats command in either startup line or autoexec.bat?

Yes,

Startup command:

>>20889664 I probably have exactly the same plug as you do (I bought 2 of them, by mistake as I wanted the Zigbee version): Same CB2S+BL0937, same tuya firmware 1.1.15. That gave me the occasion to experiment, so I flashed both with OpenBK7231N_1.17.391 and put them on my home network. Good practice for my soldering and de-soldering skills (the second one was nasty, CB2S was very tight).
I stopped before the full configuration (only did the wifi config so it's more convenient to access them) cause I am on linux and was not able to launch the configuration extractor (a windows exe). Could you share your configuration? I think the chance of your plugs being exactly like mines is high, so appart from extracting the info from the tuya.bin it's my best shot at getting things right first try....

BTW I also plan to use MQTT to communicate with my HomeAssistant (so that it is close to my other zigbee plugs connected to my zigbee2mqtt bridge) so I will report if I manage to do it (or not).