Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tam
Device seems to be using CB2S module, which is BK7231N chip.
- Relay (channel 1) on P26
- WiFi LED on P8
- Button (channel 1) on P10
- BL0937 ELE on P7
- BL0937 VI on P6
- BL0937 SEL on P24
// This aliased command will turn off relay on CH1 after 10 seconds
// addRepeatingEvent [IntervalSeconds][RepeatsOr-1][CommandToRun]
alias turn_off_after_time addRepeatingEvent 10 1 setChannel 1 0
// this will run the turn off command every time that CH1 becomes 1
addChangeHandler Channel1 == 1 turn_off_after_time
// display seconds timer
setChannelType 2 TimerSeconds
// set start values as "remember in flash"
SetStartValue 1 -1
SetStartValue 2 -1
// channel 2 is timer
// channel 1 is relay
// here is countdown value in seconds - 30
alias turn_off_after_time backlog setChannel 2 30
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
// this will run the turn off command every time that CH1 becomes 1
addChangeHandler Channel1 == 1 turn_off_after_time
// this will run the turn off command every time that CH1 becomes 0
addChangeHandler Channel1 == 0 on_turned_off
again:
if $CH2!=0 then do_tick
delay_s 1
goto again
alias do_check if $CH2==0 then turn_off_relay
!=
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.batfor 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,
-1relay startup, and a retained low-numbered channel for timers solved LED control, power-loss behavior, and Home Assistant automation.
delay_s 5 before POWER ON or setChannel 1 1. [#20819243]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]-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]-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]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]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]-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]configuration.yaml for integrating that value into Home Assistant behavior. [#20802077]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]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]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]