Changelog

1.5.0

2026-10-14

Highlights

Companion 1.5.0 can now connect to crawlers on networks where automatic discovery does not work: crawlers running Edge 2.24.0 or later can be added to the crawler list manually by IP address or hostname. Restoring measurement data now pauses data acquisition automatically on crawlers running Edge 2.24.0 or later and resumes it afterwards — previously a manual step. In addition, the version fixes several issues around export and backup — run export is available again on crawlers that require a login, the dataset link of a Deepview export is preserved, and measurement data backups are checked for faulty checksums while they are being created. Failures during backups, restores, updates, and network changes are now also reported when the respective page has been left in the meantime. Empty exports are also no longer uploaded to Deepview, and Companion no longer stays locked in “updating” after an update. Deepview now opens at the new address deepview.invisyne.com.

New Features

Add crawlers by IP address or hostname (requires Edge 2.24.0 or later) — A crawler running Edge 2.24.0 or later can now be added to the crawler list directly by its IP address or hostname. Older crawlers cannot be added by address and have to be updated first; they continue to be found by automatic discovery on the network. This helps on networks where automatic discovery does not work — segmented networks (VLANs), switches or WLAN controllers that suppress broadcasts, routed subnets, or access over VPN. In those cases the crawler list previously stayed empty, leaving no Companion feature usable — even though the devices themselves could be addressed and only automatic discovery failed to find them. Manually added crawlers behave like automatically discovered ones: monitoring, updates, network configuration, backup and restore, and export are available unchanged, and name, network interfaces, and device status are reported by the device itself. The entries survive an application restart and can be removed again at any time. A crawler that is also found by automatic discovery appears only once in the list.
Data acquisition is paused automatically (requires Edge 2.24.0 or later) — When restoring measurement data, it previously had to be ensured manually that data acquisition on the crawler was not running at the same time — otherwise the restore competed with the ongoing writes. That step is gone: Companion now pauses acquisition itself for the duration of the restore and resumes it automatically afterwards. Even if the connection drops during the operation or the application is closed, acquisition on the device restarts by itself after a short while — no device is left without running acquisition. On crawlers running an older Edge version, acquisition still has to be paused manually as before. Backing up measurement data needs no such pause, as before: acquisition keeps running unchanged.
Deepview at a new address — The “Open in Deepview” button now leads to deepview.invisyne.com. Previously shared dataset links remain valid and are redirected to the new address automatically; older Companion versions keep working unchanged.

Bug Fixes

Notice when a crawler has been reset to factory settings — After a reset to factory settings, a crawler returns to its default IP address and is therefore usually no longer reachable. Actions in Companion then failed without any discernible reason — restoring a saved configuration was not possible either. Companion now recognises this state: the affected areas — updates, backup, and export — are disabled and state the reason, and the device’s details page points out that the crawler has to be set up again.
Run export available on crawlers that require a login — On crawlers that require a login, the switch to run export was disabled, with the misleading notice that the crawler does not support runs. The cause was a check performed before any login, whose failure was interpreted as a missing feature — so depending on whether credentials were stored on the machine, run export worked sometimes and sometimes not. Whether a crawler supports runs is now determined from its software version; if the login is missing, Companion asks for it when switching to run export or when retrieving runs, instead of disabling the feature. In addition, the lock icon on the details page now reflects the actual authentication state, even when it changes in the background.
Deepview export: the dataset link is preserved — During an export to Deepview, Companion waits for the data to be processed on the server after the upload. If the export page was left during that time, the result was lost: after returning, the processing progress was missing, and once finished the “Open in Deepview” button was no longer available — the dataset had to be located in Deepview manually. Progress and result of a running export are now preserved and continue to be shown when returning to the export page.
Measurement data backup: checksums are verified while the backup is created — With large amounts of data, measurement data backups occasionally contained faulty checksums. The data packages are now verified while the backup is being created, so a faulty backup is detected immediately.
Failures of running operations are reliably reported — Backups, restores, updates, and network configuration changes keep running on the crawler even when the corresponding page in Companion is left. If an error occurred in the meantime, it was previously not shown at all or only for a few seconds — for backup and restore, possibly even against the wrong device. Failures are now always reported: if the affected page is open, the message appears right there; otherwise a notice is shown, and the affected crawler in the crawler list as well as the corresponding menu item are marked.
Exporting empty runs: no more empty datasets in Deepview — When a run without measurement data was exported to Deepview, Companion uploaded an empty dataset and then offered the “Open in Deepview” button — with no indication that the export contained no data; the link led nowhere. An export without data is now no longer uploaded; instead, Companion points out that the selected runs or the selected time range contain no data. The same applies to the CSV export, which previously produced a file containing only column headers. In addition, the link to Deepview is only shown once processing on the server has finished successfully.
Companion no longer stays locked in “updating” after an update — After a successful installation, Companion could fail to recognise that the update had finished: the progress bar stopped moving, the “Confirm” button did not respond, and export and network configuration stayed locked for the rest of the session — clicking the crawler always led back to the update page. The device itself was updated correctly. Companion now reliably recognises the end of the installation, and “Confirm” always releases the remaining functions again.

Prerequisites

