Hi, could you please add this fingerprint to the Zigbee Button Mc driver? It’s a Tuya Smart Knob (Moes).
-
Manufacturer: _TZ3000_1fqpj6qz
-
Model: TS004F
Thank you in advance!
You can try ask @zambobmaz to add to his driver. open an issue in his Github:
Una pena que no esté más por aquí, pero muchísimas gracias por toda la ayuda que nos brindó a todos nosotros durante estos años. ¡La mejor de las suertes en lo que sea que usted haga!
PD: Los drivers que usted generosamente nos brindó ¿van a seguir funcionando sin usted?
@Mariano_Colmenarejo is still around and his drivers work well!
I would like to request a new fingerprint for your “Zigbee Smoke Detector Mc” driver. It is a Tuya Smoke and CO Combination Detector.
I have already enrolled in your channel and installed the correct driver on my Hub. However, when I try to “Select another driver”, I only see “Zigbee Device Config Mc” and “Zigbee Thing Mc”. Your “Zigbee Smoke Detector Mc” is NOT appearing in the list of available drivers for this device.
It seems the fingerprint is missing from the driver’s library. Here are the details:
Manufacturer: _TZE284_6ycgarab
Model: TS0601
I am attaching the screenshots showing the manufacturer ID and the driver list. Could you please add this fingerprint to your driver?
Thank you very much for your help and for your great work!
Since this device uses EF00 cluster , @Mariano_Colmenarejo won’t support it. You can Try @w35l3y EF00 specific driver and select Smoke Sensor profile
Thank you @dotan_shai for the clarification.
I have already installed @w35l3y’s Personal Tuya Devices driver, but the device is still recognized only as a ‘Zigbee Thing’. I’ve already contacted the developer to request the addition of this specific fingerprint (_TZE284_6ycgarab).
I’m now waiting for the update to be released so I can finally pair it correctly. Thanks again for the support!
My understanding of that generic EF00 driver is that you change the driver and configure it according to the instructions to fit your device without needing device specific fingerprints.
Hi @motocicletta, thanks for the suggestion.
I am aware that the EF00 driver allows manual configuration, but since this is a Smoke and CO detector, I want to be 100% sure the mapping is correct for safety reasons.
If anyone knows the specific DP IDs for this model (_TZE284_6ycgarab), I’d be happy to try manual configuration. Otherwise, I think waiting for @w35l3y to officially add it is the safest bet. What do you think?
Well, i think this train already leaved the station 
3rd party developed drivers are “unsupoorted” by smartthings platform, so isnt assured to work 100%.
if you you want to be 100% sure the device will function correctly, your best bet is to buy a officially suported device.
Hi @Mariano Colmenareio,
Could you please add the new Sonoff
ZBMINIR2 (with Neutral) to your Zigbee
Switch Mc driver?
Here are the details:
Model: ZBMINIR2
Manufacturer: SONOFF
Endpoint: Ox01
I’m looking forward to using the “Power On
State” feature with your driver.
Thank you very much!
I am new to using edge drivers and am looking for one to support this device:
Model: TS0043
Manufacture: _TZ3000_1kmurvlx
This device is a Moes Zigbee Switch - 3 gang 9 scenarios. Is there one available?
Thank you very much!!!
@zambobmaz already have a driver for this device. His Channel is here:
https://api.smartthings.com/invitation-web/accept?id=2d6da83b-ae22-4fda-8af5-bbb8890872d4
Not sure if this will work !!!
I copied all zigbee-switch-v6.5 from @Mariano_Colmenarejo Github . Also adde ZBMINIR2 fingerprint. All was done by AI (Co-Pilot). My channel is here.
https://bestow-regional.api.smartthings.com/invite/Q1jP7By0KVlL
Let me know if I succeed 
───────────────────────────────────────────────────
Driver Id 8ec67fcf-49d4-4b87-bfbd-e51c4f903a75
Name Zigbee Switch SD
Package Key Zigbee_Switch
Version 2026-05-08T11:19:47.332378062
───────────────────────────────────────────────────
Please note the new features of:
Cluster 0xFC11 Custom Attributes
| Attribute | ID | Type | Meaning |
|---|---|---|---|
external_trigger_mode |
0x0016 | uint8 | Edge/Pulse/Follow modes |
detach_relay |
0x0017 | bool | Relay follows external switch or not |
turbo_mode |
0x0012 | int16 | Boost mode (9=off, 20=on) |
Are not supported !! Only simple single switch
It worked perfectly!
Thank you so much for adapting this driver, it will be a lifesaver! 
@Mauro_Ferreira Maybe these can be set with this driver
Hello, With the help of @dotan_shai, I managed to use my device (MOES ZM-102-M-EU-MS TS601 _TZE204_jktmrpoj) with my SmartThings hub using a @w35l3y EF00 driver. However, I don’t have access to all the expected features (I only have access to the command and the position sensor’s feedback), and most importantly, I have an integration problem with Alexa, which doesn’t recognize the device correctly, while the other devices connected to my hub work normally. Can anyone help me?
@w35l3y is only a generic driver. It let you contorll specific DP.
If you want to contorll all feathers you better use AI tool (I recommend Claude.AI) to generate your own driver and deploy it to your channel and hub. these are the available DP and their functionality:
Hello everyone,
I am facing a persistent issue with the SONOFF ZBM5-2C-120 switch and the SmartThings platform. The device is marketed with “Detached Relay” capabilities, but these are not exposed or functional in the SmartThings app.
I have already attempted to use Mariano’s Edge Drivers, but this specific model is not supported, and my own attempts at custom driver development have hit a wall.
I’ve analyzed the technical specifications and Zigbee2MQTT (MQTT) documentation for this device here: **[SONOFF ZBM5-2C-120 control via MQTT | Zigbee2MQTT]( SONOFF ZBM5-2C-120 control via MQTT | Zigbee2MQTT )**. According to the specs, the device clearly supports input mode configurations (Detached Relay) via specific ZCL clusters/attributes.
It seems that the current integration (both stock and community drivers) fails to map these specific attributes correctly, causing the device to act as a standard switch regardless of the configuration.
I am looking for some input from experienced driver developers:
1. Has anyone successfully managed to map the specific clusters for the ZBM5-2C-120 to a SmartThings Edge Driver?
2. Is it possible that the current drivers are missing the necessary Cluster/Attribute definitions to trigger the input mode?
I would appreciate any guidance on whether this is a driver limitation or a platform-wide issue. Any help in bridging this gap would be greatly appreciate
Could you please add the fingerprint for the Aqara E1 Wireless Remote Switch (Double Rocker) to your Zigbee Multi Button Mc driver?
SmartThings is currently identifying it as a generic “Zigbee Thing” and won’t let me switch to a functional driver.
Here are the device details:
• Manufacturer: LUMI
• Model: lumi.remote.acn004
• Device Type: Wireless Double Rocker Scene Switch (Aqara E1)
Thank you so much for your amazing work supporting the community!