Appliance specs, network ports, on-board services, minimums and data privacy.
elausys · 18 August 2026On this page
The server
Item
Specification
Form
Compact, always-on server appliance running the HyperVisu software and its optional services
Network
Wired Ethernet; DHCP by default
Always-on addresses
192.168.1.60 while no DHCP address has been obtained; 169.254.60.60 when it is the only server on the network
Network name
hypervisu-<serial>.local, plus hypervisu.local when it is the only server on the network
Identity
Serial number (on the label and in the app) + server token (System page)
Network & ports
Path
Port / protocol
Admin panel & web app
HTTP(S) on the server's address
Remote access
Outbound tunnel to the Elausys Cloud Service — no port forwarding required
KNX/IP
UDP 3671 (tunnelling / multicast routing)
Modbus TCP
TCP 502 (default, configurable per connection)
Home Assistant
TCP 8123 (default HA port)
MQTT (as a client)
TCP 1883 (plain) or 8883 (TLS, mqtts://) to the broker — configurable per connection; ws:// / wss:// also supported
MQTT (built-in broker)
TCP 1883 (on by default) and 9001 websockets (off by default) — each port and bind address configurable; ports already used on the appliance are refused. Neither listener is encrypted: LAN only (see “The Built-in MQTT Broker”)
BACnet/IP
UDP 47808 (standard BACnet port) — the server binds the local port 47808 for its shared socket and sends to each device's configured port
TCP/UDP
As configured per device connection (TCP or UDP, any port — e.g. AUDAC XMP44 TCP 5001); an optional UDP listen port for devices that push
Sonos
TCP 1400 to each speaker, plus one local event listener port on the server (default 6329) that the speakers send their status events to
E-mail (SMTP)
465 (SSL/TLS) or 587 (STARTTLS)
Compatibility
Item
Supported
ETS project import
.knxproj files from ETS 5 and ETS 6, including password-protected projects
Devices Library
Device templates from multiple brands, shipped with the server and extended by updates; your own templates can be imported (see “Devices Library & Sonos Binding”)
On the server, in your building — nothing is required to leave it
Cloud traffic
Only for what needs it: remote access through the Elausys Cloud Service, system e-mail relay (password reset), and the optional ElauPro link/sync
Weather & energy prices
Fetched by the server from the providers you configure, with your own API keys
📘 Note: Working with no internet connection is supported for day-to-day use on the LAN; remote access, weather, energy prices, e-mail and password reset by e-mail need connectivity.
Frequently Asked Questions
Does HyperVisu work without internet?+
Yes. Day-to-day control works on the local network. Remote access, weather, energy prices, email and email password resets require connectivity.
Do I need port forwarding for remote access?+
No. HyperVisu uses an outbound tunnel to the Elausys Cloud Service.
Which ETS project files can I import?+
HyperVisu supports .knxproj files from ETS 5 and ETS 6, including password-protected projects.
Where are my configuration and history stored?+
Configuration, users and history are stored on the HyperVisu server in your building.
Keep exploring
Find the other guides for this product in the documentation.
