IoT Mesh Network Integration Simulator

Network

Device count 10

Radio range 3.2 m*

Auto-generate sensor traffic

Actions

Link Status

Network initialized. Nodes discovering peers…

Connected to gateway

0 / 0

Active links

Delivered / Dropped

0 / 0

Last route hops

—

How it works

Real IoT deployments rarely have every device within radio range of the gateway. Instead, nearby devices integrate into a self-organizing wireless mesh: each node discovers peers inside its radio range and the network computes multi-hop routes, exactly as Zigbee, Thread and Bluetooth Mesh do in practice.

Link exists:  dist(i, j) ≤ R_radio
Route found:  shortest path i → gateway via BFS
              over the graph of live links
Self-healing: when a relay node fails, its edges
              are removed and BFS re-runs, finding
              the next-shortest surviving path

Device count / Radio range — controls network density. Too sparse (short range, few devices) and nodes become unreachable islands.
Send Packet Now — a random sensor emits a reading; it is routed hop-by-hop toward the gateway (breadth-first search = fewest hops, the standard baseline mesh routing metric).
Fail Random Node — simulates a dead battery or radio fault. Any packet that depended on that node as a relay must find a new path — this is the "self-healing" property that makes mesh topologies robust for real deployments.
Connected to gateway — the count of devices that currently have *any* surviving multi-hop path to the gateway, live-recomputed as links and node health change.

This is the core integration challenge in real IoT systems: heterogeneous, unreliable, battery-powered devices must discover each other and cooperatively relay data to a common gateway without any single point of failure dominating.

Gateway Sensor node Actuator node Failed node Packet in flight

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.