logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Turning Off LED on Tuya AU LSPA9 Smart Socket After Successful Openbeken Flash

ciknururko 6900 57
Best answers

How can I turn off the LED on a Tuya AU LSPA9 smart socket after flashing OpenBeken so it no longer stays on all the time?

Identify which GPIO drives the LED, then remap it in the template so it follows the socket state instead of staying always on. For this device, the template decode showed a CB2S/BK7231N module with the WiFi LED on P8 [#20796031] After changing the mapping from “WiFi LED on P8” to “LED_N on P8,” the LED started toggling correctly with the plug state [#20796043]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #31 20801972
    ciknururko
    Level 3  
    Posts: 44

    Thank you.... Changed as suggested by you. Working now as needed.

    Please guide me on the following:-

    I have set CH15 as the inching timer. Can I update this text field value from Home Assistant?

    Kindly guide
  • ADVERTISEMENT
  • #32 20802077
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14604
    Help: 654
    Rate: 12618
    Of course, the whole idea of channels is to be fully scriptable variables.

    You can refer to our documentation here:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/mqttTopics.md

    You can publish data to channel MQTT topic and listen to it, here are details:
    Table showing information on MQTT topics, sample values, and descriptions for OpenBeken.
    You can use channel data in anyway you like, just use Home Assistant configuration.yaml script to adjust HA behaviour to your needs.
    Helpful post? Buy me a coffee.
  • #33 20802308
    ciknururko
    Level 3  
    Posts: 44
    Thank you worked....
  • #34 20802372
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14604
    Help: 654
    Rate: 12618
    Can you please post here your full autoexec.bat, device config, and HASS Yaml, so our readers can also use those scripts? Thanks!
    Helpful post? Buy me a coffee.
  • #35 20803372
    ciknururko
    Level 3  
    Posts: 44

    Here is my HASS YAML

    Code: YAML
    Log in, to see the code


    and autoexec.bat

    Code: text Expand Select all Copy to clipboard
    
setChannelType 2 TimerSeconds
alias turn_off_after_time backlog setChannel 2 $CH15
alias on_turned_off setChannel 2 0
alias turn_off_relay setChannel 1 0
alias do_check if $CH2==0 then turn_off_relay 
alias do_tick backlog addChannel 2 -1; do_check
addChangeHandler Channel1 == 1 turn_off_after_time 
addChangeHandler Channel1 == 0 on_turned_off
again:
if $CH2!=0 then do_tick
delay_s 1
goto again

  • #36 20819079
    ciknururko
    Level 3  
    Posts: 44

    >>20802077
    Hi,

    I have two queries:

    1. In addition to my current autoexec.bat, how can I set a time function so that at a specified time the switch gets TURN ON or TURN OFF?
    e.g. if current_time == 17:00, turn off switch.

    2. How to make the switch turn on after 5 seconds when the main power to the switch is turned on?

    Kindly guide.
  • #37 20819243
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14604
    Help: 654
    Rate: 12618
    ciknururko wrote:

    1. In addition to my current autoexec.bat, how can I set a time function so that at a specified time the switch gets TURN ON or TURN OFF?
    e.g. if current_time == 17:00, turn off switch.

    This can be done with addClockEvent function.
    Screenshot of addClockEvent documentation in the OpenBK7231T_App GitHub project.
    Read more at:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/commands.md
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/autoexecExamples.md
    NTP must be run in order for clock events to work.

    ciknururko wrote:

    2. How to make the switch turn on after 5 seconds when the main power to the switch is turned on?

    Let me ask, by main power, you mean after the plug got mains power? After the reboot?
    Well, if that's the case, use the following script:
    Code: text Expand Select all Copy to clipboard
    
// your current autoexec.bat here

// now delay
delay_s 5
// now power ON
POWER ON

    Alternatively, you can manipulate channels there:
    Code: text Expand Select all Copy to clipboard
    
// your current autoexec.bat here

// now delay
delay_s 5
// now power ON
setChannel 1 1

    Alternatively, you can use an event:
    Code: text Expand Select all Copy to clipboard
    
// This command will turn on relay on CH1 after 10 seconds
// addRepeatingEvent	[IntervalSeconds][RepeatsOr-1][CommandToRun]
addRepeatingEvent 10 1 setChannel 1 1

    Let me know if you have any futher questions or guidance.
    Helpful post? Buy me a coffee.
  • #38 20819295
    ciknururko
    Level 3  
    Posts: 44
    p.kaczmarek2 wrote:
    // your current autoexec.bat here

    // now delay
    delay_s 5
    // now power ON
    POWER ON


    worked.... thank you

    Added after 5 [minutes]:

    p.kaczmarek2 wrote:
    This can be done with addClockEvent function.


    Code: text Expand Select all Copy to clipboard
    setChannelType 2 TimerSeconds
alias turn_off_after_time backlog setChannel 2 $CH15
alias on_turned_off setChannel 2 0
alias turn_off_relay setChannel 1 0
alias do_check if $CH2==0 then turn_off_relay 
alias do_tick backlog addChannel 2 -1; do_check
addChangeHandler Channel1 == 1 turn_off_after_time 
addChangeHandler Channel1 == 0 on_turned_off

startDriver ntp
ntp_timeZoneOfs +05:30
alias plug_on backlog POWER ON

waitFor NTPState 1
if $hour>=14&&$hour<21 then plug_on

again:
if $CH2!=0 then do_tick
delay_s 1
goto again



    1. I have set inching of 10 seconds via GUI just for testing purposes(plug should turn off after 10 seconds).
    2. The plug gets turn on if $hour>=14&&$hour<21 but it doesn't get turn off automatically after 10 seconds.

    Am I doing something wrong here?

    Added after 22 [minutes]:

    Also can I call some other file from within autoexec.bat

    e.g

    Code: text Expand Select all Copy to clipboard
    //autoexec.bat
//some commands in autoexec.bat
function.bat

//function.bat (this is another file created)
startDriver ntp
ntp_timeZoneOfs +05:30
delay_s 5
POWER ON
  • #39 20821836
    ciknururko
    Level 3  
    Posts: 44
    Kindly reply
  • ADVERTISEMENT
  • #40 20821983
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14604
    Help: 654
    Rate: 12618
    1. Maybe you can try using setChannel instead of POWER, but both should work.
    Change:
    Code: text Expand Select all Copy to clipboard
    
alias plug_on backlog POWER ON

    to:
    Code: text Expand Select all Copy to clipboard
    
alias plug_on backlog setChannel 1 1

    This should call:
    Code: text Expand Select all Copy to clipboard
    
addChangeHandler Channel1 == 1 turn_off_after_time 

    if not, I will have to test for a bug in the scripting and fix it.


    2. You can use startScript:
    Code: text Expand Select all Copy to clipboard
    
startScript	[FileName] [Label] [UniqueID]

    like:
    Code: text Expand Select all Copy to clipboard
    
startScript myBat.bat * 12345

    NOTE: the ID 12345 can be used to cancel script later
    Helpful post? Buy me a coffee.
  • #41 20822030
    ciknururko
    Level 3  
    Posts: 44
    p.kaczmarek2 wrote:
    startScript myBat.bat * 12345


    Worked....

    Added after 4 [minutes]:

    p.kaczmarek2 wrote:
    alias plug_on backlog setChannel 1 1


    Code: text Expand Select all Copy to clipboard
    setChannelType 2 TimerSeconds
alias turn_off_after_time backlog setChannel 2 $CH15
alias on_turned_off setChannel 2 0
alias turn_off_relay setChannel 1 0
alias do_check if $CH2==0 then turn_off_relay 
alias do_tick backlog addChannel 2 -1; do_check
addChangeHandler Channel1 == 1 turn_off_after_time 
addChangeHandler Channel1 == 0 on_turned_off

startDriver ntp
ntp_timeZoneOfs +05:30
alias plug_on backlog setChannel 1 1

waitFor NTPState 1
if $hour>=14&&$hour<21 then plug_on

again:
if $CH2!=0 then do_tick
delay_s 1
goto again



    still not working after changing as suggested by you..... The plug gets TURN ON but doesn't TURN OFF after "10 seconds" which is set using GUI
    Screenshot of an interface with the Toggle 1 button turned on, an entry field Change channel 15 value set to 10, and a Set! button below.

    Kindly check and guide
  • ADVERTISEMENT
  • #42 20822140
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14604
    Help: 654
    Rate: 12618
    I need to check on my side, but what about a temporary workaround?
    Change:
    Code: text Expand Select all Copy to clipboard
    
alias plug_on backlog setChannel 1 1

    To:
    Code: text Expand Select all Copy to clipboard
    
alias plug_on backlog setChannel 1 1; turn_off_after_time 

    Maybe that can help.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #43 20822665
    ciknururko
    Level 3  
    Posts: 44
    Not working...
  • #44 20822736
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14604
    Help: 654
    Rate: 12618
    I think it is working, there is another problem.

    Most likely your channel 15 is 0.

    That would cause delay to be non-existent.

    Here is my current version that fixes channel 15 and makes sure it has non zero value:
    Code: text Expand Select all Copy to clipboard
    

// TODO: adjust second 15 here
setChannel 15 15

setChannelType 15 TextField
setChannelLabel 15 TurnOffTime
setChannelType 2 TimerSeconds
alias turn_off_after_time backlog setChannel 2 $CH15
alias on_turned_off setChannel 2 0
alias turn_off_relay setChannel 1 0
alias do_check if $CH2==0 then turn_off_relay 
alias do_tick backlog addChannel 2 -1; do_check
addChangeHandler Channel1 == 1 turn_off_after_time 
addChangeHandler Channel1 == 0 on_turned_off

startDriver ntp
ntp_timeZoneOfs 1
alias plug_on backlog setChannel 1 1

waitFor NTPState 1
if $hour>=14&&$hour<21 then plug_on

again:
if $CH2!=0 then do_tick
delay_s 1
goto again

    Tested on BK7231 device:
    Eurobatt power strip with connected adapter and activated switch.
    Helpful post? Buy me a coffee.
  • #45 20823009
    ciknururko
    Level 3  
    Posts: 44

    This worked....

    But the timer is hardcoded to 15 seconds (or whatever we set it). I was hoping to set the timer from Home Assistant, which I was doing in my version of the script.

    Is it not possible to achieve the same without hardcoding??

    Kindly guide.
  • #46 20823023
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14604
    Help: 654
    Rate: 12618
    Only first 10 channels or so can be retained.

    So you need to change channel 15 to let's say 5 and then set start value to "-1" which means "save in flash":
    Code: text Expand Select all Copy to clipboard
    

setStartValue 5 -1
setChannelType 5 TextField
setChannelLabel 5 TurnOffTime
setChannelType 2 TimerSeconds
alias turn_off_after_time backlog setChannel 2 $CH5
alias on_turned_off setChannel 2 0
alias turn_off_relay setChannel 1 0
alias do_check if $CH2==0 then turn_off_relay 
alias do_tick backlog addChannel 2 -1; do_check
addChangeHandler Channel1 == 1 turn_off_after_time 
addChangeHandler Channel1 == 0 on_turned_off

startDriver ntp
ntp_timeZoneOfs 1
alias plug_on backlog setChannel 1 1

waitFor NTPState 1
if $hour>=14&&$hour<21 then plug_on

again:
if $CH2!=0 then do_tick
delay_s 1
goto again

    Fragment of a table with channel setting options.

    This will make value of channel 5 (inching time) remembered between reboots and settable via Home Assistant.

    Added after 47 [seconds]:

    PS: You will also need to clear the channel type 15 in the Web App, so the second text field diseappers
    Helpful post? Buy me a coffee.
  • #47 20823845
    ciknururko
    Level 3  
    Posts: 44

    Perfect worked....... Thank you so much for your help and guidance...

    startDriver ntp
    ntp_timeZoneOfs +05:30
    alias plug_on backlog setChannel 1 1
    //addClockEvent 14:36 0xff 1 plug_on

    addClockEvent if $hour>=14&&$hour<21 then 0xff 1 plug_on

    Can we use addClockEvent in the above manner? I mean, is combining IF THEN possible with addClockEvent?

    Kindly reply
  • #48 20823941
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14604
    Help: 654
    Rate: 12618
    Currently it's not possible, it's an event, by definition, not a zone.

    Futhermore that would not allow user override of state.

    You should rather do:
    1. at hour 14 do turn on and on hour 21 turn off
    2. alternatively, you can make a loop in autoexec.bat and poll current hour, let's say, every minute, manually, and there put that if condition, this would work, but it would not allow user to override the relay state between 14 and 21

    Do you want user to be able to override the relay state (via WWW panel, HA, or a button) between 14 and 21?
    Helpful post? Buy me a coffee.
  • #49 20825578
    ciknururko
    Level 3  
    Posts: 44

    No, nothing like that... I was just curious if it can be used in that manner.

    Again, I would really like to thank you for all your help. I really appreciate it.
  • #50 20826035
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14604
    Help: 654
    Rate: 12618
    ciknururko wrote:

    No, nothing like that... I was just curious if it can be used in that manner.

    We have considered this in the past, but the problem is, how would we then allow user to "override" the state of the lamp? Maybe we could set a flag to specify whether user is allowed to override it or not...
    Helpful post? Buy me a coffee.
  • #51 20826107
    ciknururko
    Level 3  
    Posts: 44
    Yes... if possible kindly implement that.
  • #52 20830509
    ciknururko
    Level 3  
    Posts: 44

    Hi,

    Is there a way to check from HA if an update is available for the plug?
    e.g. For Chipset: BK7231N Build: Build on Nov 13 2023 14:23:53 version 1.17.308 is the latest.

    If there is any OTA available in the future, can we have a sensor in HA that reports that an update is available???

    Secondly, I am having a very peculiar issue. If the plug is powered ON and is detected by HA. After some time, if I restart HA, after the restart the plug is shown as unavailable in HA until I manually toggle it. Any idea why this is happening?

    Kindly reply
  • #53 20830592
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14604
    Help: 654
    Rate: 12618
    ciknururko wrote:

    Is there a way to check from HA if an update is available for the plug?
    e.g. For Chipset: BK7231N Build: Build on Nov 13 2023 14:23:53 version 1.17.308 is the latest.

    It is a bit problematic because Github is now HTTPS-only and current version of OBK can't do HTTPS request, only HTTP. Still, why do you want to update that often?


    ciknururko wrote:

    Secondly, I am having a very peculiar issue. If the plug is powered ON and is detected by HA. After some time, if I restart HA, after the restart the plug is shown as unavailable in HA until I manually toggle it. Any idea why this is happening?

    It was discussed here:
    https://www.elektroda.com/rtvforum/topic4001877.html
    I would fix it just by enabling "broadcast self state every N seconds" in flags
    Helpful post? Buy me a coffee.
  • #54 20830622
    ciknururko
    Level 3  
    Posts: 44

    p.kaczmarek2 wrote:
    It is a bit problematic because GitHub is now HTTPS-only and the current version of OBK can't make HTTPS requests, only HTTP. Still, why do you want to update that often?

    Just wanted to know if it was possible..
    p.kaczmarek2 wrote:
    I would fix it just by enabling "broadcast self state every N seconds" in flags

    Fixed.... thank you
  • #55 20830637
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14604
    Help: 654
    Rate: 12618
    That OTA check, would you like it done on HA side, or on OBK side?

    Maybe it would be possible to do a HTTPS query with HA script somehow. And if you want it on OBK side, then we either need to add HTTPS to OBK or create our own simple update HTTP server with public IP.
    Helpful post? Buy me a coffee.
  • #56 20830663
    ciknururko
    Level 3  
    Posts: 44

    p.kaczmarek2 wrote:
    That OTA check, would you like it done on HA side, or on OBK side?
    HA side
  • #57 20830723
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14604
    Help: 654
    Rate: 12618
    Then we would need to port our Javascript getReleases function to HA:
    https://github.com/OpenBekenIOT/webapp/blob/d...a07bdb06175492405e7884e4bf22/vue/ota.vue#L323
    However, I don't think that we can run Javascript in HA. I haven't tried doing that kind of thing yet. Do you know how we could do a HTTPS GET on HA side?
    Helpful post? Buy me a coffee.
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion revolves around the Tuya AU LSPA9 Smart Socket, which was successfully flashed with OpenBeken firmware. The main issue addressed is how to turn off the LED indicator on the device when it is powered off. Users explored GPIO extraction to identify the LED control pin and confirmed that the LED is connected to GPIO P8. Solutions were proposed to configure the device to remember its last state after reboot and to implement a countdown timer for automatic shutoff after a specified duration. Users also discussed integrating the device with Home Assistant for remote control and setting inching timers via a GUI. Additionally, there were inquiries about switching between firmware versions and backing up settings.
Generated by the language model.
Today's popular

FAQ

TL;DR: For BK7231N/CB2S LSPA9 plugs, 6 GPIOs were identified, and one fix solved the main issue: change P8 from WiFi LED to LED_N. As the expert said, "set it to -1" to restore last-state memory, then use autoexec.bat for auto-off timers, startup delays, and NTP-based schedules. [#20796861]

Why it matters: This FAQ gives OpenBeken users a fast, reusable path to fix LED behavior, restore state memory, add inching, and expose controls to Home Assistant.

Option What it does Main advantage Main limitation
Full OpenBeken flash Replaces Tuya firmware Web UI, scripts, MQTT, Tasmota Control support Moving to ESPHome is possible but problematic on BK devices
"Cut from cloud" Keeps local Tuya-style control without cloud Works with TinyTuya Android app path was unclear in the thread
Restore original Tuya Flash back a 2 MB backup over UART Returns stock behavior Requires prior backup and wired flashing

Key insight: Most problems in this thread were configuration issues, not hardware faults. Correct pin mapping, -1 relay startup, and a retained low-numbered channel for timers solved LED control, power-loss behavior, and Home Assistant automation.

Quick Facts

  • The decoded CB2S/BK7231N template exposed 6 key pins: relay P26, WiFi LED P8, button P10, BL0937 ELE P7, BL0937 VI P6, and BL0937 SEL P24. [#20796031]
  • The original device JSON showed power-monitoring protection values of 10,500 mA over-current, 275 V over-voltage, and 85 V low-voltage on the same LSPA9 plug family. [#20796024]
  • Auto-off examples in the thread used 10 s, 15 s, and 30 s timers, and one user target was 20 minutes after turn-on. [#20797359]
  • A startup automation example delayed relay activation by 5 seconds after mains power returned, using delay_s 5 before POWER ON or setChannel 1 1. [#20819243]
  • For retained user-set timers, only the first ~10 channels can be remembered in flash, so the working solution moved the delay value from CH15 to CH5. [#20823023]

How do I turn off the power button LED on a Tuya AU LSPA9 smart socket after flashing OpenBeken?

Change the LED pin role from the default WiFi LED to LED_N on P8. In the thread, that change made the button LED start toggling correctly instead of staying on when the relay was off. If your socket uses the same CB2S layout, P8 is the first pin to test for LED behavior after flashing. [#20796043]

What's the correct GPIO mapping for the LED, relay, button, and BL0937 on a CB2S-based Tuya AU LSPA9 smart plug?

The decoded mapping was relay P26, WiFi LED P8, button P10, BL0937 ELE P7, BL0937 VI P6, and BL0937 SEL P24. The module was identified as CB2S, which uses a BK7231N chip. That mapping came directly from the extracted Tuya JSON and the template importer decode. [#20796031]

How can I make an OpenBeken-flashed smart plug remember its last relay state after a power loss or reboot?

Set the relay startup value to -1 so OpenBeken restores the state from before reboot. In the thread, the plug remembered state correctly before a script change, then worked again after a reset and correct startup configuration. If it still powers on unexpectedly, check startup values, scripts, and pin configuration first. [#20796260]

Where do I set the OpenBeken startup option to use "Remember last state" with a value of -1?

Open Config -> Configure Startup and enter -1 for the relay channel. The expert answer was exact: "enter -1 in field for relay channel." One mobile limitation appeared in the thread: some phones show a numeric keyboard that makes typing a minus sign difficult. [#20796861]

What is GPIO extraction in OpenBeken, and how do I use the template importer to identify pins on a Tuya plug?

"GPIO extraction" is a device-analysis method that reads Tuya configuration data, identifies which MCU pins drive relay, LEDs, buttons, and sensors, and converts that data into a usable OpenBeken pin map. Use it in 3 steps: 1. Extract the device JSON. 2. Paste it into the web template importer. 3. Read the decoded pin assignments, such as P8, P10, and P26 on this plug. [#20796031]

How can I create an inching or auto-off timer in OpenBeken so the socket turns off after a set number of seconds or minutes?

Use autoexec.bat with a change handler that starts a countdown when the relay turns on. The simplest working example was: alias turn_off_after_time addRepeatingEvent 10 1 setChannel 1 0 plus addChangeHandler Channel1 == 1 turn_off_after_time. Change 10 to any delay in seconds, or build a channel-based countdown for longer periods. [#20797359]

What is autoexec.bat in OpenBeken, and how is it used for relay timers, startup behavior, and automation scripts?

"autoexec.bat" is an OpenBeken startup script file that runs commands automatically after boot, stores automation logic, and can control relays, timers, NTP actions, and channel behavior without manual clicks. In this thread it was used for auto-off countdowns, a 5-second delayed power-on, and clock-based control. It is stored separately, so backing up only the CFG partition is not enough. [#20797988]

How do I add a TextField channel in OpenBeken so the turn-off delay can be changed from the web UI instead of hardcoding the time in the script?

Create a channel as TextField, then reference that channel in the timer alias instead of a fixed number. The thread's working approach used a user-editable channel and replaced the hardcoded delay with $CHx, so the web UI value became the active turn-off delay. If the field is 0, add a condition so auto-off stays disabled. [#20801960]

Why does an OpenBeken timer script stop the plug from remembering the last state, and what configuration mistakes should I check?

A timer script usually breaks last-state behavior because of configuration errors, not because timers are unsupported. Check 3 items: 1. Relay startup is still -1. 2. Your current script does not force setChannel 1 1 on boot. 3. Pin and startup pages match the real hardware. In the thread, a reset restored correct behavior, which strongly pointed to a bad configuration state. [#20797512]

How can I update an OpenBeken channel value such as an inching timer from Home Assistant over MQTT?

Publish the new value to the channel's MQTT topic from Home Assistant. The expert explained that OpenBeken channels are fully scriptable variables, so a retained TextField channel such as CH5 can hold the delay and be changed externally. The thread specifically points to channel MQTT topics and configuration.yaml for integrating that value into Home Assistant behavior. [#20802077]

What is the difference between flashing full OpenBeken firmware and using the "Cut from cloud" option on a Tuya plug?

Full OpenBeken flashing gives you the OpenBeken web UI, scripts, and app compatibility such as Tasmota Control, while "Cut from cloud" only removed cloud dependence and still let the user control the plug with TinyTuya. The thread did not confirm a dedicated Android app for the "Cut from cloud" path, and even the expert marked that area as less commonly used. [#20800338]

OpenBeken vs ESPHome on BK7231N plugs: which is easier to switch to, and what are the limitations of moving between them?

OpenBeken was the easier path in this thread, and switching from ESPHome back to BK firmware was described as possible but problematic because of a "strange OTA format." Returning to original Tuya firmware was easier if you had a 2 MB backup and a UART programmer. So the safe rule is: experiment only after you save a wired restore image first. [#20797521]

How do I back up and restore an OpenBeken device, including the CFG partition, template, and autoexec.bat, before experimenting with settings or firmware changes?

Back up three things: the device template text, the autoexec.bat text, and the full CFG partition. The web app can export the template and download the CFG partition, which includes much more than the template, including SSID-related data. To restore stock Tuya later, flash back the 2 MB backup over UART. Do not forget that autoexec.bat is not inside the CFG partition. [#20797988]

What's the best way to schedule a Tuya/OpenBeken plug to turn on or off at a specific time using addClockEvent, NTP, or startup scripts?

Use addClockEvent for exact clock times and start NTP first. The working pattern is: 1. startDriver ntp 2. set ntp_timeZoneOfs such as +05:30 3. add a clock event or a boot-time delay script like delay_s 5 then POWER ON. The thread also confirmed that addClockEvent does not support combining if ... then as a time-range zone in one command. [#20823941]

How could Home Assistant check whether a newer OpenBeken OTA build is available for a BK7231N device, such as by using REST commands or another HTTPS-based method?

Do the update check on the Home Assistant side with an HTTPS-capable method such as rest_command. The thread ruled out a simple device-side check because the current OpenBeken build could make only HTTP requests, while GitHub releases are HTTPS-only. The suggested direction was to port the web app's release-check logic to Home Assistant instead of the plug itself. [#20830904]
Generated by the language model.
ADVERTISEMENT