I probably understand the problem.
I removed all the drivers, the DHs and the device, then I installed your version 1.3.0 and re-paired the device which is now recognized as a “scene switch” and works correctly.
So I think the problem is that during the first pairing I used the @zambobmaz driver, and that simply replacing it with yours is not enough.
I think the correct procedure is to remove the device and re-pair and bind the correct driver from 0 instead a simplu driver exchange
Finally, after a heavy sprint on my job I’ve been able to check this once more time and when I was about to consolidate my driver versions I noticed something quite important regarding the fingerprint you shared, see below:
As you can see, the manufacturer is simply TZ3000_wkai4ga5, without the initial underscore, as it happens with all the other tuya fingerprints I’ve pushed so far into the repo (for a better reference, check here), so, I believe that it should be as follows:
I’ll submit the update at the battery-button-v1.3.1 version under the @erickv Shared Drivers in case you’re able/willing to test it out.
I was reviewing the fingerprints that my button-battery driver supports and noticed that it is already supporting the 3-Button Loratap Remote, so, I’ve added the fingerprint you shared and you can install the driver enrolling to the following channel:
(Note: to make an effective installation, you might need to delete the DTH from your setup.)
I found that model really interesting, so, I might get one of those soon = P.
I added the fingerprint at the button-battery-v1.3.1 from the @erickv Shared Drivers channel, but I’m not sure that every feature will work as expected, especially the built-in dimmer, but I have high hopes that the button will report acordingly.
However, it would be great if you could share with me in a PM a set of logs while interacting with the device (dimmer and button), just to check if reports button events as expected and how dimmer events are generated.
Logs can be tracked through the SmartThings CLI with this command:
At this point I’m quite confident that my driver can handle the 4 Moes models so, if you’re able to share the fingerprint at this thread, I can add support for it and will notify you as soon as posible =]
Thank Erick. I live in the UK and can only find the Moes Wifi single gang switch (not the zigbee one) so before I can order the Wifi switch, can you let me know what a fingerprint is? I am not a developer so excuse my ignorance.