search

Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
12.11k stars 1.68k forks source link

support Osram Smart+ Motion Sensor? #507

Closed salopette closed 5 years ago

salopette commented 6 years ago

Hello, is Osram Smart + Motion Sensor supported?

https://www.osram-lamps.de/ekatalog/smart-home/smart-home-komponenten/smart-motion-sensor/index.jsp

Koenkk commented 6 years ago

No, but can be if you have the device and follow: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices

nebman commented 6 years ago

I recently got one, but it failed while pairing. Tried several factory resets and button presses but kept getting the following error msg:

zigbee2mqtt:error 22/10/2018, 21:13:51 Cannot get the Node Descriptor of the Device: 0x000d6f000fffffff (Error: Timed out after 10000 ms)

The sensor blinks blue (searching network) followed by green every other time (indicating successful pairing) and then keeps repeating this sequence after some seconds.

Which DEBUG parameters would be helpful to debug?

nebman commented 6 years ago

I created a log file with DEBUG=cc-znp, would this be helpful? @Koenkk
Lines start when pluggin in the battery in the motion sensor and ends at the error message.

Link to Logfile

salopette commented 6 years ago

Okt 23 15:49:22 raspberrypi npm[602]: zigbee2mqtt:debug 2018-10-23 15:49:22 Check online 0x00124b0014d9dafa 0x00124b0014d9dafa Okt 23 15:49:36 raspberrypi npm[602]: zigbee2mqtt:debug 2018-10-23 15:49:36 Saving state to file /opt/zigbee2mqtt/data/state.json Okt 23 15:49:42 raspberrypi npm[602]: zigbee2mqtt:error 2018-10-23 15:49:42 Cannot get the Node Descriptor of the Device: 0x000d6f000f71110c (Error: Timed out after 10000 ms)

Saving state to file /opt/zigbee2mqtt/data/state.json

