Trying to connect door/window sensor MC510A-A002

Device Requests
1

Hi,

I´m trying to implement a door/windows sensor which has a model no. printed on the circuit board: MC510A-A002
Unfortunately it won´t connect to my conbee2 device. Any chance to get it implemented?

log:

13:07:02:822 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0 13:07:08:940 APS-DATA.indication srcAddr: 0x15FB, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -47 13:07:08:940 asdu: 00fb152c3da5009438c1a480 13:07:08:940 0xA4C1389400A53D2C 0x07DF nwk changed to 0x15FB 13:07:08:957 APS-DATA.indication from child 0x15FB 13:07:08:957 device announce 0xA4C1389400A53D2C (0x15FB) mac capabilities 0x80 13:07:08:957 set fast probe address to 0xA4C1389400A53D2C (0x15FB) 13:07:08:957 FP indication 0x0000 / 0x0013 (0xA4C1389400A53D2C / 0x15FB) 13:07:08:957 ... (0xA4C1389400A53D2C / 0x15FB) 13:07:08:957 device announce 0xA4C1389400A53D2C (0x15FB) mac capabilities 0x80 13:07:08:957 DEV Tick.Join: event/device.anounce 13:07:08:957 DEV Tick: fast poll 0xA4C1389400A53D2C, mac capabilities: 0x80 13:07:09:822 [1] get node descriptor for 0xa4c1389400a53d2c 13:07:09:822 ZDP get node descriptor for 0x15FB 13:07:09:822 APS-DATA.request id: 251, addrmode: 0x03, addr: 0xA4C1389400A53D2C, profile: 0x0000, cluster: 0x0002, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00 13:07:09:822 asdu (length: 3): 0AFB15 13:07:10:472 APS-DATA.confirm id: 251, status: 0x00 SUCCESS 13:07:10:823 saved node state in 0 ms 13:07:10:823 sync() in 0 ms 13:07:11:275 APS-DATA.indication srcAddr: 0x15FB, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8002, lqi: 255, rssi: -47 13:07:11:275 asdu: 0a00fb150240808612424200002c420000 13:07:11:275 APS-DATA.indication request id: 251 -> finished 13:07:11:275 APS-DATA.indication from child 0x15FB 13:07:11:275 APS-DATA.request id: 251 erase from queue 13:07:11:275 DB pushZdpDescriptorDb() 13:07:11:275 APS-DATA.request id: 253, addrmode: 0x02, addr: 0x15FB, profile: 0x0000, cluster: 0x0005, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00 13:07:11:275 asdu (length: 3): A9FB15 13:07:11:275 FP indication 0x0000 / 0x8002 (0xA4C1389400A53D2C / 0x15FB) 13:07:11:275 ... (0xA4C1389400A53D2C / 0x15FB) 13:07:11:276 ZDP indication search sensors 0xA4C1389400A53D2C (0x15FB) cluster 0x8002 13:07:11:276 ZDP indication search sensors 0xA4C1389400A53D2C (0x15FB) clear timeout on cluster 0x8002 13:07:11:281 [2] get active endpoints for 0xa4c1389400a53d2c 13:07:11:281 ZDP get active endpoints for 0x15FB 13:07:11:281 APS-DATA.request id: 254, addrmode: 0x03, addr: 0xA4C1389400A53D2C, profile: 0x0000, cluster: 0x0005, ep: 0x00 -> 0x00 queue: 1 len: 3 tx.options 0x00 13:07:11:281 asdu (length: 3): 0BFB15 13:07:11:534 APS-DATA.confirm id: 253, status: 0x00 SUCCESS 13:07:11:793 APS-DATA.confirm id: 254, status: 0x00 SUCCESS 13:07:12:049 APS-DATA.indication srcAddr: 0x15FB, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8005, lqi: 255, rssi: -47 13:07:12:049 asdu: a900fb150101 13:07:12:049 APS-DATA.indication request id: 253 -> finished 13:07:12:049 APS-DATA.indication from child 0x15FB 13:07:12:049 APS-DATA.request id: 253 erase from queue 13:07:12:049 FP indication 0x0000 / 0x8005 (0xA4C1389400A53D2C / 0x15FB) 13:07:12:049 ... (0xA4C1389400A53D2C / 0x15FB) 13:07:12:049 ZDP indication search sensors 0xA4C1389400A53D2C (0x15FB) cluster 0x8005 13:07:12:049 ZDP indication search sensors 0xA4C1389400A53D2C (0x15FB) clear timeout on cluster 0x8005 13:07:12:306 APS-DATA.indication srcAddr: 0x15FB, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8005, lqi: 255, rssi: -47 13:07:12:306 asdu: 0b00fb150101 13:07:12:306 APS-DATA.indication request id: 254 -> finished 13:07:12:306 APS-DATA.indication from child 0x15FB 13:07:12:306 APS-DATA.request id: 254 erase from queue 13:07:12:306 FP indication 0x0000 / 0x8005 (0xA4C1389400A53D2C / 0x15FB) 13:07:12:306

