[RE-RELEASE] Zemismart ZigBee Wall Switch Multi-Gang

[kkossev]

This is a re-release of the popular 'Zemismart ZigBee Wall Switch Multi-Gang' driver, initially published by @muxa back in 2019.

The driver can now be installed from HPM - search for 'Zemismart'.
Important: if you have this driver already installed manually, first perform a 'MatchUp' in HPM and then update to the latest version.

Note, that most switches wo;; work out of the box using the Hubitat stock drivers. This driver adds the following Tuya-platform-specific features :

• Individual on/off control for all gangs, where, in some rare cases, the HE stock driver switches all the relays at once. Some Tuya devices require a Tuya-specific magic spell to be cast during the Zigbee pairing process.
• 'toggle' command - makes toggling all the switches easier in the automations.
• ping() command to check the Zigbee connectivity speed and reliability.
• Configuration of :
  • powerOnState - configures the switch power-on behavior (on, off, or preserve the last state)
  • switch type - configures the type of the mechanical wall switch wired to the module - toggle, state, momentary.
  • LED mode - configures the switch LEDs - disabled, lit when on, lit when off
  • switch backlight - enables or disables the switch backlight for these models which have it.

The actual states of the configuration preferences are shown as attributes in the 'Current States' section, if confirmed back by the device.
Note, that not all switches support all the configuration options.

Even when the HPM is used to install the latest stable version, before reporting any issues please make sure that you have first updated the driver to the latest development version - the code can be imported from GitHub :

https://raw.githubusercontent.com/kkossev/hubitat-muxa-fork/development/drivers/zemismart-zigbee-multigang-switch.groovy

[kkossev]

Reserved #2

[kkossev]

Version 1.1.0 adds support for the first of the Tuya new series of combined physical switches + scene buttons TS0726. More details on these new combined devices will come later.

AliExpress : (link)

[joshlobe]

Thank you so much!!
I just used HPM and the match-up worked perfectly.
What was the issue with that?

Looking forward to the additional features.
Thanks again!!

EDIT:
I see the other thread. NM

[kkossev]

Hi @youra ,

I am cross-posting here, as this is the new HE community thread for the Muxa's Zemismart driver.

@youra

So - I have one of these 4-way switches, and a while ago I was having trouble getting it to initialise at all - an upgrade to a C-8 seems to have dealt with that, but then the device (including the child devices) would work exactly as expected for a short while (say around 10min) then seemingly disappear from view - they worked locally, but the hub could no longer communicate with them. So I upgraded to the "Ver. 1.1.0 2024-05-02" driver, and now they still initialise properly (in particular for example I can set the switch type to momentary, which is not the reset default), but even though the child devices are created, they do nothing. Unfortunately I didn't keep track of with which driver version the switches were working for a short time.
Two questions:

• What logs/debug would be useful for debugging this behaviour?
• Any recommendations for a specific brand of 4-way switch that's known to work as expected?
  Thanks!

The first, and the most important is to identify your device. This driver supports more than 143 different devices ... I will need the Zigbee model and the manufacturer, as shown at the bottom of the HE device web page, 'Device Details', Data section. Please select, copy and paste as a text (not as a picture) the information there.

The second important thing is to update the driver to the latest version. Currently, it is Ver. 1.1.1 2024-05-05 (the link is in the top post).

There is a ping() button , that checks the device connectivity. What are the 'rtt' (round-trip time) values that you see in the Curent States (also in the live logs)?

If you get 'timeout!' instead of numeric values, this means that the Zigbee connectivity to your device has been lost.

[youra]

Thank you.

The Device info is:

• endpointId: 01
• application: 44
• manufacturer: _TZ3000_ltt60asa
• model: TS0004
  As far as I understand it, this is in the list of supported devices in the driver.

I've made sure the drivers updated, it gets found and apparently initialised, but then right away the Ping gives a timeout.
In the State Variables, it does however say: * lastTx : {pingTime=1717360890243} - I don't know what that number represents though...
What's a little confusing to me is that a previous driver version (unfortunately I don't know which version) but would have been a few months old did actually, consistently, function for a few minutes after each joining/initialisation before "going timeout".

[youra]

Just looked back - the "older" driver I was using I think would have been whatever was current in July '23...

[kkossev]

This seems to be the C-8 Zigbee 3.0 connectivity issue with some devices (mostly Tuya).

To make sure, change the driver to the HE inbuilt 'Device' driver. It will not control the switches, but if the device is connected and you click on the 'Get Info' button, you should see some info in the live logs.

Pair the device again (stay on the 'Device' driver). Will 'Get Info' provide some output in the live logs?
Wait 2 or 5 minutes, then check again the 'Get Info' button. If nothing in the live logs - this is the C-8 Zigbee 3.0 connectivity issue.

[youra]

Thanks again - OK, it does indeed seem to be the connectivity issue, which is entirely not helpful
Are the Hubitat Devs looking at this, or does the problem lie elsewhere?
Are there any known workarounds (i've tried connection without repeaters), or do I simply need to find a different device?

[vctgomes]

Hi, guys.

I'd like to report the new Zemismart Brazilian outlets is working ok with this driver, even the model with 2gang+outlet, including LEDs control and I guess the power-on behavior too.

Unfortunately it's being identified as a switch instead of a outlet on all models (it's not good to use on HomeKit+Siri).

Smart 2 poles outlet:
fingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0003,0004,0005,0006,E000,E001", outClusters:"0019,000A", model:"TS011F", manufacturer:"_TZ3000_xeumnff9", controllerType: "ZGB"

Problems: it's identifying a lot a light switchs, when we have only 2 outlets only the two first works.

Smart 2 gangs switch with Outlet
fingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0003,0004,0005,0006,E000,E001", outClusters:"0019,000A", model:"TS0003", manufacturer:"_TZ3000_aknpkt02", controllerType: "ZGB"

Problem: none
Note: all 3 items are being identified as switches

Smart 20A Outlet
Not installed yet. I'll send Fingerprint soon.

[kkossev]

Thank you for the feedback, Victor!

The Zemismart driver is not designed to control outlets, that's why it handles these as switches.

As a workaround, you can use the HE inibuilt Mirror app - present the switches as outlet/plug.

If a a particular manufacturer Id is not defined explicitly in this driver, it defaults to creating 4 child devices. I will check later and add the missing fingerprint in the next driver update.