[Solved] MOES MS108WR Smart Curtain Switch Module Teardown: Reflashing Beken BK7231T Firmware 1.17.201

Hello,
I am adding a teardown for my MOES MS108WR Smart Curtain Switch Module.





It's running the Beken BK7231T.
I've removed the small board to reflash it, but I think you can leave it on



I have run into trouble because I couldn't make a proper backup and flash it right away. For reasons that are unclear, I got error messages when reading the Tuya parameters.

I was able to provide it with new Firmware: 1.17.201 (without error messages).
It has some instability issues. But I think there is a newer version (208), so I got to update it (ota).

This is the json file for the unit, with the correct config:


For the dashboard (card) I used the code from richardsg307 and adapted it for my needs.


( I really need to update the firmware to version 1.17.208 as soon as possible because it is now very unstable
hopefully it will solve it.)

also forgot to post the autoexec file, so here it is
// Set up Aliases MOES MS-108WR Curtainswitch
alias Set_Stop backlog setChannel 3 0; setChannel 2 0; setChannel 1 0; setButtonColor 3 red; setButtonColor 2 red; setButtonColor 1 red
alias Set_Open backlog setChannel 1 1; setButtonColor 1 blue
alias Set_Close backlog setChannel 2 1; setButtonColor 2 blue
alias Set_Finish backlog setChannel 3 1; setButtonColor 3 blue
alias Start_Opening backlog stopAllScripts; startScript autoexec.bat openobk5593B8EB
alias Start_Closing backlog stopAllScripts; startScript autoexec.bat closeobk5593B8EB
alias Stop_All backlog stopAllScripts; startScript autoexec.bat stopobk5593B8EB

// create GUI buttons for HTTP panel
startDriver httpButtons

setButtonEnabled 1 1
setButtonLabel 1 "Open Scherm"
setButtonCommand 1 Start_Opening
setButtonColor 1 red

setButtonEnabled 2 1
setButtonLabel 2 "Sluit Scherm"
setButtonCommand 2 Start_Closing
setButtonColor 2 red

setButtonEnabled 3 1
setButtonLabel 3 "Stop"
setButtonCommand 3 Stop_All
setButtonColor 3 red

// Hide the default GUI buttons
setChannelVisible 1 0
setChannelVisible 2 0
setChannelVisible 3 0

// Loading Event Handlers
addEventHandler OnClick 7 Start_Closing
addEventHandler OnClick 8 Start_Opening
//addEventHandler OnClick 10 Stop_All

// Stop obk5593B8EB on power up
goto stopobk5593B8EB

// do not proceed
return

openobk5593B8EB:
Set_Stop
delay_s 0.1
Set_Open
delay_s 15
Set_Stop
Set_Finish
delay_s 3
Set_Stop
return

closeobk5593B8EB:
Set_Stop
delay_s 0.1
Set_Close
delay_s 15
Set_Stop
Set_Finish
delay_s 3
Set_Stop
return

stopobk5593B8EB:
Set_Stop
Set_Finish
delay_s 3
Set_Stop
return

Hello, can you provide some information what are those "stability issues"? Without having a concrete information it's very hard to say what goes wrong. Maybe you just need a PowerSave 1 in startup command because your device power supply is a low quality one...

Well, I'm investigating what the problem is.
It boots perfectly, then after 60 sec. the whole interface is not responsive, you can still ping the device with no problem.

It looks like it's running fine now, I just powered up the device and waited for a couple of hours.
Now it works perfectly and is 100% responsive.

Maybe it's just this one. I was planning to buy another one anyway so I can test it too.
If I have time, I will boot/start it cold again and monitor the logs, maybe that will give clues.

Added after 4 [minutes]:

I forgot to mention that I have now updated the firmware to 208 (latest version)

Added after 1 [hours] 7 [minutes]:

Okay, now I see that V210 is available. I've now been able to flash it without any problems.
After flashing and rebooting, everything works perfectly so far.

Wait... but there were no changes related to stability in those revisions.

The only thing changed was a driver that does not run by default.

Okay, maybe it was a bad flash from my side.
Anyways, it now seems to work flawlessly.
I'm on the latest firmware: Build on Aug 10 2023 07:03:36 version 1.17.210
So I'm happy

So after a few weeks of testing, I can confirm it works flawlessly

I am happy to hear that the issue is resolved. Let me know if I can help you with anything else.

Problem was probably a bad flash, re-flashed it with the newest firmware version and it worked (stable).