Devices (sidebar group BUILDING) is where every widget in the installation is created and wired. A device (widget) is what the resident sees and controls in the app; behind it sit one or more communication objects — the individual values (switch state, position, temperature, …) that connect to the physical world through a protocol.
What you need: at least one room and one category (see “Building Structure & Categories”), the relevant protocol enabled (see “Services & Protocols”), and a connection for it (see “Connections”). Protocol-specific binding is covered per protocol: KNX (see “KNX Integration”), Home Assistant (see “Home Assistant Integration”), Modbus (see “Modbus TCP Integration”), HTTP (see “HTTP Integration”), MQTT (see “MQTT Integration”), BACnet/IP (see “BACnet/IP Integration”), TCP/UDP (see “TCP/UDP Integration”), Sonos (see “Devices Library & Sonos Binding”).
💡 Tip: Before wiring a device object by object, look for it in the Devices Library (see “Devices Library & Sonos Binding”). For a covered inverter, meter, charger, relay or speaker, the library creates the widgets with every object already bound — an address is all you type.
The Devices workspace
The page has three columns:
- Left rail — browse. Filter the device list by Rooms, Categories, Device Types or Protocols, each with a device count. The rail also offers inline shortcuts: Add Room, Add Category, Add Floor, Add Protocol.
- Center — the device list. Search, filters, and one row per device. The page header holds a round icon button with no text (its tooltip reads Health; it opens the Health page, see “Value Transformations & Health”), then Categories (manage categories, see “Building Structure & Categories”), Add from library (the Devices Library, see “Devices Library & Sonos Binding”) and Add Device.
- Right rail — Communication objects. The source material to bind from, on two tabs: KNX shows the group-address tree (see “KNX Integration”), Home Assistant shows the entities (see “Home Assistant Integration”). The rail does not depend on the selected device. If it is hidden, reopen it with the Show communication objects button next to the device search field.
Per device row you can:
- Change its icon — click the icon tile at the start of the row.
- Toggle Visible in the app — hide a device without deleting it (useful for devices that only feed logic or logging).
- Open its Activity (see “Device Activity Log”).
- Edit Device — change the name, description, room, category, protocol, type or subtype. Read the warning under “Widget types & sub-types” below before you change the type or subtype.
- Show objects — expand the row to reveal the device's communication objects.
- Delete the device (with confirmation; this cannot be undone).
Chips and icons summarize the configuration at a glance. On the device row itself:
| Chip | Meaning |
|---|---|
| Protocol chip | The protocol (connection) the device uses. |
| NO GLOBAL | The device is excluded from global commands (see “Alarm PIN & Global-Command Exclusions”). |
Expand the device to see the rest. A legend above the object list names the four icons that can appear at the end of each object row:
| Legend | Meaning |
|---|---|
| LOGGED | A database icon: this object logs its history (see “Object Settings, Logging & Notifications”). |
| GRAFANA | A chart button, on logged objects only: opens the Grafana panel builder (see “Object Settings, Logging & Notifications”). |
| TRANSFORMS | The round button that opens the object's transformation chain (see “Value Transformations & Health”). |
| SETTINGS | The gear that opens the object settings (Edit Object, see “Object Settings, Logging & Notifications”). |
On an alarm device, the PIN CODE card above the objects shows PIN SET or NO PIN (see “Alarm PIN & Global-Command Exclusions”).
Adding a device
- Click Add Device.
- Enter the Device Name.
- Pick the widget Type and, where a Subtype field appears, the subtype (see “Widget types & sub-types” below).
- Pick an Icon and optionally enter a Description.
- Pick the Room and the Category.
- Pick the Protocol — this is the connection the device uses (see “Connections”). Camera, videophone and web view types have no Protocol field.
- Click Create Device.
The new device has its objects, but none is bound yet: a dash in the binding column means the object is not connected to the equipment.
To create several similar devices at once, turn on Add Multiple Devices (offered only when you add a device, not when you edit one). Under Additional Device Names, type the second name and click Add another device for each further name. One device per name is created with the same settings; an empty line is skipped, and the dialog does not check for duplicate names. The button becomes Create Devices.
Widget types & sub-types
The widget Type decides everything about a device: which controls the app shows, and which communication objects exist. Objects are created automatically from the device type — you never add objects by hand. Many types offer a Subtype that varies the control set. For a shutter, SHUTTER has the slats and BLIND is position only. The Type list has a search field and prints the names in title case, for example Analog Input and Analog Output.
Each object has:
- a direction — whether the value flows in (from the device to HyperVisu), out (commands to the device), or both;
- a data type — boolean, number, text, and so on.
Choose the type that matches the physical function, not the protocol: a KNX-driven light and a Home Assistant light both use the same light widget type. The complete catalog of types, sub-types and their objects is in the widget type reference (see “Widget Types Overview”).
⚠️ Warning: Choose the type and subtype carefully. Changing Type or Subtype later in Edit Device replaces all the device's objects with those of the new type, and every binding is lost. The dialog shows no warning and asks for no confirmation. Changing the name, icon, room or category keeps the objects.