OpenBeken Timer Functionality and Web Interface Limitations

User question

openbk timer webinterface

Artificial Intelligence Response

Direct answer to the question

‐ Recent OpenBeken (OpenBK) builds do contain a graphical “Scheduler / Timers” editor inside the Web Application.
‐ If your firmware is older, you will only find command-line scripting ( addClockEvent, addRepeatingEventID …) and no GUI.
‐ Timers rely on correct NTP time, time-zone and (for sunrise/sunset) geo-location settings.

Key points
• Launch the WebApp → “Schedules” tab → Add/Edit timers.
• Four trigger types: fixed Time, Sunrise, Sunset, Interval.
• Commands typed in the Action field are executed exactly as in the console.
• CLI scripting and MQTT/Home-Assistant automations remain available for complex jobs or on very old firmware.

Detailed problem analysis

1. Firmware versions and feature set
   • v1.16 (≈Q2 2023) and later: React-based WebApp shipped with “Schedules” page – a real GUI for timers.
   • Pre-v1.16 or stripped community forks: no GUI, timers only through scripting commands.
   • Therefore two apparently contradictory statements in community posts: both are correct, but refer to different firmware builds.

2. Internal architecture
   • Persistent events are stored in flash as Scheduler entries (JSON).
   • Volatile one-shot timers are created with the SetTimer command; they disappear after a reboot.
   • Scheduler is evaluated by a cooperative task every second; accuracy is typically ±1 s when NTP is locked.
   • CLI API (still available even when GUI exists):

    addClockEvent HH:MM DOW_mask "command" //fixed time
   addSunEvent sunrise|sunset offset "command"
   addRepeatingEventID id seconds count "command"
   listEvents
   clearEvent id

3. GUI workflow (current builds)
   a) Device → “Launch Web Application” → “Schedules”.
   b) “Add event” dialog:
   • Enabled (checkbox)
   • Type: Time / Sunrise / Sunset / Interval
   • Time or Offset field
   • Week-days selector
   • Random (0–60 min)
   • Action (OpenBK command string; multiple commands separated by ;)
   • Channel (optional convenience field; populates the Action string)
   c) Press ✓ to save; changes are written immediately – no reboot required.

4. Example configurations
   • Daily porch light:
   Event 1: Type=Sunset, Offset = -10, Action = Power1 1, Weekdays=Mon-Sun.
   Event 2: Type=Time, Time = 23:30, Action = Power1 0.
   • Interval ventilation: Interval=1800 s, Action=Toggle 1.
   • Vacation randomisation: same as porch light but Random = 15.

5. Error sources & diagnostics
   • Wrong time → check “Time” line in the header; fix NTP host / time-zone (Config → General).
   • Command typo → copy the Action string, paste into WebApp “Console”, ensure it behaves.
   • Event did not fire → “Log” tab shows “SCHED: event # fired …”. Absence = event disabled or time not matched.

Current information and trends

‐ Development pace is high; the “Schedules” GUI is still marked beta, new fields (astro dawn/dusk, cron-style expressions) are already in pull-requests (spring 2024).
‐ Community request list: visual calendar view, import/export, DST auto-handling.
‐ Home-Assistant integration through MQTT is the mainstream workaround for users who prefer a fully fledged automation editor today.

Supporting explanations and details

• Day-mask encoding (CLI): bit0=Mon … bit6=Sun, so 127 = every day, 62 = Tue-Sat.
• Sunrise/Sunset algorithm uses NOAA civil twilight; location is set once in Config → General.
• Random field = uniform 0…N minutes added (positive) or subtracted (negative) to the calculated trigger.

Ethical and legal aspects

‐ Automations that control mains-powered loads must comply with local electrical safety rules.
‐ If timers drive actuators without physical feedback (e.g. heaters), add watchdog or sensor-based interlocks to avoid unsafe states.
‐ GDPR / privacy: NTP servers log IP time sync; you may host a local NTP source to avoid external queries.

Practical guidelines

1. Always configure NTP, UTC offset, latitude/longitude first, then start adding schedules.
2. Name events descriptively – GUI lists only the command string otherwise.
3. For critical loads, create a “failsafe” repeating watchdog event (e.g. addRepeatingEventID 99 600 0 publish2 domoticz/in ...) so that you know the scheduler task is alive.
4. Backup: curl http://device_ip/config/download saves all events; keep a human-readable copy.

Possible disclaimers or additional notes

‐ Features described require at least OpenBK commit 2023-05-14 or later; on earlier firmware the steps under “CLI only” must be used.
‐ The sunrise/sunset calculation ignores local DST rules; adjust offset seasonally or use HA automations if you need automatic DST.

Suggestions for further research

‐ Monitor GitHub issue #606 (“Cron syntax for Scheduler”) for upcoming advanced patterns.
‐ Evaluate native Matter/Thread port of OpenBeken once BK7231N secure-boot is fully unlocked; may bring event sharing across devices.
‐ Compare OpenBK scheduler with Tasmota v14 “Rules Lite” and ESPHome “Time trigger” for performance and persistence.

Brief summary

Recent OpenBeken firmware finally offers a built-in web “Scheduler” so you can create, view and manage timers without scripting. Verify your device runs a new enough build, set up NTP and location, then use the WebApp’s “Schedules” tab to add fixed-time, sunrise/sunset or interval events. Older firmware builds fall back to command-line methods such as addClockEvent. Integration with Home Assistant remains a powerful option for complex or graphical automations.

Disclaimer: The responses provided by artificial intelligence (language model) may be inaccurate and misleading. Elektroda is not responsible for the accuracy, reliability, or completeness of the presented information. All responses should be verified by the user.