Normally is due to device pairng with a custom dth or generic fingerprint.
I would have to add the generic fingerprint and then anyone who does not want to use the driver on some switch, would have to uninstall the switches paired to the driver and remove the driver.
If your switch paired with de DTH zigbe switch power stock, normally is due to device pairng with a generic fingerprint.
I would have to add the generic fingerprint to driver but then anyone who does not want to use the driver on some switch, would have to uninstall the switches paired to the driver and remove the driver.
As I understand it, the multi gang tuya switches use the proprietary EF00 cluster to manage the extra gangs and so need custom code. The stock multigang Zigbee switch DTH doesn’t work with them.
The only thing that creates some problems is the dynamic change of the icon, in the sense that sometimes it goes back to the old profile then changes again.
Also you should edit the profiles within the “Zigbee Light Multifunction Mc” driver for these devices that I have and they work fine
ST motion and plug are still pairing with stock dth.
Ecolink pairs and works with exception of battery data.
TS0001 paired as a “thing” as it did originally and has to change to ZigBee switch in IDE and did work as intended on the stock dth.
Mmm…I haven’t seen comments about issues pairing Sonoff devices from other devs, but it could be the case for the _TX3000_hktqahrq manufacturer
But @Paul_Oliver, please verify the fingerprint values of both devices in the Hub events when the device is paired.
Got to the IDE and select “My Hubs”
Tap on “List Events” (it is the penultimate option in the table)
The paint event is before the “deviceAdd” event. Eg.
@nayelyz,
I do not quite understand what is happening so there are more problems to match the drives when the devices have full or generic fingerprints in DTH Stokcs.
The ST motion sensor motionv5 is in the dth stock smartsense motion sensor