[New device support]: Dresden Elektronik Scene Switch

Link

https://www.dresden-elektronik.de/produkt/scene-switch.html

Database entry

{"id":31,"type":"EndDevice","ieeeAddr":"0x00212effff01482b","nwkAddr":46612,"manufId":4405,"manufName":"dresden elektronik","powerSource":"Battery","modelId":"Scene Switch ","epList":[1],"endpoints":{"1":{"profId":49246,"epId":1,"devId":2048,"inClusterList":[0,4096,64512],"outClusterList":[4096,3,6,8,4,5,768,0,65280,25],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":1,"stackVersion":3,"hwVersion":2,"dateCode":"20151212","swBuildId":"02010032","zclVersion":1,"interviewCompleted":true,"meta":{},"lastSeen":1707578979491}

Comments

I closely followed the "support new devices" page and could pair the Scene Switch so that it shows up in Z2M and outputs messages to the log. However, no matter what I type into the .js file as converter definition, the messages in the log always stay the same. I have the feeling that Z2M does not even attempt to decode the messages. From the messages I get in the log it looks like it should be a cakewalk to write a converter for this switch, based on fz.genOnOff and the like in the fromzigbee field, but I am at a complete loss and have been ripping my hair our over this for a few days now. Any help or suggestion where I might have gone wrong would be appreciated.

The switch has one dimmer button ("elongated button"), and 4 scene recall buttons (buttons 1-4) in addition. Here is the response I get in the log for using the switches

Elongated button, short press top Debug 2024-02-09 20:27:42Received Zigbee message from 'DresdenSwitch', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 10999 Debug 2024-02-09 20:27:42No converter available for 'Scene Switch ' with cluster 'genOnOff' and type 'commandOn' and data '{}'

Elongated button, short press bottom Debug 2024-02-09 20:27:43Received Zigbee message from 'DresdenSwitch', type 'commandOff', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 10999 Debug 2024-02-09 20:27:43No converter available for 'Scene Switch ' with cluster 'genOnOff' and type 'commandOff' and data '{}'

Elongated button, start long press top ... Debug 2024-02-09 20:27:46Received Zigbee message from 'DresdenSwitch', type 'commandMoveWithOnOff', cluster 'genLevelCtrl', data '{"movemode":0,"rate":40}' from endpoint 1 with groupID 10999 Debug 2024-02-09 20:27:46No converter available for 'Scene Switch ' with cluster 'genLevelCtrl' and type 'commandMoveWithOnOff' and data '{"movemode":0,"rate":40}'

... and after releasing the button Debug` 2024-02-09 20:27:46Received Zigbee message from 'DresdenSwitch', type 'commandStop', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 10999 Debug 2024-02-09 20:27:46No converter available for 'Scene Switch ' with cluster 'genLevelCtrl' and type 'commandStop' and data '{}'

Elongated button, start long press bottom ... Debug 2024-02-09 20:27:49Received Zigbee message from 'DresdenSwitch', type 'commandMove', cluster 'genLevelCtrl', data '{"movemode":1,"rate":40}' from endpoint 1 with groupID 10999 Debug 2024-02-09 20:27:49No converter available for 'Scene Switch ' with cluster 'genLevelCtrl' and type 'commandMove' and data '{"movemode":1,"rate":40}'

... and after releasing the button Debug 2024-02-09 20:27:50Received Zigbee message from 'DresdenSwitch', type 'commandStop', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 10999 Debug 2024-02-09 20:27:50No converter available for 'Scene Switch ' with cluster 'genLevelCtrl' and type 'commandStop' and data '{}'

Button 1: Debug 2024-02-09 20:27:51Received Zigbee message from 'DresdenSwitch', type 'commandRecall', cluster 'genScenes', data '{"groupid":10999,"sceneid":1}' from endpoint 1 with groupID 10999 Debug 2024-02-09 20:27:51No converter available for 'Scene Switch ' with cluster 'genScenes' and type 'commandRecall' and data '{"groupid":10999,"sceneid":1}'

Button 2 Debug 2024-02-09 20:27:52Received Zigbee message from 'DresdenSwitch', type 'commandRecall', cluster 'genScenes', data '{"groupid":10999,"sceneid":2}' from endpoint 1 with groupID 10999 Debug 2024-02-09 20:27:52No converter available for 'Scene Switch ' with cluster 'genScenes' and type 'commandRecall' and data '{"groupid":10999,"sceneid":2}'

Button 3 Debug 2024-02-09 20:27:53Received Zigbee message from 'DresdenSwitch', type 'commandRecall', cluster 'genScenes', data '{"groupid":10999,"sceneid":3}' from endpoint 1 with groupID 10999 Debug 2024-02-09 20:27:53No converter available for 'Scene Switch ' with cluster 'genScenes' and type 'commandRecall' and data '{"groupid":10999,"sceneid":3}'

Button 4 Debug 2024-02-09 20:27:54Received Zigbee message from 'DresdenSwitch', type 'commandRecall', cluster 'genScenes', data '{"groupid":10999,"sceneid":4}' from endpoint 1 with groupID 10999 Debug 2024-02-09 20:27:54No converter available for 'Scene Switch ' with cluster 'genScenes' and type 'commandRecall' and data '{"groupid":10999,"sceneid":4}'

Each of these messages is followed by a linkquality statement, as the linkquality was recognized as automatically exposed. Looks like this: Info 2024-02-09 20:27:52MQTT publish: topic 'zigbee2mqtt/DresdenSwitch', payload '{"last_seen":"2024-02-09T19:27:54.287Z","linkquality":36}'

External definition

const {identify} = require('zigbee-herdsman-converters/lib/modernExtend');

const definition = {
    zigbeeModel: ['Scene Switch   '],
    model: 'Scene Switch   ',
    vendor: 'dresden elektronik',
    description: 'Automatically generated definition',
    extend: [identify()],
    meta: {},
};

module.exports = definition;

Koenkk / zigbee2mqtt