Known Issues

Tracking of known problems, workarounds and fix status across versions.

Active Issues

No known active issues on the latest version (26.03).

Issue	Affected Versions	Fixed in	Workaround
.NET 8 install triggers data corruption on ARM architectures	25.02	25.03	No workaround available
DOMService synchronization sometimes stuck	24.07	24.10	In DOMPloy 12.0: click the Offline tab
Online coupling stuck in "coupling" state	22.12	23.03	Open RFNM settings → "route devices" tab → submit again
Battery replacement not always detected	23.07	23.10	No workaround available

DOMController proactively works around known issues in third-party components it depends on.

Issue	Component	Handled since
Backup file corruption on affected MariaDB versions (10.5.25, 10.6.18, 10.11.8, 11.0.6, 11.1.5, 11.2.4, 11.4.2)	MariaDB	25.04

FIXED

Affected versions: 25.02
Fixed in: 25.03

Description: Installing .NET 8 on the standard (ARM) DOMController triggers data corruption in the services.

Workaround: No workaround available. Upgrading to version 25.03, which completes the migration to .NET 8, is recommended.

FIXED

Affected versions: 24.07
Fixed in: 24.10

Description: Synchronization with the DOMService application could randomly get stuck.

Workaround: A workaround is available in DOMPloy 12.0 by clicking on the "Offline" tab.

FIXED

Affected versions: 22.12
Fixed in: 23.03

Description: Online coupling could sometimes get stuck indefinitely with the device remaining in "coupling" state.

Workaround: Open RFNM settings → go to the "route devices" tab → submit the configuration again.

FIXED

Affected versions: 23.07
Fixed in: 23.10

Description: Battery replacement was not always correctly detected and stored.

Workaround: No workaround available. Upgrading to version 23.10 is recommended.