Complete guide to setting up and using MQTT Dashboard Client
An MQTT broker is a server through which devices exchange messages. To get started, add at least one broker.
A broker can have several connection addresses (endpoints). This is useful when the broker is reachable via multiple addresses — for example, a local IP at home and a cloud domain over the internet. If the current address is unavailable, the app automatically switches to the next one.
The first address is set when you create a broker. To add more, open the broker editor and tap Add endpoint.
Additional settings:
Widgets are the main UI elements for displaying data from the broker and sending commands.
Each parameter added during widget creation can be configured individually: choose the type, topics, and data processing. Click a parameter type below to expand its detailed configuration guide.
The app supports multiple ways to extract data from MQTT payloads.
Extracts a value from a JSON message.
Supports dot notation ($.object.array[0].value) and bracket notation ($[\'store\'][\'book\'][0][\'title\']).
Extracts data using regular expressions. Works as a second stage after JsonPath.
Three-step pipeline:
Regex Time — separate expression for extracting a timestamp from the payload.
Extracts a timestamp from a separate JSON field.
Add text before and after values for formatting.
Format data before sending to the broker.
Useful for building JSON commands.
Format received data before displaying on the widget.
Convenient for adding measurement units.
Groups help organize widgets by meaning — for example, "Sensors", "Light Control", "Temperature".
On the main screen, groups are shown as section headers: tapping a header collapses or expands the group. On the Groups tab the list can be sorted manually, by name, or by widget count.
Scripts allow you to automate actions: send messages based on conditions, execute scenarios on app start, and more.
A disabled script can be opened and edited — changes are saved and take effect when the script is re-enabled.
A scene is a switch that sends several messages to different devices with a single tap. A scene has two states — On and Off — and each one has its own list of messages. Scenes are started manually; they never fire on a condition — use scripts for that.
A scene does not work with raw topics — it works with widgets you have already configured, so the topic, QoS and prefix/suffix come from the widget parameter. You therefore need at least one widget before creating a scene.
A finished scene appears on the Scripts tab as a switch. Turning it on sends every message from the "On" list; turning it off sends the "Off" list. The icon and color change with the state.
Connect to brokers with encryption and custom certificates.
Suitable for local servers (Raspberry Pi, home server).
For corporate and cloud MQTT brokers.
Save and restore your complete app configuration — all widgets, brokers, scripts, scenes, and settings.
Widgets
Brokers
Widget Groups
Scripts and Automation
Scenes
App Settings
Settings → Interface: how the app looks, plus everything related to the Home screen.
Settings → Interface → Home screen → Lock Home screen. Off by default.
With the lock on, a long press on a widget does nothing: no context menu, no haptic feedback, no dragging. The layout cannot be broken by accident — useful on a shared or wall-mounted tablet.
Settings → Interface → Home screen. Seven sizes, each configured separately:
Each item opens a screen with a slider and a preview of the Home screen, so changes are visible right away on your own widgets. Auto means the app picks the size itself; a value you set manually is shown in dp next to the setting name.