MOES 1-2 Light Switch: WB2S BK7231T TuyaMCU configuration for OpenBeken

Name: MOES 1-2 Light Switch: WB2S BK7231T TuyaMCU configuration for OpenBeken
Uploaded: 2023-04-12T22:06:29+02:00
Description: Hello and welcome I have a pair of MOES lighting switches, model WS-EUB, purchased from ali, I would like to get rid of the tuya, so thanks to the help of p.kaczmarek2, I uploaded soft BK7231T via UART. The soft uploaded wifi I put it on my WIFI but I got stuck at the stage of setting this BK :(...

Question

Hello and welcome I have a pair of MOES lighting switches, model WS-EUB, purchased from ali, I would like to get rid of the tuya, so thanks to the help of p.kaczmarek2, I uploaded soft BK7231T via UART. The soft uploaded wifi I put it on my WIFI but I got stuck at the stage of setting this BK :(...

p.kaczmarek2 · Accepted Answer

Autoexec is created here: here Create file: since you say only one button, I think I already know how to configure it In autoexec.bat paste: Code: text Expand Select all Copy to clipboard startDriver TuyaMCU setChannelType 1 toggle linkTuyaMCUOutputToChannel 1 bool 1 save, reboot. You should get a button on the GUI that controls the relay. Check.

p.kaczmarek2 · Accepted Answer

Most likely the LED indicates that the MCU thinks it is not paired. OpenBeken defaults to the "paired" state when you also connect MQTT, but if you want a shortcut and silence the LED, try adding the following to autoexec at the end:
tuyaMcu_defWiFiState 4
This will set the MCU's WiFi state to 4, which is "connected to router and to cloud", and should calm the LED down.

You can find the command documentation here:
https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/README.md

Unless it's about another diode, then we'll think about it.

p.kaczmarek2 · Answer

At this point, you're already up and running TuyaMCU - startDriver TuyaMCU in autoexec.bat, right?
If not, then in Open Web Application, in LittleFS, do autoexec.bat and there enter "startDriver TuyaMCU" so that it starts automatically at system startup. Do a reboot.

I also see you posted the log:


Info:TuyaMCU:TUYAMCU received: 55 AA 00 00 00 01 01 01 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 0 (Hearbeat) with 8 bytes
Info:TuyaMCU:TUYAMCU received: 55 AA 00 07 00 08 07 02 00 04 00 00 00 00 1B 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 7, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 0
Info:TuyaMCU:TUYAMCU received: 55 AA 00 07 00 05 01 01 00 01 01 0F 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=0]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 1, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 
Info:TuyaMCU:TUYAMCU received: 55 AA 00 00 00 01 01 01

this log shows the dpID of the variables responsible for the relays/buttons, but it's in such a form that I don't know what is what.

Can you do the following test:
1. In Web App Logs, clear the log
2. Press the first touch button
3. Copy this web app log, and note which ones dpID from the log corresponds to him
4. Repeat steps 1 2 and 3 for each touch button

The pictures don't show how many buttons it has. Four touch buttons? Two?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.

PSlowik · Answer

As for LittleFS, I don't know what it is, where it is etc :/ The on/off switch is just a single button physical button

PSlowik · Answer

I confirm there is a button and it reacts like pressing the keys on the plate lighting up green or the relay is working I don't know yet because the mammpkytki are fully assembled but I will test it soon.
But what to do with the LED that blinks all the time ...?
In tuya it worked so that if the light was not turned on, the diode barely shines and when the light is turned on, the diode starts to shine strongly ...
And now it's blinking...

PSlowik · Answer

haha it actually worked the diode reacts perfectly, now just some MQTT and then recommends 2-button switches

)

Do you have to recreate the autoexec every time you run it? because it disappears after reboot

I confirm the relay is working, the light is on

You are great!

Now spr to set mqtt because OpenBK is probably not integrated with HA??

p.kaczmarek2 · Answer

For normal devices there is automatic HA discovery where everything happens by itself:
https://www.youtube.com/watch?v=pkcspey25V4&ab_channel=Elektrodacom
This way you can pair a lot and everything configures itself.

Unfortunately, your device is weird by the manufacturer - I don't know why it needs TuyaMCU and UART control to control ONE relay and you have to write the Yaml code for it manually.

Start by configuring MQTT in Configure MQTT. On the web panel, the MQTT status should be connected.

Then in Home Assistant add the device via configuration.yaml:

Log in, to see the code

change the names of course, I'm testing on a simulator on windows. You will have a different name than me, you will probably enter something else as "Client Topic" (I have WindowsOBK there)

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.

PSlowik · Answer

It worked

I'm really glad…

It will still help if I put soft on the 2-button switch

if I can.

Please tell me how is the overall stability of this software? Much better because it doesn't work in the cloud...

p.kaczmarek2 · Answer

Remember to enable autoexec too startDriver SSDP for Windows to see devices: Stability test showed it can run for months, here is a screenshot of the status as of January 11, 2023 : Uptime 46 days Recently, we have additionally enabled the watchdog to be able to automatically restart the software in the event of a possible suspension of the software soft with two buttons probably similarly only you set 2 toggles and map two TuyaMCU variables, probably ID 1 and 2