Adding a crawler by IP address or hostname requires a crawler running Edge 2.24.0 or later. Older crawlers have to be updated first; they continue to be found by automatic discovery on the network.
Pausing data acquisition automatically while measurement data is restored requires a crawler running Edge 2.24.0 or later. On older crawlers, acquisition still has to be paused manually as before.
Run export requires a crawler running Edge 2.21.0 or later.

1.4.0

2026-08-03

Highlights

Companion 1.4.0 brings backup and restore directly into the app: both a crawler’s configuration and its measurement data can be backed up, downloaded as a file, and later restored to a device. In addition, the reliability of device discovery on the network has been improved.

New Features

Back up and restore configuration — A crawler’s configuration – name, network settings, Grafana dashboards, Node-Red flows, and the structure database – can be backed up directly from Companion. The full configuration or only selected components can be included. The backup is downloaded as a file and can later be restored to a device – for example after a hardware replacement, a migration, or a device failure. A progress bar shows the progress, and running operations can be cancelled.
Back up and restore measurement data — A crawler’s recorded measurement data can be backed up for a selectable time range and downloaded as a file. A saved backup can then be restored to a device. The backup process does not interfere with ongoing measurement data acquisition. A progress bar shows the progress of the backup and restore operations.

Bug Fixes

More stable device discovery on the network — Crawlers that shared one of their default IP addresses with another device on the network were previously detected briefly and then repeatedly grayed out. Companion now verifies a crawler’s reachability specifically through the network interface on which its response was received, and confirms the device’s identity in the process. As a result, the display stays stable even when IP addresses are assigned more than once on the network.

Prerequisites

Backup and restore require a crawler running Edge 2.23.0 or later.

1.3.0

2026-06-29

Highlights

Companion 1.3.0 adds compatibility with Edge 2.22, which introduces an additional security layer for all device services. From this version on, configuration changes on an Edge device require a login with the device password. Companion prompts for these credentials through a login dialog when needed and can store them per crawler in the local credential store (OS keyring).

New Features

Compatibility with Edge 2.22 — Companion now connects correctly to Edge devices running version 2.22 or later. All device communication, including firmware and software updates, works correctly with the new security configuration.
Login for configuration changes — Edge devices running version 2.22 or later require a login before configuration changes can be made. Companion shows a login dialog whenever a protected action is performed. The relevant credential is the Edge device password — not the Hub login. Credentials can be saved per crawler in the operating system’s local credential store (OS keyring), so the login is not required again for every action.

Prerequisites

Edge devices running firmware 2.22.0 or later require Companion 1.3.0 or later.
Configuration changes on an Edge device require the password of the respective device.
Network settings of an already configured crawler (version 2.22 or later) can only be changed while the crawler is reachable over the network. If it is unreachable, network changes are only possible again after a factory reset.

1.2.0

2026-06-24

Highlights

Version 1.2.0 enables optional login via Invisyne Hub for use with Deepview and stores session data securely on the local machine. Runs can now be uploaded to a Deepview workspace and analysed there. A display error on the updater page for failed updates has also been fixed.

New Features

Hub Login — Login is performed using Hub credentials. The login page follows the Hub design. Login credentials are stored locally in encrypted form, so they are retained when the application is reopened.
Deepview Integration — Runs and time-period based data exports can be uploaded directly from Companion into the customer’s own Deepview workspace.

Bug Fixes

Updater page showed incorrect success status — After a failed crawler update, the updater page incorrectly displayed “successful” while the main view correctly showed the failure. The status is now displayed consistently across both views.

Requirements

A Deepview subscription is required for the Deepview integration.

1.1.0

2026-04-16

Highlights

Version 1.1.0 adds a run data export to Companion: measurement data can be downloaded as a CSV file over a defined time period.

New Features

Run Data Export — Measurement data can be downloaded as a CSV file via a new run export.
New CSV Export Format — All CSV exports (run export and timeframe export) use a unified wide-table format from version 1.1.0 onwards: one time column followed by one column per configured measurement data point. Two header rows — one with short names and one with the full data point path — allow unambiguous identification of identically named data points. The column separator is ”;”, the decimal separator is ”.”. The format is optimised for direct use in Excel. The timeframe export no longer splits output across multiple files — all data is written to a single file.

Bug Fixes

None.

Requirements

Runs are only available on Crawlers running version 2.21 or later.

1.0.2

2026-03-27

Highlights

First release of Invisyne Companion — a Windows desktop application for local management of Invisyne Edge devices on the network. Devices on the same local network are automatically discovered and displayed in a unified device list.

New Features

Device Discovery — Automatic search and listing of all Invisyne Edge devices on the same local network. Devices can be found and identified without manual IP entry.
Local Management — Network parameters (IP address, DNS, gateway) can be set directly. Live status and technical device data are accessible; direct navigation to the device’s WebUI is available.
Firmware & Software Updates — Firmware and software updates can be installed directly on Edge devices.
Measurement Data Export — Configured measurement data points can be exported as CSV over a selectable timeframe. If the export timeframe exceeds the configurable maximum file duration, multiple files are created automatically. The CSV files use a custom format with time, signal, and value columns.

Bug Fixes

Device Discovery on All Network Adapters — Crawlers were not reliably discovered on systems with multiple network adapters. Discovery now runs stably on all available adapters without Windows Firewall conflicts.

Requirements

Requirement	Details
Operating System	Windows 10, 11
Network	PC must be physically on the same network as the Edge device
Compatibility	Crawler version 2.18 or later required for the updater and full network configuration