{ "0x00124b0014d9dafa": { "description": "0/0x00124B0014D9D6F9", "type": "COORD", "rssi": 48, "linkquality": 47 }, "0x00158d0001bc53c4": { "battery": "99.00", "voltage": 3022, "linkquality": 84 }, "0x00158d0001f9efde": { "battery": "99.00", "voltage": 3025, "linkquality": 63 }

Koenkk commented 6 years ago

@kirovilya do you know why these Cannot get the Node Descriptor of the Device: 0x000d6f000f71110c (Error: Timed out after 10000 ms) timeout appear? Does the device not announce itself correctly?

tb-killa commented 6 years ago

@salopette please provide full debug logfile via DEBUG=* npm start and do fresh pairing. It could be that you have first of all remove your actually device entry from your database.db file.

for pairing please refer to this: https://images-eu.ssl-images-amazon.com/images/I/C18QWX-dFxS.pdf

Reset the Motion Sensor: Press and hold the marked button for longer than 10 seconds

it could be that you have to keep the device on wakeup by press the button e.g. every second on pairing process themselve. please test again and report.

nebman commented 6 years ago

it could be that you have to keep the device on wakeup by press the button e.g. every second on pairing process themselve. please test again and report.

I have tried the button-press-keep-awake method. but the device doesnt look like it goes to sleep. it starts repairing after some seconds, well before we get the 10s timeout message in the log file

I can get my hands on a fresh spare CC2530 module in a few days, then I can provide a full log with only this motion sensor

dcsg commented 6 years ago

Any news on this?

dcsg commented 6 years ago

I was able to use DEBUG=* this is what I got:

  serialport:poller received "readable" +27s
  serialport:bindings read +27s
  serialport:unixRead Starting read +27s
  serialport:unixRead Finished read 17 bytes +2ms
  serialport:main binding.read finished +27s
  cc-znp { sof: 254,
  cc-znp   len: 12,
  cc-znp   type: 'AREQ',
  cc-znp   subsys: 'ZDO',
  cc-znp   cmd: 'tcDeviceInd',
  cc-znp   payload: { nwkaddr: 16252, extaddr: '0x000d6f000e0597b7', parentaddr: 0 },
  cc-znp   fcs: 137,
  cc-znp   csum: 137 } +27s
  serialport:main _read reading +10ms
  serialport:bindings read +14ms
  serialport:unixRead Starting read +12ms
  cc-znp:AREQ <-- ZDO:tcDeviceInd, { nwkaddr: 16252, extaddr: '0x000d6f000e0597b7', parentaddr: 0 } +7ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd +1ms
  serialport:unixRead waiting for readable because of code: EAGAIN +5ms
  serialport:poller Polling for "readable" +20ms
  serialport:poller received "readable" +410ms
  serialport:bindings read +416ms
  serialport:unixRead Starting read +412ms
  serialport:unixRead Finished read 18 bytes +2ms
  serialport:main binding.read finished +420ms
  cc-znp { sof: 254,
  cc-znp   len: 13,
  cc-znp   type: 'AREQ',
  cc-znp   subsys: 'ZDO',
  cc-znp   cmd: 'endDeviceAnnceInd',
  cc-znp   payload:
  cc-znp    { srcaddr: 16252,
  cc-znp      nwkaddr: 16252,
  cc-znp      ieeeaddr: '0x000d6f000e0597b7',
  cc-znp      capabilities: 128 },
  cc-znp   fcs: 64,
  cc-znp   csum: 64 } +421ms
  serialport:main _read reading +10ms
  serialport:bindings read +13ms
  serialport:unixRead Starting read +11ms
  cc-znp:AREQ <-- ZDO:endDeviceAnnceInd, { srcaddr: 16252, nwkaddr: 16252, ieeeaddr: '0x000d6f000e0597b7', capabilities: 128 } +8ms
  zigbee-shepherd spinlock: false [] +1ms
  zigbee-shepherd:request REQ --> ZDO:nodeDescReq +2ms
  cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 16252, nwkaddrofinterest: 16252 } +2ms
  serialport:main _write 9 bytes of data +12ms
  serialport:bindings write 9 bytes +12ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:endDeviceAnnceInd +22ms
  serialport:unixWrite Starting write 9 bytes offset 0 bytesToWrite 9 +28s
  serialport:unixRead waiting for readable because of code: EAGAIN +32ms
  serialport:poller Polling for "readable" +48ms
  serialport:unixWrite write returned null 9 +2ms
  serialport:unixWrite wrote 9 bytes +1ms
  serialport:unixWrite Finished writing 9 bytes +0ms
  serialport:main binding.write write finished +23ms
  serialport:poller received "readable" +6ms
  serialport:bindings read +29ms
  serialport:unixRead Starting read +10ms
  serialport:unixRead Finished read 6 bytes +2ms
  serialport:main binding.read finished +10ms
  cc-znp { sof: 254,
  cc-znp   len: 1,
  cc-znp   type: 'SRSP',
  cc-znp   subsys: 'ZDO',
  cc-znp   cmd: 'nodeDescReq',
  cc-znp   payload: { status: 0 },
  cc-znp   fcs: 102,
  cc-znp   csum: 102 } +19ms
  serialport:main _read reading +8ms
  serialport:bindings read +13ms
  serialport:unixRead Starting read +9ms
  cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +7ms
  serialport:unixRead waiting for readable because of code: EAGAIN +5ms
  serialport:poller Polling for "readable" +19ms
  serialport:poller received "readable" +2s
  serialport:bindings read +2s
  serialport:unixRead Starting read +2s
  serialport:unixRead Finished read 23 bytes +2ms
  serialport:main binding.read finished +2s
  cc-znp { sof: 254,
  cc-znp   len: 18,
  cc-znp   type: 'AREQ',
  cc-znp   subsys: 'ZDO',
  cc-znp   cmd: 'nodeDescRsp',
  cc-znp   payload:
  cc-znp    { srcaddr: 16252,
  cc-znp      status: 0,
  cc-znp      nwkaddr: 16252,
  cc-znp      logicaltype_cmplxdescavai_userdescavai: 2,
  cc-znp      apsflags_freqband: 64,
  cc-znp      maccapflags: 128,
  cc-znp      manufacturercode: 4174,
  cc-znp      maxbuffersize: 82,
  cc-znp      maxintransfersize: 82,
  cc-znp      servermask: 0,
  cc-znp      maxouttransfersize: 82,
  cc-znp      descriptorcap: 0 },
  cc-znp   fcs: 27,
  cc-znp   csum: 27 } +2s
  serialport:main _read reading +11ms
  serialport:bindings read +14ms
  serialport:unixRead Starting read +13ms
  cc-znp:AREQ <-- ZDO:nodeDescRsp, { srcaddr: 16252, status: 0, nwkaddr: 16252, logicaltype_cmplxdescavai_userdescavai: 2, apsflags_freqband: 64, maccapflags: 128, manufacturercode: 4174, maxbuffersize: 82, maxintransfersize: 82, servermask: 0, maxouttransfersize: 82, descriptorcap: 0 } +6ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:nodeDescRsp +2ms
  zigbee-shepherd:request REQ --> ZDO:activeEpReq +1ms
  cc-znp:SREQ --> ZDO:activeEpReq, { dstaddr: 16252, nwkaddrofinterest: 16252 } +2ms
  serialport:main _write 9 bytes of data +11ms
  serialport:bindings write 9 bytes +10ms
  serialport:unixWrite Starting write 9 bytes offset 0 bytesToWrite 9 +2s
  serialport:unixRead waiting for readable because of code: EAGAIN +12ms
  serialport:poller Polling for "readable" +28ms
  serialport:unixWrite write returned null 9 +3ms
  serialport:unixWrite wrote 9 bytes +0ms
  serialport:unixWrite Finished writing 9 bytes +1ms
  serialport:main binding.write write finished +5ms
  serialport:poller received "readable" +7ms
  serialport:bindings read +11ms
  serialport:unixRead Starting read +8ms
  serialport:unixRead Finished read 6 bytes +2ms
  serialport:main binding.read finished +8ms
  cc-znp { sof: 254,
  cc-znp   len: 1,
  cc-znp   type: 'SRSP',
  cc-znp   subsys: 'ZDO',
  cc-znp   cmd: 'activeEpReq',
  cc-znp   payload: { status: 0 },
  cc-znp   fcs: 97,
  cc-znp   csum: 97 } +21ms
  serialport:main _read reading +7ms
  serialport:bindings read +10ms
  serialport:unixRead Starting read +9ms
  cc-znp:SRSP <-- ZDO:activeEpReq, { status: 0 } +5ms
  serialport:unixRead waiting for readable because of code: EAGAIN +3ms
  serialport:poller Polling for "readable" +15ms
  serialport:poller received "readable" +955ms
  serialport:bindings read +960ms
  serialport:unixRead Starting read +957ms
  serialport:unixRead Finished read 13 bytes +1ms
  serialport:main binding.read finished +963ms
  cc-znp { sof: 254,
  cc-znp   len: 8,
  cc-znp   type: 'AREQ',
  cc-znp   subsys: 'ZDO',
  cc-znp   cmd: 'activeEpRsp',
  cc-znp   payload:
  cc-znp    { srcaddr: 16252,
  cc-znp      status: 0,
  cc-znp      nwkaddr: 16252,
  cc-znp      activeepcount: 2,
  cc-znp      activeeplist: <Buffer 01 02> },
  cc-znp   fcs: 201,
  cc-znp   csum: 201 } +966ms
  serialport:main _read reading +9ms
  serialport:bindings read +12ms
  serialport:unixRead Starting read +10ms
  cc-znp:AREQ <-- ZDO:activeEpRsp, { srcaddr: 16252, status: 0, nwkaddr: 16252, activeepcount: 2, activeeplist: <Buffer 01 02> } +5ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:activeEpRsp +2ms
  zigbee-shepherd:request REQ --> ZDO:simpleDescReq +2ms
  cc-znp:SREQ --> ZDO:simpleDescReq, { dstaddr: 16252, nwkaddrofinterest: 16252, endpoint: 1 } +1ms
  serialport:main _write 10 bytes of data +10ms
  serialport:bindings write 10 bytes +9ms
  serialport:unixWrite Starting write 10 bytes offset 0 bytesToWrite 10 +998ms
  serialport:unixRead waiting for readable because of code: EAGAIN +11ms
  serialport:poller Polling for "readable" +25ms
  serialport:unixWrite write returned null 10 +2ms
  serialport:unixWrite wrote 10 bytes +1ms
  serialport:unixWrite Finished writing 10 bytes +0ms
  serialport:main binding.write write finished +4ms
  serialport:poller received "readable" +7ms
  serialport:bindings read +10ms
  serialport:unixRead Starting read +9ms
  serialport:unixRead Finished read 6 bytes +1ms
  serialport:main binding.read finished +8ms
  cc-znp { sof: 254,
  cc-znp   len: 1,
  cc-znp   type: 'SRSP',
  cc-znp   subsys: 'ZDO',
  cc-znp   cmd: 'simpleDescReq',
  cc-znp   payload: { status: 0 },
  cc-znp   fcs: 96,
  cc-znp   csum: 96 } +20ms
  serialport:main _read reading +7ms
  serialport:bindings read +10ms
  serialport:unixRead Starting read +8ms
  cc-znp:SRSP <-- ZDO:simpleDescReq, { status: 0 } +4ms
  serialport:unixRead waiting for readable because of code: EAGAIN +3ms
  serialport:poller Polling for "readable" +13ms
  serialport:poller received "readable" +871ms
  serialport:bindings read +874ms
  serialport:unixRead Starting read +876ms
  serialport:unixRead Finished read 18 bytes +1ms
  serialport:main binding.read finished +881ms
  cc-znp { sof: 254,
  cc-znp   len: 13,
  cc-znp   type: 'AREQ',
  cc-znp   subsys: 'ZDO',
  cc-znp   cmd: 'leaveInd',
  cc-znp   payload:
  cc-znp    { srcaddr: 16252,
  cc-znp      extaddr: '0x000d6f000e0597b7',
  cc-znp      request: 0,
  cc-znp      removechildren: 0,
  cc-znp      rejoin: 0 },
  cc-znp   fcs: 139,
  cc-znp   csum: 139 } +883ms
  serialport:main _read reading +6ms
  serialport:bindings read +12ms
  serialport:unixRead Starting read +7ms
  cc-znp:AREQ <-- ZDO:leaveInd, { srcaddr: 16252, extaddr: '0x000d6f000e0597b7', request: 0, removechildren: 0, rejoin: 0 } +4ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:leaveInd +1ms
  serialport:unixRead waiting for readable because of code: EAGAIN +8ms
  serialport:poller Polling for "readable" +21ms
  zigbee2mqtt:error 2018-11-1 22:48:51 Not connected to MQTT server!
  serialport:poller received "readable" +8s
  serialport:bindings read +8s
  serialport:unixRead Starting read +8s
  serialport:unixRead Finished read 17 bytes +2ms
  serialport:main binding.read finished +8s
  cc-znp { sof: 254,
  cc-znp   len: 12,
  cc-znp   type: 'AREQ',
  cc-znp   subsys: 'ZDO',
  cc-znp   cmd: 'tcDeviceInd',
  cc-znp   payload: { nwkaddr: 61832, extaddr: '0x000d6f000e0597b7', parentaddr: 0 },
  cc-znp   fcs: 179,
  cc-znp   csum: 179 } +8s
  serialport:main _read reading +10ms
  serialport:bindings read +13ms
  serialport:unixRead Starting read +10ms
  cc-znp:AREQ <-- ZDO:tcDeviceInd, { nwkaddr: 61832, extaddr: '0x000d6f000e0597b7', parentaddr: 0 } +5ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd +2ms
  serialport:unixRead waiting for readable because of code: EAGAIN +4ms
  serialport:poller Polling for "readable" +18ms
  serialport:poller received "readable" +406ms
  serialport:bindings read +411ms
  serialport:unixRead Starting read +407ms
  serialport:unixRead Finished read 18 bytes +1ms
  serialport:main binding.read finished +413ms
  cc-znp { sof: 254,
  cc-znp   len: 13,
  cc-znp   type: 'AREQ',
  cc-znp   subsys: 'ZDO',
  cc-znp   cmd: 'endDeviceAnnceInd',
  cc-znp   payload:
  cc-znp    { srcaddr: 61832,
  cc-znp      nwkaddr: 61832,
  cc-znp      ieeeaddr: '0x000d6f000e0597b7',
  cc-znp      capabilities: 128 },
  cc-znp   fcs: 64,
  cc-znp   csum: 64 } +416ms
  serialport:main _read reading +9ms
  serialport:bindings read +12ms
  serialport:unixRead Starting read +11ms
  cc-znp:AREQ <-- ZDO:endDeviceAnnceInd, { srcaddr: 61832, nwkaddr: 61832, ieeeaddr: '0x000d6f000e0597b7', capabilities: 128 } +6ms
  zigbee-shepherd spinlock: true [] +1ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:endDeviceAnnceInd +1ms
  serialport:unixRead waiting for readable because of code: EAGAIN +5ms
  serialport:poller Polling for "readable" +19ms
  zigbee-shepherd:request REQ --> ZDO:nodeDescReq +669ms
  cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 16252, nwkaddrofinterest: 16252 } +2ms
  serialport:main _write 9 bytes of data +679ms
  serialport:bindings write 9 bytes +679ms
  serialport:unixWrite Starting write 9 bytes offset 0 bytesToWrite 9 +10s
  serialport:unixWrite write returned null 9 +1ms
  serialport:unixWrite wrote 9 bytes +1ms
  serialport:unixWrite Finished writing 9 bytes +0ms
  serialport:main binding.write write finished +4ms
  serialport:poller received "readable" +689ms
  serialport:bindings read +16ms
  serialport:unixRead Starting read +692ms
  serialport:unixRead Finished read 6 bytes +1ms
  serialport:main binding.read finished +17ms
  cc-znp { sof: 254,
  cc-znp   len: 1,
  cc-znp   type: 'SRSP',
  cc-znp   subsys: 'ZDO',
  cc-znp   cmd: 'nodeDescReq',
  cc-znp   payload: { status: 0 },
  cc-znp   fcs: 102,
  cc-znp   csum: 102 } +48ms
  serialport:main _read reading +27ms
  serialport:bindings read +31ms
  serialport:unixRead Starting read +29ms
  cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +5ms
  serialport:unixRead waiting for readable because of code: EAGAIN +3ms
  serialport:poller Polling for "readable" +35ms
  zigbee2mqtt:error 2018-11-1 22:49:01 Not connected to MQTT server!
  serialport:poller received "readable" +3s
  serialport:bindings read +3s
  serialport:unixRead Starting read +3s
  serialport:unixRead Finished read 18 bytes +2ms
  serialport:main binding.read finished +3s
  cc-znp { sof: 254,
  cc-znp   len: 13,
  cc-znp   type: 'AREQ',
  cc-znp   subsys: 'ZDO',
  cc-znp   cmd: 'leaveInd',
  cc-znp   payload:
  cc-znp    { srcaddr: 61832,
  cc-znp      extaddr: '0x000d6f000e0597b7',
  cc-znp      request: 0,
  cc-znp      removechildren: 0,
  cc-znp      rejoin: 0 },
  cc-znp   fcs: 177,
  cc-znp   csum: 177 } +3s
  serialport:main _read reading +12ms
  serialport:bindings read +16ms
  serialport:unixRead Starting read +14ms
  cc-znp:AREQ <-- ZDO:leaveInd, { srcaddr: 61832, extaddr: '0x000d6f000e0597b7', request: 0, removechildren: 0, rejoin: 0 } +7ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:leaveInd +3ms
  serialport:unixRead waiting for readable because of code: EAGAIN +5ms
  serialport:poller Polling for "readable" +24ms
  zigbee2mqtt:error 2018-11-1 22:49:09 Cannot get the Node Descriptor of the Device: 0x000d6f000e0597b7 (Error: Timed out after 10000 ms)

