BK7231N Full Command Manual and DSTTIME Documentation Download Sources

4711leow wrote:

i am looking for a manual for all commands like dsttime and all others for bk7231n where to download it @ElektrodaBot @ElektrodaBot
AI: which firmware or software are you using with the bk7231n (e.g...

Initial assessment of available information
- The string you posted, qio1.18.213, matches OpenBeken build naming (QIO image, v1.18.x). That strongly suggests your BK7231N device is running OpenBeken, not Tuya stock. OpenBeken is the only case where a comprehensive “commands manual” exists and is updated continuously. The official command references are maintained in the OpenBeken repository and are auto-generated from source code on every release. (newreleases.io)

Direct answer to your question
- The up-to-date “manual for all commands” is here (both are canonical):
- docs/commands-extended.md – the exhaustive, auto-generated list (best for searching everything). (github.com)
- docs/commands.md – the shorter, user-centric version. (github-wiki-see.page)
- How to download for offline use:
- Open the repo and use “Download ZIP” (gets the whole docs directory including both files), or clone with Git. (github.com)
- Where to send commands:
- Web UI Console on the device, HTTP Tasmota-compatible endpoint /cm?cmnd=…, or via MQTT cmnd/<topic>/<Command>. (elektroda.com)

Detailed problem analysis
1) Distinguishing hardware vs firmware
- BK7231N is the SoC. Command sets come from firmware. Tuya stock firmware exposes no user CLI. OpenBeken adds a Tasmota-like console, HTTP API and MQTT control, and that’s where commands like Power, backlog, setPinRole, startDriver, etc., live. (github.com)

2) “dsttime” specifically
- In Tasmota the time/DST setup is typically done with TimeStd/TimeDst and Timezone (often “Timezone 99” + explicit rules). If you saw “dsttime” in examples, it was likely shorthand for those Tasmota concepts. In OpenBeken mainline, DST is handled by the NTP/Clock subsystem with commands prefixed ntp_… and with scheduling primitives (addClockEvent). Recent OBK builds add an automatic DST engine so you normally set a base offset and let firmware switch. In practice you will use:
- startDriver NTP
- ntp_setServer <host> (optional)
- ntp_timeZoneOfs ±HH[:MM]
- ntp_setLatlong <lat> <lon> (optional, for sunrise/sunset and some schedules)
- addClockEvent … (for local-time schedules)
These are documented in the command lists and discussed in the DST threads. (elektroda.com)

3) Command categories you will find in the manual
- System: restart, reboot_reason, loglevel, crashlog…
- Network and cloud: WifiSSID/WifiPassword, WifiMode, MqttHost/MqttUser/MqttPassword, ota_http…
- GPIO/pins and channels: setPinRole, setPinChannel, setChannel, addChannel; roles for Button/Relay/LED/PWM, etc.
- Drivers: startDriver/stopDriver for power metering (BL0942/BL0937), TuyaMCU, SM2135/BP5758 LED ICs, IR, I²C/SPI helpers, etc.
- Lighting: led_enableAll, led_dimmer, led_temperature, led_basecolor_rgbcw…
- Time and scheduling: startDriver NTP, ntp_* commands, addClockEvent, waitFor NTPState, $hour/$minute/$sunrise/$sunset constants.
- Power saving / sleep: PowerSave, DeepSleep, PinDeepSleep. (github.com)

4) Concrete examples (OpenBeken)
- Basic NTP/time (United States example, Eastern Time with automatic DST):
- backlog startDriver NTP; ntp_setServer 0.pool.ntp.org; ntp_timeZoneOfs -5:00
- If you use the build with the new DST engine, the offset will shift automatically; otherwise add a tiny script that flips ntp_timeZoneOfs twice a year as shown in the DST threads. (elektroda.com)
- Sunset-based lighting:
- backlog ntp_setLatlong 38.895 -77.036667; waitFor NTPState 1; addClockEvent sunset 0xff 1 high_lights
- See NTP/scheduling examples in the article and docs. (elektroda.com)
- Reduce idle power draw on many BK7231 smart plugs:
- PowerSave 1 (make it persistent in autoexec.bat if needed). (github.com)

5) Version note
- As of November 22, 2025 the latest tagged OpenBeken releases are in the 1.18.20x series. Your qio1.18.213 likely indicates a recent QIO build from the same branch. New builds can add commands, which is why the repo-generated lists are the authoritative reference. (github.com)

Current information and trends
- The command lists are now auto-generated from code on every build (script getcommands.js), so docs/commands-extended.md is the single source of truth for “all commands,” and stays aligned with firmware updates. (newreleases.io)
- Timekeeping evolved: OBK moved from fixed offsets to an NTP/Clock engine that supports sunrise/sunset and automatic DST switching with minimal scripting. (elektroda.com)

Supporting explanations and details
- OpenBeken’s HTTP API is intentionally Tasmota-compatible (/cm?cmnd=…), so mass configuration can be done with curl or your automation server using backlog to chain multiple commands in one request. This is handy when building your own “manual” by saving the config scripts you tested. (elektroda.com)

Practical guidelines
- If you only need a manual: download docs/commands-extended.md and docs/commands.md for offline reading (use Download ZIP). (github.com)
- If you also want examples: fetch docs/autoexecExamples.md and browse the scheduling and driver starters there, plus the NTP/DST threads for ready-made snippets. (elektroda.com)
- On the device: keep short, critical init in Startup Command; put longer logic in autoexec.bat or scripts in LittleFS. (github.com)

Ethical and legal aspects
- If you alter energy counters, calibration, or logging via commands, be mindful these readings are not certified for billing; do not use them for regulated metering. (General best practice in home-automation projects.)

Suggestions for further research
- Review the release notes before upgrading; new builds may add or rename commands. (github.com)
- Use the supported devices database and the Web App tools (Template Importer, GPIO Doctor) to speed up configuration beyond just raw commands. (openbekeniot.github.io)

Brief summary
- For BK7231N running OpenBeken, the “manual of all commands” is the auto-generated pair docs/commands-extended.md (full) and docs/commands.md (concise). Download those from the repo for offline reference. For DST/time, use the NTP/Clock commands (ntp_timeZoneOfs, ntp_setLatlong, addClockEvent) and, in current builds, the automatic DST feature. (github.com)

Two quick questions so I can tailor examples for you
- Which time zone/country do you want to configure (so I can paste the exact ntp_timeZoneOfs and, if needed, an auto-switch snippet)?
- What device role are you configuring first (relay plug, dimmer, RGBCW bulb, TuyaMCU board)? I can point you to the smallest applicable command set for that role.