[New device support] LS 756200643 remote

[tonyschuite]

Link

https://www.opo.de/medias/Montageanleitung-1504960-Mec-Driver-1-Kanal-Modul.pdf?context=bWFzdGVyfHJvb3R8MTA4NTgxMXxhcHBsaWNhdGlvbi9wZGZ8YURjM0wyaGtNQzg0T1RZNU5EWXpNVFk1TURVMEwwMXZiblJoWjJWaGJteGxhWFIxYm1jZ01UVXdORGsyTUNCTlpXTWdSSEpwZG1WeUlERXRTMkZ1WVd3Z1RXOWtkV3d1Y0dSbXxhYjYzNWUwZTM4Zjc2ZTE4ZDI2NWI2ZGZjZmE4YmY0NjRhNjA4M2I2YmM4YjVjOGMwMWVmNGE0NDhiMDg5N2Q0

What does/doesn't work with the external definition?

identifies as SEMOTE from Bweetech

working: On Off

temp button color_temperature_step_up (short press) color_temperature_step_down (long press)

Sun button alternates between: brightness_step_up brightness_step_down

NOT WORKING: 1/2/3/4 buttons (grouped circles left half of the remote)

Details

zigbee-herdsman-converters: 25.14.0 software_build_id: 4.6.07_016 date_code: `` endpoints:

{"1":{"bindings":[],"clusters":{"input":["genBasic","genPowerCfg","genIdentify","genGroups","touchlink"],"output":["genIdentify","genGroups","genScenes","genOnOff","genLevelCtrl","lightingColorCtrl","touchlink"]},"configured_reportings":[],"scenes":[]}}

External definition:

import * as m from 'zigbee-herdsman-converters/lib/modernExtend';

export default {
    zigbeeModel: ['SEMOTE'],
    model: 'SEMOTE',
    vendor: 'Bweetech',
    description: 'Automatically generated definition',
    extend: [m.battery(), m.commandsOnOff(), m.commandsLevelCtrl(), m.commandsColorCtrl()],
    meta: {},
};

[chris-1243]

Could you provide the entry of this device from your database.db ?

[tonyschuite]

How do I do that?

[chris-1243]

In the folder in which you have your configuration.yaml, there is a file called database.db. Open it and find the lines corresponding to your device

[tonyschuite]

thanks!

{"id":19,"type":"EndDevice","ieeeAddr":"0x540f57fffecdb1ea","nwkAddr":48556,"manufId":4107,"manufName":"Bweetech","modelId":"SEMOTE","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":261,"inClusterList":[0,1,3,4,4096],"outClusterList":[3,4,5,6,8,768,4096],"clusters":{"genBasic":{"attributes":{"powerSource":0,"stackVersion":0,"dateCode":""}}},"binds":[{"cluster":0,"type":"endpoint","deviceIeeeAddress":"0x7cc6b6fffef7561b","endpointID":1},{"cluster":3,"type":"endpoint","deviceIeeeAddress":"0x7cc6b6fffef7561b","endpointID":1},{"cluster":6,"type":"endpoint","deviceIeeeAddress":"0x7cc6b6fffef7561b","endpointID":1},{"cluster":1,"type":"endpoint","deviceIeeeAddress":"0x7cc6b6fffef7561b","endpointID":1}],"configuredReportings":[],"meta":{}}},"appVersion":16,"stackVersion":0,"hwVersion":1,"dateCode":"","swBuildId":"4.6.07_016","zclVersion":3,"interviewCompleted":true,"interviewState":"SUCCESSFUL","meta":{},"lastSeen":1762300870573}

[chris-1243]

Would add this code as an external converter. Check this link to know how to add this

https://www.zigbee2mqtt.io/advanced/more/external_converters.html

Add this code as a *.mjs file.

import * as m from "zigbee-herdsman-converters/lib/modernExtend";

export default {
    zigbeeModel: ["SEMOTE"],
    model: "756200643",
    vendor: "L&S Lighting",
    description: "Zigbee remote",
    extend: [m.battery(), m.commandsOnOff(), m.commandsLevelCtrl(), m.commandsColorCtrl(), m.commandsScenes()],
};

