by Ponlakshmi
As IoT ecosystems grow more complex, the ability to simulate large-scale device behavior has become essential for developers, QA engineers, and solution architects. IoT simulators provide a cost-effective way to model thousands (or more) of devices, manage message flows, and evaluate communication patterns—without the overhead of deploying physical hardware fleets. This approach accelerates development, reduces integration risk, and helps ensure that IoT applications behave reliably under real-world conditions.
Cloud-based MQTT brokers like HiveMQ Cloud and our own Cloud MQTT Broker (CrystalMQ) provide scalable, secure infrastructure for managing device messaging at scale. One critical part of any IoT deployment is ensuring that your simulated devices integrate smoothly with the MQTT broker that anchors your data flow.
The Bevywise IoT Simulator enables realistic device traffic generation, security validation, and performance testing across any MQTT broker—including brokers like HiveMQ. In this blog, we’ll walk through how to use the Bevywise IoT Simulator and integrate it with an MQTT broker like HiveMQ Cloud, enabling a scalable, secure, and production-like IoT simulation environment.
Integrating an IoT simulator with an MQTT broker isn’t just about “does it connect?” It’s about reproducing traffic and operational realities you’ll see in production. By combining the Bevywise IoT Simulator with a HiveMQ environment, you can:
A repeatable sim‑to‑broker workflow gives you confidence that a HiveMQ‑based architecture can scale, secure, and sustain real IoT workloads—before you invest in hardware rollouts.
If your goal is to reach production faster, catch scaling issues earlier, and reliably feed your data streams with realistic device behavior, Bevywise gives you more control:
In short: Bevywise makes it easier for HiveMQ users (and anyone running MQTT) to simulate production‑like behavior without writing custom traffic generators every time.
Before you start, confirm the following:
To start the Bevywise IoT Simulator, simply double‑click the simulator ".exe" file.
After launch, a terminal session will open in the background, and you’ll be directed to the Bevywise IoT Simulator Dashboard in your browser.
On first launch, you’ll see a default network named "HEALTH_CARE".
This is a starter template created by Bevywise Networks. The simulator interface is served locally at: 127.0.0.1:9000
Use this default network to explore the UI, or create your own.
1. Click the menu icon (☰) in the top‑left corner.
2. Choose New Network (you’ll also see Existing Network and Templates).
3. In the dialog that appears, provide a Name and Description.
4. Click Create.
Your newly created network will appear in the left navigation panel above the Dashboard entry.
Open your HiveMQ Cloud console and locate the Overview section for your cluster.
Copy the URL from the connection details and paste it into the IP Address field in the simulator settings, as instructed below.
1. In the Bevywise IoT Simulator, switch to the network you created.
2. Click the Settings icon in the top‑right corner.
3. In the connection settings dialog, enter:
4. Click Save to apply settings.
1. In the top‑right corner, click the `` icon next to Settings.
2. Select Blank Device.
3. In the device dialog, enter:
4. Click Save.
Your device appears in the device list. A red status dot indicates the device is currently inactive (not connected).
Before you bring devices online, create credentials in HiveMQ:
1. Go to the HiveMQ Cloud Access Management Page.
2. Click Add Credentials.
3. Provide a Username, Password, and Permissions (read/publish rules as needed).
4. Save the credentials.
After creating the credentials, use the same Username and Password in the simulator:
1. Select the device you created.
2. Enable Authentication.
3. Enter the mapping:
Note : Use the exact same username and password created in HiveMQ Access Management when configuring device credentials in the simulator.
Events control what and when your simulated devices publish.
To create an event:
1. Click the `+` icon (same as used for device creation).
2. Choose an event type—e.g., Whole Day.
3. In the event dialog, configure schedule, topic, payload pattern, and interval.
After saving, an event topic will appear in the Event Menu for the selected device/network.
Activate Device & Start Publishing
Once your simulator devices are connected, data is already being published to your HiveMQ Cloud instance. To monitor that data in real time, you can use the HiveMQ Web Client, which acts as a subscriber.
To use the Web Client:
1. Open the HiveMQ Web Client in your HiveMQ Cloud console.
2. Enter your Username and Password, then click Connect
3. In Topic Subscriptions, enter the topic you configured in your simulator events.
4. Click Subscribe
5. Scroll down to view incoming MQTT messages in the console as they arrive.
You’ve now validated end‑to‑end connectivity between Bevywise IoT Simulator and your HiveMQ environment.
The steps above get you connected. The sections below help you turn that connection into a full HiveMQ testing and HiveMQ data simulation lab powered by Bevywise.
Use your Bevywise simulation to run controlled experiments:
1. Smoke Test
Bring up 5–10 devices; confirm connect/publish/subscribe flows work.
2. Scale Ramp
Increase virtual devices in stages (100 → 1k → 10k). Monitor broker resource use and connection stability.
3. Burst / Spike Test
Publish high message bursts (e.g., 10x normal rate for 60s) to see how the broker handles backlog and QoS.
4. Soak / Longevity Test
Run 24‑hour or multi‑day connections with periodic publishes to detect memory leaks, slowdowns, or session dropouts.
5. Disconnect / Reconnect Storm
Script rolling disconnects to mimic network flaps in the field. Observe session state, queued QoS1/2 delivery.
6. Security Validation
Try invalid credentials, missing certs, or blocked topics to confirm broker enforcement.
The Bevywise IoT Simulator lets you reproduce realistic device data models. Consider these patterns:
Pattern | Use Case | Notes |
---|---|---|
Periodic | Sensor reports at fixed | Great for dashboards & trend |
Telemetry | interval | analytics. |
State Change Events | Alarms, status flips | Low volume; high importance. |
Bulk Upload / Batch | Gateway uploads array of readings | Useful for bandwidth efficiency tests. |
Command / Response | Cloud → Device → Ack | Validate bi-directional topics. |
Retained Status | Last known value | Check retained message handling in broker. |
{
"deviceId": "device-001",
"ts": 1737446400,
"tempC": 22.4,
"humidity": 58,
"status": "ok"
}
Good MQTT topic structure makes testing easier and analytics cleaner.
<env>/<account>/<deviceId>/telemetry
<env>/<account>/<deviceId>/events
<env>/<account>/<deviceId>/state
Examples:
dev/demo/device-001/telemetry
prod/factory-a/line3-sensor07/events
Keep topic depth consistent so you can subscribe with wildcards (e.g., dev/+/+/telemetry).
Symptom | Likely Cause | Fix |
---|---|---|
Cannot connect | Wrong host/port or TLS mismatch | Verify endpoint & port 8883; upload correct cert. |
Auth failed | Username/password mismatch | Re-enter credentials from HiveMQ Access Management. |
No messages seen | Topic mismatch or device inactive | Confirm event topic; device icon should be green. |
Cert error | Expired or missing CA root | Re-download ISRG Root X1 and upload again. |
Random disconnects | Duplicate Client IDs | Ensure unique Device ID per client. |
Ready to level up your HiveMQ testing?
Bevywise IoT Simulator combined with HiveMQ Cloud offers developers a powerful way to simulate IoT environments, configure MQTT brokers, and publish real-time data securely. This integration ensures faster testing, reduced costs, and more reliable deployments without relying on physical devices.
Download our IoT Simulator and try it out now to connect with HiveMQ Cloud (and other MQTT brokers) in minutes and start building robust IoT solutions today!