Unable to bind Zigbee end devices when using softdevice

Question

Hello Nordic team, 
 I have a Nordic Zigbee application that uses libzboss.a and nrf_radio_driver_softdevice.a , with Nordic working as a coordinator. With this application, I was able to bind Zigbee end devices such as motion sensor, window sensor etc and able to receive data from them. 
 Later, I added softdevice s140 to my application as I wanted my application to be able to operate in either BLE mode or Zigbee mode. After adding softdevice, I had to change the radio driver to nrf_radio_driver_softdevice.a. In this new application, there is no change in code with respect to Zigbee functionality. However, I am no longer able to bind Zigbee end devices. Could you please let me know if there are any changes to be done when using Softdevice and Nordic is operating as a Zigbee coordinator? 
 Regards, 
 Anusha

AHaug · Accepted Answer

Hi, An update from me 
 anusha_14 said: I went through this link and I don't think all the points mentioned in this page are applicable in my case because there is no switching between protocols and from what I understand from an earlier question posted to Nordic support is that, full radio control is available to whichever protocol is running (in the case where only protocol is active). 
 Thank you for reminding me about the previous case for more background information and that we've discussed your project previously. 
 If it is possible it might be easier to redesign parts of your application to be able to use the multiprotocol, but lets investigate this issue first! 
 anusha_14 said: In BLE mode, the functionality works fine as I can see that bonding to a device works fine, able to perform GATT read and write, perform scanning and advertising. But in Zigbee mode, the functionality seems to have changed as I can no longer bind a Zigbee end device. 
 How far have you gotten in the development? Are you able to for instance do: 
 
 Boot up as Zigbee device -> bind ZED -> Everything works as expected -> power cycle 
 Boot up as BLE device -> perform GATT read and write, scan and andvertise -> everything works as expected -> power cycle 
 Boot up as Zigbee device -> Binding does not work 
 
 If this is the case, there might be some renmants of the Zigbee device stored in the network that leads for the network to believe that the device is still in the network, and you might have to remove the ZED from the Zigbee network when you power cycle to become a BLE device, so that the network are able to identify the same ZED and reprovision it whenever you power cycle back to a Zigbee device. 
 Let me know if this points you in the correct direction and if you have any runtime logs and or Zigbee sniffer traces that you could post here that could indicate what is going on! 
 Kind regards, Andreas