MOES ZigBee Wall Touch Smart Light Switch

  • manufacturer: _TZE200_amp6tsvy
1 Like

Although it is from the same Tuya white-label seller, this switch is very different than the previous 2 gang switch, it will not work with the inbuilt drivers.

I recommend using this driver:

https://raw.githubusercontent.com/martinkura-svk/Hubitat/main/Moes%20ZigBee%20Wall%20Switch

2 Likes

thank you your a magician. working now

1 Like

Sorry to again need your help .
I just got 2 more switches from same company and they do not work with any of the above drivers ....
after checking the manufacturer on this 2 switches i noticed they have different name (bought same product as before and from same seller :triumph:).
Now the manufacturer name is : _TZ3000_hhiodade .
Can you teach me how you search for correct driver ?

Hi @sagi.bracha,

I search for a proper driver for Tuya devices this way:

  1. Search in the community forum here for the manufacturer ID : _TZ3000_hhiodade . If there are results, I usually sort by last date. In the comments there is usually a link to an existing driver or other solution. In our case, however, no luck...
  2. Search Github for the same manufacturer. I see that this switch is already supported in Zigbee2MQTT, ZHA and SmartThings (Edge driver). From the comments/discussions in Github I see that the device type model is TS0011 .
  3. I search again in Hubitat forum for TS0011, sorted by last post, I see in this [post : Zemismart Zigbee 1/2/3/4 gang light switches - #36 by kkossev

"...Muxa's driver currently supports Tuya models TS0001 and TS0011 single gang switches.."

so this could be the solution.

The latest driver version does not contain your new device fingerprint, but if you change the driver manually and press the Initialize button, there is a very good chance that this driver will work for your device.

No this driver doesn't seem to work either :pensive:
I tried this zemismart and also the generic switch and the generic multi switch and the moes driver you sent me before ...
non of the above are working

Keep the Muxa’s driver assigned to your device,

Pair it again to HE. If it doesn’t work again, send me the debug logs.

I tried and still not working ...

dev:6842022-08-05 17:33:35.972 infoCorridor switch 1 Turning all child switches on

dev:6842022-08-05 17:33:33.236 infoCorridor switch 1 Turning all child switches off

dev:6842022-08-05 17:33:16.798 infoCorridor switch 1 Turning all child switches off

dev:6842022-08-05 17:33:14.949 infoCorridor switch 1 Turning all child switches on

dev:6842022-08-05 17:33:14.344 infoCorridor switch 1 Turning all child switches off

dev:6842022-08-05 17:33:11.003 debugCorridor switch 1 sendZigbeeCommands received : [he raw 0x989A 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, zdo bind 0x989A 0x01 0x01 6 {A4C138657DA599E6} {}, delay 2000, he cr 0x989A 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0x989A 0x01 6 0 {}, delay 2000]

dev:6842022-08-05 17:33:10.997 debugCorridor switch 1 configure()..

dev:6842022-08-05 17:33:10.836 debugCorridor switch 1 sendZigbeeCommands received : [he raw 0x989A 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, zdo bind 0x989A 0x01 0x01 6 {A4C138657DA599E6} {}, delay 2000, he cr 0x989A 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0x989A 0x01 6 0 {}, delay 2000]

dev:6842022-08-05 17:33:10.828 debugCorridor switch 1 configure()..

dev:6842022-08-05 17:33:10.648 debugCorridor switch 1 sendZigbeeCommands received : [he raw 0x989A 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, zdo bind 0x989A 0x01 0x01 6 {A4C138657DA599E6} {}, delay 2000, he cr 0x989A 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0x989A 0x01 6 0 {}, delay 2000]

dev:6842022-08-05 17:33:10.641 debugCorridor switch 1 configure()..

dev:6842022-08-05 17:33:10.153 debugCorridor switch 1 Parent createChildDevices

dev:6842022-08-05 17:33:10.151 debugCorridor switch 1 model: TS0011 buttons: 0

dev:6842022-08-05 17:33:10.149 debugCorridor switch 1 Parent deleteChildren

dev:6842022-08-05 17:33:10.148 debugCorridor switch 1 Parent setupChildDevices

dev:6842022-08-05 17:33:10.146 infoCorridor switch 1 InitializeVars()... fullInit = true

dev:6842022-08-05 17:33:10.145 debugCorridor switch 1 Initializing...

dev:6842022-08-05 17:33:09.847 infoCorridor switch 1 Turning all child switches off

dev:6842022-08-05 17:33:09.675 infoCorridor switch 1 Turning all child switches off

dev:6842022-08-05 17:33:08.496 debugCorridor switch 1 sendZigbeeCommands received : [he wattr 0x989A 0x01 0xE001 0xD030 0x30 {00} {}, delay 2000]

dev:6842022-08-05 17:33:08.493 debugCorridor switch 1 setting Switch Type to: toggle (0)

dev:6842022-08-05 17:33:06.681 infoCorridor switch 1 Turning all child switches off

dev:6842022-08-05 17:33:06.343 infoCorridor switch 1 Turning all child switches off

dev:6842022-08-05 17:33:05.736 infoCorridor switch 1 Turning all child switches on

dev:6842022-08-05 17:33:05.266 infoCorridor switch 1 Turning all child switches on

dev:6842022-08-05 17:33:03.314 infoCorridor switch 1 Turning all child switches off

dev:6842022-08-05 17:33:00.778 debugCorridor switch 1 Parent createChildDevices

dev:6842022-08-05 17:33:00.776 debugCorridor switch 1 model: TS0011 buttons: 0

dev:6842022-08-05 17:33:00.769 debugCorridor switch 1 Parent deleteChildren

dev:6842022-08-05 17:33:00.768 debugCorridor switch 1 Parent setupChildDevices

dev:6842022-08-05 17:33:00.766 infoCorridor switch 1 InitializeVars()... fullInit = true

dev:6842022-08-05 17:33:00.765 debugCorridor switch 1 Initializing...

dev:6842022-08-05 17:32:59.775 debugCorridor switch 1 sendZigbeeCommands received : [he wattr 0x989A 0x01 0x0006 0x8002 0x30 {02} {}, delay 2000]

dev:6842022-08-05 17:32:59.771 debugCorridor switch 1 setting Power On State option to: Last state (2

dev:6842022-08-05 17:31:53.821 debugZemismart ZigBee Wall Switch Multi-Gang Parent switch on

dev:6842022-08-05 17:31:53.818 debugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:989A0100060A00001001, dni:989A, endpoint:01, cluster:0006, size:0A, attrId:0000, encoding:10, command:01, value:01, clusterInt:6, attrInt:0]

dev:6842022-08-05 17:31:51.758 debugZemismart ZigBee Wall Switch Multi-Gang Zemismart ZigBee Wall Switch Multi-Gang unprocessed EP: 01 cluster: 0006 attrId: null

dev:6842022-08-05 17:31:51.754 debugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:catchall: 0104 0006 01 01 0040 00 989A 00 00 0000 07 01 00000000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:989A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00, 00, 00, 00]]

