[Release] Tuya/Lonsonho 1-gang and 2-gang zigbee dimmer module driver

not working at all. I hope my wiring was right. will get some drawing post early next week
when I said 3 way switch, I meant there are 3 switches at 3 locations with one being an intermediate switch.

Hello @silvermane, buttering up is always welcome. I have looked now at the thread you indicated. The proprietary messages for those switches is sufficiently different that it really needs it's own separate driver - so the better course of action is for someone with access to the device to do the modifications that @CPS suggested. I'm afraid without having one to test with it is not practical to try to write and debug the code for such a set of changes.

Fair enough @fc352bf0a6929e9fa80f . For me it's a chicken or egg story: If I had the skills to make the modifications I'd get the device for sure. And maybe if I had the device already I would try to see if I could upskill to edit the driver :smiley:
As it stands though, it's neither and as such it's too much of a risky proposition.
Thanks for looking into it though!

I've followed @ugm2byww and joined team @fc352bf0a6929e9fa80f after all :smiley:
After some deeper digging on Ali, I was able to score the Lonsonho 2-gang dimmers for almost the same price as the Moes ones.

Looking forward to using your drivers @fc352bf0a6929e9fa80f, Thx in advance!

Hey Matt @fc352bf0a6929e9fa80f, I fiiiinally received my 2 gang dimmer modules and installed your driver via HPM but for some reason it's not creating the child devices even though I've hit configure after it was picked up by HE and I selected your driver for the device... :thinking::thinking:

Any chance you'd be able to help out?

  • endpointId: 01
  • application: 41
  • softwareBuild:
  • inClusters: 0000,0004,0005,0003,0006,0008
  • outClusters: 0019,000A
  • model: TS1101
  • manufacturer: _TZ3000_7ysdnebc
1 Like

Ok, based on what I was able to quickly understand from some of the previous stuff, I just added:

