Trust/KlikaanUit fire not working

[enboer]

Does the issue really belong here?

• I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this?

• I have searched the existing issues and there is none for the bug at hand

Describe the bug

I updated to deconz 2.32.5 and have an issue that my klikaanuit fire alarm does not work. I had ir running with the attached .ddf file. Any idea what is wrong.
Without this .ddf the device is not recognized, only as ZSDR-850

zsdr-850.json

Steps to reproduce the behavior

Add the device,
it reads the .ddf file.
But if there is a alarm (test button pressed) not notification in Domoticz

Expected behavior

When the button is pressed in previous releases my notifcation was sent. Now nothing happens. Did rejoining the network but no luck.

Screenshots

No response

Environment

• Host system: (Raspberry Pi / PC / NAS / MAC)
• Running method: (Raspbian / Ubuntu / Home Assistent deCONZ Add-on / deconz-docker container / Windows / Virtual Machine)
• Firmware version: (26xxyy00)
• deCONZ version (not Home assistant Addon version!): (2.xx.yy)
• Device: (ConBee I / ConBee II / ConBee III / RaspBee I / RaspBee II)
• Do you use an USB extension cable: (yes / no) -- only relevant for ConBee I/II/III
• Is there any other USB or serial devices connected to the host system? If so: Which?

deCONZ Logs

No response

Additional context

No response

[mattreim]

Since the device is not yet officially supported, I would like to ask you to open a device request.

[enboer]

Just after reporting the issue the devices works now again, not sure why. Maybe it takes time to enroll a IAS Zone as I now see 'enrolled' ?

[mattreim]

Yes, it always takes a while after a restart for all devices to be registered. Since the device isn't yet supported, your DDF might be incorrect. For example, is the firmware displayed correctly?