Dedicated MQTT Broker Help Guide

Introduction

Bevywise’s Dedicated MQTT Broker is a fully managed, cloud-hosted MQTT solution built for businesses that need secure, isolated, and scalable IoT communication. Unlike shared environments, a dedicated broker gives you exclusive broker resources, greater control over your deployment, and consistent performance for production workloads.

Designed for reliability and ease of use, the platform helps you set up secure MQTT infrastructure without the burden of server provisioning, maintenance, or ongoing operational management. This guide explains how to configure, connect, manage, and monitor your dedicated MQTT broker so you can run your IoT applications with confidence.

Feature Highlights

• No complex setup
• No server maintenance
• Scalable infrastructure
• Accessible from anywhere, at any time
• Flexible data processing and integration options

Get Started

To begin using the Bevywise Dedicated MQTT Broker, you first need to create an account on the Bevywise cloud platform.

Bevywise offers two types of broker deployments:

• Shared FREE Plan – A shared broker hosted on a common infrastructure, ideal for learning, testing, and small-scale projects. This plan is free and great for evaluation but has limited resources and isolation.
• Dedicated MQTT Broker – A private, isolated broker instance designed for production-grade IoT applications. It provides dedicated resources, stronger security, and full control over device connections, topics, and configurations.

For production deployments requiring reliability, security, and high scalability, choose the Dedicated MQTT Broker. Once your instance is provisioned, you can log in to the cloud dashboard, configure authentication and access controls, and start connecting your devices.

Quick Steps to Explore Our Broker

Getting started with our dedicated broker is simple. Once you sign up and create an account, you can begin using the service by following these basic steps:

1. Sign up for a new account
2. Choose a suitable plan
3. Start using the service
4. Connect your devices or clients

Sign Up for a New Account

To create an account, go to the signup page and enter the required information.

You will need to provide:

• Email address
• Phone number
• Account password

Note: Use a valid email address, as account verification is required before you can begin using the service.

After entering your details, click Signup for FREE.

A confirmation email will be sent to the email address you provided. Check your inbox or spam folder and follow the instructions in the email to verify your account.

Once you click the confirmation link and complete the activation process, your account will be enabled. You can then log in to the Bevywise Dedicated MQTT broker using your registered email address.

After logging in, you will be taken to the Connection Settings page.

Connection Settings

On this page, you can view connection details such as:

• Host address
• TCP port
• WebSocket port
• API token
• Other broker properties

From the same page, you can create authentication credentials for MQTT clients.

You can add:

• MQTT Username (Access Key)
• MQTT Password (Access Token)

These credentials can be mapped to specific Client IDs.

The Clients field can be configured in different ways:

• A single Client ID
• Multiple Client IDs separated by commas
• Wildcards
• * to allow clients with any Client ID to connect

These credentials can be edited or deleted whenever required.

Access Control

In the Access Control page, you can define ACLs for clients.

ACLs allow you to create fine-grained permissions by specifying which devices or clients are allowed or denied access to publish or subscribe on particular MQTT topics. This helps strengthen security and enforce topic-level access policies within the broker.

To add an ACL:

1. Go to the Access Control page
2. Click Add in the top-right corner
3. Select the required Client ID from the dropdown
4. Specify the topic
5. Choose whether to allow or deny publish and/or subscribe access

Note: Allowing # gives full access to all topics. Denying # blocks all publish or subscribe actions.

Existing ACLs can be modified at any time by selecting the Edit option.

Data Dashboard

The Data Dashboard gives you a quick summary of recent activity on the platform.

It includes the following information:

• Active Clients – total number of active clients or devices
• Topics – number of topics published in the last 24 hours
• Recent Events – a log of recently published messages with client ID, topic, payload, and timestamp
• Recent Connections & Disconnections – recently connected or disconnected devices

Custom Dashboard

By clicking the New menu, you can create a custom dashboard by entering a name and description.

Once the custom dashboard is created, you can add widgets to visualize your device data using different chart and graph formats.

Widgets

The platform supports eight widget types for data visualization, including:

