No logs on the CLI coordinator that a new device has been added to the Zigbee network

[nickit94]

Hello,

I'm still just starting to deal with Zigbee and I have a question. I use 2 nRF52840 chips. One as a Zigbee Coordinator (CLI in SDK\examples\zigbee\experimental\cli\cli_agent_router), the second as a Zigbee Router (any example which is not a coordinator). SDK version 4.0.0.

I figured out some of the coordinator's commands and already learned how to manage the Zigbee Router through the console. Everything works. But I just can’t get any logs (in UART) from the coordinator about the fact that a new device has been added to the zigbee network! I see this only in the logs of the device itself (Zigbee Router - [<info> app: Joined network successfully (Extended PAN ID: f4ce369d28a86677, PAN ID: 0xEADF)]). I included all available logs and still there is nothing:

• log enable info zboss
• log enable info zigbee.cli
• log enable info zigbee.eprxzcl
• log enable info zigbee.ping
• log enable info zigbee.report

Example:

It was added to the network and wrote about this in log. Well done:

ZC. A device was added to him, but it is silent! Not well done:

Please, help!

Thanks in advance.

[Jørgen Holmefjord]

Hi,

Not everything is logged in the application, and some logs may only be provided in the "DEBUG" log level. Are you able to set the log level to DEBUG in the CLI? If not, you may have to enable this in the application and rebuild it.

If this does not work, I can also check if there are any lines in the firmware that log when a device is added to the ZC. Please let me know.

Best regards,
Jørgen

[nickit94]

Hi,

Thanks for the answer. Here is the full list of log levels that I found:

#define NRFX_CLOCK_CONFIG_LOG_LEVEL 3
#define NRFX_GPIOTE_CONFIG_LOG_LEVEL 3
#define NRFX_PRS_CONFIG_LOG_LEVEL 3
#define NRFX_RNG_CONFIG_LOG_LEVEL 3
#define NRFX_TIMER_CONFIG_LOG_LEVEL 3
#define NRFX_UARTE_CONFIG_LOG_LEVEL 3
#define NRFX_UART_CONFIG_LOG_LEVEL 3
#define NRF_MPU_LIB_CONFIG_LOG_LEVEL 3
#define NRF_STACK_GUARD_CONFIG_LOG_LEVEL 3
#define TASK_MANAGER_CONFIG_LOG_LEVEL 3
#define CLOCK_CONFIG_LOG_LEVEL 3
#define COMP_CONFIG_LOG_LEVEL 3
#define GPIOTE_CONFIG_LOG_LEVEL 3
#define LPCOMP_CONFIG_LOG_LEVEL 3
#define MAX3421E_HOST_CONFIG_LOG_LEVEL 3
#define NRFX_USBD_CONFIG_LOG_LEVEL 3
#define PDM_CONFIG_LOG_LEVEL 3
#define PPI_CONFIG_LOG_LEVEL 3
#define PWM_CONFIG_LOG_LEVEL 3
#define QDEC_CONFIG_LOG_LEVEL 3
#define RNG_CONFIG_LOG_LEVEL 3
#define RTC_CONFIG_LOG_LEVEL 3
#define SAADC_CONFIG_LOG_LEVEL 3
#define SPIS_CONFIG_LOG_LEVEL 3
#define SPI_CONFIG_LOG_LEVEL 3
#define TIMER_CONFIG_LOG_LEVEL 3
#define TWIS_CONFIG_LOG_LEVEL 3
#define TWI_CONFIG_LOG_LEVEL 3
#define UART_CONFIG_LOG_LEVEL 3
#define USBD_CONFIG_LOG_LEVEL 3
#define WDT_CONFIG_LOG_LEVEL 3
#define APP_BUTTON_CONFIG_LOG_LEVEL 3
#define APP_BUTTON_CONFIG_INITIAL_LOG_LEVEL 3
#define APP_TIMER_CONFIG_LOG_LEVEL 3
#define APP_TIMER_CONFIG_INITIAL_LOG_LEVEL 3
#define APP_USBD_CDC_ACM_CONFIG_LOG_LEVEL 3
#define APP_USBD_CONFIG_LOG_LEVEL 3
#define APP_USBD_DUMMY_CONFIG_LOG_LEVEL 3
#define APP_USBD_MSC_CONFIG_LOG_LEVEL 3
#define APP_USBD_NRF_DFU_TRIGGER_CONFIG_LOG_LEVEL 3
#define NRF_ATFIFO_CONFIG_LOG_LEVEL 3
#define NRF_BALLOC_CONFIG_LOG_LEVEL 3
#define NRF_BALLOC_CONFIG_INITIAL_LOG_LEVEL 3
#define NRF_BLOCK_DEV_EMPTY_CONFIG_LOG_LEVEL 3
#define NRF_BLOCK_DEV_QSPI_CONFIG_LOG_LEVEL 3
#define NRF_BLOCK_DEV_RAM_CONFIG_LOG_LEVEL 3
#define NRF_CLI_BLE_UART_CONFIG_LOG_LEVEL 3
#define NRF_CLI_LIBUARTE_CONFIG_LOG_LEVEL 3
#define NRF_CLI_UART_CONFIG_LOG_LEVEL 3
#define NRF_LIBUARTE_CONFIG_LOG_LEVEL 3
#define NRF_MEMOBJ_CONFIG_LOG_LEVEL 3
#define NRF_PWR_MGMT_CONFIG_LOG_LEVEL 3
#define NRF_QUEUE_CONFIG_LOG_LEVEL 3
#define NRF_SDH_ANT_LOG_LEVEL 3
#define NRF_SDH_BLE_LOG_LEVEL 3
#define NRF_SDH_LOG_LEVEL 3
#define NRF_SDH_SOC_LOG_LEVEL 3
#define NRF_SORTLIST_CONFIG_LOG_LEVEL 3
#define NRF_TWI_SENSOR_CONFIG_LOG_LEVEL 3
#define PM_LOG_LEVEL 3
#define SER_HAL_TRANSPORT_CONFIG_LOG_LEVEL 3
#define ZIGBEE_CLI_CONFIG_LOG_LEVEL 3