2

Hello, we need the model ID + Manufacture name to reconize the device.
But you probably can use an existing DDF and add thoses informations

3

I´m running decon on a raspberry pi without any desktop or GUI, so I cannot use the deconz GUI!
The sensor is actually a cheap one from AliExpress, only thing I know is the model no. I´ve posted + it needs the eWelink app.

4

Using zigbee2mqtt I could gather the following information:

Device Name
0xa4c1389400a53d2c

Description
Last Seen
N/A

Availability
Disabled

Device Type
EndDevice

Zigbee Model
SNZB-04

Zigbee Manufacturer
eWeLink

Description
Contact sensor

Support Status
Supported

IEEE Address
0xa4c1389400a53d2c

Network Address
0xE367 / 58215

Firmware Version
0122052017

Manufacturer
eWeLink

Model
SNZB-04

Power Supply
Battery 100%

Interview Successful
True

I used ChatGPT to create a DDF File:

{
    "schema": "devcap1.schema.json",
    "doc:path": "ewelink/snzv-04_contact_sensor.md",
    "doc:hdr": "SNZB-04 Contact Sensor",
    "manufacturername": "eWeLink",
    "modelid": "SNZB-04",
    "product": "SNZB-04 Contact Sensor",
    "status": "Gold",
    "md:known_issues": [],
    "supportsMgmtBind": true,
    "subdevices": [
        {
            "type": "$TYPE_CONTACT_SENSOR",
            "restapi": "/sensors",
            "uuid": ["$address.ext", "0x01"],
            "items": [
                { "name": "attr/lastannounced" },
                { "name": "attr/lastseen" },
                { "name": "attr/manufacturername" },
                { "name": "attr/modelid" },
                { "name": "attr/name" },
                { "name": "attr/swversion" },
                { "name": "attr/type" },
                { "name": "attr/uniqueid" },
                { "name": "state/contact" },
                { "name": "state/reachable" },
                { "name": "state/battery" }
            ]
        }
    ],
    "bindings": [
        {
            "bind": "unicast",
            "src.ep": 1,
            "cl": "0x0000", 
            "report": [
                { "at": "0x0000", "dt": "0x20", "min": 5, "max": 1800 }
            ]
        },
        {
            "bind": "unicast",
            "src.ep": 1,
            "cl": "0x0402", 
            "report": [
                { "at": "0x0000", "dt": "0x20", "min": 5, "max": 1800 }
            ]
        },
        {
            "bind": "unicast",
            "src.ep": 1,
            "cl": "0x0006", 
            "report": [
                { "at": "0x0000", "dt": "0x10", "min": 5, "max": 1800 }
            ]
        }
    ]
}

Do I just have to upload this file through the phoscon web frontend I should be able to connect the sensor?

edit: upload through frontend fails :frowning:

edit2: I googled the model no. which assumed this device is originally a sonoff window/door sensor. Next step was to google the model no. + deconz and I found this link: SONOFF SNZB-04 · Issue #3036 · dresden-elektronik/deconz-rest-plugin · GitHub

So it should actually be supported!?

5

So your device is supported since this PR DDF clones for Sonoff SNZB-04P by Smanar · Pull Request #8002 · dresden-elektronik/deconz-rest-plugin · GitHub

6

Any idea why it´s still not working?

7

What is your deconz version ?