Client Credentials
| MQTT Username | MQTT Password | Clients | Delete |
|---|
Connection Parameters
Host Address
Copied !
Secure MQTT Connection
CA Certificate for TLS
MQTT over TCP Port
Copied !
MQTT over WebSocket Port
Copied !
MQTT over TLS Port
Copied !
MQTT over Secure WebSocket Port
Copied !
API Token
Copied !
This token expires at
Ready to Use MQTT Client Applications
Disable TLS
Do you want to disable secure connections between your clients and the broker?
- Disabling TLS will restart the Crystal MQ Broker, disconnecting all devices.
- After clicking Confirm, refresh the page.
- Devices must connect using the updated ports.
- Do you wish to proceed?
** Please ensure the broker is restarted after Disabling TLS.
Add MQTT Authentication
Settings
×
Active Clients
0
Topics
0
Events
0
Commands
0
Events
| Client ID | Topic | Message | Time |
|---|---|---|---|
| No Recent Events Found | |||
Client Log
| Client ID | IP | Status | Time |
|---|---|---|---|
| No Client Log Found | |||
Connections
| Client ID | IP | Time |
|---|---|---|
| No Recent Connections Found | ||
Disconnections
| Client ID | IP | Time |
|---|---|---|
| No Recent Disconnections Found | ||
| Topic | Client ID | Last Published Message | Last Published Time | |
|---|---|---|---|---|
| No Data Found | ||||
| Topic | Client ID | QoS |
|---|---|---|
| No Data Found | ||
Please upgrade your plan!
Upgrade to Advanced Plan
- Visualise better with Dashboards & Widgets
- Powerful Rule Engine to create Event-based Alerts
- Extended Data Storage
Topic :
Total Messages :
0
Messages in last hour :
0
Devices creating Events
| Device Id | IP | Status | Time |
|---|
Devices listening to Command
| Device Id | IP | Status | Time |
|---|
New Rule
Condition
Action
Condition
Action
Condition
Action
M
Tu
W
Th
F
Sa
Su
Access Control List
Control client access to Publish and Subscribe for specific topics. Client ID-based ACL if configured, overrides username-based ACL
MQTT
Username
Clients
| Client ID | Publish Topics | Subscriptions | Edit |
|---|
| Client ID | Publish Topics | Subscriptions | Edit |
|---|
MQTT
Username
Clients
| MQTT Username | Publish Topics | Subscriptions | Edit |
|---|
| MQTT Username | Publish Topics | Subscriptions | Edit |
|---|
Add MQTT Authentication
Add ACL for Client
Edit ACL for Client
Add ACL for MQTT Username
Edit ACL for MQTT Username
New Dashboard
New Widget
Export data
Client Log
Displays a list of errors reported by clients. Use this log to identify and troubleshoot issues such as connection failures, authentication errors, or message delivery problems.
| Client ID | Error | IP Address | Time |
|---|
Welcome to Bevywise Crystal MQ
The Fastest & highly extendable MQTT Broker
Connect your MQTT clients to the Bevywise MQTTBroker running in local machine
Get Started by downloading MQTT Clients for your Operating System.
Download & connect Clients
Connect your clients to the MQTT Broker or download it from the tab MQTT Clients
You will have the clients for Windows , Linux , Mac & ESP. Looking for some other clients, contact Support
Use the following Broker details to connect.
Broker address - localhost
Broker Port - 1883
TLS/SSL Broker Port - 8883
Configure Rules
Rules help you enable powerful M2M Communication between Devices.
Event based rules based on Message, Topic & Client.
Timer based rules to automate scheduled events.
VisitMessage Rulesand configure Messages now.
View Dashboard & Device Details
The Dashboard will give a quick view of what is happening with the device connected to the Crystal MQ.
The individual device details can be seen by visiting the Devices tab. The connection status and the messages published will be dynamically update.
Get More out of the MQTT Broker
Crystal MQ is capable of doing much more than just handing MQTT Messages.
- Complete MQTT Support
- TLS / SSL Support
- MQTT Authentication
- Integrate with any Big Data Engine Elastic Search | Mongo DB | Custom Store
- Visualize Data withTableau | Elastic Search
- RESTful API to manage your Devices
- UI Customization & Live Updates on interface
- Localize to your language
- Support for Linux, Mac, Windows / Windows Server , Raspberry PI
- Closer Integration with your Application
MQTT Client Help
- Download the client code that is compatible with your OS.
- Install python 2.7 for your machine / PC
- Please change the following parameters as required.
- MQClientID
- Publish_Topic_Name
- Publish_Message
- Subscribe_Topic_Name
- You can change the QoS , Retain , and other parameters if needed.
Download MQTT Client
Connectors
Push real-time data streams to remote systems using built-in connectors.
MySQL
MongoDB
Kafka
Postgres
Redis
HTTP request
MQTT Bridge
InfluxDB
Amazon Kinesis
- Host : The hostname or IP address of the MySQL server.
- Port : The port number on which the MySQL server is listening (default is 3306)
- Username :It is used to authenticate with the MySQL server
- Password :The password associated with the MySQL username.
- Database : The name of the database to which you want to connect
- SSL : Enable if you want to use SSL for the connection. If SSL is enabled, just upload the Certificate Authority (CA) certificate file and SSL key as well as SSL certificate if necessary.
- CA Certificate : The Certificate Authority (CA) certificate. Upload this certificate if the server’s certificate is self-signed or issued by a CA that is not widely recognized.
- Client Certificate & Client Key : Upload these files if the server requires mutual authentication, allowing both the client and server to verify each other’s identity.
- Host : The hostname or IP address of the MongoDB server.
- Port : The port number on which the MongoDB server is listening (default is 27017)
- Username :It used to authenticate with the MongoDB server
- Password :The password associated with the MongoDB username.
- Database : The name of the database to which you want to connect
- SSL : Enable if you want to use SSL for the connection. If SSL is enabled, just upload the Certificate Authority (CA) certificate file and SSL key as well as SSL certificate if necessary.
- CA Certificate : The Certificate Authority (CA) certificate. Upload this certificate if the server’s certificate is self-signed or issued by a CA that is not widely recognized.
- Client Certificate & Client Key : Upload these files if the server requires mutual authentication, allowing both the client and server to verify each other’s identity.
- Host : The hostname or IP address of the Kafka server
- Port : The port number on which the Kafka server is listening (default is 9092)
- SASL Mechanism :
- None : No Authentication Required.
- PLAIN : Simple authentication with a username and password.
- SCRAM : Secure authentication using SHA-512.
- Plain username : It is used to authenticate with the Kafka server
- Plain password : The password associated with the Kafka username
- mqtt topic : The topic to which you want to push the data. Use * if you wish to push the data to all the topics
- SSL : Enable if you want to use SSL for the connection. If SSL is enabled, just upload the Certificate Authority (CA) certificate file and SSL key as well as SSL certificate if necessary.
- CA Certificate : The Certificate Authority (CA) certificate. Upload this certificate if the server’s certificate is self-signed or issued by a CA that is not widely recognized.
- Client Certificate & Client Key : Upload these files if the server requires mutual authentication, allowing both the client and server to verify each other’s identity.
- Host : The hostname or IP address of the Postgres server.
- Port : The port number on which the MongoDB server is listening (default is 5432)
- Username :t is used to authenticate with the Postgres server
- Password :The password associated with the Postgres username
- Database : The name of the database to which you want to connect
- SSL : Enable if you want to use SSL for the connection. If SSL is enabled, just upload the Certificate Authority (CA) certificate file and SSL key as well as SSL certificate if necessary.
- CA Certificate : The Certificate Authority (CA) certificate. Upload this certificate if the server’s certificate is self-signed or issued by a CA that is not widely recognized.
- Client Certificate & Client Key : Upload these files if the server requires mutual authentication, allowing both the client and server to verify each other’s identity.
- Host : The hostname or IP address of the Redis server.
- Port : The port number on which the Redis server is listening (default is 6379)
- Username :It is used to authenticate with the Redis server
- Password :The password associated with the Redis username.
- Database : The name of the database to which you want to connect
- SSL : Enable if you want to use SSL for the connection. If SSL is enabled, just upload the Certificate Authority (CA) certificate file and SSL key as well as SSL certificate if necessary.
- CA Certificate : The Certificate Authority (CA) certificate. Upload this certificate if the server’s certificate is self-signed or issued by a CA that is not widely recognized.
- Client Certificate & Client Key : Upload these files if the server requires mutual authentication, allowing both the client and server to verify each other’s identity.
Connectors / MQTT Bridge Connector
- Broker URL : The URL of the MQTT broker to which you want to connect.
- Port : The port number on which the MQTT broker is listening (default is usually 1883 for non-SSL and 8883 for SSL)
- Client ID :Unique Client ID of the device to connect with your Remote MQTT Broker
- Protocol version :protocol version of the above mentioned client(eg: 3 or 5)
- MQTT Username :The username for authenticating with the MQTT broker (if required).
- MQTT Password : The password for authenticating with the MQTT broker (if required).
- SSL : Select whether to use SSL/TLS for the connection. If SSL is enabled, just upload the Certificate Authority (CA) certificate file and SSL key as well as SSL certificate if necessary.
- Request URL : The API URL to which the HTTP POST request will be sent. (Eg - http://example.com/some_url)
- Authentication Type : Select the type of authentication required for the HTTP POST request. Following are the types of authentication :
- No Authentication : No authentication is needed
- Basic : Give username and password for authenticating the requested URL
- API-KEY : Give the API-key for authenticating the requested URL
- Token : Give Token for Authenticating the request URL
- Bearer Token : Give Bearer token for Authenticating the request URL
- SSL : Select whether to use SSL/TLS for the connection If SSL is enabled, just upload the Certificate Authority (CA) certificate file and SSL key as well as SSL certificate if necessary.
- Host : The hostname or IP address of the InfluxDB server (eg : http://serverurl.com).
- Port : The port number on which the InfluxDB server is listening (default is 8086)
- Token :The token used for authenticating with the InfluxDB server.
- Bucket name :The name of the bucket to which the data will be written in InfluxDB
- Organization : The organization name associated with the InfluxDB instance.
- SSL : Select whether to use SSL/TLS for the connection If SSL is enabled, just upload the Certificate Authority (CA) certificate file and SSL key as well as SSL certificate if necessary.
- CA Certificate : The Certificate Authority (CA) certificate. Upload this certificate if the server’s certificate is self-signed or issued by a CA that is not widely recognized.
- Client Certificate & Client Key : Upload these files if the server requires mutual authentication, allowing both the client and server to verify each other’s identity.
- Kinesis Stream Name : The name of the Kinesis stream where data will be sent.
- AWS Region : The AWS region where your Kinesis stream is located (e.g., us-east-1).
- AWS Access Key : The AWS access key is used for authenticating to the AWS services
- AWS Secret Key : The AWS secret key is used for authenticating to the AWS services
Confirmation
You already configured the connector on and enabled . Enabling this connector will disable the existing connector. Do you want to proceed?
Warning : Enabling Connector Without SSL Might Cause Security Issues
Enable Data Connector
Enabling this connector will push data stream to external system.
Do you want to proceed ?
** Without SSL, security risks may arise.
Disable Data Connector
Disabling this connector will stop streaming data to your external system.
Do you want to
proceed?