does it help?

dcsg commented 6 years ago

@Koenkk anything I can do to help?

Koenkk commented 6 years ago

This device probably requires an enroll request (as explained here: https://github.com/zigbeer/zigbee-shepherd/issues/8). As I don't have the device, it is hard for me to work further on this.

ViP3R76 commented 5 years ago

What do you need to get it working? Is a ssh session to my server useful to get it working? Or a teamviewer session?

Koenkk commented 5 years ago

@ToTXR4Y can you check if joining works in the: https://github.com/Koenkk/zigbee2mqtt/tree/osram_motion branch?

nebman commented 5 years ago

@Koenkk looks like it's connected! 😃 

  zigbee2mqtt:info 30/11/2018, 19:31:44 MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"device incoming"}'
  zigbee2mqtt:info 30/11/2018, 19:31:44 New device with address 0x000d6f000f710e13 connected!
  zigbee2mqtt:info 30/11/2018, 19:31:44 MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_connected","message":"0x000d6f000f710e13"}'
  zigbee2mqtt:warn 30/11/2018, 19:31:44 Device with modelID 'Motion Sensor-A' is not supported.
  zigbee2mqtt:warn 30/11/2018, 19:31:44 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices
  zigbee2mqtt:debug 30/11/2018, 19:31:44 Received zigbee message of type 'devStatus' with data '"online"' of device 'Motion Sensor-A' (0x000d6f000f710e13)
  zigbee2mqtt:warn 30/11/2018, 19:31:44 Device with modelID 'Motion Sensor-A' is not supported.
  zigbee2mqtt:warn 30/11/2018, 19:31:44 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices
