The CAN bus showed a remote frame with ID different from the extended-address set in communication settings because zenon did not apply the configured extended address when forming the CAN identifier.
The issue has been addressed and the behavior is now as expected.
To benefit from this fix: