HyperVisu stores time-series history in the on-appliance history database (InfluxDB). This chapter covers connecting it, exporting measurement data as CSV, building Grafana panels, and moving whole configuration tables in and out of the server as CSV files.
InfluxDB connection
History needs the InfluxDB service. Open Services and check that the InfluxDB row is switched on. If you switch it on now, a Pending Changes banner appears: click Restart Server and wait for the server to come back.
The InfluxDB Configuration page (Services → InfluxDB → Configure) holds a connection to a history database of your choice. On a standard installation the fields can be empty: the server then writes and reads history through its built-in connection, and you have nothing to fill in.
| Field | What to enter |
|---|---|
| URL | The address of the InfluxDB instance (e.g. http://localhost:8086). |
| API Token | A token with read/write permissions. Use the eye button to show or hide it. |
| Organization | The organization name in your InfluxDB instance. |
| Bucket | The bucket where data is stored. |
Click Test Connection to verify the connection shown in the form, then Save to store it. The Database Status card changes from Not Tested to Connected and shows the Last tested time. Test Connection needs the four fields: when the page is empty there is nothing to test here, and you check the result on a trend page in the app instead. For security a saved token is never shown again; leave the field empty to keep it. If the InfluxDB service itself is disabled, an alert on the page tells you to enable it from the Services page first.
Once a connection is saved, the page also shows the storage used and a Data retention setting. Shortening the retention period deletes older data permanently.
What gets logged. Logging is a switch on each communication object. The objects of a meter and of a trending analog input are logged automatically; for any other object you opt in:
- Open Devices, expand the device and click the Edit Object button (the gear) of the object.
- Switch Log historical values on.
- Click Save object. The object row now shows a database icon and a chart icon. No Apply changes is needed.
Each value the object receives is recorded from that moment on, whether or not it changed; nothing earlier is rebuilt (see “Object Settings, Logging & Notifications”). Logged objects feed the trend charts and meter history in the app, Grafana dashboards, the KNX bus-monitor charts, and the CSV export below.
CSV data export
The CSV Data Export page turns logged history into a spreadsheet-friendly file. It has no entry of its own in the sidebar: open Services and click Export on the InfluxDB row.
- In Object Selection, tick the objects to export. They are grouped by room; use the search box or Select all. If the list is empty, no objects have logging enabled yet — enable it first (see “Object Settings, Logging & Notifications”).
- In Time Period, set Start and End, or use a shortcut: Last 24h, Last 7 days, Last 30 days, Last year.
- In Format, choose the Separator: Comma, Semicolon or Tab.
- Choose the Timezone in which the timestamps are written. The field opens on
Europe/Pariswhatever the server's own timezone is, so check it. - Click Export CSV. The button reads Generating... while the server prepares the file.
- When File ready appears, click Download file.
📘 Note: The download link is valid for 1 hour; after that, start a new export. The file is UTF-8 with BOM, so it opens correctly in Excel.
Device activity log
Separate from the history database, the server also keeps a per-device activity log: every command sent to a device and every state change it reports, with its origin — the resident and the client they used, the scenario, automation, Logic function, schedule, group, KNX bridge or webhook that caused it — and whether the device confirmed the command. It opens from the Activity button on each device row, and its recording and retention settings live on the Services → Device Activity Log page. Both are described in “Device Activity Log”.