"_TZ3000_7ysdnebc": [
numEps: 2,
joinName: "Tuya Zigbee 2-Gang Dimmer module"

to the driver and it is now creating the 2 child instances but it is not showing any device state for the child devices when I try to turn them on/off.
Probably too optimistic on my part to think that that would be all it would take :joy:
I'll try to get my head around the driver some more but my limited coding days are 20 years behind me so appreciate if you could still help out Matt :wink:

Ok, nvm... mental note to self: don't wake up all excited about setting up your new toys with only 4 hours of sleep! :smiley:
If you forget to actually turn on the device again after you switched it off because you were doing some extra wiring, then of course the child device isn't going to display any status! :sweat_smile:

FWIW (don't know if it was necessary) but I also changed the driver to

modelConfigs.each{ data ->
fingerprint profileId: "0104",
inClusters: "0000,0004,0005,0003,0006,0008",
outClusters:"0019,000A",
model:"TS1101",
manufacturer: data.key,
deviceJoinName: data.value.joinName

Might not have been necessary though, feeding the switch some power is what really did the trick! :joy:

1 Like

Glad you got it working! I'll add the device fingerprint your supplied. Probably not until after the weekend though. Either way, shouldn't affect you. I might also tweak it to match the fingerprint more closely as per your last post.

1 Like

Hey @fc352bf0a6929e9fa80f, you wouldn't happen to know the reset procedure for these dimmers would you?
it would typically be a number of on/off actions but the provided booklet only mentions holding the physical reset button for 10 seconds.
Unfortunately one of the 6 that I installed I can't get to that easily and as luck would have it that is of course the one that has dropped of the grid... :frowning:

UPDATE: actually, I might not need to reset the device after all as it turns out it is still being seen by HE. I believe it might be an issue with the child devices instead. I can still control the dimmer from the parent device but turning that on/off only turns on/off the first child device.
I can't however turn the child devices on/off from within the child device. Which is especially weird for the first child device as that gets turned on/off from the parent :thinking::thinking:

This is what I get while trying to turn on CH01 (without anything actually happening):
dev:11082021-12-13 08:52:06.877 pm debugSending actions: [he cmd 0x753C 0xnull 0x0006 1 {}]

And this is what I get on CH01 and Ch02 when I hit configure and refresh:
dev:11082021-12-13 08:59:55.728 pm debugSending actions: [he rattr 0x753C 0xnull 0x0006 0 {}, delay 100, he rattr 0x753C 0xnull 0x0008 0 {}, delay 100]

dev:11082021-12-13 08:59:52.199 pm debugSending actions: [he rattr 0x753C 0xnull 0x0006 0 {}, delay 100, he rattr 0x753C 0xnull 0x0008 0 {}, delay 100]

dev:11102021-12-13 08:59:49.212 pm debug[label:Tuya Zigbee dimmer module (CH02), componentName:ch02, componentLabel:Channel 02, completedSetup:true, isComponent:true]

dev:11092021-12-13 08:59:41.398 pm debug[label:Tuya Zigbee dimmer module (CH01), componentName:ch01, componentLabel:Channel 01, completedSetup:true, isComponent:true]

That looks pretty normal as far as I can tell.

Hitting configure and then refresh on the parent device is a different story though:
dev:11082021-12-13 09:02:55.204 pm errorjava.lang.NullPointerException: Cannot invoke method onSwitchLevel() on null object on line 418 (method parse)

dev:11082021-12-13 09:02:55.198 pm debugReceived parsed: [raw:753C0100080A00002000, dni:753C, endpoint:01, cluster:0008, size:0A, attrId:0000, encoding:20, command:01, value:00, clusterInt:8, attrInt:0]

dev:11082021-12-13 09:02:55.195 pm infoReceived raw: read attr - raw: 753C0100080A00002000, dni: 753C, endpoint: 01, cluster: 0008, size: 0A, attrId: 0000, encoding: 20, command: 01, value: 00

dev:11082021-12-13 09:02:55.137 pm errorjava.lang.NullPointerException: Cannot invoke method onSwitchState() on null object on line 409 (method parse)

dev:11082021-12-13 09:02:55.130 pm debugReceived parsed: [raw:753C0100060A00001001, dni:753C, endpoint:01, cluster:0006, size:0A, attrId:0000, encoding:10, command:01, value:01, clusterInt:6, attrInt:0]

dev:11082021-12-13 09:02:55.127 pm infoReceived raw: read attr - raw: 753C0100060A00001001, dni: 753C, endpoint: 01, cluster: 0006, size: 0A, attrId: 0000, encoding: 10, command: 01, value: 01

dev:11082021-12-13 09:02:52.756 pm debug[model:TS1101, application:41, manufacturer:_TZ3000_7ysdnebc]

I have a similar problem. Once for a few months the driver stops working and I have to remove and add all child devices to start working again. In logs I have "Cannot invoke method onSwitchState() on null object on line 409 (method parse)"

Hi! First of all, thanks for the effort and drivers.

Im having a problem with a 2 gang Moes Smart Switch Module (with neutral). I believe the device fingerprint is not recognized by the drivers. Whenever i discover one of this devidces, HE sets it as "Generic Zigbee Multi-Endpoint Switch" and i'm only able to turn on or off the lights but i cant not use the dimer functionality.

My devices foodrpint are:

  • endpointId: 01
  • model: TS011F (note that its differenf from the "TS110F")
  • application: 43
  • isMultiEP: true
  • manufacturer: _TZ3000_pmz6mjyu

I would be more than thankfull if you could help me. Thanks!

Matt's driver may be the right one for your device, but It does not contain your device fingerprint, as it is a new model.

You can try to modify the driver yourself - open it in the Drivers code section, go to line 50 and replace

_TYZB01_v8gtiaed
with
_TZ3000_pmz6mjyu

Then save the driver and press Configure button. If the modification was done correctly, you should see two 'component devices' that should have full dimming functionality. (you may need to refresh the device web page to see the new devices).

I've tried, i also changed line 85 to " TS011F" but it sitll doesn´t work.
Every time I set the type to "Tuya Zigbee dimmer module", the "set level" paramenter seems to have a problem (its highlighted in red) and the "on-off" functions stop working.

sadly this forum doesn't let me include images or links to show the changes i made to de code (line 85 and 46), the problem i have (set parameter not saving), my devices fingerprint (wich i posted previously) and how my device and child devices show in my device list.

Again: thanks everyone!
Specially @fc352bf0a6929e9fa80f and @kkossev

1 Like

He everyone. Apologies in advance, very new to Hubitat and trying to work things out my self but stuck on this one.

I have a Moes / Tuya Smart Dimmer Module (From Ali Express) and here are the details.

endpointId: 01
application: 44
softwareBuild:
inClusters: 0000,0004,0005,EF00
outClusters: 0019,000A
model: TS0601
manufacturer: _TZE200_e3oitdyu

I have tried the drivers, and also tried replacing the device name in the driver, but nothing seems to be working. I am sure I am missing something simple, but wanted to check with you all first to see if there is anything you have tried that makes this work.

So far, no control, no child device being setup.

Would really appreciate your help and advice on this :slight_smile:

1 Like

I just went out of the device and back in and now the child is showing up with a CH01 and CH02 (after changing the name in the driver).

1 Like

Is your dimmer functional now? Can you control both the On/Off states and the levels?

Hi

The dimmer is not functioning at all via hubitat. The parent and two child devices are showing but no functionality. The status is also not showing.

Matt's driver will not work with your device, it is written and works great with TS011F model dimmers, while yours is TS0601 with Tuya specific cluster EF00 control.

It will take a while before an existing driver is found or a new one is written.

It works great for TS1101 until it doesn't :frowning:
I have constant random dropouts where I can still access the device but not the child devices.
The only way around this is to remove the device and add it to HE again but then I also have to add it to all my light groups again. This happens once every few weeks spread across 5 of these, is never consistently the same dimmer to drop out and is a real PITA.

And that's assuming that I can actually remove and rediscover the device seamlessly. Sometimes I can remove the device, the lights start flashing as the device goes into discovery mode, I rediscover it with HE and the lights stop flashing, but the device doesn't actually get added to HE. At that point I have to dismantle the physical wall switch to be able to get to the device's reset button...

Any help with this, or even confirmation that I'm not the only one to have this issue, would be much appreciated!

Hi @Silvermane, are you still using your TS1101 model device, Manufacturer _TZ3000_7ysdnebc?

When the dimmer is first removed, and then added again - is this driver selected automatically? Or do you have to manually change the driver again and press Configure button?