nebman commented 5 years ago

Tried to write a converter but I couldn't get it to trigger any kind of message...
Also the device seems to need a repairing after software restart.

Koenkk commented 5 years ago

Can you try with

    {
        zigbeeModel: ['Motion Sensor-A'],
        model: 'Motion Sensor-A',
        vendor: 'OSRAM',
        description: 'Motion detector',
        supports: 'occupancy',
        fromZigbee: [],
        toZigbee: [],
        configure: (ieeeAddr, shepherd, coordinator, callback) => {
            const device = shepherd.find(ieeeAddr, 1);
            const actions = [
                (cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb),
                (cb) => device.functional('ssIasZone', 'enrollRsp', {enrollrspcode: 0, zoneid: 23}, cb),
            ];
             execute(device, actions, callback, 1000);
        },
    },
nebman commented 5 years ago

awesome 😄 I am now working on the converters

  zigbee2mqtt:debug 30/11/2018, 20:58:55 Received zigbee message of type 'statusChange' with data '{"cid":"ssIasZone","zoneStatus":38}' of device 'Motion Sensor-A' (0x000d6f000f710e13)
  zigbee2mqtt:warn 30/11/2018, 20:58:55 No converter available for 'AC01353010G' with cid 'ssIasZone', type 'statusChange' and data '{"cid":"ssIasZone","zoneStatus":38}'
  zigbee2mqtt:warn 30/11/2018, 20:58:55 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
  zigbee2mqtt:debug 30/11/2018, 20:58:55 Received zigbee message of type 'devChange' with data '{"cid":"ssIasZone","data":{"zoneState":1,"zoneType":13,"zoneStatus":38,"iasCieAddr":"0x00124b0018ed3c2e","zoneId":23}}' of device 'Motion Sensor-A' (0x000d6f000f710e13)
  zigbee2mqtt:warn 30/11/2018, 20:58:55 No converter available for 'AC01353010G' with cid 'ssIasZone', type 'devChange' and data '{"cid":"ssIasZone","data":{"zoneState":1,"zoneType":13,"zoneStatus":38,"iasCieAddr":"0x00124b0018ed3c2e","zoneId":23}}'
  zigbee2mqtt:warn 30/11/2018, 20:58:55 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.

  zigbee2mqtt:debug 30/11/2018, 21:05:20 Received zigbee message of type 'attReport' with data '{"cid":"msTemperatureMeasurement","data":{"measuredValue":2465}}' of device 'Motion Sensor-A' (0x000d6f000f710e13)
  zigbee2mqtt:warn 30/11/2018, 21:05:20 No converter available for 'AC01353010G' with cid 'msTemperatureMeasurement', type 'attReport' and data '{"cid":"msTemperatureMeasurement","data":{"measuredValue":2465}}'
  zigbee2mqtt:warn 30/11/2018, 21:05:20 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
  zigbee2mqtt:debug 30/11/2018, 21:05:20 Received zigbee message of type 'devChange' with data '{"cid":"msTemperatureMeasurement","data":{"measuredValue":2465}}' of device 'Motion Sensor-A' (0x000d6f000f710e13)
  zigbee2mqtt:warn 30/11/2018, 21:05:20 No converter available for 'AC01353010G' with cid 'msTemperatureMeasurement', type 'devChange' and data '{"cid":"msTemperatureMeasurement","data":{"measuredValue":2465}}'
  zigbee2mqtt:warn 30/11/2018, 21:05:20 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.

  zigbee2mqtt:error 30/11/2018, 21:08:41 Failed to configure MOTION-OSRAM 0x000d6f000f710e13
  zigbee2mqtt:debug 30/11/2018, 21:08:43 Received zigbee message of type 'devChange' with data '{"cid":"ssIasZone","data":{"zoneState":1,"zoneType":13,"zoneStatus":38,"iasCieAddr":"0x00124b0018ed3c2e","zoneId":23}}' of device 'Motion Sensor-A' (0x000d6f000f710e13)
  zigbee2mqtt:warn 30/11/2018, 21:08:43 No converter available for 'AC01353010G' with cid 'ssIasZone', type 'devChange' and data '{"cid":"ssIasZone","data":{"zoneState":1,"zoneType":13,"zoneStatus":38,"iasCieAddr":"0x00124b0018ed3c2e","zoneId":23}}'
  zigbee2mqtt:warn 30/11/2018, 21:08:43 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.

  zigbee2mqtt:debug 30/11/2018, 21:11:31 Received zigbee message of type 'statusChange' with data '{"cid":"ssIasZone","zoneStatus":36}' of device 'Motion Sensor-A' (0x000d6f000f710e13)
  zigbee2mqtt:warn 30/11/2018, 21:11:31 No converter available for 'AC01353010G' with cid 'ssIasZone', type 'statusChange' and data '{"cid":"ssIasZone","zoneStatus":36}'
  zigbee2mqtt:warn 30/11/2018, 21:11:31 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
  zigbee2mqtt:debug 30/11/2018, 21:12:03 Received zigbee message of type 'statusChange' with data '{"cid":"ssIasZone","zoneStatus":38}' of device 'Motion Sensor-A' (0x000d6f000f710e13)
  zigbee2mqtt:warn 30/11/2018, 21:12:03 No converter available for 'AC01353010G' with cid 'ssIasZone', type 'statusChange' and data '{"cid":"ssIasZone","zoneStatus":38}'
  zigbee2mqtt:warn 30/11/2018, 21:12:03 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