Check the buttons which are not working. It is not quite clear if those are used to store scenes or to call a Zigbee group.

[tonyschuite]

I added it as an external converter. so far no response for the 4 extra buttons

[doogstar]

I have recently got the same remote as part of a bundle with my kitchen so am looking at options for controlling the lights and also using the remote. I have one remote set up and three kitchen lights. Moving between the numeric buttons directs the on/ off/ colour/ brightness commands to that specific light group in the kitchen.

Setting up a second remote with zigbee2mqtt with the external converter above and looking at the log entries, pressing the number buttons and then pressing the other buttons triggers an indication of group and command: -

[05/01/2026, 23:14:50] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x54dce9fffe2fab6b', payload '{"action":"color_temperature_step_down","action_group":3,"action_step_size":41,"action_transition_time":0.05,"battery":null,"linkquality":156}'

[05/01/2026, 23:14:50] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x54dce9fffe2fab6b/action', payload 'color_temperature_step_down'

[05/01/2026, 23:15:02] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x54dce9fffe2fab6b', payload '{"action":"color_temperature_step_down","action_group":2,"action_step_size":41,"action_transition_time":0.05,"battery":null,"linkquality":176}'

[05/01/2026, 23:15:02] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x54dce9fffe2fab6b/action', payload 'color_temperature_step_down'

[05/01/2026, 23:15:16] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x54dce9fffe2fab6b', payload '{"action":"brightness_stop","action_group":2,"battery":null,"linkquality":176}'

[05/01/2026, 23:15:16] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x54dce9fffe2fab6b/action', payload 'brightness_stop'

[05/01/2026, 23:15:16] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x54dce9fffe2fab6b', payload '{"action":"brightness_step_down","action_group":2,"action_step_size":30,"action_transition_time":0.05,"battery":null,"linkquality":176}'

[05/01/2026, 23:15:17] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x54dce9fffe2fab6b/action', payload 'brightness_step_down'

[05/01/2026, 23:15:22] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x54dce9fffe2fab6b', payload '{"action":"off","action_group":3,"battery":null,"linkquality":188}'

[05/01/2026, 23:15:22] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x54dce9fffe2fab6b/action', payload 'off'

[05/01/2026, 23:15:26] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x54dce9fffe2fab6b', payload '{"action":"on","action_group":4,"battery":null,"linkquality":180}'

[05/01/2026, 23:15:26] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x54dce9fffe2fab6b/action', payload 'on'

Hopefully that is helpful!

[chris-1243]

@doogstar Could you share the database.db entry once again of this device ?

[doogstar]

Here you go - this is the remote entry. I haven't worked out how to get the L&S transceiver I have to pair up yet - it's not one that I've seen in any of the previous images, it's a black box about the same size as the remote with two buttons on it that plugs into the transformer. It does say zigbee 2520 on the back of it. Will do some more probing with that soon to try and get it to pair with zigbee2mqtt.

