A reference of the terms used across the Weble IoT Universal Gateway and Weble Cloud documentation. When a page mentions a concept that is not obvious, look it up here.
Terms are grouped by area: Gateway concepts, Drivers and protocols, Routing and logic, Data and observability, APIs, Cloud concepts.
Gateway
A configured instance of a driver talking to a specific physical device or external service. Multiple gateways can run in parallel — for example two Modbus gateways talking to two different PLCs. Each gateway has a unique id, a name, a driver field that picks the protocol, and a json configuration object whose schema depends on the driver. Managed from the iot/gateways UI page or programmatically through the gateways peers module.
Address
A single data point exposed by a gateway — a Modbus register, a KNX group address, a BACnet object, an MQTT topic, an SMS recipient, etc. Addresses are protocol-agnostic from the routing engine's point of view: any address can be read from, written to, or routed to any other address regardless of the underlying protocol. Each address has an id (numeric), a name (the protocol-specific identifier), an optional alias (a human-friendly handle), and a json block that holds protocol-specific options.
Address key
Any of the three forms accepted by API methods that target an address: numeric id (23055), name ('4/7/25'), or alias ('tempLivingRoom'). The system resolves all three forms to the same internal record.
Driver
A piece of software inside the gateway that knows how to speak one specific protocol — Modbus, BACnet, KNX, MQTT, SMTP, etc. Drivers are loaded dynamically; each runs in its own isolated process under PM2. The full list is on the drivers page.
Cluster
A grouping mechanism for gateways: gateways with the same cluster integer share certain process-level resources. Use cluster 0 for single-gateway setups, or group related gateways under the same cluster id when running many of them on the same machine.
Logic instance
A programmable circuit that runs as its own process and reacts to input addresses, computes intermediate state, and writes output addresses. Used for time-based control loops, threshold alarms, complex automation. Edited from the Logic Module page.
View
A saved layout / dashboard configuration tied to one or more gateways. Used to render data graphically in the gateway's web UI. See the Views page.
Field bus
A serial or wireless network used inside a building or industrial site to connect sensors, actuators, and controllers — KNX, M-Bus, BACnet MS/TP, Modbus RTU, EnOcean, DALI, etc. The opposite of an IP-only protocol.
BACS
Building Automation and Control System — the umbrella term for everything that automates HVAC, lighting, blinds, access control, and metering inside a building. The Weble IoT Universal Gateway is a BACS protocol bridge.
Master / slave
In master/slave protocols (Modbus RTU, M-Bus, …) the master initiates every exchange and the slaves respond. The gateway can act as either side depending on the driver mode.
Polling vs push
Polling drivers fetch values by asking the device on a schedule (Modbus master, M-Bus). Push drivers receive values whenever the device decides to send them (BACnet COV, EnOcean radio, MQTT). Both end up writing values to the same address store.
Datapoint type (DPT)
A KNX-specific term for the encoding of a value on the bus — 9.001 is a 2-byte float, 1.001 is a single bit, etc. Equivalent concepts exist in other protocols (BACnet object types, Modbus function codes).
OBIS code
A standardized way of identifying meter measurements (1-0:1.8.0 = total active energy import, etc.). Used by IEC 62056 / DLMS energy meters and by the OBIS driver.
Route
A binding from a source address to one or more destination addresses, optionally through a transformation function. Routes are how the gateway translates between protocols at runtime — e.g. "every time KNX address 4/7/25 changes, write its value to Modbus register %M1 and to MQTT topic /sensors/temp". Defined on the Routes page.
Routing function
A small JavaScript snippet attached to a route to transform the value in transit — multiply by 10, convert units, dispatch based on the value, etc. Reusable across many routes.
Blockly
The visual programming editor used to write routing functions and logic block code without typing JavaScript. Generated blocks are compiled to JavaScript and run inside the routing or logic engine. See Routes functions.
Source / destination address
The source is the address whose value triggers the route; the destination is the address that receives the (possibly transformed) value. A single route can have one source and many destinations.
Routing engine
The runtime that watches every source address for changes and dispatches the values through the configured routes. It can be paused (no routes execute) or fully stopped (routes are unloaded from memory) — both are exposed through gateways.pauseRoutes and friends.
Logger
A configured database connector that persists address values for historical analysis. The gateway can run several loggers in parallel — for example a local PostgreSQL logger plus a remote cloud logger for federation. Managed via the loggers peers module.
Logger driver
The implementation of a specific logger backend — mysql, postgresql, influxdb, logServer (federation to a remote box), local, etc. Same separation as gateway drivers.
Logger connector
A logger seen from the outside: a tuple of (id, type, optional groups). The cloud uses connectors to federate queries across many gateways without caring about the underlying database.
Site
One logical data source identified by a unique id — typically the gateway's hardware MAC address for the local box, or a remote box id when accessed through a logger connector. Used by the cloud to address gateways individually.
Aggregate
A time-bucket summary of raw values: every value in the bucket is reduced to (min, avg, max). Specified as a duration string — 15m, 1h, 1d, etc. — passed to loggers.query.
NDJSON
Newline-delimited JSON: a streaming format where each line is a complete JSON object, terminated by \r\n. Used by the REST loggers endpoints when streaming=1 is set. See REST loggers.
Live value subscription
A long-lived connection over which the gateway pushes value changes as they happen, instead of forcing the client to poll. Available both through the peers loggers.live method and the REST /loggers/live endpoint.
Crash log
A snapshot of the state of a process at the moment it crashed — captured automatically by PM2 and retrievable via the API. One per crashed driver / logger / logic instance.
Peer
One process on the gateway's internal P2P mesh. Drivers, the routing engine, the logic module, the web server, the UI, and external clients are all peers. They share modules and exchange events through the peers protocol.
Peers mesh
The set of currently-connected peers. Visible from any peer with peers.connectedPeers(). The main gateway process is named 'supervision' and is the peer external clients usually talk to.
Module
A named bundle of methods that one peer exposes to others. Core modules are gateways, loggers, system, accounts, logics. Loaded with peer('supervision').require('moduleName', callback).
Bootstrap (POST /auth)
The HTTPS handshake that lets a remote client (browser, Node.js process) load the peers runtime. Returns the source code of peers.js and socket.io-client.js plus a session id; the client evals the runtime and gets a connected peer object. See getting started.
Peers dispatcher (REST)
The /peers/{peer}/{module}/{method} HTTP endpoint that lets a REST client invoke any peers method without loading the peers runtime. Documented at REST peers.
Streaming endpoint
The /peers/{driver}/{id}/streaming HTTP endpoint for binary upload / download through driver streams (file transfer over field-bus protocols). See REST streaming.
Weble Cloud
The hosted platform that provides remote access (VPN), monitoring, and a unified dashboard for all the gateways a customer owns. Documented under /cloud.
Weble Connect
The cloud-side application that gives users a unified interface to their hosts, dashboards, and on-demand VPN connections. See Weble Connect.
Host
A single registered gateway in the cloud — identified by its hardware id, listed under VPN hosts and reachable through the cloud's VPN mesh.
VPN mesh
The Tinc-based encrypted mesh that connects every Weble gateway and the cloud servers. Hosts on the mesh use addresses in the 26.x.x.x range and can route traffic between each other through the cloud.
On-demand VPN
A temporary VPN connection requested from the cloud UI: it stays up only as long as the user needs it, then closes automatically. Used for occasional remote troubleshooting without leaving permanent VPN tunnels open.
Group
A logical collection of hosts that share access policies, dashboards, or VPN topology. Managed under VPN groups.
Site-to-site VPN
A permanent VPN tunnel between two sites' gateways through the cloud, used to bridge their local networks. See Site to site.
Base device
The hardware model of the gateway — UniPi Iris, UniPi Patron, Raspberry Pi CM3+, G100, G110, etc. Determines available ports, supported drivers, and firmware variant. Reported by system.getInformations.
1-Wire
A low-cost serial bus used for temperature sensors and small actuators. Supported by the IO driver.
Modem
The optional 4G/LTE cellular modem some gateway models can have, used as a fallback or primary uplink. Toggled with system.setModemEnable.
Tinc
The mesh VPN daemon used to connect every gateway to the VPN mesh. Toggled with system.setTincEnable.