• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 57 subscribers
  • Views 679 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LAUNCHXL-CC26X2R1: Pairing with CC2652RB development stick

David Racl
Prodigy 20 points
Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: SIMPLELINK-CC13X2-26X2-SDK

Hi,

I just bought a LAUNCHXL-CC26X2R1 board and want to pair to my Zigbee coordinator (CC2652RB development stick) with zigbee2mqtt firmware. I uploaded successfully "zed_sw" and "zed_light" demos to the board, but when I press the BTN-1 the searching process starts and counting from 180 to 0 and no pair success. Other zigbee devices like SONOFF SNZB-02 works perfectly. 

Any idea? What am I doing wrong? Thanks!

Board uart status:

Device Info: [IEEE Addr] 00124B00219FB207 [Power Mode] Sleepy
NWK Info: [PAN ID] 0x1a62 [Channel] 11 [Short Address] 0x96a0
NWK Info: [Parent Address] 0x0000
ZDO Info: [Logical Device] End Device [State] In the network
BDB Info: -- JOIN Id000 Srch173/00
Bind Info: --
APP Info: [Remote Light] 0xffff state is Unknown

In my coordinator I am getting only:

{
  "message": "announce",
  "meta": {
    "friendly_name": "0x00124b00219fb207"
  },
  "type": "device_announced"
}

OR

{
"data": {
"friendly_name": "0x00124b00219fb207",
"ieee_address": "0x00124b00219fb207"
},
"type": "device_announce"
}
  • 0
    Guru 735695 points

    Not sure what you mean by "no pair success." Since you can see device_announced in your gateway, it means device has tried to joins. If the following key exchange process goes well, the device should join successfully. For key exchange, you can use sniffer to check if it goes well.

  • 0
    TI__Guru**** 219527 points

    Hi David,

    Please provide sniffer logs of the working vs non-working devices and comment on what behavior you expect to see.  As YK mentioned, all user interfaces imply that the devices have commissioned properly and formed/joined a network.  Also, what SIMPLELINK-CC13X2-26X2-SDK are you evaluating with?   may be able to provide further zigbee2mqtt instructions.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 20 points

    Looks like I solved my problem to pair the device (there was none, I was just looking bad, because some configuration was missing). Sorry.

    Now I am trying to run zed_temperaturesensor demo, but my coordinator does not get any report from end device. BDB_REPORTING is enabled. Do I need to somehow create bind table (in zigbee2mqtt) to make periodically reports work?

    My SDK is 4.30.00.54

  • 0 in reply to David Racl
    TI__Guru**** 219527 points

    Your ZED temperature sensor needs to create a bind for the ZC, either because it finds a matching temperature measurement cluster on the client (BDB F&B) or because the ZNP sends a bind request (MT API from zigbee2mqtt interface).

    Regards,
    Ryan