p.kaczmarek2 · Answer

UPDATE 2023-05-01 From today, Home Assistant Discovery also works for Toggle channels from TuyaMCU. This means you don't have to write YAML by hand anymore. Configuration below: It is seen by Home Assistant Discovery and can be added automatically to the HA.

styb113 · Answer

Hello, I have a similar device to this one with 3 buttons and relays. It also has RF functionality. If I flash it with OpenBK how do I have to configure the settings for the TUYA MCU?

PullScanner1 · Answer

bonjours, j’utilise OpenBK7231T sur un interrupteur Tuya (BK7231T + MCU Tuya).
Le relais fonctionne correctement et est bien piloté via TuyaMCU + MQTT + Home Assistant.
Configuration actuelle :
startDriver TuyaMCU
setChannelType 1 toggle
linkTuyaMCUOutputToChannel 1 bool 1
MQTT OK (publication et contrôle depuis HA OK)
tuyaMcu_defWiFiState 4

mon problème ( enfin si on peut dire que s'est un probléme ) le relais fonctionne parfaitement, le bouton physique est OK (retour état id 1)
MQTT remonte correctement dans HA, mais la LED reste allumée en permanence, indépendamment de l’état ON/OFF du relais
mon hypothèse LED non mappée à un GPIO OpenBK ou LED pilotée en inverse / mal configurée
ou LED liée à un autre DP ID Tuya non encore mappé

mon objectif trouver le GPIO LED ou DP correspondant
lier la LED au channel du relais pour synchronisation état ON/OFF,
merci de votre aide.

divadiow · Answer

did you take a backup of the original Tuya firmware?

PullScanner1 · Answer

désoler mais non je n'est pas fait de copie du firmware original

divadiow · Answer

OK, no worries. The Tuya config data may still be present and downloadable. We should be able to get any remaining dpIDs from the schema, assuming the product key is shown in the extraction.

open the saved file in Easy Flasher

you may need to remove any saved wifi credentials from the json before posting the output, if you paired device with Tuya app ever. Credentials may be in base64

PullScanner1 · Answer

J'ai effectué la manipulation dans OBK, mais cela m'indique que tout est effacé. Par contre, il y a eu une évolution depuis hier : la LED du bouton clignote au démarrage, comme pour se connecter au Wi-Fi (donc normal), puis elle reste constamment éteinte lors de l'appui sur le bouton ON/OFF. (Je suis débutant.)

divadiow · Answer

send command tuyaMcu_sendQueryState from the logs tab in the web app. do you get a list of dpIDs and a product code returned?

PullScanner1 · Answer

Après quelques recherches sur ce site, j’ai découvert un fichier autoexec.bat que j’ai téléversé (fichier original).
La configuration des LED était la suivante :

LED1 : verte (Wi-Fi)
LED2 : bleue (état relais)

Configuration initiale du fichier :

startDriver TuyaMCU
setChannelType 1 toggle
linkTuyaMCUOutputToChannel 1 bool 1
tuyaMcu_defWiFiState 4

Le relais fonctionnait correctement, mais la LED1 (Wi-Fi) ne s’activait pas.

Ensuite, avec un peu d’aide et une modification du fichier autoexec.bat, j’ai fait une découverte intéressante.
Après avoir téléversé le fichier modifié et redémarré l’appareil, rien ne semblait fonctionner au départ.

En revanche, après avoir débranché l’appareil, attendu 2 à 3 minutes, puis l’avoir rebranché, le comportement a changé :

La LED1 Wi-Fi s’est mise à clignoter correctement lors de la connexion
Elle s’est ensuite éteinte une fois la connexion Wi-Fi établie
La LED2 est désormais synchronisée avec l’état du relais

Voici le fichier autoexec.bat modifié :

startDriver TuyaMCU
setChannelType 1 toggle
linkTuyaMCUOutputToChannel 1 bool 1

linkTuyaMCUOutputToChannel 2 bool 16

tuyaMcu_defWiFiState 4

Si cela peut aider certaines personnes

MOES 1-2 Light Switch: WB2S BK7231T TuyaMCU configuration for OpenBeken

How do I configure OpenBeken after flashing a BK7231T MOES WS-EUB TuyaMCU switch so the relay works and the front LED stops blinking?

Didn't find an answer? Ask Artificial Intelligence

Topic summary

FAQ

Quick Facts

How do I start TuyaMCU and get a working GUI button on OpenBeken?

Where do I create autoexec.bat so settings persist?

The front LED keeps blinking after flashing—how do I stop it?

How do I find the TuyaMCU dpIDs for my buttons or relays?

How do I configure a two‑button MOES switch?

How do I configure a three‑button switch (even if it has RF)?

Does Home Assistant auto‑discovery work with these TuyaMCU toggles?

How do I add the switch to Home Assistant manually with MQTT/YAML?

How do I set up MQTT on the OpenBeken device?

How can Windows discover my OpenBeken devices on the network?

Is OpenBeken stable on BK7231T hardware?

Why does my single‑relay MOES use TuyaMCU over UART?

Where is the official OpenBeken command documentation?