Tasmota and OpenBeken MQTT Reboot Command: Restart vs Reset, FullTopic, Security

User question

reboot by mqtt command

Artificial Intelligence Response

Direct answer to the question

• Send an MQTT “restart” command to the device’s command topic.
• Tasmota: publish payload “1” to topic cmnd//Restart.
• OpenBeken: publish to the device’s command topic for “restart” (commonly cmnd//restart). If your OBK build uses a reversed FullTopic, it may be /cmnd/restart. Check the device’s MQTT settings.

Detailed problem analysis

• MQTT command pathing
  • Most ESP-based firmwares subscribe to a command topic derived from a configurable FullTopic string.
  • Tasmota default FullTopic is "%prefix%/%topic%/". With prefix cmnd, topic , and command Restart, the full topic is cmnd//Restart. The command requires a parameter; send payload “1” to perform a software reboot.
  • OpenBeken (OBK) follows a Tasmota-like command model but different builds/configs may set FullTopic to either "%prefix%/%topic%/" or "%topic%/%prefix%/". That’s why you’ll see either cmnd//restart or /cmnd/restart in the wild. The command is “restart”; payload is typically not needed but “1” is accepted.
• Why use Restart and not Reset (Tasmota)
  • In Tasmota, Restart 1 safely reboots without altering configuration.
  • Reset in Tasmota clears configuration to various degrees depending on the parameter; it is not the same as a simple reboot. Do not use Reset unless you intend to wipe settings. This corrects a common misconception.
• Broker and client prerequisites
  • Ensure the device is connected to your broker (host, port, credentials/TLS) and that you know its exact . Topics are case-sensitive; commands are case-insensitive.

Current information and trends

• Tasmota has long standardized on Restart 1 over MQTT for soft reboot.
• OpenBeken, being Tasmota-command compatible in many areas, uses “restart” over its MQTT command topic; however, OBK projects frequently expose the FullTopic as user-configurable, so verify the exact topic string in the device UI before sending fleet commands.
• Industry trend: moving brokers to TLS (port 8883) with ACLs, and managing bulk actions (like reboots) via orchestrators (Home Assistant/Node-RED/automation backends) with guardrails (rate limits, windowing).

Supporting explanations and details

• Minimal working examples (replace placeholders with your values)
  • Tasmota (simple TCP):
  • mosquitto_pub -h -t "cmnd//Restart" -m "1"
  • Tasmota (with auth and TLS):
  • mosquitto_pub -h -p 8883 --cafile ca.crt --cert client.crt --key client.key -u -P -t "cmnd//Restart" -m "1"
  • OpenBeken (common default):
  • mosquitto_pub -h -t "cmnd//restart" -m "1"
  • OpenBeken (reversed FullTopic variant):
  • mosquitto_pub -h -t "/cmnd/restart" -m "1"
• Home Assistant service call
  • service: mqtt.publish
  • data: topic: cmnd//Restart, payload: "1"
• Node-RED
  • Inject -> function setting msg.topic = "cmnd//Restart"; msg.payload = 1 -> MQTT out.

Ethical and legal aspects

• Security: Never expose your MQTT broker unauthenticated to the internet. Use strong credentials, TLS, and ACLs so only authorized principals can issue control-plane commands like reboot.
• Safety: A reboot can interrupt critical loads (HVAC, pumps, medical devices). Coordinate maintenance windows and notify stakeholders. Log who/when initiated the action for auditability.
• Privacy: MQTT topics often leak device names/locations; use non-identifying topics and encrypted transport.

Practical guidelines

• Identify the exact command topic
  • Tasmota: check the device web UI → Configuration → Configure MQTT. Note “Topic” and “FullTopic”. Expect cmnd//Restart with FullTopic "%prefix%/%topic%/".
  • OpenBeken: check Web UI → MQTT settings. Confirm whether FullTopic is prefix/topic or topic/prefix.
• Verify the reboot occurred
  • Subscribe to LWT: tele//LWT. You should see “Offline” then “Online” during reboot.
  • Query status after: publish “0” to cmnd//Status and observe stat//STATUS or tele//STATE with a small Uptime, confirming a fresh boot.
• Batch operations
  • Rate-limit reboots (e.g., 1–2 s between devices) to avoid broker load spikes and power surges on relays switching simultaneously.
• Troubleshooting
  • No response: confirm device is publishing telemetry (subscribe to tele/#). If silent, it’s offline or misconfigured.
  • Wrong topic: mismatched FullTopic is the most common cause; compare your publish topic with the device’s FullTopic string.
  • ACLs: ensure your MQTT user has publish rights to cmnd/… topics.

Possible disclaimers or additional notes

• OpenBeken’s MQTT topic layout can vary by build/config; always trust your device’s reported FullTopic over generic examples.
• Using Tasmota “Reset” commands will erase configuration to varying degrees; avoid unless you intend to re-provision.

Suggestions for further research

• Review your firmware’s command reference for the exact semantics of Restart vs Reset and the FullTopic variable.
• Implement fleet-safe reboot workflows (staggering, health checks) using Node-RED or an automation server.
• Evaluate broker-side ACL design and device-unique credentials to minimize blast radius.

Brief summary

• To reboot via MQTT:
  • Tasmota: publish payload “1” to topic cmnd//Restart.
  • OpenBeken: publish to “restart” on the device’s command topic (commonly cmnd//restart; may be /cmnd/restart if FullTopic is reversed).
• Verify with LWT and Status/Uptime, and protect the broker with proper auth/TLS. Avoid Tasmota “Reset” unless you intend to wipe configuration.

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.