Zigbee4Domoticz. Provisioning IKEA E1603 wallsocked

[jpmd]

I have a fresh installation of Raspberry Pi with Domoticz and the Zigbee4domoticz plugin.
I was able to connect a doorsensor via the Zigbee4domoticz web interface.
Unfortunately, the connection with the IKEA-E1603-wall-socket isn't working properly.
During provisioning, the website doesn't show that the connection has been established. After canceling the provisioning,
I exported the "Raw Devices plugin." See the attached file (uploaded as a .txt but it is a .json file). You can see the E1603 in it, so zigbee4domoticz has seen it.
Even though the ZigBee4Domoticz website doesn't indicate that the E1603 has been detected, a device switch has been created in Domoticz.
However, when I click on it, the physical wall socket doesn't respond, and the value in the device changes from "Off" to "99%." Strange.

Schermafbeelding 2025-10-28 164715.jpg (9.3 KiB) Viewed 68 times

Schermafbeelding 2025-10-28 164642.jpg (12.04 KiB) Viewed 68 times

There are no errors shown in Domotics-log and not in the Zigbee4domoticz website.

Does anyone know what's wrong?

[gizmocuz]

Seems you switched from an old Zigbee2MQTT python script to Zigbee4Domoticz.
Why not use Zigbee2MQTT natively without Python (Just install it as docker compose) and use the MQTT Auto Discovery hardware to work together?

https://wiki.domoticz.com/Zigbee2MQTT

If you start from scratch, do I recommend this path

[waltervl]

Ignore @gizmocuz on this. People are still free to choose what they want....
It seems something went wrong during pairing.
Try to delete the device from Domoticz. If more Domoticz devices are created from this zigbee node they need to be deleted too in Domoticz. It should also delete the device from Zigbee for Domoticz (check the webgui of Z4D menu device management on port 9440).
If not deleted from Z4D you should be able to see a delete option for this device on the device management page. Delete it from here too and try to pair it again.

[jpmd]

Deleting device did not help.
I'v switched back to zigbee2MQTT and there is provisioning with E1603 no problem.