OpenBeken autoexec.bat script to toggle relay on BK7231 from two button inputs

User question

how do I write an autoexec.bat to toggle the relay from either input

Artificial Intelligence Response

Direct answer to the question

• If you’re on an OpenBeken/BK72xx device: put two event handlers in autoexec.bat so the relay toggles when either button/input fires.
• Minimal working script (example: buttons on channels 1 and 2, relay on channel 3):
  • setChannel 3 0
  • addEventHandler OnClick 1 toggleChannel 3
  • addEventHandler OnClick 2 toggleChannel 3

Key points

• Map your GPIOs to channels first (two inputs as Button roles, one output as Relay).
• Use OnClick to get one toggle per press (debounce handled by firmware).
• Reboot to apply; verify with eventDump in the console.

Detailed problem analysis

• Goal: emulate a two‑way/three‑way light switch—either input causes a single output (the relay) to toggle state.
• Event-driven vs. polling: OpenBeken provides an event engine; you register handlers that react to input transitions. This is superior to legacy DOS batch polling because it is low-latency, debounced, and does not waste CPU.
• Channel roles:
  • Inputs: set each input GPIO to a Button role (Button, Button_n depending on the electrical polarity).
  • Output: set the relay GPIO to Relay (or Relay_n) role.
• Why OnClick: It triggers once per short press (debounced). Using OnChannelChange would also work, but you must guard against both edges if you only want a single toggle on a press.
• Power‑on state: explicitly force a known relay state at boot (setChannel 3 0 or 1) so subsequent toggles are deterministic.

Current information and trends

• Modern Wi‑Fi smart switches that run OpenBeken expose a startup script called autoexec.bat and an event system (OnClick/OnDblClick/OnHold, etc.). The approach above aligns with current community best practices for multi-input-to-one-relay behavior on BK7231-class devices.
• For very old PCs (pure DOS), autoexec.bat cannot directly read hardware pins; you must call a helper utility or TSR. That path is increasingly rare compared to embedded firmware solutions.

Supporting explanations and details

• Example autoexec.bat (OpenBeken)
  • setChannel 3 0
  • addEventHandler OnClick 1 toggleChannel 3
  • addEventHandler OnClick 2 toggleChannel 3
  • Optional alternatives:
  • If you prefer to toggle on any state change (older firmware or no OnClick):
    • addEventHandler OnChannelChange 1==1 toggleChannel 3
    • addEventHandler OnChannelChange 2==1 toggleChannel 3
  • If one input is active-low, set that channel’s role to Button_n (or invert with setPinRole or invertChannel) so OnClick semantics stay consistent.
• Validation steps
  • In Web UI: configure Module → map pins to channels (1,2 = Button/Button_n; 3 = Relay/Relay_n).
  • Console: eventDump to confirm handlers; press each input and watch log messages; getChannel 3 to see relay state; set logLevel 4–6 for more detail.

Ethical and legal aspects

• If the relay switches mains voltage, you must ensure:
  • Adequate creepage/clearance, proper enclosure, and strain relief.
  • Use components with appropriate agency ratings (UL/ETL) and follow local electrical code (e.g., NEC in the United States).
  • Provide fail-safe defaults (e.g., relay off on boot for safety-critical loads).

Practical guidelines

• Implementation checklist (OpenBeken)
  • Identify channels: which GPIOs are your two inputs and the relay?
  • Assign roles: two Buttons + one Relay; adjust polarity (…_n roles) if needed.
  • Create autoexec.bat with the three lines shown.
  • Reboot; test each input; confirm single toggle per click.
• Robustness tips
  • Force known state at boot (setChannel 3 0).
  • If accidental double toggles are seen with OnChannelChange, switch to OnClick or add a short guard (e.g., a small delay command after toggle if your firmware supports it).
• Legacy DOS/PC alternative (only if you truly mean MS-DOS autoexec.bat)
  • You need a helper tool to read inputs and drive an output (e.g., RELAY.EXE, READPORT.EXE).
  • autoexec.bat then “glues” logic by calling those tools; batch alone cannot access hardware ports.
  • Example pattern:
  • @ECHO OFF
  • C:\UTIL\READIN1.EXE > C:\TMP\A.TXT
  • C:\UTIL\READIN2.EXE > C:\TMP\B.TXT
  • IF contents of A or B changed since last boot THEN C:\UTIL\RELAY.EXE /TOGGLE
  • In practice, write a small TSR/service in C and invoke it from autoexec.bat.

Possible disclaimers or additional notes

• Firmware command names can vary slightly by version; if OnClick is unavailable, use OnChannelChange with conditions as shown.
• If your device uses Tasmota or ESPHome, the syntax and file names differ (Rules/Automation or YAML); the OpenBeken script won’t apply verbatim.

Suggestions for further research

• Review your device’s channel map and roles in its Module configuration.
• Check the firmware’s event reference for all available triggers (OnClick, OnDblClick, OnHold, OnRelease) to tailor behavior.
• If using a legacy DOS PC, identify or build a small command-line tool that can read inputs and toggle the output reliably (with debounce and edge detection), then wrap it from autoexec.bat.

Brief summary

• For OpenBeken devices: put three lines in autoexec.bat to toggle the relay when either input is pressed; use OnClick on each input channel and toggleChannel on the relay channel. Ensure channel roles and polarities are correct and set a known relay state at boot.
• If you actually mean MS-DOS: autoexec.bat can only orchestrate external hardware-access utilities; you’ll need a helper program to read inputs and toggle the relay.

If you can confirm your platform (OpenBeken/BK7231 vs. a DOS PC vs. something else) and which channels/pins map to your inputs/relay, I can tailor the exact script—including polarity, initial state, and any special behaviors (double-click, long-press, lockouts).