Of these related to CLI:

#define NRF_CLI_BLE_UART_CONFIG_LOG_LEVEL 3
#define NRF_CLI_LIBUARTE_CONFIG_LOG_LEVEL 3
#define NRF_CLI_UART_CONFIG_LOG_LEVEL 3
#define ZIGBEE_CLI_CONFIG_LOG_LEVEL 3

Later I will turn on all of them (CLI) level debug. But it seems to me that such an important event as the addition of a device to the network should be displayed without debug. Maybe I need to add some callback?

I will be very grateful if you can help me do this without a debugging level.

[nickit94]

I set all CLI logs to level 4 (debug), but still nothing works.

[nickit94]

Hi, Jørgen! 

Do you have any news for me? We're under a very strict deadline

[Jørgen Holmefjord]

Have you tried enabling logs for the app?

> log enable info app
> log enable info app
> bdb role zc
Coordinator set
Done
> bdb start
Started coordinator
Done
<info> app: Production configuration is not present or invalid (status: -1)
<info> app: Zigbee stack initialized
<info> app: Device started for the first time
<info> app: Start network formation
<info> app: Network formed successfully, start network steering (Extended PAN ID: f4ce3672196e95c0, PAN ID: 0xE4B2)
<info> app: Joined network successfully (Extended PAN ID: f4ce3672196e95c0, PAN ID: 0xE4B2)
<info> app: Device update received (short: 0x216B, long: f4ce36fc853b8177, status: 1)
<info> app: New device commissioned or rejoined (short: 0x216B)
<info> app: Device authorization event received (short: 0x216B, long: f4ce36fc853b8177, authorization type: 1, authorization status: 0)

I get the log "New device commissioned or rejoined (short: 0x216B)" on the coordinator when the router joins the network.

[nickit94]

Thank you very much, Jørgen, it really worked for me. It would be great if you document this information somewhere, because it is not obvious, but it is very important