A control panel in action: each control fires an ON event that publishes back to the broker
ON <EVENT> DO <ACTION>.
First the event triggers, then each action you can wire to them. The broker parses this grammar; which triggers the HUB actually dispatches, and any write-back caveats, are documented with the input components — that catalog ships with the HUB, not the broker.
Event triggers
Actions
Publish to a topic
The workhorse: send a command or value to any MQTT topic.text-field and number-field, use WITH VALUE to publish what the operator typed — see the Input components page for full write-back examples.
Navigate between panels
Jump to another panel by name:Common mistakes
The control shows data but does nothing when used
The control shows data but does nothing when used
Input components don’t publish by themselves — the
ON <EVENT> DO handler does. A button without ON CLICK DO PUBLISH ... is a label in practice.The handler runs but nothing changes on the panel
The handler runs but nothing changes on the panel
PUBLISH writes to the broker; the panel only reflects it if some component binds to that topic. Check the bound topic and the published topic match (command vs. feedback topics are often intentionally different).Next Steps
Input & control components
The controls that fire these events, with full write-back examples.
Common patterns
Complete panels that put events and actions to work.