③ Integrate 接 · Free & open source

Gateway

Bring mesh data into the system you already run. A desktop app connects a node by USB or BLE and forwards its data onward — MQTT, a transparent serial tunnel, and more. The node stays pure-mesh; the host does the rest.

Free Open source · GPLv3 Windows / macOS / Linux
siliqs-mesh-bridge · 127.0.0.1:8765
Transport (the node)
◆ /dev/ttyACM0 — USB node
Output MQTT
broker · msh/2/json/<ch>/<node>
Start ● running

What it solves

One job: get the data out of the mesh and into a system you already run.

Who
Someone who needs the mesh data in their own system — an integrator, IT, or anyone with a cloud or plant-control setup.
The pain
“The node runs on the mesh, but the data is stuck in the mesh — my cloud / database / SCADA can’t reach it. And I don’t want to put WiFi/MQTT on the node.”
What it removes
The node never has to be online; the host translates the mesh data and delivers it onward.
In → out
A node on USB/BLE → (pick a north-bound output) → data into MQTT / a serial tunnel / (soon) Modbus-TCP.
Done when
The remote RS485 device’s values show up in the user’s existing system.

How it works

Download & run

Grab the app for Windows, macOS or Linux and open it — a browser control panel opens at 127.0.0.1:8765. No Python, no command line.

Connect the node

Pick your node from the port list (USB) or by BLE name — connected nodes are marked and sorted first.

Pick an output & Start

MQTT gateway (telemetry → your broker) or a serial tunnel (a wireless serial cable between two hosts). Click Start; data flows.

The builds are unsigned community apps — on macOS right-click → Open the first time; on Windows choose “More info → Run anyway”. Prefer a package manager or a headless box (RPi / OpenWrt)? pip and Docker paths are on GitHub.

Earlier steps

Provision → configure → integrate. This is the last step — the first two get the node ready.