Koenkk commented 5 years ago

Great! 😄

nebman commented 5 years ago 
  zigbee2mqtt:info 30/11/2018, 22:20:19 Mount the cieApp, epId: 11
  zigbee2mqtt:error 30/11/2018, 22:20:24 Failed to configure MOTION-OSRAM 0x000d6f000f710e13
  zigbee2mqtt:debug 30/11/2018, 22:20:26 Received zigbee message of type 'devChange' with data '{"cid":"ssIasZone","data":{"zoneState":1,"zoneType":13,"zoneStatus":38,"iasCieAddr":"0x00124b0018ed3c2e","zoneId":23}}' of device 'Motion Sensor-A' (0x000d6f000f710e13)
  zigbee2mqtt:info 30/11/2018, 22:20:26 MQTT publish: topic 'zigbee2mqtt/MOTION-OSRAM', payload '{"occupancy":true,"battery":"OK","linkquality":110,"temperature":23.62,"tamper":true}'

As of now I got this working. Still showing "Failed to configure" despite working.... 🤔
Just wondering... why does it retain the temperature property when it should be reported from another converter?

Also: I don't know what the tampering flag does... When you press the button for longer than 2 sec it will flip to false but switches back to true immediately after releasing the button. Shouldn't it be the other way round? 😅 According to the manual it should reset the device when presssing 10s, but as I see this, it just sends this flag, no reset possible other than removing the battery.

Koenkk commented 5 years ago

Can you provide the log with DEBUG=* npm start? That will show why the configure failed..

nebman commented 5 years ago

(So many loglines with 12 devices in this network 😅)

I could isolate it to the following lines, if you need more just let me know

  zigbee-shepherd-converters:devices Configured '(cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb)' with result 'Error: request unsuccess: 112' +0ms
  zigbee2mqtt:error 01/12/2018, 10:43:23 Failed to configure MOTION-OSRAM 0x000d6f000f710e13
Koenkk commented 5 years ago

Can you check again with the updated https://github.com/Koenkk/zigbee2mqtt/tree/osram_motion branch. Please repair the device.

nebman commented 5 years ago

Fantastic work @Koenkk!

  zigbee2mqtt:info 01/12/2018, 15:31:48 Mounted the cie app, (epId {epId})
  zigbee2mqtt:info 01/12/2018, 15:31:51 MQTT publish: topic 'zigbee2mqtt/MOTION-OSRAM', payload '{"occupancy":true,"tamper":true,"battery_low":false,"linkquality":105}'
  zigbee2mqtt:info 01/12/2018, 15:32:00 MQTT publish: topic 'zigbee2mqtt/MOTION-OSRAM', payload '{"occupancy":true,"tamper":true,"battery_low":false,"linkquality":105}'
  zigbee2mqtt:info 01/12/2018, 15:32:01 MQTT publish: topic 'zigbee2mqtt/MOTION-OSRAM', payload '{"occupancy":true,"tamper":false,"battery_low":false,"linkquality":105}'
  zigbee2mqtt:info 01/12/2018, 15:32:02 MQTT publish: topic 'zigbee2mqtt/MOTION-OSRAM', payload '{"occupancy":true,"tamper":true,"battery_low":false,"linkquality":105}'
  zigbee2mqtt:info 01/12/2018, 15:32:03 MQTT publish: topic 'zigbee2mqtt/MOTION-OSRAM', payload '{"occupancy":true,"tamper":false,"battery_low":false,"linkquality":105}'
  zigbee2mqtt:info 01/12/2018, 15:32:03 Succesfully configured MOTION-OSRAM 0x000d6f000f710e13
  zigbee2mqtt:info 01/12/2018, 15:32:03 MQTT publish: topic 'zigbee2mqtt/MOTION-OSRAM', payload '{"occupancy":true,"tamper":false,"battery_low":false,"linkquality":105,"temperature":23.79}'

After removing and (somehow) pairing the device again, I had to restart zigbee2mqtt before receiving any messages. But now it looks very good.