dev:6842022-08-05 17:31:49.788 debugZemismart ZigBee Wall Switch Multi-Gang Zemismart ZigBee Wall Switch Multi-Gang unprocessed EP: 00 cluster: 8021 attrId: null

dev:6842022-08-05 17:31:49.784 debugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:catchall: 0000 8021 00 00 0040 00 989A 00 00 0000 00 00 7700, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:989A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[77, 00]]

dev:6842022-08-05 17:31:49.686 debugZemismart ZigBee Wall Switch Multi-Gang Zemismart ZigBee Wall Switch Multi-Gang unprocessed EP: null cluster: null attrId: 0004

dev:6842022-08-05 17:31:49.681 debugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:989A01000068040042105F545A333030305F6868696F646164650000002003010000204505000042065453303031310700003003FEFF003000, dni:989A, endpoint:01, cluster:0000, size:68, attrId:0004, encoding:42, command:01, value:_TZ3000_hhiodade, clusterInt:0, attrInt:4, additionalAttrs:[[value:03, encoding:20, attrId:0000, consumedBytes:4, attrInt:0], [value:45, encoding:20, attrId:0001, consumedBytes:4, attrInt:1], [value:TS0011, encoding:42, attrId:0005, consumedBytes:9, attrInt:5]]]

dev:6842022-08-05 17:31:49.668 infoZemismart ZigBee Wall Switch Multi-Gang InitializeVars()... fullInit = false

dev:6842022-08-05 17:31:49.663 debugZemismart ZigBee Wall Switch Multi-Gang updating the settings from the current driver version null to the new version 0.2.8 2022/07/13 9:56 PM

dev:6842022-08-05 17:31:49.352 debugZemismart ZigBee Wall Switch Multi-Gang sendZigbeeCommands received : [he raw 0x989A 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, zdo bind 0x989A 0x01 0x01 6 {A4C138657DA599E6} {}, delay 2000, he cr 0x989A 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0x989A 0x01 6 0 {}, delay 2000]

dev:6842022-08-05 17:31:49.341 debugZemismart ZigBee Wall Switch Multi-Gang configure()..

dev:6842022-08-05 17:31:49.334 debugZemismart ZigBee Wall Switch Multi-Gang Parent installed

1 Like

Do you see anything in the logs when you press the physical switch?

No

Okay, some hours later I will send you an updated driver to test again.. although theoretically there shouldn’t be such need, but let’s try.

i appreciate so much your help and support hope we can find a solution

1 Like

Please download and install the development branch version of the driver (the second link) from this post: Zemismart Zigbee 1/2/3/4 gang light switches - #36 by kkossev

The recommended procedure is to first delete the device from the HE device web page, wait 1 minute, then pair the switch again to HE. The "Zemismart ZigBee Wall Switch Multi-Gang" driver should be assigned automatically during the initial discovery process this time.

Let me know if this driver will work for you.

Saved me once again :partying_face::partying_face::partying_face::partying_face::partying_face:
working great now.
one question what does the configuration/ping button do ?

1 Like

The Configure button sends a sequence of initialization and configuration commands to Tuya device, which in some of the cases work, in other cases (like yours) doesn't. The reason is that some Tuya devices require these commands to be sent in a very narrow time frame during the initial pairing process. That's why with some devices simply pressing the Configure button doesn't make them work as expected. The device fingerprint must be added into the driver, then the devices must be deleted from HE web page and paired again as a new one. Only then it works! :0

Ping is an artifact from the "Health Check" capability, that has been used with SmartThings drivers in the past. I think it is obsolete now and no HE apps are using it, so I will research a bit more on this topic and will probably remove it in one of the next driver updates.

1 Like

You help learn so much and i rely do appreciate all of your help
thank you

Need Help !
I just purchased the Moes 2 Gang Switch from Amazon also and when I try to pair it HE says
device found but then times out with an error. "Looks like your having trouble pairing your device"
I have loaded both drivers
[Zemismart ZigBee Wall Switch Multi-Gang] and [Zemismart ZigBee Wall Switch Multi-Gang]
but not sure how to use them??
Question? after loading the drivers how to I add the new switch and tell it to use the loaded drivers?
I have tried using Generic and same problem.. device just will not pair..

You first need to pair successfully the switch,” to HE, and then we can check which drives works with this device.

What is your hub model, C-8 or C-7 ?

Do you have problems pairing any other Zigbee devices, or only this one can not finish the initial pairing process?