Zemismart zigbee wall switch multi-gang

[jpage4500]

@kkossev

Isn't the Dashboard picking the device label, not the automatically created device name?

FWIW I had to check since I was curious and by default HD+ picks the label if it's set. Then, the name if not set. You can override both though and it'll use that instead.

There is a setting though to switch the order -- so name would come before label - but that's not the default

[kkossev]

@jshimota

I'm sooo looking forward to being able to really dive into Tuya devices - they are cheap, effective and readily available - I'm hoping a central libary ...

The name of the central library is 'Matter Gateway'. Did you order your Zemismart M1 Matter Gateway hub already?

[jshimota]

ARGH! tried too! unavailable in USA and Aliexpress has it late February.... crap. Great price tho!

[Reigh]

I tried to pair Zemismart 4-gang zigbee wall switch to HE. I selected 'Zemismart zigbee wall switch multi-gang' driver and found one one switch was shown and even the switch is not working. The finger print is:

• endpointId: 01
• application: 46
• manufacturer: _TZE200_1n2kyphz
• model: TS0601

What is this message meaning?
IMPORTANT
In order to operate normally, please pair the device to HE after changing to this driver!

After changed to this driver I cannot pair without removing device because it is already paired.
Please help.

[Reigh]

Following is the log:

dev:4282024-03-07 01:57:54.552 PMdebugMain Lights Parent createChildDevices

dev:4282024-03-07 01:57:54.550 PMinfoMain Lights model: TS0601 gangs:1 child devices: 0

dev:4282024-03-07 01:57:54.547 PMdebugMain Lights Parent deleteChildren

dev:4282024-03-07 01:57:54.546 PMdebugMain Lights Parent setupChildDevices

dev:4282024-03-07 01:57:54.541 PMdebugMain Lights sendZigbeeCommands : [he raw 0x4480 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0x4480 0x01 0x0000 0xFFDE 0x20 {0D} {}, delay 50, zdo bind 0x4480 0x01 0x01 6 {A4C13827EA1605D1} {}, delay 2000, he cr 0x4480 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0x4480 0x01 6 0 {}, delay 2000]

dev:4282024-03-07 01:57:54.534 PMdebugMain Lights configure()..

dev:4282024-03-07 01:57:54.524 PMinfoMain Lights InitializeVars()... fullInit = true

dev:4282024-03-07 01:57:54.522 PMdebugMain Lights Initializing...

dev:4282024-03-07 01:57:50.609 PMinfoMain Lights initialize aborted! (str=--- Select ---)

dev:4282024-03-07 01:57:36.544 PMdebugMain Lights sendZigbeeCommands : [he raw 0x4480 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0x4480 0x01 0x0000 0xFFDE 0x20 {0D} {}, delay 50, zdo bind 0x4480 0x01 0x01 6 {A4C13827EA1605D1} {}, delay 2000, he cr 0x4480 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0x4480 0x01 6 0 {}, delay 2000]

dev:4282024-03-07 01:57:36.539 PMdebugMain Lights configure()..

[kkossev]

@Reigh

_TZE200_1n2kyphz

It's really confusing which driver to use with all these Tuya 100 different variations ...

UK. Moes Zigbee 1,2,3 or 4 gang light switch

Hi RG, You have accidentally updated (technically - changed) to the wrong driver. For Tuya switches model: TS0601 devices -> use Martin's driver : https://raw.githubusercontent.com/martinkura-svk/Hubitat/main/Moes%20ZigBee%20Wall%20Switch ( latest revision 1.04 - 2022-10-12) For Tuya dimmers models TS0601, TS110F, TS110E -> use this driver: https://raw.githubusercontent.com/kkossev/hubitat-matt-hammond-fork/master/drivers/tuya-zigbee-dimmer-module.groovy For Tuya switches models TS0001, …

You have a new device whose fingerprint is not in the Martin's driver yet.
First install the "Moes ZigBee Wall Switch 1/2/3-Gang" driver, then manually change your device driver to this one.

Then, obligatory, pair the device again to the hub. Although the fingerprint is missing, the driver should create 4 child devices (if not already created). Let me know if this will work.

[Reigh]

Hi, kkossev, thanks for your help.
I tried to use the driver you suggested.
I recognized number of buttons(4) correctly and showed 4 child devices.
But, all 4 child devices showed blank 'Current States' in the device pages and on and off buttons were not working. The wall switches were not responding.
Actually I bought the wall switch about a year ago. So, I thouhgt there is a driver for the wall switch. Following is the log:

