Skip to main content
Navigating to the Command Console in the Coreflux HUB by selecting System in the top navigation and clicking Command Console

Opening the Command Console from the Coreflux HUB System menu

​
Why Use the Command Console?

You need to run broker commands—add Actions, remove Routes, or perform other operations—without connecting an external MQTT client. The Command Console lets you execute broker commands directly from the Coreflux HUB.

​
When to Use It

  • Adding entities — Send -addAction, -addRoute, or similar commands
  • Removing entities — Send -removeAction, -removeRoute, etc.
  • Other operations — Any command supported by the broker’s command topic

​
How It Works

The Command Console sends your input to $SYS/Coreflux/Command. The broker replies with a JSON envelope on $SYS/Coreflux/Command/Output, which the HUB displays. You do not need to:
  • Subscribe to the command topic yourself
  • Use an external MQTT client (for example, MQTT Explorer)
  • Publish from the command line
Use -requestId when you send several commands in a row and need to tell the replies apart. The full command list is in Broker Commands.
Coreflux HUB Command Console window with a connected status indicator, a header reading Coreflux Command Console v1.0 and Type commands below to interact with the broker — Use the help button for available commands, two Subscribed to command output topic confirmations, a timestamped $ prompt ready for input, and an Enter command input field with a send button at the bottom, plus connection, clear, and help icons in the top-right

Command Console showing the ready prompt with subscription confirmations and the command input field at the bottom

​
Entering Commands

  1. In the HUB top navigation, select System, then Command Console.
  2. Enter the command in the input field (e.g., -addAction DEFINE ACTION ...).
  3. Send the command. The broker processes it and returns a result.

​
Next Steps

MQTT Broker Commands

Learn available broker commands and syntax.

Broker Logs

View command execution logs.
Last modified on August 28, 2026