Should I send you a pull request to zigbee-shepherd-converters?

In the devices.js file I had two additional line for temperature reporting, copied those off another device at first and I'm not sure the are necessary? But they dont generate any error message either...

configure: (ieeeAddr, shepherd, coordinator, callback) => {
            const device = shepherd.find(ieeeAddr, 1);
            const actions = [
                (cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb),
                (cb) => device.functional('ssIasZone', 'enrollRsp', {enrollrspcode: 0, zoneid: 23}, cb),
                (cb) => device.bind('msTemperatureMeasurement', coordinator, cb),
                (cb) => device.report('msTemperatureMeasurement', 'measuredValue', 30, 600, 1, cb),
            ];
            execute(device, actions, callback);
        },
Koenkk commented 5 years ago

Looks good, you can keep the bind and report for msTemperatureMeasurement.

What does tamper/battery_low mean? How do you get to these messages? For the battery I would prefer a % (to keep it the same as other devices)

nebman commented 5 years ago

See https://www.nxp.com/docs/en/user-guide/JN-UG-3077.pdf page 459 has a table of flags for b16ZoneStatus where I took the information from. ZoneStatusis the only property that gets transmitted. The device just sends a bit for "Battery OK" or "Battery Low", same for the "Tampered" status (which I observed just indicates a longer button press on this device?!).

ViP3R76 commented 5 years ago

Tamper should be an "opening" detection of the device itself.

nebman commented 5 years ago

Tamper should be an "opening" detection of the device itself.

Can't really see any switch or detection mechanism on the inside @ToTXR4Y

nebman commented 5 years ago

Just hooked the device up to a lab power supply and confirmed it will send a battery_low=true flag. Down at around 1.8V it stops working.

Koenkk commented 5 years ago

Does battery reporting work with:

    {
        zigbeeModel: ['Motion Sensor-A'],
        model: 'Motion Sensor-A',
        vendor: 'OSRAM',
        description: 'Motion detector',
        supports: 'occupancy',
        fromZigbee: [],
        toZigbee: [],
        configure: (ieeeAddr, shepherd, coordinator, callback) => {
            const device = shepherd.find(ieeeAddr, 1);
            const actions = [
                (cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb),
                (cb) => device.functional('ssIasZone', 'enrollRsp', {enrollrspcode: 0, zoneid: 23}, cb),
                (cb) => device.bind('msTemperatureMeasurement', coordinator, cb),
                (cb) => device.report('msTemperatureMeasurement', 'measuredValue', 30, 600, 1, cb),
                (cb) => device.bind('genPowerCfg', coordinator, cb),
                (cb) => device.report('genPowerCfg', 'batteryPercentageRemaining', 0, 1000, 0, cb),
            ];
             execute(device, actions, callback, 1000);
        },
    },
nebman commented 5 years ago

After trying about an hour to re-pair the motion sensor, I am now back at 

  zigbee-shepherd-converters:devices Configured '(cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb)' with result 'Error: request unsuccess: 112' +0ms
  zigbee2mqtt:error 01/12/2018, 20:20:45 Failed to configure 0x000d6f000f710e13 0x000d6f000f710e13

I dont know... this thing is slowly driving me insane and I need a break now ☹️ At least messages are arriving (but no battery status), so I will post the converters and other can try their luck too 😅

johnnyletrois commented 5 years ago

I got the Iris motion/temp sensor working based on your work @nebman and @koenkk. See here: https://github.com/Koenkk/zigbee2mqtt/issues/600#issuecomment-443520206

Thanks!

nebman commented 5 years ago

Just caught this genPowerCfg reports, but wont seem worthwhile to really add, looks like just another low battery warning?

Dec 04 20:35:35 rpi-home npm[19950]:   zigbee2mqtt:debug 04/12/2018, 20:35:35 Received zigbee message of type 'attReport' with data '{"cid":"genPowerCfg","data":{"batteryAlarmState":0}}' of device 'Motion Sensor-A' (0x000d6f000f710e13)
Dec 04 20:35:35 rpi-home npm[19950]:   zigbee2mqtt:warn 04/12/2018, 20:35:35 No converter available for 'AC01353010G' with cid 'genPowerCfg', type 'attReport' and data '{"cid":"genPowerCfg","data":{"batteryAlarmState":0}}'
Dec 04 20:35:35 rpi-home npm[19950]:   zigbee2mqtt:warn 04/12/2018, 20:35:35 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
Dec 04 20:35:35 rpi-home npm[19950]:   zigbee2mqtt:debug 04/12/2018, 20:35:35 Received zigbee message of type 'devChange' with data '{"cid":"genPowerCfg","data":{"batteryAlarmState":0}}' of device 'Motion Sensor-A' (0x000d6f000f710e13)
Dec 04 20:35:35 rpi-home npm[19950]:   zigbee2mqtt:warn 04/12/2018, 20:35:35 No converter available for 'AC01353010G' with cid 'genPowerCfg', type 'devChange' and data '{"cid":"genPowerCfg","data":{"batteryAlarmState":0}}'
Koenkk commented 5 years ago

Doesn't look important indeed, we can ignore this message by adding an ignore converter.

nebman commented 5 years ago

I can add that and push it. But I will watch the logs a bit more just in case there are also other uncaught messages.

dcsg commented 5 years ago

What is missing here in order to get released?

Koenkk commented 5 years ago

It's supported in the dev branch now, will be part of the next release.

Morphy99 commented 5 years ago

I'm using the Hass.io Add-on zigbee2mqtt-edge and I get this error still:

Cannot get the Node Descriptor of the Device: 0x000d6f000e056cfd (Error: Timed out after 10000 ms)

EDIT: I tried pairing it again and now got it connected but this shows in log: Failed to configure 0x000d6f000e056cfd 0x000d6f000e056cfd

johnnyletrois commented 5 years ago

@Morphy99 it should work even with the error. Try it out.

Morphy99 commented 5 years ago

Hmm so it appears to be added but not doing anything. I also have a temp sensor in devices as well!? Powering on and off just shows

zigbee2mqtt:warn 2019-1-5 10:27:58 Message without device!

All I have in state attributes is

{ "friendly_name": "PIR Sensor", "device_class": "motion" }

