OpenBK PowerSave 1 Command via curl on BK7231 Devices

User question

enable powersave in startup command

Artificial Intelligence Response

Assuming you mean OpenBeken / OpenBK, the startup command you want is simply:

PowerSave 1

Direct answer to the question

• To enable power saving at boot, put PowerSave 1 in the device’s startup command.
• The most reliable method is to add it to autoexec.bat.
• If using curl, a typical command is:

curl "http://DEVICE_IP/cm?cmnd=lfs_append%20autoexec.bat%20PowerSave%201"

Then reboot:

curl "http://DEVICE_IP/cm?cmnd=restart"

Verify after reboot:

curl "http://DEVICE_IP/cm?cmnd=PowerSave"

Expected result:

{"PowerSave":1}

Detailed problem analysis

In OpenBeken, PowerSave 1 is a runtime command. If you enter it manually in the console, it takes effect immediately, but the important engineering question is whether it is re-applied automatically after reset or power loss.

There are two common startup mechanisms:

1. autoexec.bat

This is the preferred method for persistent boot-time commands.

• autoexec.bat is executed during startup.
• Put one command per line.
• For your case, the file should contain:

PowerSave 1

If you use the web interface, place that exact line into the startup script editor.

If you use HTTP API with curl:

curl "http://DEVICE_IP/cm?cmnd=lfs_append%20autoexec.bat%20PowerSave%201"

Then restart:

curl "http://DEVICE_IP/cm?cmnd=restart"

2. Short startup command

Some OpenBeken builds expose a Short startup command field in the configuration UI.

If that field exists, you can enter:

PowerSave 1

If you already have another startup command there, combine them carefully. For example:

backlog Command1 ; PowerSave 1

This is useful for short, single-line initialization, but autoexec.bat is generally better if you expect to add more commands later.

Why autoexec.bat is usually better

From a firmware-maintenance standpoint:

• Easier to read
• Easier to extend
• Better for multiple initialization commands
• Less risk of packing too much logic into one line

Important implementation detail

lfs_append literally appends text to the file. That means:

• If you run it multiple times, you may add duplicate lines.
• If the file formatting is wrong, commands may concatenate.

So if you already have an existing startup script, the safest approach is to open and edit it from the web UI, ensuring PowerSave 1 is on its own line.

Current information and trends

For OpenBeken-style embedded Wi-Fi devices, the current practical pattern is:

• Use HTTP command interface for automation and provisioning
• Use autoexec.bat for boot persistence
• Use query commands after reboot to verify state

The Linux/Windows “power saving on startup” commands sometimes shown in generic answers are not relevant here if your target is an OpenBeken device. For OpenBK, the correct context is the device command processor, not the host operating system.

Supporting explanations and details

Recommended exact command set

Immediate test

First test the command live:

curl "http://DEVICE_IP/cm?cmnd=PowerSave%201"

Make it persistent

Then append it to startup:

curl "http://DEVICE_IP/cm?cmnd=lfs_append%20autoexec.bat%20PowerSave%201"

Reboot

curl "http://DEVICE_IP/cm?cmnd=restart"

Verify

curl "http://DEVICE_IP/cm?cmnd=PowerSave"

If authentication is enabled

Use:

curl -u username:password "http://DEVICE_IP/cm?cmnd=lfs_append%20autoexec.bat%20PowerSave%201"

If you want to inspect the startup file

Depending on the build, a LittleFS read/cat command may be available. Example:

curl "http://DEVICE_IP/cm?cmnd=lfs_read%20autoexec.bat"

or

curl "http://DEVICE_IP/cm?cmnd=lfs_cat%20autoexec.bat"

If supported, confirm that the file contains:

PowerSave 1

Practical interpretation

Think of PowerSave 1 as a post-boot configuration bit that must be asserted each time the firmware starts, unless the firmware explicitly stores it elsewhere. Putting it in startup makes that behavior deterministic.

Ethical and legal aspects

• Do not expose the device HTTP API to the public internet.
• If remote access is needed, use a VPN or segmented management network.
• If the device controls mains-powered hardware, validate that power-saving mode does not interfere with required responsiveness or safety behavior.
• In regulated or safety-relevant applications, verify that entering power-save mode does not violate timing, watchdog, or communication requirements.

Practical guidelines

Best practice

• Test on one device first.
• Confirm Wi-Fi stability after enabling power save.
• Reboot and verify state retention.
• Only then roll out to multiple devices.

Common pitfalls

• Appending the command multiple times
• No newline separation in autoexec.bat
• Forgetting to reboot after editing startup
• Assuming runtime command execution automatically persists

Good workflow

1. Run:

   curl "http://DEVICE_IP/cm?cmnd=PowerSave%201"

2. Confirm it works.
3. Add it to startup:

   curl "http://DEVICE_IP/cm?cmnd=lfs_append%20autoexec.bat%20PowerSave%201"

4. Reboot.
5. Verify:

   curl "http://DEVICE_IP/cm?cmnd=PowerSave"

Possible disclaimers or additional notes

• Command names and filesystem helper commands can vary slightly by build/version.
• If lfs_append is unavailable in your firmware, use the web UI startup editor instead.
• If PowerSave returns 0 after reboot, check whether another later startup command disables it.

Suggestions for further research

You may also want to verify:

• Whether your firmware build supports Short startup command
• Whether PowerSave affects:
  • Wi-Fi reconnect latency
  • MQTT responsiveness
  • ADC/button polling timing
  • power consumption in idle state

For engineering validation, measure both:

• current draw before/after enabling power save
• network response latency before/after boot persistence

Brief summary

For OpenBeken, to enable power saving at startup, put:

PowerSave 1

into the startup script, preferably autoexec.bat.

Most direct curl method:

curl "http://DEVICE_IP/cm?cmnd=lfs_append%20autoexec.bat%20PowerSave%201"
curl "http://DEVICE_IP/cm?cmnd=restart"

Then verify with:

curl "http://DEVICE_IP/cm?cmnd=PowerSave"

If you want, I can also give you:

1. the exact web UI path, or
2. a safe one-line curl command that replaces the startup file cleanly instead of appending.