cancel
Showing results for 
Search instead for 
Did you mean: 

NUCLEO-WBA55CG Zigbee_OnOff project - LED not blinking/toggling as expected

smishra125
Associate

I am working with the NUCLEO-WBA55CG board on a Zigbee_OnOff project, and I am facing an issue with the LED behavior.

Environment

  • Board: NUCLEO-WBA55CG
  • MCU: STM32WBA55CG
  • STM32CubeMX version: 6.17.0
  • Firmware package: STM32CubeWBA
  • Application type: Zigbee On/Off example / based project

The project is able to run, and Zigbee side behavior appears to be partially working, but the LED is not blinking/toggling as expected.

The problem is:

  • button press has no visible impact on the LED, or
  • Zigbee On/Off action does not toggle/blink the LED as expected

In my case, the issue looks more related to the GPIO / board mapping / callback path than to Zigbee network joining itself.

Screenshot 2026-03-15 165507.png

2 REPLIES 2
Imen.D
ST Employee

Hello @smishra125 

Make sure the GPIOs and physical connection are correctly mapped and configured in your project according to your board's schematic. For example, the Blue LED is PB4 and the user button is PC13. The LED pin configured as GPIO_OUTPUT, and the user button as GPIO_EXTI (external interrupt).

You can refer to the wiki articles related to Zigbee on STM32WBA Series.

When your question is answered, please close this topic by clicking "Accept as Solution".
Thanks
Imen

Hi,

Thanks for your response.

However, I would like to clarify something important:

If the Zigbee_OnOff example project provided in STM32CubeWBA is intended for the NUCLEO-WBA55CG board, then ideally it should work out-of-the-box without requiring manual GPIO remapping, especially for basic functionality like LED control.

To help further analysis, I am sharing my project as well.

It would be helpful to know:

the exact function where the On/Off cluster triggers LED control
whether any board-specific BSP layer is expected to map LEDs
Because currently:

Zigbee side seems functional (joining etc.)
but no LED response, which makes me suspect either:
mismatch between example and board
or missing linkage between Zigbee callback and GPIO