[RELEASE] Tuya Scene Switch TS004F driver (w/ healthStatus)

That's a shame. I saw that the 'Dimmer' mode is referenced in the driver and thought I was missing an option to switch to that.

Thanks for this driver! I have the Moes TS0044. I'm not seeing any battery being reported. Is there anything I need to do to get this?

The driver processes both 2 standard methods for battery percentage remaining reports if these are sent by the device. My remote reports the battery, but it is another manufacturer and the model is TS004F, not TS0044.

Leave the Debug option on for 24 hours and later check the logs page for your device - do you see any '' DID NOT PARSE MESSAGE" logs?

Mine shows double clicks for single pushes. Pretty annoying.

1 Like

What is your device Manufacturer value? (from the device web page Data section)

_TZ3000_vp6clf9d
thank you

I see a comment 'not tested' in the driver code.... and most probably the device fingerprint is wrong.

Can you please switch to the HE inbuilt driver named 'device' and click on the 'Get Info' button, while pressing any button on the device at the same time?

I will need the 'fingerprint' log that should be seen in the logs.

2022-10-20 16:27:07.931infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,000A,0001,0006", outClusters:"0019", model:"TS0044", manufacturer:"_TZ3000_vp6clf9d"

1 Like

ZCL version:03

dev:3762022-10-20 16:27:07.715traceSoftware Build Id:unknown

dev:3762022-10-20 16:27:07.714traceModel:TS0044

dev:3762022-10-20 16:27:07.713traceManufacturer:_TZ3000_vp6clf9d

dev:3762022-10-20 16:27:07.694traceZCL version:03

dev:3762022-10-20 16:27:07.691traceSoftware Build Id:unknown

dev:3762022-10-20 16:27:07.690traceModel:TS0044

dev:3762022-10-20 16:27:07.688traceManufacturer:_TZ3000_vp6clf9d

dev:3762022-10-20 16:27:07.641traceZCL version:03

dev:3762022-10-20 16:27:07.639traceSoftware Build Id:unknown

dev:3762022-10-20 16:27:07.638traceModel:TS0044

dev:3762022-10-20 16:27:07.637traceManufacturer:_TZ3000_vp6clf9d

dev:3762022-10-20 16:27:07.487infoZigbee parsed:[raw:catchall: 0104 0006 04 01 0040 00 DB78 01 00 0000 FD 00 00, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:04, destinationEndpoint:01, options:0040, messageType:00, dni:DB78, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:FD, direction:00, data:[00]]

dev:3762022-10-20 16:27:01.983debuggetting info for unknown Zigbee device...

Please update the driver to the dev. branch version 2.4.4 linked in the second post in this thread.

You will need to pair the scene switch again to HE, very close to the hub. This driver should be automatically selected now. If it doesn't work from the first try, try pairing it again, these devices are difficult to pair to HE.

1 Like

thank you very much.
How to update the driver please?
And how to pair it again i cant remember.
cheers

You can refer to the HE documentation - http://docs2.hubitat.com/en/how-to/install-custom-drivers

Pairing the device again - it depends on the particular model, but try pressing and holding down the bottom left key for about 7-10 seconds, until all the LEDs start to blink.

1 Like

@kkossev Is it possible to include the 3 gang model in this driver?

fingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0006", outClusters:"0019,000A", model:"TS0043", manufacturer:"_TZ3000_w8jwkczz"

image

thank you

Added in the dev. branch version 2.4.4 timeStamp "2022/10/22 8:39 PM"

Thank you. It's is working perfectly with the "Reverse button order" activated.

1 Like

Just cant get this to work. I have been messing with this for hours @kkossev , any ideas? ?

image

image

Hi @mike.rapach ,

You need to pair this scene switch very close to the HE hub. Usually, about 1 meter distance from the hub is enough to ensure that the Tuya-specific initialization during the pairing is successful.

I notice you are using a bit older version of the driver, I will recommend to update to the latest version first which will help with the troubleshooting (although the previous versions should work with your device also).

If pairing again close to the hub does not help (try at least 2 times), enable the Debug logging option and post the logs from the time when you start pairing the device to HE hub.

EDIT: I have found a bug in the previous version, please update first to the latest one :

image

Just to say I bought a single button scene switch controller in a Black Friday sale and it paired perfectly using the drivers installed via HPM. Thanks, @kkossev - I used the drivers you wrote for the Aqara P1 the other day too and they were also spot on. :+1:

1 Like

@kkossev nice job, paired my Tuya Scene Switch no problem. Then i exposed it to HomeKit, also working. Quite responsive when using scenes, a bit slower when directly actuating devices. I bet thats due to the extra interaction.

Anyway, all fine so far, but… :yum:

The battery level is shown correctly (new battery, 100%) in Hubitat but as 0% in Homekit.

I tried the same with my Lightify (Osram Smart+ mini) and that shows up correct on both Hubitat as Homekit. Can this be a driver glitch?

Using driver version 2.4.6 by the way
Tuya Scene Switch TS004F

If you go to the device web page Events, do you see any battery events registered there periodically?
TBH, I haven't tested my TS004F switch and rotary button in Homekit yet.