As far as I know, some of the solar panel or battery powered devices don’t report their shade status or position status correctly.
These values should be displayed correctly while moving via both, APP and Remote Control.
I made this work with those exact shade motors.
I had to go on iquix GitHub, download his code. Then I added my finger print to that file, then uploaded it to my own hub via the CLI.
A little research on how to use the CLI and it works great.
You do get shade status. Just not battery level.
If iquix adds the finger print, his driver will work.
@iquix I’ve been using your test driver the status and position are working fine with it.
I was asking if it was possible to add battery and light sensor information in addition to those that already work.
Anyway, thanks a lot for the driver.
@Weboperations, thanks for the tip.
I didn’t need to download the driver from github. I added it from the web like others for testing and it worked great.
But I will try to download it and find a way to add the battery level and light sensor.
Maybe I have some luck.
I have a battery powered tuya zigbee motor in my home, but battery power is not displayed even in the tuya smartlife app.
There’s physically no way make the battery displayed, when the device is originally not designed to send battery packets.
I’ve added _TZE200_zah67ekd to the driver, as well as generic zigbeeThing.
You don’t need Tuya Window Shade for Devices NOT TESTED driver anymore, and this will be removed from my channel.
You can apply Tuya Window Shade driver to any zigbee devices.
Thanks changing to Tuya Window Shade
Can you please explain how to replace ? I have this module as well. @iquix , did you add this curtain motor fingerprint to your driver ?
Ensure you have the generic zigbee “thing” driver installed from the smartthings edge beta channel Smartthings Edge Beta. Pair the motor and it should default to “thing” edge driver. If you have a custom groovy DTH that matches the motor, you might need to delete the DTH to ensure that it defaults to the “thing” edge driver.
From there change the driver to “Tuya Window Shade”. This driver can be applied to any zigbee device and needs no matching fingerprint.
Guys, how do I get this to work with the smart things app and aeotec hub? my steps are:
I’ve seen comments regarding click the 3 dots and changing the drivers. I don’t have this option in the IOs smarthing app.
I’m at a loss 
This is because it is paired with DTH thing.
You need to install Zigbee Thing driver from Official SmartThings Beta Edge channel.
Then you may delete and re-pair with the device, and it will paired with Edge Zigbee Thing. Then you can change the driver.
@nayelyz,
Since Groovy has been shut down, zigbee thing driver in the beta chennel should be moved to production channel.
If a new device is paired with DTH thing, there’s no way to use the device, because installing DTH is no longer available. This is what happens if a new device is paired with DTH Thing: cannot do anything with this.
@iquix do you have a link please? I end up searching hundreds of website.
OK. I think we are connected, but when I now go to the smartthing app and shade to open and close. There are no options. Just says status connected
its working 
Hi, @mrbradley1. Did it end up using a DTH or a driver? You mentioned above that the option to change the driver didn’t appear, is that still the case and have you changed the DTH assigned from the IDE to get it working?
Hi, @iquix, thanks for tagging me!
The part of DTHs hasn’t been shut down, only Groovy SmartApps. There are still some devices that cannot connect with drivers by default so, they (DTHs) are still part of the onboarding process.
I’ll check with the team details about the priority to see if there’s something we can do.
What I mean by groovy shut down is that it is impossible to install NEW custom DTH.
I agree that there’s no problem with groovy when the device is paired with the appropriate built-in DTH. I know not all WWST DTHs are ported to Edge drivers.
However, when it comes to the Thing, it means there’s no matching built-in DTH/Edge, nor already installed custom DTH, nor custom Edge driver which is installed on the hub.
Since we cannot install NEW custom DTHs at this point, there’s nothing we can do with this groovy Thing device.
I think Thing should be migrated into Edge Thing, so that the Edge driver could be applied when appropriate driver is installed AFTER pairing of the device.
Ok, after discussing this with the team, this is happening because of the priority order to find a compatible handler.
Searching on the stock DTHs (those published by SmartThings) are checked first than drivers with generic fingerprints (that includes the ones of Zigbee/Z-Wave thing).
So, for now, people need to install a driver with generic fingerprints or with the manufacturer’s fingerprints to connect their devices to one when there’s no compatible stock driver in the default channel (one with the manufacturer’s fingerprints).
This will change later on when the migration is finished. For now, as the Zigbee Thing DTH falls in the category I mentioned above and we cannot exclude single DTHs from the process, this is the expected behavior.
Can you describe how you got it working? I’m also just seeing the “connected” message and no controls
