Skip to content

Version 25.02

June 2025 · API v30

New Features

  • Officially supports the new DOM Online Mesh products (please contact us for more details).
  • Week/day schedules can now be set per device instead of system-wide, allowing for more flexibility.
  • OSS dynamic validity can now be set in terms of weeks, months or years.
  • It is now possible to assign different key numbers when configuring OSS (out of the standard).
  • Using the OSS Updater, the timeout for transponder read/write is now configurable.

Set transponder timeout with OSS Updater

  • PackId configuration can be defined globally to the site (still possible to override it per door).
  • DOMController can be updated through the API instead of SSH (though it is longer and only for fallback).
  • Devices can now be discovered directly via their IP address.

Discover devices via IP Discover devices via IP

  • A "Name" field is now available for devices in the DOM Service app, and connections to DOMControllers can be saved.

Name field for device Name field for device Name field for device, alternate view Saved connections

  • Redesigned OSS configuration screen.

OSS configuration OSS configuration

Fixes

  • Changing a user's password no longer deactivates the account.
  • Daylight Saving Time is now better managed when having more than 3 years of old dates.
  • Mobile keys based on OSS model can now be used with no actual OSS configuration in the doors.
  • When blacklisting an OSS transponder, it had one last access before the blacklist was actually pushed — fixed.
  • WebSocket connections are now limited to 10. An error 429 "Too Many Requests" is raised when trying to connect an 11th one.

Known Issues

Major issue with .NET 8 installed: this triggers data corruption in the services on ARM architectures (standard DOMController).

Fixed in: 25.03, which completes the migration to .NET 8.

Download

Files are hosted on the DOM Security SharePoint (sign-in required): DOMConnect v.25.02 folder, which also holds the manuals and changelogs of this release.

Target File Size
DOMPloy — Windows deployment tool DOMPloy_Setup_6.0.0.1815.exe 71 MB
DOMController (ARM) DOMConnect_25.02.02.2070_arm.enc + .sig 143 MB
DOMController Premium (VM / x86) DOMConnect_25.02.02.2070_x86.enc + .sig 147 MB
DOM Online Mesh — T2BLE package 1.8.2 T2BLE-TBR-1.8.2.ipk + signature 2.3 MB
DOM Online Mesh — T2BLE firmware 1.8.2 t2ble_1.8.2.bin 611 KB
BLE dongle driver (Windows) dfu.inf 6 KB

Start with DOMPloy: install it on a Windows machine, then use it to push the .enc package matching your controller. The .enc/.sig pair is not meant to be installed manually.

The BLE dongle driver is required for BLE dongles on this release. It is a set of files (.inf/.cat + coinstallers) that must be installed together, not just the .inf linked above.