• State Not Answered
  • Replies 5 replies
  • Subscribers 88 subscribers
  • Views 1253 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 263555
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

ZigBee TCLK Authorization Timeout With signled sensor

WestCoastDaz

I am working with signled door sesnor and it supports ZigBee 3.0 as it has an install code and mac address on the side of the sensor in the form of a QR code.  When I run the ZigBee CLI in ZC mode and use the commands  bdb start and bdb ic add <code> <mac addr> the sensor doesn't join the network it looks like their is a TCLK failure.  The RTT logs have the following statements and Wireshark trace is below.  If the bdb legacy enable command is used then the sensor joins the network without issue.

<00> info> app: Device update received (short: 0x782F, long: b0ce1814000e8942, status: 1)

<00> info> app: Device update received (short: 0x782F, long: b0ce1814000e8942, status: 1)

<00> info> app: New device commissioned or rejoined (short: 0x782F)

 
<00> info> app: Device authorization event received (short: 0x782F, long: b0ce1814000e8942, authorization type: 0, authorization status: 0)

 
<00> info> app: Device authorization event received (short: 0x782F, long: b0ce1814000e8942, authorization type: 1, authorization status: 1)

 
<00> info> app: Child left the network (long: b0ce1814, rejoin flag: 0)

 
<00> info> app: Device authorization event received (short: 0x782F, long: b0ce1814000e8942, authorization type: 1, authorization status: 1)

 
<00> info> app: Device update received (short: 0x2BC4, long: b0ce1814000e8942, status: 1)

 
<00> info> app: Device update received (short: 0x2BC4, long: b0ce1814000e8942, status: 1)

 
<00> info> app: New device commissioned or rejoined (short: 0x2BC4)

 
<00> info> app: Device authorization event received (short: 0x2BC4, long: b0ce1814000e8942, authorization type: 0, authorization status: 0)

 
<00> info> app: Device authorization event received (short: 0x2BC4, long: b0ce1814000e8942, authorization type: 1, authorization status: 1)

 
<00> info> app: Child left the network (long: b0ce1814000e8942, rejoin flag: 0)

 
<00> info> app: Device authorization event received (short: 0x2BC4, long: b0ce1814000e8942, authorization type: 1, authorization status: 1)

 
<00> info> app: Device update received (short: 0x0224, long: b0ce1814, status: 1)

 
<00> info> app: Device update received (short: 0x0224, long: b0ce1814000e8942, status: 1)

 
<00> info> app: New device commissioned or rejoined (short: 0x0224)

 
<00> info> app: Device authorization event received (short: 0x0224, long: b0ce1814000e8942, authorization type: 0, authorization status: 0)

 
<00> info> app: Device authorization event received (short: 0x0224, long: b0ce1814000e8942, authorization type: 1, authorization status: 1)

 
<00> info> app: Child left the network (long: b0ce1814000e8942, rejoin flag: 0)

 
<00> info> app: Device authorization event received (short: 0x0224, long: b0ce1814000e8942, authorization type: 1, authorization status: 1)

 
<00> info> app: Device update received (short: 0x1DD0, long: b0ce1814000e8942, status: 1)

 
<00> info> app: Device update received (short: 0x1DD0, long: b0ce1814000e8942, status: 1)

 
<00> info> app: New device commissioned or rejoined (short: 0x1DD0)

 
<00> info> app: Device authorization event received (short: 0x1DD0, long: b0ce1814, authorization type: 0, authorization status: 0)

 
<00> info> app: Device authorization event received (short: 0x1DD0, long: b0ce1814000e8942, authorization type: 1, authorization status: 1)

 
<00> info> app: Child left the network (long: b0ce1814000e8942, rejoin flag: 0)

 
<00> info> app: Device authorization event received (short: 0x1DD0, long: b0ce1814000e8942, authorization type: 1, authorization status: 1)

 
<00> info> app: Device update received (short: 0x6D8D, long: b0ce1814000e8942, status: 1)

 
<00> info> app: Device update received (short: 0x6D8D, long: b0ce1814000e8942, status: 1)

 
<00> info> app: New device commissioned or rejoined (short: 0x6D8D)

 
<00> info> app: Device authorization event received (short: 0x6D8D, long: b0ce1814000e8942, authorization type: 0, authorization status: 0)

 
<00> info> app: Device authorization event received (short: 0x6D8D, long: b0ce1814000e8942, authorization type: 1, authorization status: 1)

 
<00> info> app: Child left the network (long: b0ce1814, rejoin flag: 0)

 
<00> info> app: Device authorization event received (short: 0x6D8D, long: b0ce1814000e8942, authorization type: 1, authorization status: 1)

 
<00> info> app: Device update received (short: 0x4226, long: b0ce1814000e8942, status: 1)

 
<00> info> app: Device update received (short: 0x4226, long: b0ce1814000e8942, status: 1)

 
<00> info> app: New device commissioned or rejoined (short: 0x4226)


sengled_join_failure.pcapng

Thoughts?

Parents
  • 0

    Hello,

    What did the function that added the IC return? Is the doorlock running on an nRF, or is it an off the shelf product?

    If it is an nRF, how did you add the IC on the doorlock?

    I have an old modified example running on the 4.1.0 SDK that implemented ICs on the light control example. 

    Perhaps you can try these on a couple of DKs, so you know that you are setting up the ICs correctly.

    light_control_ic.zip

    Did you create the doorlocks yourself?

    BR,

    Edvin

Reply
  • 0

    Hello,

    What did the function that added the IC return? Is the doorlock running on an nRF, or is it an off the shelf product?

    If it is an nRF, how did you add the IC on the doorlock?

    I have an old modified example running on the 4.1.0 SDK that implemented ICs on the light control example. 

    Perhaps you can try these on a couple of DKs, so you know that you are setting up the ICs correctly.

    light_control_ic.zip

    Did you create the doorlocks yourself?

    BR,

    Edvin

Children
  • 0 in reply to Edvin

    I am not using the door lock example, I am using the ZigBee CLI example on an nRF52840 DK as a ZigBee coordinator.  I am trying to get the Singled door sensor to join my coordinator.  I used the bdb ic add <code> <mac addr> command where <code> was the install code and <mac addr> of the Signled sensor.  I got these by scanning the QR code on the sensor.

    I have successfully added many Samsung SmartThings sensors to my nRF DK coordinator using the install code command and I haven't had a join issue so I'm pretty sure my approach is correct.  

    Thoughts,

  • 0 in reply to WestCoastDaz
    WestCoastDaz said:
    I have successfully added many Samsung SmartThings sensors to my nRF DK coordinator using the install code command and I haven't had a join issue so I'm pretty sure my approach is correct.  

     Ok, that was the intention of sending that project, to make sure that you are using the correct approach.

    So the "Signled/Sengled door sensor" is a commercial product?

    So what does the call to the ic_add function return? (that is, the call to zb_secur_ic_add())

  • 0 in reply to Edvin

    Yes the singled door sensor is a commercially available product.  When i execute bdb add via the CLI I get Done just like the other times I have used it.

  • 0 in reply to WestCoastDaz

    And are you sure it is the correct IC that is added? 

    Perhaps you can try to capture another network trace, like we did in one of your earlier tickets here on DevZone? I don't remember the details on what we were looking into in that ticket, but I remember that we needed to use a custom debug library. Do you still have that?

    BR,

    Edvin

Related