{"id":2,"type":"EndDevice","ieeeAddr":"0x54dce9fffe2fab6b","nwkAddr":43450,"manufId":4107,"manufName":"Bweetech","modelId":"SEMOTE","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":261,"inClusterList":[0,1,3,4,4096],"outClusterList":[3,4,5,6,8,768,4096],"clusters":{"genBasic":{"attributes":{"powerSource":0,"stackVersion":0,"dateCode":""}}},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":17,"stackVersion":0,"hwVersion":1,"dateCode":"","swBuildId":"4.9.03_017","zclVersion":3,"interviewCompleted":true,"interviewState":"SUCCESSFUL","meta":{},"lastSeen":1767654924608}

[chris-1243]

This not possible to have the action_group as an argument in modernExtend and the device seems to have only one endpoint.

https://github.com/Koenkk/zigbee-herdsman-converters/blob/1d8d5b6ff7a82f32cc6b960bd200fb1a9db35ce0/src/lib/modernExtend.ts#L622

or

https://github.com/Koenkk/zigbee-herdsman-converters/blob/1d8d5b6ff7a82f32cc6b960bd200fb1a9db35ce0/src/lib/modernExtend.ts#L1344

We could add it but when creating an automation, you would need to listen to both the action and action_group unless someone has more knowledge than me and is able to modify the modernExtend or to create a device specific function.

[hlathome]

Hello @chris-1243 many thanks for highlighting my request as dupe to this - I failed to recognize it.

Speaking for me, I would be more than happy to have a converter which is better than the "self created" one with limited functionality. Even with the caveats of action and action_group; if someone would not get along they could still go back to the basic support (at least I presume)?

[chris-1243]

@hlathome You will not get more than what the device exposes and what it is described in the user manual.

• On/Off
• Brightness step/move
• Color temperature step/move
• Group selection (defined as action_group 1-4)

Could you share the output of a double press ON and OFF (enable debug log. It is stored in a file not in the console)

[chris-1243]

Added in

• https://github.com/Koenkk/zigbee-herdsman-converters/pull/11253

There is a lot work apparently to have all the commands working. This PR has been moved to draft for the time

[hlathome]

Many thanks!

to your question, "double press" does not seem to be recognized as such. In the debug log are many more lines in between, however I am not sure if they belong to the remote or to some other devices (I have ~70 lamps and devices being quite active):

`[2026-01-09 17:52:34] debug: z2m: Received Zigbee message from 'kueche_semote_dimmertaster', type 'commandOff', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 4

[2026-01-09 17:52:34] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/kueche_semote_dimmertaster', payload '{"action":"off","action_group":4,"battery":null,"device":{"applicationVersion":17,"dateCode":"","friendlyName":"kueche_semote_dimmertaster","hardwareVersion":1,"ieeeAddr":"0x94a081fffee21263","manufacturerID":4107,"manufacturerName":"Bweetech","model":"SEMOTE","networkAddress":52445,"softwareBuildID":"4.9.03_017","stackVersion":0,"type":"EndDevice","zclVersion":3},"linkquality":76}'

[2026-01-09 17:52:34] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/kueche_semote_dimmertaster/action', payload 'off'

...

[2026-01-09 17:52:35] debug: z2m: Received Zigbee message from 'kueche_semote_dimmertaster', type 'commandOffWithEffect', cluster 'genOnOff', data '{"effectid":0,"effectvariant":0}' from endpoint 1 with groupID 0

[2026-01-09 17:52:35] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/kueche_semote_dimmertaster', payload '{"action":"off","battery":null,"device":{"applicationVersion":17,"dateCode":"","friendlyName":"kueche_semote_dimmertaster","hardwareVersion":1,"ieeeAddr":"0x94a081fffee21263","manufacturerID":4107,"manufacturerName":"Bweetech","model":"SEMOTE","networkAddress":52445,"softwareBuildID":"4.9.03_017","stackVersion":0,"type":"EndDevice","zclVersion":3},"linkquality":80}'

[2026-01-09 17:52:35] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/kueche_semote_dimmertaster/action', payload 'off' `

[chris-1243]

There is a difference.

First try is single press

[2026-01-09 17:52:34] debug: z2m: Received Zigbee message from 'kueche_semote_dimmertaster', type 'commandOff', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 4

And second try is double press

[2026-01-09 17:52:35] debug: z2m: Received Zigbee message from 'kueche_semote_dimmertaster', type 'commandOffWithEffect', cluster 'genOnOff', data '{"effectid":0,"effectvariant":0}' from endpoint 1 with groupID 0

Correct am I?

[hlathome]

Yes to my best knowledge, I am not completely sure how quick the second press needs to come. I could repeat a bit more scientifically if you confirm these are the log entries you are looking for (and not the many lines in between)?

[chris-1243]

Those two lines are what I am looking for as the type of command is not the same.

If you could share:

• single press and some debug log lines
• double press and some debug lines.

That is all I need.

[doogstar]

I'm in a good position as I have literally nothing else Zigbee on my zigbee2mqtt so everything is just this remote.

zigbee.log

I've done slightly more to capture the following with timestamps in the logs Off once 21:00:46 Off double click 21:00:58 Off long press - remote leaves network. Re-paired and re-started On once 21:01:13 On double click 21:01:24 - 21:01:43 multiple times as wasn't showing in web frontend log but shows in log file On long press - nothing recorded - short pressed 21:05:36 to check working Colour temp once 21:08:08 Colour temp double click 21:08:26 Colour temp long press 21:08:56-21:08:59 Bright once 21:09:38 Bright double click 21:10:01 Bright long press 21:10:13-21:10:17

The off double click sends an action off without a group. The on double click sends commandOnWithRecallGlobalScene which I think isn't handled by the current extension.

In the live implementation I have without involving zigbee2mqtt where I have a remote paired to 3 L&S receivers, double click off switches off all 3, and double click on recalls the last state - i.e. if 1 and 3 were on but not 2 when I double clicked off, they'd be restored to that same state.

Hope that helps!

[chris-1243]

@doogstar Could you provide:

• Bright short press;
• Bright short press (wait some seconds between the two commands);
• Bright long press;
• Bright long press (wait some seconds between the two commands);

And the same for the color temperature? No need to try a double click as according to the manual there are no commands sent.

Thanks

[doogstar]

Here you go @chris-1243 , should be just what you specified.

zigbee2.log

[chris-1243]

@doogstar Would you test this converter ?

You need to add it as an external converter.

LS_remote_test.mjs

[doogstar]

@chris-1243 - Thanks - I think that's done the trick - showing the double button catches in the logs now - is there anything else needed?

zigbee3.log

[chris-1243]

Could you download and try the converter again (https://github.com/Koenkk/zigbee2mqtt/issues/28547#issuecomment-3734382807 - the link in the comment have been updated to the new version). I made some small corrections and I need you to test it. If you may submit a debug log like the last one, it would be nice.

Also, in the expose tab, I added an Action_group section. Could confirm it works. Select a group on the remote and press a button. You should have a number displayed (1-4) normally and below in Action the payload like on.

[doogstar]

@chris-1243 here you go thanks! I've gone through the same button stuff and generated a debug log. I can confirm that the Action_group shows up in the device expose tab, along with the relevant latest action 👍

zigbee4.log

[chris-1243]

@doogstar Your device has been added in

• https://github.com/Koenkk/zigbee-herdsman-converters/pull/11253

It will be available in the next official release or in the latest-dev when the PR will accepted and merged by the dev team.

Thanks @Koenkk for the huge help in the code writing!

[Koenkk]

Thanks @chris-1243 !

Changes will be available in the dev branch in a few hours from now and in the next release which is every 1st of the month.

[tonyschuite]

I have added this into my external converter. The Mqtt device does however not report the action to the MQTT server. Only Battery and Action Group. Also I am not able to get a "double_on" and "off" action on my remote in the exposes tab nor logs. Im using homeassistant.

[tonyschuite]

I have now updated to the new version / addon with the appropriate native support. The problem persists where i don't receive the actions in HA. i have no idea how to troubleshoot.

[chris-1243]

@tonyschuite Carefuly read the begining of this discussion.

• Koenkk/zigbee2mqtt/discussions/24198

In case you really need the action sensors, add the following to your configuration.yaml.

homeassistant:
  legacy_action_sensor: true

[tonyschuite]

hmm... i honestly don't understand...

the MQTT message published is

[04/02/2026, 11:37:31] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/MultiRemote', payload '{"action":"on","action_group":2,"battery":null,"device":{"applicationVersion":16,"dateCode":"","friendlyName":"MultiRemote","hardwareVersion":1,"ieeeAddr":"0x540f57fffecdb1ea","manufacturerID":4107,"manufacturerName":"Bweetech","model":"756200643","networkAddress":31528,"softwareBuildID":"4.6.07_016","stackVersion":0,"type":"EndDevice","zclVersion":3},"linkquality":112}' [04/02/2026, 11:37:31] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/MultiRemote/action', payload 'on'

I understand that the legacy actions are not supported anymore. However where in HA do i find the button presses for this specific device? The info page for MQTT Device Trigger explains it is automatically added using MQTT Discovery.