Connections (sidebar group SYSTEM) manages the configured links between the server and the outside world. A connection is one configured link — one KNX interface, one Home Assistant server, one Modbus device, one HTTP endpoint, one MQTT broker, one BACnet device, one TCP/UDP device. Devices are then attached to a connection (see “The Devices Workspace”).
How many connections a protocol takes:
- KNX, Home Assistant and Virtual — exactly one connection each.
- Modbus TCP, HTTP, MQTT, BACnet/IP and TCP/UDP — as many as you need: one per physical device or endpoint (one per broker for MQTT).
What you need: the protocol enabled on the Services page (see “Services & Protocols”). A connection defined for a disabled protocol shows Enable <protocol> in Services instead of a live status.
The connections list
The list shows every connection with a live status.
For each connection you can:
- Search by name, host or device.
- Enable/disable the individual connection.
- Test — runs a live connection test and reports Connection succeeded or Connection failed. The button is offered for KNX, Home Assistant, MQTT, TCP/UDP, BACnet/IP and Sonos.
- Duplicate — copies the connection (named "(copy)"); useful for a second Modbus or TCP/UDP device with similar settings.
- Delete — a warning states how many devices lose their source: the devices are kept and marked unreachable, not removed.
Duplicate and Delete are not offered on the KNX, Home Assistant and Virtual connections: there is exactly one of each.
Selecting a connection opens its detail panel:
- Where it connects — the protocol-specific address settings.
- How often and how long to wait — poll interval and timeout, where the protocol uses them.
- Devices on this connection — the devices using this link, with an Open in Devices shortcut.
Adding a connection
- Click Add connection.
- Pick the protocol first: Modbus TCP, HTTP, MQTT, TCP/UDP, BACnet or Sonos. The dialog then shows only that protocol's fields.
- Enter an Instance Name — this is the name you see on devices that use the link.
- Fill in the protocol fields and click Create connection. The button stays disabled until the name and the address are filled in.
The new connection is saved at once and opens in its settings. The dialog asks only for the essential fields; the remaining settings described under “Per-protocol settings” below are in the connection's settings, where you change them and click Save connection.
📘 Note: KNX, Home Assistant and Virtual are not offered in this dialog, because each has exactly one connection. Select its row in the connections list instead. The Home Assistant row appears when you switch on Home Assistant Protocol on the Services page (see “Services & Protocols”).
Per-protocol settings
KNX
| Field | Description |
|---|---|
| IP Address / Port | The KNX/IP interface or router on your LAN. |
| Individual Address | The physical address HyperVisu uses on the bus. |
| Communication Protocol | Tunnel UDP (point-to-point to an interface) or Multicast (routing). |
| Bus Date/Time | Optional: the server broadcasts the current date and time to the bus on a group address, every send cycle seconds. |
Click Discover interfaces to scan the network for KNX/IP interfaces. Pick one from the results and its settings fill the connection fields.
Home Assistant
| Field | Description |
|---|---|
| Home Assistant URL | Full URL including http:// or https:// and the port. |
| API Token | A long-lived access token, generated in Home Assistant's user settings. |
There is no Home Assistant entry under Add connection. Select the Home Assistant connection in the list, fill in the two fields and click Save connection. The server reconnects with the new settings by itself.
Modbus TCP
| Field | Description |
|---|---|
| Server IP Address | The Modbus TCP device. |
| Modbus TCP Port | Default 502. This field is not in the Add connection dialog: a new connection is created on port 502. If the device listens on another port, select the new connection, change the port and click Save connection. |
| Poll Interval (seconds) | How often the server reads the registers, in seconds. The grey 30 in the field is only a hint: left empty, the server polls every 5 seconds. |
HTTP
| Field | Description |
|---|---|
| Base URL | e.g. https://api.example.com/v1. Object paths are appended to it (see “HTTP Integration”). A non-standard port is part of the URL; there is no separate port field. |
| Poll Interval (seconds) | Seconds between polls. Set 0 for a write-only endpoint. The grey 60 in the field is only a hint: left empty, the endpoint is never polled. |
| Timeout (ms) | Request timeout in milliseconds, from 1000 to 120000. Left empty, a request waits 30 seconds. |
| Authentication | None, API Key (Header), API Key (Query Parameter), Basic Authentication, Bearer Token, or Custom Headers (sent with every request). |
An HTTP connection has no Test button. Its status reads State unknown until one of its bound objects has exchanged a request, then Connected.
MQTT
| Field | Description |
|---|---|
| Broker address | Host, or a full URL (mqtt://, mqtts://, ws://, wss://); a plain host means mqtt://. |
| Port | The broker's listener port: usually 1883 for plain MQTT and 8883 for mqtts://. Always type it in the Add connection dialog, where an empty port is saved as 1883 whatever the scheme. The Port field overrides a port written in the address. |
| Username / Password / Client ID | Credentials if the broker requires them; leave the client ID empty to derive one from the server's MAC address. |
| Accept self-signed certificates | TLS only (mqtts:// / wss://): off by default, so the broker's certificate is verified. Switched on, it is not verified at all. |
| CA certificate | TLS only, and only in the connection's settings after Create connection — the Add connection dialog does not have it. Paste the signing authority's PEM certificate when it is not a public one. |
| Broker options | Keepalive (60 s), Default QoS (0/1/2), Availability topic (hypervisu/status) with Announce HyperVisu availability, Clean session. Only in the connection's settings after Create connection; a new connection starts with these defaults. |
Test connects to the broker and waits for its acknowledgement — also available in the add-connection dialog before the connection exists (see “MQTT Integration”). In the dialog it tries the values you typed; on a saved connection it checks the saved values, so click Save connection first when you changed a field.
When the built-in broker is running and nothing is connected to it yet, the Connections page offers a shortcut instead: a panel titled The local MQTT broker is running with a Use the local broker button, which creates the connection with the account HyperVisu manages itself — no address or password to type (see “The Built-in MQTT Broker”).
BACnet/IP
| Field | Description |
|---|---|
| Device address | IP address of the BACnet device, or of the router in front of it. |
| Port | The UDP port the device listens on (standard 47808). |
| Device instance | The device object instance (0–4194302); optional, checked by the test when set. |
| COV subscription lifetime | Seconds before a change-of-value subscription is renewed; empty = service default (600 s). |
| Poll Interval (seconds) | How often points without a COV subscription are re-read (default 30). |
The network scan exists only on a saved connection. The Add connection dialog has no scan and needs a Device address, so the order is:
- Click Add connection, pick BACnet and enter the Device address (a provisional one if you do not know it yet), with the Port and Device instance if you know them.
- Click Test to check the values you typed, then click Create connection.
- In the new connection's settings, click Scan network beside Where it connects. The server broadcasts a Who-Is and lists the devices that answer.
- Select the device and click Use this device: address, port and instance are filled in. They are not saved yet.
- Click Save connection (see “BACnet/IP Integration”).
COV subscription lifetime is also set in the connection's settings only.
TCP/UDP
| Field | Description |
|---|---|
| Device address / Port | The device (AUDAC XMP44: port 5001). |
| Poll Interval (seconds) | How often to re-read the device; 0 for a device that pushes its state on its own. |
| Framing and timing | Transport (TCP · persistent connection / UDP · datagrams), Frame delimiter (\r\n), Payload encoding (ASCII text / HEX bytes), Listen port (UDP), Heartbeat frame • Every (TCP), Connect timeout, Delay between commands, Read everything on connect. |
The Add connection dialog asks for the Device address, the Port, the Poll Interval (seconds), the Transport and the Frame delimiter, and offers Test. The other Framing and timing settings are in the connection's settings after Create connection.
The frames themselves are configured per object (see “TCP/UDP Integration”).
Virtual
Nothing to configure — virtual devices live entirely on the server (see “Virtual Devices & Node-RED”).