|
View MQTT Broker Stats
More Clients
0
0
0
0
QoS1 & QoS2
1 message at 1 KB per second
Data Support
The Public MQTT Broker is an open instance of the Bevywise CrystalMQ Server, allowing connection from any standard MQTT Client for data exchange. It operates without MQTT authentication, so caution is advised when transmitting sensitive information, as it can be accessed by any connected client.
Our Public MQTT Broker operates by providing an open instance of the CrystalMQ Server. It allows MQTT clients to connect via TCP (port 1883) or Websocket (port 10443) for real-time data exchange. However, it does not require MQTT authentication and lacks TLS encryption, making it suitable for non-sensitive data applications.
You can connect your MQTT Client to the host address `public-mqtt-broker.bevywise.com` or `broker.bevywise.com` using port `1883` for MQTT over TCP and `10443` for MQTT over Websocket. Ensure your client implements reconnection logic to maintain connectivity during updates or changes to the broker.
TLS is not currently supported on the public MQTT Broker. However, TLS and MQTT Authentication are available on our FREE MQTT Broker and dedicated premium instances. We are actively working to implement TLS support on the public MQTT server as well.
The Public MQTT Server does not permanently store data. For handling QoS1 and QoS2, data is temporarily held until acknowledgment is received. Our premium MQTT broker instances offer options for data storage and visualization.
No, we do not recommend using the public instance of the MQTT broker for production purposes. However, we offer a FREE private MQTT Broker instance that you can sign up for production use, with data transfer limitations. For secure and reliable MQTT data transfers without limitations, consider our premium options.
