(EDGE Driver-Mc) Zigbee switch MC, Zigbee switch power MC, Zigbee multi switch and child MC

That’s unfortunate, my hope was that refreshing the device would solve your problem. If refresh worked a simple refresh Rule would have been a work around.

@Mariano_Colmenarejo

Could you add this 3 gang switch to your driver please?

Mariano is no longer developing for the ST platform.

You can use @w35l3y default clusters drivers. This is a generic driver that can support:

_TZ3000_aezbqpcu

https://api.smartthings.com/invite/6Vjd4YPVJwjN

Anyone else having the words switch to another language? It shows english briefly and then switches to this. In addition, I can not change my driver.

2 Likes

I resubscribed. It still doesn’t explain the language change.

Yes I have seen language change since re-subscribing to the channel…

Same here. Was able to re-subscribe but still see Spanish. Anyone else? Ideas to return to English?

Yes, same here. All of the controls are in Spanish but the settings are still in English. There was a commit 3 days ago which I assume introduced the bug. Not sure why I’ve only seen a few posts about it. Hoping for a fix to come soon. Or maybe there’s another channel where the Mc drivers are forked?

Just wait for it

4 Likes

Thanks so much! Works great!

1 Like

Hello,
I have a problem with the Zigbee switch _TZ3000_hafsqare. The device is correctly added to SmartThings and detects the Zigbee Switch Mc driver, but it cannot be controlled, and the data does not load. Is there any solution for this?

Add the “ZigBee Thing Mc” driver to your hub, and change you driver to that. It is located in the same place as ZigBee Switch Mc".

Then post a screenshot of the history. It may give us some clues.

Manufacturer: _TZ3000_hafsqare
Model: TS0011
FingerPrinted_EndPoint.Id: 0x01
App Version: Unknown
ZCL Version: Unknown
Network ID: 0xEBAD
Zigbee EUI: A4C1381A16D34D5B
Device ID: fa9cb126-ac19-4ec6-9043-bbdc5f54eede

Server Cluster:
Ep: 0x01={ 0003,0004,0005,0006,0000 }

Client Clusters:
Ep: 0x01={ 0019,000A }

Signal Metrics:

I don’t see any EF00 clusters, so I would delete the device and repair the device.

2 Likes

Do you think the best option would be to return the button for a warranty claim?

Have you checked github? Is this device included in the driver?

If not then it is not at fault…

I did it for you guys…

Of course its fingerprint is there because as he already mentioned, the driver is being loaded.

Can you post some screenshots?

1 Like

Fair point, lack of joined up thought on my behalf there :roll_eyes:

1 Like