Skip to content

Profinity 2.2.5 release notes

The major change in this release is that the data folder moves from the Documents folder to the AppData folder on Windows, which improves reliability for users who have their home directory stored in OneDrive. The release also improves upgrade safety and reliability for desktop, Docker, and CAN adapter deployments, and surfaces dashboard and configuration errors earlier through stricter schema validation.

Changes in this release

  • Profinity's default artefacts directory moved to the operating system's application-data location, with automatic migration from the old locations.
  • Windows installer sample and profile content updated to match the new default location.
  • Improved reliability and diagnostics in the desktop application and for CAN adapter connections.
  • Stricter dashboard validation and updates to bundled dashboards and DBC (CAN database) handling.

Installation and data locations

New default artefact location

Profinity stores its artefacts in the operating system's local application data folder, under Prohelion/Profinity. This includes the Config/ and Profiles/ folders, logs, and other saved artefacts. Profinity 2.3 renames these folders to lowercase. Refer to the Profinity 2.3 release notes.

Automatic migration from legacy locations

On startup, Profinity migrates an older Prohelion/Profinity folder into the new location when that folder contains Config/Config.yaml, moving or merging its files into the new location, depending on what the new location already holds.

Upgrade guidance:

  • If you have automation or backups that reference legacy paths (for example "Documents" or home-based paths), update them to the new location.
  • If you maintain custom profiles/config files, ensure you have a backup before upgrading.

Docker

On Linux, Profinity 2.2.5 stores its data under $XDG_DATA_HOME when that variable is set and under $HOME/.local/share otherwise, so a root container with no overrides uses /root/.local/share/Prohelion/Profinity/. Existing Docker Compose mounts that target /root/Prohelion/Profinity/... keep working in 2.2.5 when you set XDG_DATA_HOME=/root and keep your volume mappings. Profinity 2.3 on Linux ignores XDG_DATA_HOME and uses /var/lib/prohelion/profinity unless PROFINITY_HOME is set, so Docker users who move on to 2.3 should follow Upgrade from Profinity 2.2.

Dashboards

  • Dashboard examples and templates were refreshed to match the dashboard schema validation rules.
  • Validation of dashboards, schemas, and DBC files is stricter, so invalid content is reported when Profinity loads it rather than failing later at runtime.

If you maintain custom dashboards, validate them against the current schema and review any schema error messages during load.

CAN and adapters

  • Improved handling of connection edge cases including an adapter that is connected but sees no CAN traffic, which Profinity now reports as a warning rather than an error.
  • Virtual CAN adapters no longer try to connect when the required network capabilities are missing.
  • Ewert Energy CANdapter adapter reliability improvements:
  • Serial port selection is more reliable (handles COM port case differences such as com3 and COM3).
  • When no port is configured, Profinity scans the serial ports for a connected CANdapter for a limited time instead of failing with an unusable adapter.
  • When no device is detected, the settings page shows a warning and hides the empty fields until a CANdapter is available.
  • Improved error messages when the selected serial port is missing or invalid.

Desktop GUI stability

  • Cleanup of the desktop application's embedded browser (WebView2) was hardened during reload and shutdown, which reduces the chance that shutdown is blocked.

Battery Management Systems (BMS)

  • Updates across Prohelion D1000Gen1 BMS components and bundled DBC content to address issues found in the field, including engagement, heartbeat, and state machine improvements.