dev:4282024-03-07 03:09:21.066 PMdebug{executed} 0xF975 0x01 0xEF00 0x00

dev:4282024-03-07 03:09:21.034 PMdebugcomponent refresh 428-02 Main Lights EP02

dev:4282024-03-07 03:09:20.090 PMdebug{executed} 0xF975 0x01 0xEF00 0x00 {00010201000101}

dev:4282024-03-07 03:09:20.086 PMinfoMain Lights EP02 is ON

dev:4282024-03-07 03:09:20.085 PMdebugcomponent state is ON - Main Lights EP02 {428-02}

dev:4282024-03-07 03:09:18.775 PMdebug{executed} 0xF975 0x01 0xEF00 0x00 {00010201000100}

dev:4282024-03-07 03:09:18.772 PMinfoMain Lights EP02 is OFF

dev:4282024-03-07 03:09:18.771 PMdebugcomponent state is OFF - Main Lights EP02 {428-02}

dev:4282024-03-07 03:09:17.138 PMdebug{executed} 0xF975 0x01 0xEF00 0x00 {00010201000101}

dev:4282024-03-07 03:09:17.135 PMinfoMain Lights EP02 is ON

dev:4282024-03-07 03:09:17.133 PMdebugcomponent state is ON - Main Lights EP02 {428-02}

dev:4282024-03-07 03:07:51.753 PMinfoRefreshing...

dev:4282024-03-07 03:07:51.691 PMinfoChild device 428-04 already exists (Main Lights EP04)

dev:4282024-03-07 03:07:51.687 PMinfoChild device 428-03 already exists (Main Lights EP03)

dev:4282024-03-07 03:07:51.684 PMinfoChild device 428-02 already exists (Main Lights EP02)

dev:4282024-03-07 03:07:51.678 PMinfoChild device 428-01 already exists (Main Lights EP01)

dev:4282024-03-07 03:07:51.673 PMdebugParent createChildDevices

dev:4282024-03-07 03:07:51.671 PMinfomodel: _TZE200_1n2kyphz buttons: 4

dev:4282024-03-07 03:07:51.665 PMdebugParent deleteChildren

dev:4282024-03-07 03:07:51.663 PMdebugParent setupChildDevices

dev:4282024-03-07 03:07:51.662 PMwarnDebug logging will be automatically disabled after 30 minutes!

dev:4282024-03-07 03:07:51.661 PMinfoInitializing...

[kkossev]

Wait one more day, and I will add this device fingerprint to the driver, and then you can try again.
Some weird Tuya devices will not work in HE if their fingerprints are not in the driver.

[Reigh]

Thanks for your kindness.
I'll look forward to update.

[kkossev]

@Reigh

_TZE200_1n2kyphz

Is your device this one ?

[Reigh]

Yes.

[Reigh]

I paired the wall switch to Zemismart M1 matter hub, which was paired to Homekit and HE, but I could see it in neither Home app nor HE. Very weird device.
That's why I want to pair HE directly.

[kkossev]

