Getting Started; Your MQTT Service Is Ready
Thank you for your order. Your managed MQTT service is now provisioned and ready for use. This guide walks through the essentials so you can connect quickly, verify operation, and integrate with Mesh-Plug or other IoT clients with minimal friction.
What You Received
After checkout, your account is automatically provisioned with:
- A secure MQTT broker endpoint (TLS-enabled)
- Unique credentials (username and password or token-based access)
- Permission-scoped topics based on your plan
- WebSocket access (if applicable)
- Compatibility with Mesh-Plug and standard MQTT clients
Your connection details are available in your My Account area. Keep these credentials secure; they function as direct access keys to your broker.
Basic MQTT Connection Details
You will need the following values when connecting any client:
- Broker Host: (provided in your account)
- Port:
- TLS MQTT; typically
8883 - MQTT over WebSocket; typically
9001or443
- TLS MQTT; typically
- Username / Password: issued at provisioning
- Protocol: MQTT v3.1.1 or v5
- TLS: Enabled; required for all production connections
Most MQTT libraries work out of the box with these settings.
Verifying Your Connection (Recommended)
Before integrating with applications, confirm your broker access using a test client:
- Publish a test message to an allowed topic
- Subscribe to the same topic and confirm receipt
- Validate that the connection negotiates TLS successfully
This confirms credentials, permissions, and network access are all functioning correctly.
Mesh-Plug Basic Setup
Mesh-Plug allows you to visualize and interact with MQTT data directly inside WordPress.
Minimum Requirements
- WordPress installed and up to date
- Mesh-Plug plugin installed and activated
- An active MQTT service (this order)
Initial Configuration Steps
- Open Mesh-Plug โ Settings in WordPress
- Enter your MQTT broker host and port
- Enable TLS and paste your credentials
- Define the root topic(s) you want Mesh-Plug to subscribe to
- Save settings and allow Mesh-Plug to establish the connection
Once connected, incoming messages will populate dashboards, tables, maps, or charts depending on your configuration.
Topics, Permissions, and Data Flow
Your service uses topic-level access controls. Only approved topic paths are readable or writable by your credentials.
Best practices:
- Use predictable topic hierarchies
- Separate telemetry, chat, and control topics
- Avoid publishing large payloads at high frequency unless required
Mesh-Plug automatically sanitizes and parses supported payloads before rendering.
Troubleshooting and Developer Resources
If you encounter issues such as connection failures, missing data, or unexpected behavior, consult the Mesh-Plug documentation first:
- Mesh-Plug Developer Docs:
- Developer Reference https://michaelwinchester.com/mesh-plug/developer-reference/
- Getting Connected to Mesh-Plug https://michaelwinchester.com/mesh-plug/2025/11/04/getting-connected-to-mesh-plug/
- Local/User Event Settings https://michaelwinchester.com/mesh-plug/local-event-user-settings/
- Known Good Baseline Settings https://michaelwinchester.com/mesh-plug/known-good-baseline-checklist/
- Troubleshooting Guide:
- MQTT Troubleshooting Guide https://the-link-builders.com/mqtt-troubleshooting-guide/
- MQTT Topic & Payload Reference:
These resources cover common setup mistakes, broker connectivity checks, and data format expectations.
When to Contact Support
Reach out if you experience:
- Authentication errors with valid credentials
- Broker connection timeouts across multiple clients
- Suspected permission or topic-scope issues
- Billing or provisioning discrepancies
Include your account email and a brief description of the issue to speed resolution.
Final Notes
Your MQTT infrastructure is designed to be reliable, secure, and scalable. You should be spending time building devices, dashboards, and integrations; not maintaining broker infrastructure.
We are glad to have you onboard.

