How to Send HTTP Commands to OpenBeken Devices: Tasmota-Style API, Power, Dimmer, Scheduling

User question

how send command per http to obenbeken?

Artificial Intelligence Response

Direct answer to the question

• Use a Tasmota‑style HTTP GET to the device’s /cm endpoint with a cmnd parameter.
• Basic form: http://DEVICE_IP/cm?cmnd=COMMAND_AND_ARGS_URL_ENCODED
• Example (turn relay on): http://192.168.1.100/cm?cmnd=Power%20On

Key points

• URL‑encode spaces, semicolons, colons, etc. (space → %20, ; → %3B, : → %3A)
• The string after cmnd= is exactly what you would type in the OpenBeken Console.
• Responses are simple JSON/text you can parse in scripts.
• If HTTP auth is enabled, add credentials (Basic auth or user/password query args).

Detailed problem analysis

• Endpoint and protocol
  • OpenBeken embeds an HTTP server. Commands are accepted via GET on /cm with the cmnd query parameter. This mirrors Tasmota’s HTTP API, so most examples you know from Tasmota work unchanged.
  • The command parser is the same one used by the Web Console. Any console command can be sent via HTTP as the cmnd string.
• URL encoding
  • Always percent‑encode reserved characters in the command string:
  • space → %20
  • semicolon ; → %3B (needed inside Backlog)
  • colon : → %3A (times, RGB hex with separators, etc.)
• Typical control examples
  • Relay power:
  • On: http://IP/cm?cmnd=Power%20On
  • Off: http://IP/cm?cmnd=Power%20Off
  • Toggle: http://IP/cm?cmnd=Power%20Toggle
  • Multi‑channel: http://IP/cm?cmnd=Power1%20On , http://IP/cm?cmnd=Power2%20Off
  • Dimming / PWM:
  • Generic dimmer: http://IP/cm?cmnd=Dimmer%2050
  • Per‑channel (depends on your template): http://IP/cm?cmnd=SetChannel%201%20200 or http://IP/cm?cmnd=Channel1%2050
  • RGB LED (OpenBeken LED driver):
  • http://IP/cm?cmnd=led_enableAll%201
  • http://IP/cm?cmnd=led_basecolor_rgb%2000FF00
  • Status / diagnostics:
  • http://IP/cm?cmnd=Status
  • http://IP/cm?cmnd=GetPins
  • http://IP/cm?cmnd=Help (lists available commands for your build)
• Sequencing multiple commands
  • Use Backlog to chain commands in one request; separate with semicolons (encode as %3B).
  • Example: turn on, wait, then off:
  • http://IP/cm?cmnd=Backlog%20Power%20On%3B%20delay_ms%20500%3B%20Power%20Off
  • Note: OpenBeken supports millisecond‑style delays (delay_ms). Some builds also accept Delay with different units—prefer delay_ms for clarity.
• Scheduling (clocks/timers)
  • Use addClockEvent to schedule a command at a time with a weekday bitmask.
  • Every day 08:30: http://IP/cm?cmnd=addClockEvent%2008%3A30%3A00%20127%201%20Power%20On
  • 127 = all days enabled; final “1” enables the event.
  • Accurate time requires NTP/timezone to be configured on the device.
• Authentication
  • If HTTP auth is enabled:
  • Basic auth with curl: curl -u admin:password "http://IP/cm?cmnd=Power%20On"
  • Or query args (if enabled): http://IP/cm?user=admin&password=pass&cmnd=Power%20On
• Response handling
  • Typical JSON payloads, e.g. {"POWER":"ON"} or {"Channel1":50}. Parse to confirm success and current state.
• Tools and integration
  • Browser (quick test): paste the URL and observe JSON.
  • curl: curl "http://IP/cm?cmnd=Power%20Toggle"
  • Python (requests):
  • import requests; r = requests.get("http://IP/cm?cmnd=SetChannel%201%20200"); print(r.json())
  • Home Assistant: rest_command or HTTP switch; Node‑RED: HTTP request node.

Current information and trends

• OpenBeken maintains Tasmota‑like JSON‑over‑HTTP control via /cm and cmnd, so migration from Tasmota HTTP automations is straightforward.
• Scheduling commonly uses addClockEvent; community tools exist to generate these events from a UI.
• Active builds expose rich LED commands (led_enableAll, led_basecolor_rgb) in addition to Power/Dimmer, improving parity with common smart‑lighting use cases.

Supporting explanations and details

• Command naming can vary slightly by feature set compiled into your firmware (e.g., SetChannel vs Channel1, Delay vs delay_ms). The Help command on your device is authoritative.
• Backlog executes commands sequentially; delays prevent race conditions (e.g., sensor reads after a power change).

Ethical and legal aspects

• Security: Do not expose the device’s HTTP port to the public internet. Use strong credentials, place IoT devices on an isolated VLAN/subnet, and consider firewall rules. Avoid embedding credentials in URLs in shared scripts or logs.

Practical guidelines

• Give the device a DHCP reservation so the IP remains stable.
• Test commands in the Console first, then mirror the exact string (URL‑encoded) in HTTP.
• When scripting, check the HTTP status code and parse the returned JSON to verify success; implement retries with backoff.
• If calling from a web page, note browser mixed‑content/CORS restrictions (HTTPS pages cannot call HTTP devices directly). Use a local proxy or your home automation platform as a bridge.

Possible disclaimers or additional notes

• Firmware builds differ; some commands may be absent or renamed. Always consult Help on the device you are targeting.
• Older builds may lack a GUI for timers; use addClockEvent via HTTP/Console.

Suggestions for further research

• Review your device’s Help output to enumerate supported commands.
• Explore the Commands and Scripting documentation for feature‑specific commands (IR, sensors, TuyaMCU mapping).
• Look into the community “Schedules/addClockEvent generator” tools if you plan many timed events.

Brief summary

• Send HTTP GET to http://IP/cm?cmnd=..., with the console command URL‑encoded.
• Use Backlog for sequences and addClockEvent for schedules.
• Parse JSON responses, secure access with auth and network isolation, and verify available commands via Help.

If you tell me the exact device type and what you want to control (relay, PWM, RGB, schedule, IR, TuyaMCU), I’ll craft ready‑to‑paste URLs for your case.

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.