Not all Tuya devices (even when labeled 'Zemismart') are exposed via the Tuya Zigbee to Matter Bridge (even with Zemismart M1 logo on the plastic box). And no one can say which devices are supported via the bridge and which are not... : (

Please update the 'Moes ZigBee Wall Switch 1/2/3-Gang' driver to version 1.1.0.
First, delete the device (use the red button "REMOVE DEVICE" at the bottom right of the page). Then pair it again - this driver should be selected automatically. If not, I will need the device detailed fingerprint - you can obtain it from the HE inbuilt 'Device' driver clicking on 'Get Info' button.

Let me know if this works.

---

Update: the driver is now available for installation via HPM :

[RE-RELEASE] Moes ZigBee Wall Switch 1/2/3-Gang (Tuya TS0601 Switches)

This is a re-release of the popular 'Moes ZigBee Wall Switch 1/2/3-Gang' driver, initially published by @martinkura back in 2021. The driver can now be installed from HPM - search for 'Moes ZigBee Wall Switch '. Important: if you have this driver already installed manually, first perform a 'MatchUp' in HPM and then update to the latest version. Note, that Tuya TS0601 switches will not work out of the box using the Hubitat stock drivers. This driver is required for TS0601 switch devices. Ev…

[Reigh]

I tried steps what you guided. No luck.
Initially 'Tuya Scene Switch TS004F' was selected automatically.
I changed driver to 'Moes Zigbee Wall Switch...'
With the updated driver all 4 child devices showed blank 'Current States' in the device pages and on and off buttons were not working.
I found Error in the log:

org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method:
user_driver_Moes_1_31_Moes_ZigBee_Wall_Switch_1_2_3_Gang_760.deviceHealthCheck() is applicable for argument types: () values: (method deviceHealthCheck)

Following is the fingerprint captured when pairing:

Device pairing info
Manufacturer: _TZE200_1n2kyphz
Endpoint 01 application: 46
Endpoint 01 endpointld: 01
Endpoint 01 idAsInt:1
Endpoint 01 inClusters:0004,0005,EF00,0000
Endpoint 01 initialized:true
Endpoint 01 manufacturer: _TZE200_1n2kyphz
Endpoint 01 model: TS0601
Endpoint 01 outClusters: 0019,000A
Endpoint 01 profileld:0104
Endpoint 01 stage:4

[kkossev]

@Reigh

Initially 'Tuya Scene Switch TS004F' was selected automatically

This is the problem - my assumption for the fingerprint was wrong... I have corrected it now (thank you for the data!).

Pleae update again - the driver version is the same 1.1.0, just the timeStamp is different (2024/03/08 7:38 AM). You will need to remove the device again and pair it as a new one. It is critical that this driver is selected automatically during the initial pairing.

The exception is due to a scheduled job from the previously wrongly selected driver (TS004F). it should be gone after deleting and pairing again.

If still problems, please post the logs that follow the initial pairing.

[kkossev]

Wait, I just realized that this driver is missing the tuyaMagic() spell - it will probably not work again. I have to go now, will add the magic initialization later tonight.

[Reigh]

Ok, I'll wait. Thank you.

[kkossev]

I looked at the same switch implementation in Home Assistant (both ZHA and Z2M) and in SmartThings - there is nothing unusual there, magic initialization is not required..

Maybe we have a Zigbee connectivity problem?

Is your hub C-8 ?

From your previous logs, I don't see anything received from the device ... Do you see anything in the live logs (with Debug option turned on) when you press one of the buttons on the wall switch?

[Reigh]

I removed the device and device driver, and installed the '(2024/03/08 7:38 AM)' version driver.
When I tried to pair, the Moes driver was selected automatically.
I found six errors in the log. Following is the entire log:

dev:4722024-03-08 04:14:49.238 PMdebug{executed} 0xF04B 0x01 0xEF00 0x00 {00010101000100}
dev:4722024-03-08 04:14:49.235 PMinfoMoes ZigBee Wall Switch 1/2/3-Gang EP01 is OFF
dev:4722024-03-08 04:14:49.233 PMdebugcomponent state is OFF - Moes ZigBee Wall Switch 1/2/3-Gang EP01 {472-01}
dev:4722024-03-08 04:14:47.701 PMdebuguser_driver_Moes_1_31_Moes_ZigBee_Wall_Switch_1_2_3_Gang_761$_componentOn_closure3@f1669a
dev:4722024-03-08 04:14:47.692 PMinfoMoes ZigBee Wall Switch 1/2/3-Gang EP01 is ON
dev:4722024-03-08 04:14:47.691 PMdebugcomponent state is ON - Moes ZigBee Wall Switch 1/2/3-Gang EP01 {472-01}
dev:4722024-03-08 04:12:17.893 PMinfoRefreshing...
dev:4722024-03-08 04:12:17.814 PMinfoChild device 472-04 already exists (Moes ZigBee Wall Switch 1/2/3-Gang EP04)
dev:4722024-03-08 04:12:17.809 PMinfoChild device 472-03 already exists (Moes ZigBee Wall Switch 1/2/3-Gang EP03)
dev:4722024-03-08 04:12:17.805 PMinfoChild device 472-02 already exists (Moes ZigBee Wall Switch 1/2/3-Gang EP02)
dev:4722024-03-08 04:12:17.802 PMinfoChild device 472-01 already exists (Moes ZigBee Wall Switch 1/2/3-Gang EP01)
dev:4722024-03-08 04:12:17.798 PMdebugParent createChildDevices
dev:4722024-03-08 04:12:17.797 PMinfomodel: _TZE200_1n2kyphz buttons: 4
dev:4722024-03-08 04:12:17.781 PMdebugParent deleteChildren
dev:4722024-03-08 04:12:17.780 PMdebugParent setupChildDevices
dev:4722024-03-08 04:12:17.779 PMwarnDebug logging will be automatically disabled after 30 minutes!
dev:4722024-03-08 04:12:17.777 PMinfoInitializing...
dev:4722024-03-08 04:11:45.839 PMerrorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 108 (method parse)
dev:4722024-03-08 04:11:45.835 PMdebug[raw:F04B01EF000A00002000, dni:F04B, endpoint:01, cluster:EF00, size:0A, attrId:0000, encoding:20, command:01, value:00, clusterInt:61184, attrInt:0]
dev:4722024-03-08 04:11:45.814 PMerrorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 108 (method parse)
dev:4722024-03-08 04:11:45.809 PMdebug[raw:F04B01EF000A00002000, dni:F04B, endpoint:01, cluster:EF00, size:0A, attrId:0000, encoding:20, command:01, value:00, clusterInt:61184, attrInt:0]
dev:4722024-03-08 04:11:44.175 PMerrorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 108 (method parse)
dev:4722024-03-08 04:11:44.170 PMdebug[raw:F04B01EF000A00002000, dni:F04B, endpoint:01, cluster:EF00, size:0A, attrId:0000, encoding:20, command:01, value:00, clusterInt:61184, attrInt:0]
dev:4722024-03-08 04:11:43.992 PMerrorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 108 (method parse)
dev:4722024-03-08 04:11:43.987 PMdebug[raw:F04B01EF000A00002000, dni:F04B, endpoint:01, cluster:EF00, size:0A, attrId:0000, encoding:20, command:01, value:00, clusterInt:61184, attrInt:0]
dev:4722024-03-08 04:11:43.962 PMerrorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 108 (method parse)
dev:4722024-03-08 04:11:43.957 PMdebug[raw:F04B01EF000A00002000, dni:F04B, endpoint:01, cluster:EF00, size:0A, attrId:0000, encoding:20, command:01, value:00, clusterInt:61184, attrInt:0]
dev:4722024-03-08 04:11:43.874 PMerrorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 108 (method parse)
dev:4722024-03-08 04:11:43.828 PMinfoRefreshing...
dev:4722024-03-08 04:11:43.825 PMdebug[raw:F04B01EF000A00002000, dni:F04B, endpoint:01, cluster:EF00, size:0A, attrId:0000, encoding:20, command:01, value:00, clusterInt:61184, attrInt:0]
dev:4722024-03-08 04:11:43.779 PMdebug{executed} 0xF04B 0x01 0xEF00 0x00
dev:4722024-03-08 04:11:43.776 PMdebugcomponent refresh 472-04 Moes ZigBee Wall Switch 1/2/3-Gang EP04
dev:4722024-03-08 04:11:43.728 PMinfoCreating device 472-04
dev:4722024-03-08 04:11:43.722 PMdebug{executed} 0xF04B 0x01 0xEF00 0x00
dev:4722024-03-08 04:11:43.719 PMdebugcomponent refresh 472-03 Moes ZigBee Wall Switch 1/2/3-Gang EP03
dev:4722024-03-08 04:11:43.673 PMinfoCreating device 472-03
dev:4722024-03-08 04:11:43.667 PMdebug{executed} 0xF04B 0x01 0xEF00 0x00
dev:4722024-03-08 04:11:43.664 PMdebugcomponent refresh 472-02 Moes ZigBee Wall Switch 1/2/3-Gang EP02
dev:4722024-03-08 04:11:43.616 PMinfoCreating device 472-02
dev:4722024-03-08 04:11:43.602 PMdebug{executed} 0xF04B 0x01 0xEF00 0x00
dev:4722024-03-08 04:11:43.594 PMdebugcomponent refresh 472-01 Moes ZigBee Wall Switch 1/2/3-Gang EP01
dev:4722024-03-08 04:11:43.382 PMinfoCreating device 472-01
dev:4722024-03-08 04:11:43.376 PMdebugParent createChildDevices
dev:4722024-03-08 04:11:43.375 PMinfomodel: _TZE200_1n2kyphz buttons: 4
dev:4722024-03-08 04:11:43.369 PMdebugParent deleteChildren
dev:4722024-03-08 04:11:43.368 PMdebugParent setupChildDevices
dev:4722024-03-08 04:11:43.367 PMwarnDebug logging will be automatically disabled after 30 minutes!
dev:4722024-03-08 04:11:43.365 PMinfoInstalling...

To avoid zigbee connection problem, I moved my HE hub close to the wall switch before pairing.(about 3feet away)
I turned on and off from the wall switch and found no log about this action.
My hub is C-7.

[kkossev]

That's good news - something was received from the device, so it is not a connectivity problem (C-7 is usually fine with Tuya devices).

I have secured the processing of unexpected messages and added some extra logging.
Please update again (timestamp '2024/03/08 10:04 AM') and press each of the 4 physical buttons - I need the debug logs that follow a physical button press.

Observe the switch attribute status of the child devices - do they change when the switches are pressed?