Can't see any mqtt messages in the log either.

I've set an automation up with this but nothing either:

trigger:
  - entity_id: binary_sensor.0x000d6f000e056cfd_occupancy
    platform: state
    to: 'on'
  action:
    service: homeassistant.turn_on
    entity_id: light.spot1_light_2
dreimer1986 commented 5 years ago

I second the mentioned behavior in NOT edge, but most recent stable on most recent Hass.IO on firmware 24122018: https://hastebin.com/repifinoga.apache After the error I get my two new devices: motion and temperature but both stay silent completely.

nebman commented 5 years ago

@Morphy99 maybe it's not paired correctly? Try repairing it.

One note though, I think the instructions given in the manual are not correct, holding the button for >10sec did nothing for me.
I guess to fully reset the device you can try holding the button while inserting the battery. The status light will change to some kind of red or purple IIRC

Morphy99 commented 5 years ago

I've done that a few times, I even had the red/purple light you mention but no I idea what that means. AFAIK the pairing mode is when the blue light flashes three times then once it connects it goes to solid green for a second and then off. This is all I get:

zigbee2mqtt:info 2019-1-8 18:15:49 Device incoming... zigbee2mqtt:info 2019-1-8 18:15:49 MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"device incoming"}' zigbee2mqtt:info 2019-1-8 18:15:49 MQTT publish: topic 'homeassistant/binary_sensor/0x000d6f000e056cfd/occupancy/config', payload '{"payload_on":true,"payload_off":false,"value_template":"{{ value_json.occupancy }}","device_class":"motion","state_topic":"zigbee2mqtt/0x000d6f000e056cfd","availability_topic":"zigbee2mqtt/bridge/state","name":"0x000d6f000e056cfd_occupancy","unique_id":"0x000d6f000e056cfd_occupancy_zigbee2mqtt","device":{"identifiers":"zigbee2mqtt_0x000d6f000e056cfd","name":"0x000d6f000e056cfd","sw_version":"Zigbee2mqtt 1.0.1","model":"SMART+ Motion Sensor (AC01353010G)","manufacturer":"OSRAM"}}' zigbee2mqtt:info 2019-1-8 18:15:49 MQTT publish: topic 'homeassistant/sensor/0x000d6f000e056cfd/temperature/config', payload '{"unit_of_measurement":"°C","device_class":"temperature","value_template":"{{ value_json.temperature }}","json_attributes":["linkquality","battery","voltage"],"state_topic":"zigbee2mqtt/0x000d6f000e056cfd","availability_topic":"zigbee2mqtt/bridge/state","name":"0x000d6f000e056cfd_temperature","unique_id":"0x000d6f000e056cfd_temperature_zigbee2mqtt","device":{"identifiers":"zigbee2mqtt_0x000d6f000e056cfd","name":"0x000d6f000e056cfd","sw_version":"Zigbee2mqtt 1.0.1","model":"SMART+ Motion Sensor (AC01353010G)","manufacturer":"OSRAM"}}' zigbee2mqtt:error 2019-1-8 18:15:55 Failed to configure 0x000d6f000e056cfd 0x000d6f000e056cfd zigbee2mqtt:warn 2019-1-8 18:19:27 Message without device! zigbee2mqtt:warn 2019-1-8 18:20:22 Message without device! zigbee2mqtt:warn 2019-1-8 18:20:33 Message without device! zigbee2mqtt:warn 2019-1-8 18:20:36 Message without device! zigbee2mqtt:warn 2019-1-8 18:20:37 Message without device! zigbee2mqtt:warn 2019-1-8 18:20:46 Message without device! zigbee2mqtt:warn 2019-1-8 18:20:47 Message without device! zigbee2mqtt:warn 2019-1-8 18:20:53 Message without device! zigbee2mqtt:warn 2019-1-8 18:21:20 Message without device! zigbee2mqtt:warn 2019-1-8 18:21:27 Message without device!

Morphy99 commented 5 years ago

Ok it's connected finally! I removed the device by sending the zigbee2mqtt/bridge/config/remove topic and after a while after repairing this happened:

zigbee2mqtt:warn 2019-1-8 19:34:24 Message without device! zigbee2mqtt:warn 2019-1-8 19:34:34 Message without device! zigbee2mqtt:warn 2019-1-8 19:34:38 Message without device! zigbee2mqtt:warn 2019-1-8 19:34:40 Message without device! zigbee2mqtt:warn 2019-1-8 19:34:41 Message without device! zigbee2mqtt:warn 2019-1-8 19:35:13 Message without device! zigbee2mqtt:warn 2019-1-8 19:35:15 Message without device! zigbee2mqtt:warn 2019-1-8 19:35:17 Message without device! zigbee2mqtt:warn 2019-1-8 19:35:35 Message without device! zigbee2mqtt:warn 2019-1-8 19:35:39 Message without device! zigbee2mqtt:warn 2019-1-8 19:35:43 Message without device! zigbee2mqtt:warn 2019-1-8 19:35:45 Message without device! zigbee2mqtt:warn 2019-1-8 19:35:47 Message without device! zigbee2mqtt:warn 2019-1-8 19:36:00 Message without device! zigbee2mqtt:info 2019-1-8 19:36:00 Device incoming... zigbee2mqtt:info 2019-1-8 19:36:00 MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"device incoming"}' zigbee2mqtt:info 2019-1-8 19:36:00 MQTT publish: topic 'homeassistant/binary_sensor/0x000d6f000e056cfd/occupancy/config', payload '{"payload_on":true,"payload_off":false,"value_template":"{{ value_json.occupancy }}","device_class":"motion","state_topic":"zigbee2mqtt/0x000d6f000e056cfd","availability_topic":"zigbee2mqtt/bridge/state","name":"0x000d6f000e056cfd_occupancy","unique_id":"0x000d6f000e056cfd_occupancy_zigbee2mqtt","device":{"identifiers":"zigbee2mqtt_0x000d6f000e056cfd","name":"0x000d6f000e056cfd","sw_version":"Zigbee2mqtt 1.0.1","model":"SMART+ Motion Sensor (AC01353010G)","manufacturer":"OSRAM"}}' zigbee2mqtt:info 2019-1-8 19:36:00 MQTT publish: topic 'homeassistant/sensor/0x000d6f000e056cfd/temperature/config', payload '{"unit_of_measurement":"°C","device_class":"temperature","value_template":"{{ value_json.temperature }}","json_attributes":["linkquality","battery","voltage"],"state_topic":"zigbee2mqtt/0x000d6f000e056cfd","availability_topic":"zigbee2mqtt/bridge/state","name":"0x000d6f000e056cfd_temperature","unique_id":"0x000d6f000e056cfd_temperature_zigbee2mqtt","device":{"identifiers":"zigbee2mqtt_0x000d6f000e056cfd","name":"0x000d6f000e056cfd","sw_version":"Zigbee2mqtt 1.0.1","model":"SMART+ Motion Sensor (AC01353010G)","manufacturer":"OSRAM"}}' zigbee2mqtt:info 2019-1-8 19:36:02 MQTT publish: topic 'zigbee2mqtt/0x000d6f000e056cfd', payload '{"occupancy":true,"tamper":false,"battery_low":false,"linkquality":60}'

