[Edge migration] Device migrated to a stock driver doesn't work correctly

The Zigbee Switch driver has some generic fingerprints that check clusters supported by the device and that could have made the driver eligible for this device.
If the device was using a Community-Created DTH, it would match with the process described in this announcement: Next Steps for Community-Created Groovy Integrations

If the device doesn’t work with the stock driver, we would need to see if it’s because it needs a special configuration (which is not included because the device is not certified) or if the basic configuration for a generically supported device doesn’t work correctly.
For that, we need your help to get the driver logs when you send the event to turn on the kitchen strip to see if there’s an error exposed there.