@kkossev disregard. I was able to use Claude to get this driver working for me.
@reedmcdowell, please send me a DM with the modified code for this device, and I will add it to the driver code.
I just installed a Moes Starfeather Zigbee Wall Switch; recognized as Model TSO601 - Manufacturer = _TZE200_z3u99qxt. Tuya Version = 1.0.1.
Purchased off of Amazon --- MOES Full Touch Smart Switch, ZigBee SF(Star Feather 2026 Version) Wall Light Switch, Neutral Wire Required, Anti-Glare Panel,Work with Smart Life/Tuya App, Alexa and Google Home White 1 Gang - Amazon.com. I have this driver installed with HPM and the device is paired and the device parameters update and the switch works when I engage it physically however, it will not turn on or off by the app. Is there any chance you can update the driver for this newer model?
'Moes ZigBee Wall Switch 1/2/3-Gang revision 1.5.0 - 2026-04-14 :
- added all known Moes Star Feather Zigbee Wall Switches (1-4 gangs) with support for all their features, including _TZE200_z3u99qxt @smc.cross
Can you update manually to the new version and test if it works OK with your device (TSO601 = _TZE200_z3u99qxt) ?
Thanks for a quick turn; as before, it pairs and allows the parameters to be changed and I manually updated the driver and saw my user name in the code. However it does not turn on the relay from the app. Attached is a short snapshot of the logs. Let me know if you need anything else or a longer run of the logs.
Hi Steven, I don't know what your device is?
Please post the Zigbee model / manufacturer as shown at the bottom of the Device Info page.
Also, please show me the logs after clicking on the Refresh() button.
UPDATE: I think that I have found the problem in the on/off functions for the Star Feather switches - I will try to update the driver this evening
UPDATE2: the fix is applied on the updated driver - same version 1.5.0, time stamp is '2026/04/15 8:23 AM'.
You rock kkossev! That did it 
This driver works for the newer MakeGood (I assume it is a rebrand) TS0601 zigbee switches. However, these newer switches use RGB LEDs and you can set the color of on and off to what ever you want on each switch.
So far it seems to work to add them to a Tuya zigbee hub, set the colors and then add it to the Hubitat. Is there any way to adjust the color within Hubitat or will that take a complete rewrite of the driver?
Can you post the complete device fingerprint? Use the HE inbuilt ‘Device’ driver, command ‘Get Info’
Is this what you mean?
fingerprint profileId:"0104", endpointId:"01", inClusters:"0004,0005,EF00,0000,ED00", outClusters:"0019,000A", model:"TS0601", manufacturer:"_TZE284_ebe3s0rz", controllerType: "ZGB"
trace
ZCL version:03
trace
Model:TS0601
trace
Manufacturer:_TZE284_ebe3s0rz
debug
getting info for unknown Zigbee device..
Zigbee parsed:[raw:C30E0100001801002046E2FF2038E4FF2000, dni:C30E, endpoint:01, cluster:0000, size:18, attrId:0001, encoding:20, command:0A, value:46, clusterInt:0, attrInt:1, additionalAttrs:[[value:38, encoding:20, attrId:FFE2, consumedBytes:4, attrInt:65506], [value:00, encoding:20, attrId:FFE4, consumedBytes:4, attrInt:65508]]]
While we are having fun with TS0601 zigbee switches.
Any thoughts on a double GPO and Light?
The light works as a single gang light with the Moe TS0601 driver.
info
Zigbee parsed:[raw:8B420100001801002041E2FF2035E4FF2000, dni:8B42,
endpoint:01, cluster:0000, size:18, attrId:0001, encoding:20, command:0A,
value:41, clusterInt:0, attrInt:1, additionalAttrs:[[value:35, encoding:20,
attrId:FFE2, consumedBytes:4, attrInt:65506], [value:00, encoding:20,
attrId:FFE4, consumedBytes:4, attrInt:65508]]]
info
fingerprint profileId:"0104", endpointId:"01",
inClusters:"0004,0005,EF00,0000", outClusters:"0019,000A",
model:"TS0601", manufacturer:"_TZE200_4jvmbiph",
controllerType: "ZGB"
Looks like this.
Someone has done a doc for HA zigbee2mqtt and info here
Actually the above switch works when I deleted it and started again with this driver. It just finds it as a 1/2/3/4 gang switch but no power monitoring and 1/2/3 work to turn on/off the 2GPOs and the light.
Hi,@kkossev!
I'm struggling to make a new four gang Zemismart switch to work. I tried several drivers, including yours Tuya Zigbee Switch, without success; the Moes ZigBee Wall Switch 1/2/3-Gang (Tuya TS0601 Switches) isn't working too - this one recognize all the 4 child devices, but they don't work. With this driver the child devices also can't have its names edited, neither command the lights.
When pairing for the first time, Hubitat recognized it as a Zemismart Zigbee Blind.
The device data is the following:
Device Data
| Application | 4E |
|---|---|
| Endpoint Id | 01 |
| Manufacturer | _TZE284_xibaabmu |
| Model | TS0601 |
| Tuya Version | 1.0.14 |
Any chance to add it to your driver? This is the device link.
Thanks in advance for any help!
@marcusvrsilva I’ve added support for your Zemismart _TZE284_xibaabmu screen switch in driver v1.5.3, including all four relays and display labels.
Please update the driver manually and click Initialize, then test each child switch, physical button presses, and the parent On/Off commands.
To change the screen text, enter Display label 1–4 under Preferences and click Save Preferences. Labels support Portuguese accents and up to 12 characters; Hubitat child names stay unchanged.
I’ve also added native master On/Off control, backlight brightness and mode, indicator mode, on/off colors, color while delayed, child lock, radar configuration, and separate power-on behavior for each relay.
These settings appear under Preferences. Leave them unset to preserve the device’s current configuration, or select values and click Save Preferences to apply them.
Please test the new controls and let me know if anything behaves unexpectedly.
Hi @kkossev
I installed the driver and followed your instructions, but the device isn't working, just when phisically activated. I'm sending the logs below.
I tried to use AI to make a driver, but the problem I found is that the device's adress seems to change dinamically.
Thanks for your efforts!
**dev:4027**2026-09-30 18:08:14.434
debug
Home Theater - Interruptor sendZigbeeCommands: [he cmd 0x7FC3 0x01 0xEF00 0x00 {AAA30401000100} {}, delay 201]
**dev:4027**2026-09-30 18:08:14.432
info
Moes ZigBee Wall Switch 1/2/3-Gang EP04 is OFF
**dev:4027**2026-09-30 18:08:14.432
debug
component state is OFF - Moes ZigBee Wall Switch 1/2/3-Gang EP04 {4027-04}
**dev:4027**2026-09-30 18:08:13.832
debug
Home Theater - Interruptor sendZigbeeCommands: [he cmd 0x7FC3 0x01 0xEF00 0x00 {2E7B0401000101} {}, delay 201]
**dev:4027**2026-09-30 18:08:13.827
info
Moes ZigBee Wall Switch 1/2/3-Gang EP04 is ON
**dev:4027**2026-09-30 18:08:13.826
debug
component state is ON - Moes ZigBee Wall Switch 1/2/3-Gang EP04 {4027-04}
**dev:4027**2026-09-30 18:08:10.418
debug
Home Theater - Interruptor sendZigbeeCommands: [he cmd 0x7FC3 0x01 0xEF00 0x00 {38930301000100} {}, delay 201]
**dev:4027**2026-09-30 18:08:10.416
info
Moes ZigBee Wall Switch 1/2/3-Gang EP03 is OFF
**dev:4027**2026-09-30 18:08:10.415
debug
component state is OFF - Moes ZigBee Wall Switch 1/2/3-Gang EP03 {4027-03}
**dev:4027**2026-09-30 18:08:09.519
debug
Home Theater - Interruptor sendZigbeeCommands: [he cmd 0x7FC3 0x01 0xEF00 0x00 {19E30301000101} {}, delay 201]
**dev:4027**2026-09-30 18:08:09.517
info
Moes ZigBee Wall Switch 1/2/3-Gang EP03 is ON
**dev:4027**2026-09-30 18:08:09.517
debug
component state is ON - Moes ZigBee Wall Switch 1/2/3-Gang EP03 {4027-03}
**dev:4027**2026-09-30 18:08:05.919
debug
Home Theater - Interruptor sendZigbeeCommands: [he cmd 0x7FC3 0x01 0xEF00 0x00 {89C10201000100} {}, delay 201]
**dev:4027**2026-09-30 18:08:05.917
info
Moes ZigBee Wall Switch 1/2/3-Gang EP02 is OFF
**dev:4027**2026-09-30 18:08:05.916
debug
component state is OFF - Moes ZigBee Wall Switch 1/2/3-Gang EP02 {4027-02}
**dev:4027**2026-09-30 18:08:04.918
debug
Home Theater - Interruptor sendZigbeeCommands: [he cmd 0x7FC3 0x01 0xEF00 0x00 {08AE0201000101} {}, delay 201]
**dev:4027**2026-09-30 18:08:04.916
info
Moes ZigBee Wall Switch 1/2/3-Gang EP02 is ON
**dev:4027**2026-09-30 18:08:04.916
debug
component state is ON - Moes ZigBee Wall Switch 1/2/3-Gang EP02 {4027-02}
**dev:4027**2026-09-30 18:07:58.711
debug
Home Theater - Interruptor sendZigbeeCommands: [he cmd 0x7FC3 0x01 0xEF00 0x00 {24FB0101000101} {}, delay 201]
**dev:4027**2026-09-30 18:07:58.706
info
Moes ZigBee Wall Switch 1/2/3-Gang EP01 is ON
**dev:4027**2026-09-30 18:07:58.706
debug
component state is ON - Moes ZigBee Wall Switch 1/2/3-Gang EP01 {4027-01}
**dev:4027**2026-09-30 18:07:47.238
debug
Home Theater - Interruptor sendZigbeeCommands: [he cmd 0x7FC3 0x01 0xEF00 0x00 {79F30D01000100} {}, delay 201, delay 1000, he cmd 0x7FC3 0x01 0xEF00 0x03 {} {}, delay 2000]
**dev:4027**2026-09-30 18:07:47.235
info
Turn all switches OFF
**dev:4027**2026-09-30 18:07:46.150
debug
Home Theater - Interruptor sendZigbeeCommands: [he cmd 0x7FC3 0x01 0xEF00 0x00 {EB060D01000101} {}, delay 201, delay 1000, he cmd 0x7FC3 0x01 0xEF00 0x03 {} {}, delay 2000]
**dev:4027**2026-09-30 18:07:46.147
info
Turn all switches ON
**dev:4027**2026-09-30 18:07:42.216
debug
Home Theater - Interruptor sendZigbeeCommands: [he raw 0x7FC3 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 1000, he cmd 0x7FC3 0x01 0xEF00 0x03 {}, delay 2000]
**dev:4027**2026-09-30 18:07:42.214
trace
queryAllTuyaDP()
**dev:4027**2026-09-30 18:07:42.213
info
Refreshing...
**dev:4027**2026-09-30 18:07:42.179
info
Child device 4027-04 already exists (Moes ZigBee Wall Switch 1/2/3-Gang EP04)
**dev:4027**2026-09-30 18:07:42.177
info
Child device 4027-03 already exists (Moes ZigBee Wall Switch 1/2/3-Gang EP03)
**dev:4027**2026-09-30 18:07:42.175
info
Child device 4027-02 already exists (Moes ZigBee Wall Switch 1/2/3-Gang EP02)
**dev:4027**2026-09-30 18:07:42.173
info
Child device 4027-01 already exists (Moes ZigBee Wall Switch 1/2/3-Gang EP01)
**dev:4027**2026-09-30 18:07:42.170
debug
Parent createChildDevices
**dev:4027**2026-09-30 18:07:42.170
info
model: _TZE284_xibaabmu buttons: 4
**dev:4027**2026-09-30 18:07:42.168
debug
Parent deleteChildren
**dev:4027**2026-09-30 18:07:42.167
debug
Parent setupChildDevices
**dev:4027**2026-09-30 18:07:42.149
warn
Debug logging will be automatically disabled after 24 hours!
**dev:4027**2026-09-30 18:07:42.149
info
Initializing...
Marcus, it may be a good idea to start fresh - completely remove the device and add it as a new device. This driver should be selected automatically during the discovery.
Please send me the debug logs in a direct message.
PM sent.