• Line chart
• Bar chart
• Timeline chart
• Meters
• Data
• Categorical charts
• Status indicators
• Send command

Widget Creation

To create a widget

1. Click the + icon in the top-right corner.
2. In the Widget Type window, select the widget you want to create.

1. Line Chart

Use a line chart to track changes in sensor values such as temperature, pressure, or usage over time.

Steps:

• Enter a title for the chart
• Select a device from the dropdown list
• Choose a topic associated with that device
• Enable the Live option for real-time updates
• Enter the Key, Label, and Unit
• Select a display color
• Use Add (+) to include additional key values if required
• Choose a suitable design option
• Click Save

2. Bar Chart

Use a bar chart to compare values across categories or across fixed time intervals.

The setup process is similar to widget creation for line chart. After entering the required details, click Save to create the bar chart.

3. Timeline Chart

A timeline chart is useful for showing events or data points along a chronological axis.

The creation steps are similar to line chart. After entering the required values, click Save to create the widget.

4. Meters

Meters are useful for displaying values such as battery level, fill status, or threshold-based ranges using circular, bar, or dial-style indicators.

Steps:

• Enter a title
• Select a device
• Choose a topic
• Enter Key, Label, and Unit
• Select a color
• Define Minimum and Maximum values
• Set value ranges and assign colors
• Choose the appropriate design
• Click Save

5. Data

The Data widget displays values in a clean tabular or card-style format.

Steps:

• Enter a title
• Select a device
• Choose a topic
• Enable the Live option to get real-time data updates
• Enter Key, Label, and Unit
• Select a color
• Add multiple keys if required
• Define Minimum and Maximum values
• Set value ranges and assign colors
• Add another band of minimum and maximum values if required
• Once all required values are entered, click Save

6. Categorical Charts

Categorical charts help visualize segmented data using formats such as pie or donut charts.

Steps:

• Enter a title
• Select a device
• Choose a topic
• Enable the Live option if real-time updates are required
• Enter Key, Label, and Unit
• Choose a color
• Add more keys if necessary
• Select a suitable design
• Click Save

7. Status Indicators

Status indicators are used to show on/off states, alarms, or connectivity using simple visual cues.

Steps:

• Enter a title
• Select a device
• Choose a topic
• Enable the Live option if required
• Enter Key, Label, and Unit
• Choose how the value should be compared
• Enter the target value
• Select the symbol to display when the condition is true
• Add more keys if needed
• Choose a design
• Click Save

8. Send Command

The Send Command widget allows you to send commands to devices remotely using buttons or toggles. Unlike other widgets that only display data received from devices, this widget is used to trigger actions or control devices directly.

Steps:

• Enter a title
• Select a device
• Choose a topic
• Choose a suitable control layout
• Select whether the button label should be plain text or a Unicode icon
• Enter the button label
• Choose a background color
• Enter the command payload that should be sent when the button is pressed
• Click Save

Clients

The Clients tab displays the full list of devices, including both active and inactive clients. It gives you a high-level view of each connected device.

From this page, you can review:

• Events published by the device
• Commands received by the device if it is subscribed
• Subscriptions associated with the device
• Device properties and Last Will settings
• Send an immediate command to the device

To use the Clients page:

1. Open the Devices / Clients tab
2. Select any device from the list

Events

Shows the messages published by the selected device, along with the topic, properties, QoS level, and publish time.

Commands

Shows the messages received from other devices on subscribed topics, along with the timestamp.

Subscriptions

Lists the topics to which the selected device is currently subscribed.

Properties & Last Will

Displays the keep-alive and clean session values, along with Last Will topic, message, QoS, and retain settings.

Connectors

The broker supports pushing live data streams to various connectors, including:

• MySQL
• MongoDB
• Kafka
• Postgres
• Redis
• HTTP
• MQTT Bridge
• InfluxDB
• Amazon Kinesis
• Elastic Search

These integrations allow you to forward MQTT data to external systems and databases in real time.

1. MySQL Connector Configuration

To connect to MySQL, provide:

• Host
• Port (default: 3306)
• Username
• Database
• Table

