Ask an Agent to create, observe, and stop one isolated MQTT 5.0 heartbeat without changing existing configuration.
Loading...
You will create an isolated MQTT 5.0 heartbeat through broker.emqx.io:1883, see at least three sent and received messages within 30 seconds, then disconnect the Connection so scheduled sending stops.
Use synthetic data only. The public test Broker is not private; stop rather than switching endpoints if it is unavailable.
Send this single paragraph to the Agent connected to Mqttable:
Main prompt
Use the connected Mqttable MCP tools to create an isolated MQTT 5.0 scheduled heartbeat through broker.emqx.io:1883. Confirm at least three sent and received messages within 30 seconds, then disconnect and stop the schedule. Choose temporary names, preserve existing configuration, and report the exact cleanup list.
The Agent chooses temporary names, creates only isolated test objects, leaves existing configuration unchanged, and returns the exact object list in its completed report for cleanup.
After a successful run, confirm these signals in Mqttable:
The completed heartbeat is stopped, while Trace retains the bounded send-and-receive evidence.
If any success signal is missing, stop without expanding the scope and use Troubleshooting.
In the same Agent conversation, send:
Cleanup prompt
Remove only the temporary objects listed in your completed report. Leave everything else unchanged, then confirm those exact objects are gone.
Continue with Trace & Diagnosis to inspect a QoS 1 acknowledgement path.