@aren I think that with a few more iterations we should get it working...
The first problem to solve is to match the correct driver during the pairing process, I see now why my driver fingerprint was not matching - the inClusters list of your device is "0003,0004,0005,0006,0702,0B04,E000,E001,0000", while my device is "0000,0003,0004,0005,0006,0702,0B04,E000,E001". It is one and the same set of clusters, but the two different devices report and HE stores them in a different order. So the simple inClusters string comparison fails. Although the above does not explain why Markus 'Zigbee - Xiaomi/Aqara Motion Sensor' driver is selected instead, the fingerprints there are very different than this Tuya plug...
Just to be sure, can you temporarily change the Tuya plug driver to a "Device" type?
Then press the "Get Info" button, copy/paste the text logs for and send the text to me.
Should look like this:
dev:12932021-12-25 16:09:37.293 infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0003,0004,0005,0006,0702,0B04,E000,E001", outClusters:"0019,000A", model:"TS011F", manufacturer:"_TZ3000_cphmq0q7"
dev:12932021-12-25 16:09:37.197 traceZCL version:03
dev:12932021-12-25 16:09:37.193 traceSoftware Build Id:unknown
dev:12932021-12-25 16:09:37.188 traceModel:TS011F
dev:12932021-12-25 16:09:37.184 traceManufacturer:_TZ3000_cphmq0q7
dev:12932021-12-25 16:09:36.968 debuggetting info for unknown Zigbee device...
The second problem is that most probably the switch on/off commands are sent to the wrong endpoint/ProfileID (the Zigbee 3.0 'Green Power')... This could be detected and prevented in a future driver version, but I hope that once the correct driver is picked up during the initial pairing process, it will start working OK. At least this was the solution for a similar Tuya plug a month ago.