dreimer1986 commented 5 years ago

Yeah, pairing the motion sensor is a real pain. Took me about 30 minutes to finally get it working. Now it runs fine and gives back motion and temperature. (And thus one thing more than before via Osram Gateway linked to Hass.IO)

Koenkk commented 5 years ago

To all: we need some help in order to verify a change which could have impact on this device.

Could you check when changing https://github.com/Koenkk/zigbee2mqtt/blob/master/lib/zapp/cie.js#L12 to 

cieClusters.init('ssIasZone', 'dir', {value: 1});

this device still works? Please re-pair after making this change.

wossix commented 5 years ago

@Koenkk, I did some first tests. But it doesn't look good. After changing ssIasZone to 1. I have tried to join a sensor multiple times - with no success.

Received: Timed out after 10000;

Cheers, Ben

Koenkk commented 5 years ago

@wossix thanks for testing, when changing it back, does it work again?

wossix commented 5 years ago

@Koenkk, yes.

Koenkk commented 5 years ago

@wossix thanks, we will leave it as is. :)

allofmex commented 5 years ago

pairing the motion sensor is a real pain. Took me about 30 minutes to finally get it working.

@dreimer1986 How did you managed to pair? I can't make it. Starting from fresh plugged cc2531, fresh shepherd instance (ioBroker in my case). Broker only says "Cannot get the Node Descriptor of the Device (Timed out after 10000ms)"

Did some sniffing:

Time | Source | Destination | Protocol |   | Info
11:03:40,125088 | 00:0d:6f:00:0e:63:a0:b9 | 0x0000 | IEEE 802.15.4 |   | Association Request, RFD
11:03:40,322863 | 00:0d:6f:00:0e:63:a0:b9 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:40,325542 | 00:12:4b:00:19:36:77:dc | 00:0d:6f:00:0e:63:a0:b9 | IEEE 802.15.4 |   | Association Response, PAN: 0x1a62 Addr: 0x9f01
11:03:40,342245 | 0x9f01 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:40,533247 | 0x9f01 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:40,669232 | 0x9f01 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:40,870101 | 0x9f01 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:41,063767 | 0x9f01 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:41,065671 | 0x9f01 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:41,068023 | 0x9f01 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:41,070088 | 0x9f01 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:41,107430 | 0x0000 | 0x9f01 | ZigBee |   | Transport Key
11:03:41,112218 | 0x0000 | 0x9f01 | ZigBee |   | Transport Key
11:03:41,117955 | 0x0000 | 0x9f01 | ZigBee |   | Transport Key
11:03:41,122115 | 0x0000 | 0x9f01 | ZigBee |   | Transport Key
11:03:41,258413 | 0x9f01 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:41,263054 | 0x0000 | 0x9f01 | ZigBee |   | Transport Key
11:03:41,328883 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:41,334531 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:41,348335 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:41,354538 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:41,362992 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:41,366576 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:41,370352 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:41,375946 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:41,399387 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:41,402507 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:41,408534 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:41,412571 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:41,422562 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:41,455791 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:41,463409 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:41,851761 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:41,857260 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:41,868297 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:41,873726 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:41,902561 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:41,914480 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:41,916874 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:41,919254 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:41,923330 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:41,942171 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:42,327510 | 0x9f01 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:42,329440 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:42,355359 | 0x9f01 | Broadcast | ZigBee ZDP |   | Device Announcement, Nwk Addr: 0x9f01, Ext Addr: Ember_00:0e:63:a0:b9
11:03:42,380246 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:43,130400 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:43,143322 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:43,147488 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:43,169774 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:43,174422 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:43,195724 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:43,333656 | 0x9f01 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:43,342542 | 0x0000 | 0x9f01 | ZigBee ZDP |   | Node Descriptor Request, Nwk Addr: 0x9f01
11:03:43,348632 | 0x9f01 | 0x0000 | ZigBee ZDP |   | Node Descriptor Response, Nwk Addr: 0x9f01, Status: Success
11:03:43,566535 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:43,642743 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:43,700203 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:44,058168 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:44,105169 | 0x9f01 | Broadcast | ZigBee ZDP |   | Match Descriptor Request, Nwk Addr: 0xfffd, Profile: 0x0104
11:03:44,337898 | 0x9f01 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:44,346821 | 0x0000 | 0x9f01 | ZigBee ZDP |   | Active Endpoint Request, Nwk Addr: 0x9f01
11:03:44,352533 | 0x9f01 | 0x0000 | ZigBee ZDP |   | Active Endpoint Response, Nwk Addr: 0x9f01, Status: Success
11:03:45,138328 | 0x9f01 | 0x0000 | ZigBee |   | Leave

Then it starts again...

11:03:52,519752 | 00:0d:6f:00:0e:63:a0:b9 | 0x0000 | IEEE 802.15.4 |   | Association Request, RFD
11:03:52,718920 | 00:0d:6f:00:0e:63:a0:b9 | 0x0000 | IEEE 802.15.4 |   | Data Request
11:03:52,721532 | 00:12:4b:00:19:36:77:dc | 00:0d:6f:00:0e:63:a0:b9 | IEEE 802.15.4 |   | Association Response, PAN: 0x1a62 Addr: 0x3856

Anyone an idea why it does not pair?