What you need: a wired network connection for the server, and a KNX/IP interface or router for KNX projects. Everything else in this section is optional or project-dependent.
Network requirements
- Ethernet — connect the server to the LAN with a cable.
- IP address — the server uses DHCP by default; a static address can be set in the admin panel (see “Network & Time Settings”). Updating the server never changes the address of a server that is already configured.
- Always reachable — whatever its main address, the server also answers at
192.168.1.60while it is waiting for a DHCP address, and at169.254.60.60when it is the only server on the network. These cover commissioning on a network that has no router yet (see “Unboxing & First Power-Up”). - Name resolution — the server announces itself on the local network (mDNS) as
hypervisu-<serial>.local, and also ashypervisu.localwhen it is the only server on the network. It appears by name in most routers and network scanners. - Time — the server synchronizes its clock over NTP. Correct time matters: schedules, automations and history timestamps depend on it.
- Internet — required for cloud access, weather, energy prices, updates, and emailed password-reset codes. Local control keeps working without it.
📘 Note: Cloud access needs no router configuration at all — the server opens an outgoing tunnel to the Elausys Cloud Service. Do not set up port forwarding.
Browsers and apps
- Admin panel and web app — any up-to-date modern browser (Chrome, Edge, Firefox, Safari) on a desktop or laptop. The admin panel is designed for desktop screens.
- HyperVisu app — from the App Store (iOS) or Google Play (Android).
- Minimum app version — the server declares a minimum app version. If your app is older, it shows an update notice and asks you to update before connecting (see “App Settings & Personalization”, “Software Updates”).
KNX prerequisites
For a KNX project you need:
- A KNX/IP interface (Tunnel UDP) or a KNX/IP router (Multicast) on the same LAN as the server.
- A free individual address on the bus for the server itself.
- The ETS project file (
.knxproj) — optional, but strongly recommended: the setup wizard can rebuild the whole visualization from it (see “First-Run Setup Wizard”).
API keys and accounts you may need
| Service | What to obtain | Needed for |
|---|---|---|
| Weather | An API key from Pirate Weather or OpenWeatherMap | Weather on the home screen, in views, automations and logic (see “Weather Service”) |
| Energy prices | An ENTSO-E API key | Day-ahead electricity prices (see “Energy Price Service”) |
| An SMTP account (e.g. a mailbox with an app password) | Email actions in automations (see “Email Service”) | |
| Dashboards | A Grafana service-account token | Embedded dashboards and the panel builder (see “History & Data Logging”) |
None of these are required to commission the system — each unlocks one optional service.
ElauPro (optional)
A HyperVisu project can be fully configured from the admin panel alone. Installers who work with ElauPro, the Elausys project cloud, can additionally link the server to an ElauPro project using the serial number and server token shown on the admin System page — centralizing the project information, producing the hand-over documentation, and reaching all their installations remotely from one place (see “Integration with ElauPro”).