Is it possible to configure a Zigbee dimmer module to work with a rocker switch?

[ndbroadbent]

I have some Moes Zigbee dimmer modules, and I would prefer to use my existing rocker switches to just turn the lights on and off. I don't mind if I can't control the brightness using my wall switch. I still like how the LED lights fade in and out nicely. And I can still control the brightness using Home Assistant automations, Alexa, Siri, etc.

I have a mix of the following dimmer modules:

• Lonsonho TS110E_1gang
• Lonsonho TS110E_2gang
• Moes MS-105B
• Moes MS-104Z
• Moes MS-105Z

They're designed to work with a push button, where a short press toggles them on/off and a long press changes the brightness. I'm trying to see if I can disable this behavior and just get them to turn on and off.

Similar discussions:

• Moes MS-105Z Zigbee Dimmer "Power On State" #12549
• Dimmer with physical "dumb" switch #11668
• Disable Dimming on a Dimmer Module? #9933
• Lonhonso 2 Gang dimmer- wall switch behaviour #5568
• Support for `device_mode` #11732

Thanks for your help!

[Matriciel]

https://www.zigbee2mqtt.io/devices/CCT5010-0001.html
This module is dimmer, with rocker, without neutral wire and ... router !!

[gregoryduckworth]

Did you get anyway with this? Realised I've gone down the same rabbit hole. I was thinking it might be possible to update the zigbee cluster to remove the functionality, but I know nothing about how to configure it.

[ndbroadbent]

This sounds very promising: #12952

1. It also has ability to configure the switch type on per-endpoint base. The Read Attributes response is consistent.

   Field	Value
   Cluster	genLevelCtrl (0x0008)
   Command	Write Attributes (0x02)
   Attribute	0xfc02
   Data Type	8-Bit Unsigned Integer (0x20)
   Possible values	0 - momentary ("kick-back switch"), 1 - toggle ("Seesaw Toggle Switch"), 2 - state ("Seesaw Sync Switch")

It sounds like the firmware probably does have this option, so there’s probably a way to set it from Z2M. I’ve seen some developer tools and low-level settings where you can send raw commands, but I’m not too sure how to do that

[gregoryduckworth]

I did some more digging on the Moes 2 gang dimmer and it looks like it isn't supported on the device itself.

[ndbroadbent]

Ah that’s a shame. Can I ask how did you find this information? I haven’t been able to find any manuals or documentation that describe which Zigbee features and commands are supported

[gregoryduckworth]

I actually used zha to find out the functionality of the device itself. It reported back as 0x16d9:1] Discovered endpoint information: SizePrefixedSimpleDescriptor(endpoint=1, profile=260, device_type=81, device_version=1, input_clusters=[0, 4, 5, 61184], output_clusters=[25, 10]) where in this case the output_clusters is important and refers to Time and OTA, so there is no external switch type like on the Lonsonho model.

[ndbroadbent]

Ah ok, thanks! In that case I suppose the only other option would be to write a custom firmware and figure out how to flash it. I don't think I would be able to do figure that out though! So might just stick with my momentary switches for now. Thanks for your help!

[ndbroadbent]

Oh wow, I just realized that a “switch type” option was added a few weeks after I posted this issue: #12952

I can confirm this is now available and working for my Lonsonho TS110E_2gang dimmer modules:

I set it to “toggle”, and now my normal rocker switches are able to turn the lights on and off. That’s awesome!

Now that I’ve seen how they did it in this PR, I should be able to modify and install a fork to try adding this option for my Moes dimmer modules. I might try that this weekend

[Alejandroid17]

What is the status of this? I have the same problem :(. I am using Moes MS-105BZ and I don't know if I should return them.

[Trickytree1984]

Same for me Moes MS-105BZ using Zigbee2MQTT and i don't have the option for "switch_type" in settings to set it to a toggle switch

[Trickytree1984]

Actually the Moes MS-105BZ pairs as a Tuya TS0601 in Zigbee2MQTT

[tvdbroeck]

I added a Lonsonho/Girier TS110E device to my network. I have the 1 gang version (manufacturer _TZ3210_zxbtub8r). I noticed that the convertor for the 1 gang version has a lot less features than the convertor for the 2 gang version. Even though these features are also supported by the 1 gang version. Specifically I was missing the tuya_switch_power_outage_memory and the TS110E_switch_type in the 1 gang version. The switch type was very important, because without it, the manual switch behaviour was unusable.
I made the following convertor, and this seems to work fine in my installation:

const definition = {
    fingerprint: [{modelID: 'TS110E', manufacturerName: '_TZ3210_zxbtub8r'}, {modelID: 'TS110E', manufacturerName: '_TZ3210_ngqk6jia'}],
    model: 'TS110E_1gang',
    vendor: 'Lonsonho',
    description: 'Zigbee smart dimmer module 1 gang with neutral',
    fromZigbee: extend.light_onoff_brightness({disablePowerOnBehavior: true}).fromZigbee.concat([
        fz.tuya_switch_power_outage_memory, fzLocal.TS110E_switch_type]),
    toZigbee: extend.light_onoff_brightness({disablePowerOnBehavior: true}).toZigbee.concat([
        tz.tuya_switch_power_outage_memory, tzLocal.TS110E_switch_type]),
    exposes: [
        e.light_brightness(),
        exposes.presets.switch_type_2(),
        exposes.enum('power_outage_memory', ea.ALL, ['on', 'off', 'restore']).withDescription('Recover state after power outage')
    ]
};

Is it possible to change this convertor on github, so other users can benefit as well?

Two additional remarks:

• the brand of my '1 gang dimmer' is Girier (https://nl.aliexpress.com/item/1005003693644741.html), but in the supported devices page (https://www.zigbee2mqtt.io/devices/TS110E_1gang.html), only the Lonsonho brand is mentioned. Could you add the Girier brand, so other users can more easily find it back?

• the 1 gang dimmer also seems to suffer from this bug (losing connectivity in 1 direction after a while): QS-Zigbee-CP03: intermittent error: 'No network route' (205) #12774
  Creating a dummy group with only this device, seems to solve the problem. Not sure what causes this, but could be useful to mention on the documentation page.
  Thanks for all the hard work!