The development branch version is updated to v 0.6.0, where some bugs related to Lonsonho TS110E _TZ3210_4ubylghk dimmer module (also _TZ3210_pagajpog and _TZ3210_ngqk6jia) are fixed.
1 Like
Please update the driver to the latest development branch version 0.6.1 2023/08/23 7:45 PM"
The link to GitHub source is in the second post in this new thread, but I am reposting it again :
Then click on the Initialize button, and press F5 to refresh the device web page.
1 Like
The driver was updated to version 0.6.2 , timeStamp "2023/09/09 3:09 PM".
It adds support for the new series of Moes 1-2-3 gang dimmers :
Hi @kkossev and thanks for the driver.
I don't understand the minimum level set. Maybe because I don't been able to get it working or I think in the wrong way. 
My question:
Should the Minimum level setting work when I press the physical button?
My device:
Zigbee 2-Gang Dimmer module
driver: v1.0.0.1025b
endpointId: 01
inClusters: 0000,0004,0005,0006,0008
manufacturer: _TYZB01_v8gtiaed
model: TS110F
outClusters: 0019,000A
profileId: 0104
Thanks for your work.
Ronnie
Just got my hands on Moes Zigbee Rotary Dimmer from Aliexpress and connected using this driver. I can see values populated on the UI however it seems like I am not able to control the device using this driver.
Device pairing info
Manufacturer: _TZE200_p0gzbqct
Endpoint 01 application: 44
Endpoint 01 endpointId: 01
Endpoint 01 idAsInt: 1
Endpoint 01 inClusters: 0000,0004,0005,EF00
Endpoint 01 initialized: true
Endpoint 01 manufacturer: _TZE200_p0gzbqct
Endpoint 01 model: TS0601
Endpoint 01 outClusters: 0019,000A
Endpoint 01 profileId: 0104
Endpoint 01 stage: 4
Happy provide any details you want to help to get this driver working with this dimmer module as well.
This is the device from Aliexpress: https://a.aliexpress.com/_mNmNaLu
Moes Model No: EDM-1ZBA-EU
Looks like it is manufactured by eardatek : EARDATEK
Logs when adding the device:
dev:142023-10-13 08:55:12.036 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 F3CB 01 00 0000 11 01 001742, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F3CB, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:11, direction:01, data:[00, 17, 42]]
dev:142023-10-13 08:55:07.903 PMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0004,0005,EF00", outClusters:"0019,000A", model:"TS0601", manufacturer:"_TZE200_p0gzbqct"
dev:142023-10-13 08:55:07.806 PMtraceZCL version:03
dev:142023-10-13 08:55:07.799 PMtraceSoftware Build Id:unknown
dev:142023-10-13 08:55:07.797 PMtraceModel:TS0601
dev:142023-10-13 08:55:07.795 PMtraceManufacturer:_TZE200_p0gzbqct
dev:142023-10-13 08:55:07.694 PMdebuggetting info for unknown Zigbee device...
dev:142023-10-13 08:54:57.629 PMdebuggetting device info in 10 seconds...
EDIT
Looks like your recent Dev code works with module. I've come across this post from last year where the one I have is the rotary version instead of the touch version this user posted: Moes Zigbee Dimmer Touch - #15 by kkossev
The rotary version has LED indicator on the top of the rotary dial. Default behaviour of this LED is as follows:
- If the dimmer is off, LED will be GREEN
- If the dimmer is ON but NOT paired with a Zigbee hub, LED is OFF.
- If the dimmer is ON and paired with a Zigbee hub, LED is WHITE
1 Like
Hey Krassimir, just found another variant of this controller. Seems to work fine with advanced zigbee rgbw inbuilt driver, but only pairs as device. Had to change driver and re-pair. Here's the fingerprint
fingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0003,0004,0005,0006,1000,0008,0300,EF00", outClusters:"0019,000A", model:"TS0505B", manufacturer:"_TZ3210_qhdmg74j"
Here is the item, looks like they're using a tuya led strip controller for a ceiling light.
EzeeLum 6 in Smart Led Recessed Light, Zigbee Upgraded Stable Connect, 15W RGBWW 2700K-6500K Dimmable Ceiling Lights for Alexa Google Support Remote, Voice Control, and Music Sync (6inch, 1 Pack) https://a.co/d/8WICgdX
EDIT not sure if these catchall messages have any useful info:
Catchall Msgs
dev:21472023-11-08 11:15:21.407 AMdebugdescMap:[raw:catchall: 0000 8022 00 00 0040 00 8417 00 00 0000 00 00 6088, profileId:0000, clusterId:8022, clusterInt:32802, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:8417, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[60, 88]]
dev:21472023-11-08 11:15:21.004 AMdebugdescMap:[raw:catchall: 0000 8022 00 00 0040 00 8417 00 00 0000 00 00 5F88, profileId:0000, clusterId:8022, clusterInt:32802, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:8417, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[5F, 88]]
dev:21472023-11-08 11:15:20.729 AMdebugdescMap:[raw:catchall: 0000 8022 00 00 0040 00 8417 00 00 0000 00 00 5E88, profileId:0000, clusterId:8022, clusterInt:32802, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:8417, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[5E, 88]]
dev:21472023-11-08 11:15:20.473 AMwarndescription logging is: true
1 Like
Tagging @mike.maxwell , this TS0505B device uses the standard ZCL clusters and is better to be added into the HE inbuilt drivers.
2 Likes
So how much longer before HE puts you on the payroll? 
2 Likes
Hey @kkossev, love your work on this and other drivers!
I'm still using the release version through HPM for 5 lonsonho TS110E Dimmers, but one thing that's always bothered my Mrs is that my physical rocker switches don't play nice with the dimmers and you have to flick them on/off to turn a light on or off.
I noticed that Zigbee2mqtt came up with a solution for this but I don't really want do add more devices to the chain to allow for zigbee2mqtt...
Is there any way your driver could include this same rocker switch support??
Or maybe this beta already does in which case I'm jumping straight to this version!
In either case you'd be an absolute life saver 
1 Like
Please post your dimmer manufacturer (the Device Data section at the bottom of the web page).
1 Like
With pleasure!
1 Like
Unfortunately, your device model TS1101 manufacturer _TZ3000_7ysdnebc doesn't seem to support rocker switches.. Or at least, I couldn't find anything in Github. The link that you posted is for another device (TS110E).
We could still try, but I will need some more data from you - to install a special driver, run some magic commands, post the results and then you can return back to the driver that you are using at the moment.
Hey @kkossev, the person in the post I referred to on github had the exact same behaviour for his devices that I had. Pls see the opening post of that same github thread: Is it possible to configure a Zigbee dimmer module to work with a rocker switch? · Koenkk/zigbee2mqtt · Discussion #12684 · GitHub
It would seem to be an issue that affects all of the Moes and Lonsonho dimmer models this incompatibility with rocker switches, not just my model.
That's why I'm hopeful if Zigbee2mqtt was able to find a fix for this, that it would be possible within Hubitat directly as well.
Happy to assist and trial things out if you want to have a go at this.
No, the devices are totally different. The only common is that they are all called 'dimmers', nothing else.
model TS1101 manufacturer _TZ3000_7ysdnebc is not mentioned in the GitHub link.
Moes and Lonsonho sell everything made by other small manufacturers in China, that can bring them some extra $$$.
Moes and Lonsongo are selling dozens of totally different devices under their white label.
The only way to be sure whether this device can handle rocker-type switches is to pair it to a Tuya Zigbee gateway and see if there is any option to configure the external switch in the Tuya Smart Life app.
I can recommend at the moment Zemismart M1 Zigbee gateway, which should be also future-proof with the possible incoming Matter Bridge support in HE.
Blockquote No, the devices are totally different. The only common is that they are all called 'dimmers', nothing else.
model TS1101 manufacturer _TZ3000_7ysdnebc is not mentioned in the GitHub link.
Oh OK, I had assumed that the TZ3000 being the common denominator was the model number and that they were all manufactured to the same spec by different manufacturers (7ysdnebc being the case for my manufacturer). If that assumption had been correct, it would have stood to reason that they would all behave in the same way.
I've considered getting a cheap extra hub in the past for that exact reason but ultimately decided against it as all the cheap Chinese ones require accounts and in some cases apps to be installed to set things up and the like. It's just a shame (if my understanding from long ago is correct) that Tuya decided to drift from the IEEE spec and in essence started to do its own thing which HE struggled to incorporate. If that understanding is correct it's commendable and I fully support that HE wants to maintain proper Zigbee protocols, but it's not helpful in adding these kinds of devices of course.
The Zemismart M1 unfortunately looks to be the same in that it will also require setup in ways I'm not comfortable with, so whilst I've just happily received a Zemismart Zigbee tube motor to put into one of my roller blinds, I'm not going to extend that same courtesy for the M1
Couldn't care less about the Matter support either as I'm happy to stick with Zigbee.
The other option, rather then a cheap Tuya hub would be to go the ZigbeeM2QTT route, but I've always been reluctant to start messing around with RPi's as it's another thing I'll have to get my head around. The choice for HE originally was to have one device and an easy way to manage things. Else I would have gone with Home Assistant from day 1.
Now that it would seem that Zigbee2MQTT is becoming more and more unavoidable, I may try my hand at the RPi after all and initially just use Zigbee2MQTT. But I reckon if I do that, it won't be long before I also install HA and start tinkering with that as I certainly like the plethora of integrations there as well as the dashboards.
Add to the mix that I'm also looking into multiroom audio and I can run Snapcast on the Pi together with the HA integration which features a Snapcast client with volume control and I reckon I'm about to hit order on either the new Rpi5 or a slightly cheaper Rpi4.
If Zigbee2MQTT does have an option for a rocker switch for the 7ysdnebc, I'll happily report back so that you can decide whether you'd like to look at building in similar support for HE of course, but it'll take some time before I get to that stage I imagine.
I have been testing this driver with the Moes _TZE200_ip2akl4w (I have purchased 1/2/3 gang versions)
Unfortunately I have been unable to get it working as expected.
The spec sheet says single touch on/off long touch for dim.
However once configure, single touch causes the light to turn on from its lowest setting and increase in brightness. second touch goes from highest to lowest and then off. no action on long press.
ordered a cheap Tuya hub for the short term, but would much prefer to run this from HE.
Happy to provide any Info I can to help troubleshoot this, and even help with updating the driver once I get my head around the language. (needed to start somewhere, so I guess this is it)
These functions should work even offline, when the dimmer is not paired to any hub.
Is this your case?
If you installed the driver after pairing this Tuya dimmer to HE, it will not work by simply changing the driver later. The driver must be automatically selected when the device pairs for the first time.
You can try again, by removing the device and pairing it again in HE.