Enable SSL if secure communication is required. When SSL is enabled, upload the CA certificate and, if needed, the SSL key and certificate.

After entering the required details, click Save to establish the connection.

2. MongoDB Connector Configuration

MongoDB setup is similar to MySQL configuration. In addition, specify the target collection.

3. Kafka Connector Configuration

To configure Kafka, provide:

• Host
• Port (default: 9092)
• SASL mechanism
• MQTT topic
• Kafka topic

Supported SASL mechanisms include:

• None
• PLAIN
• SCRAM

If required, enable SSL and upload the relevant certificates. Once complete, click Save to establish the connection.

4. Postgres Connector Configuration

Postgres configuration follows the same steps as MySQL. The default Postgres port is 5432.

5. Redis Connector Configuration

Redis setup is also similar to MySQL. The default Redis port is 6379.

Additional options include:

• Use custom key
• Use topic name as key

If Use custom key is selected, enter the key that should be used for Redis operations.

6. HTTP Request

To configure the HTTP Request connector, provide:

• Request URL
• Authentication type

Supported authentication types include:

• No Authentication
• Basic
• API Key
• Token
• Bearer Token

Enable SSL if required and upload certificates where applicable.

7. MQTT Bridge Connector

The MQTT Bridge connector allows your broker to connect to another remote MQTT broker and transfer data.

Provide the following details:

• Broker URL
• Port
• Client ID
• Protocol version
• MQTT username
• MQTT password

For secure connections, enable SSL and upload the required certificates. Click Save to complete the setup.

8. InfluxDB Configuration

To connect to InfluxDB, provide:

• Host
• Port (default: 8086)
• Organization name
• Bucket name
• Token

Enable SSL if secure communication is needed. Click Save after filling in the required details.

9. Amazon Kinesis Configuration

To configure Amazon Kinesis, enter:

• AWS stream name
• AWS region
• AWS access key
• AWS secret key

Click Save to connect to the Kinesis stream.

10. Elastic Search Connector

To configure Elastic Search, provide:

• Host
• Port
• Index
• Authentication method
• Access token if applicable

Supported authentication types include:

• Basic
• PKI
• JWT

Enable SSL if needed and click Save to complete the configuration.

Published Topics

This page displays the topics currently being published by connected devices, along with:

• Publishing client
• Published message
• Date and time of publication

Subscriptions

This page displays the topics that connected devices are subscribed to, along with:

• Client name
• QoS level
• Subscription date and time

Note: Using # in published topics or subscriptions allows the specified device to publish or subscribe to all topics without restrictions.

Rules

Rules are the first step in adding intelligence to the broker. The rule engine lets you automate actions and generate alerts based on incoming messages.

The rule engine supports:

• Event-based rules
• Timer-based rules

Timer-Based Rule Creation

Timer rules allow you to schedule actions for a specific date and time.

To create a timer rule:

1. Select Timer as the rule type
2. Choose one of the scheduling options:
   • Specific date
   • Date range
   • Days of the week
3. Enter the Client ID of the publisher. This field is optional.
4. Enter the topic subscribed to by the target device
5. Enter the message to be sent
6. Click Create

Once configured, the subscriber client will receive the alert at the scheduled time.

Event-Based Rule Creation

Event-based rules are triggered when a specific message is received on a topic.

Select Event as the rule type.

In the client condition, choose one of the following:

• Any – the rule triggers for any client publishing to the topic
• Specific – the rule triggers only for messages from a selected client

Any

When Any is selected:

• Enter the topic to monitor
• Optionally enable Compare with message and specify the value to compare against

Under the Action section:

• Enter the topic where the output should be sent
• Choose whether to send the received event as-is or send a custom alert message

Click Save to create the rule.

Specific

The steps are the same as the Any option, but here you also need to specify the Client ID. Only messages from that client will trigger the rule.

Log

The Log tab displays live broker events to help with monitoring and troubleshooting. It records real-time activities such as device connections, disconnections, publish events, subscribe events, and connection-related errors, giving you better visibility into broker activity.

Support

If you need assistance with your Bevywise Dedicated MQTT Broker, contact our team and they'll help you with setup, configuration