Skip to main content
R
rjun808
Visitor II
July 8, 2026
Question

STM32WBA65 / X-CUBE-MATTER: Alexa app does not detect Matter device during BLE commissioning

  • July 8, 2026
  • 0 replies
  • 19 views

Hi,

I am working on a Matter-over-Thread firmware project on the NUCLEO-WBA65RI / STM32WBA65RIVx, and I am seeing an issue where the Amazon Alexa app does not detect the board during Matter commissioning.

My current environment is:

  • Board: NUCLEO-WBA65RI

  • MCU: STM32WBA65

  • STM32Cube FW_WBA: V1.9.0

  • X-CUBE-MATTER: V1.6.0

  • STM32CubeIDE: 1.17.x

  • Commissioner being tested: Amazon Echo 4th Gen, model L4S3RE

  • Matter / connectedhomeip version: v1.3.0 as packaged in X-CUBE-MATTER V1.6.0

The device boots correctly, Thread and Matter initialize, and the commissioning window opens. From UART logs I can confirm:

  • Thread task starts successfully

  • Matter task starts successfully

  • BLE stack initializes successfully

  • Matter BLE advertising starts

  • Matter service UUID 0xFFF6 is present in the advertising payload

  • Manual pairing code and QR payload are generated

  • Fabric count is 0

  • Commissioning window opens successfully

The device is also visible in BLE scanner tools such as nRF Connect. nRF Connect shows the Matter BLE advertisement, so the board appears to be physically advertising correctly.

The issue is that the Alexa app / Echo 4th Gen never appears to connect to the board. In the UART logs, I do not see any BLE connection event from Alexa, so the failure appears to happen before PASE commissioning begins.

The current Matter configuration is:

  • Device type: 0x0101 / Dimmable Light

  • Product name: 12V Smart Light

  • VID: 0xFFF1

  • PID: 0x8004

  • Discriminator: 3840

  • Factory data enabled: no

  • Test commissionable data provider is being used

  • DAC provider is currently using FFF1/8004 test credentials

  • Serial number and Basic Information UniqueID are set

  • Endpoint 1 clusters: Identify, Groups, OnOff, LevelControl, Descriptor, ScenesManagement

My main questions are:

  1. Is there any known limitation when commissioning an STM32WBA / X-CUBE-MATTER V1.6.0 Matter-over-Thread device with Amazon Alexa / Echo 4th Gen?

  2. Does the Alexa app or Echo filter Matter BLE advertisements using the test VID 0xFFF1 before initiating a BLE connection?

  3. Is Alexa expected to initiate a BLE connection to a device using test VID/PID and test DAC credentials, or does Alexa require production/factory-provisioned credentials before the device is even shown during discovery?

  4. Are there any ST-specific requirements for the BLE advertisement, scan response, discriminator, commissioning mode, or factory data configuration when using Alexa as the Matter commissioner?

  5. For an Alexa-compatible test device, is 0x0101 / Dimmable Light an appropriate endpoint type, or would ST recommend using a different Lighting App profile from X-CUBE-MATTER?

UART logs for reference:

=== 12V Smart Switch BOOT ===
[RTOS] ThreadTask start
[THREAD] OpenThread instance created (will be used by Matter via ThreadStackMgr)
[BLE] HOST_BLE_Init OK; Ble_Hci_Gap_Gatt_Init
[THREAD] Thread subsystem initialized
[RTOS] MatterTask start
[RTOS] Thread ready, starting Matter
[MATTER] StackInit enter
[MATTER] InitChipStack OK
[MATTER] InitThreadStack OK
[MATTER] Thread device type set (MED)
[MATTER] DAC provider set (FFF1/8004 test creds)
[MATTER] Commissionable data provider set (test)
[MATTER] Server::Init OK
[MATTER] Fabric present: NO
[MATTER] Stored fabrics: 0
[MATTER-CHECK] Fabric count: 0
[MATTER-CHECK] Commissioning window open: no
[MATTER-CHECK] Factory data enabled: no
[MATTER-CHECK] VID: 0xFFF1
[MATTER-CHECK] PID: 0x8004
[MATTER-CHECK] Discriminator: 3840
[MATTER-CHECK] Passcode: [redacted]
[MATTER-CHECK] Device type: 0x0101 Dimmable Light
[MATTER-CHECK] Endpoint 1 clusters: Identify, Groups, OnOff, LevelControl, Descriptor, ScenesManagement
[MATTER-CHECK] Product name: 12V Smart Light
[MATTER-CHECK] Serial: [redacted]
[MATTER-CHECK] UniqueID: [redacted]
[ADV-CHECK] Matter service UUID 0xFFF6 present: yes
[ADV-CHECK] Decoded discriminator: 3840
[ADV-CHECK] Decoded VID: 0xFFF1
[ADV-CHECK] Decoded PID: 0x8004
[MATTER] Setup discriminator: 3840
[MATTER] Setup passcode: [redacted]
[MATTER] QR payload: [redacted]
[MATTER] Manual pairing code: [redacted]
[MATTER] Scheduling commissioning window open
[MATTER] Commissioning window open
[MATTER-CHECK] Fabric count: 0
[MATTER-CHECK] Commissioning window open: yes
[ADV-CHECK] Matter service UUID 0xFFF6 present: yes
[ADV-CHECK] Decoded discriminator: 3840
[ADV-CHECK] Decoded VID: 0xFFF1
[ADV-CHECK] Decoded PID: 0x8004
[BLEMGR] DriveBLEState mode=1 advEn=1 advertising=0 numCon=0
[BLEMGR] StartAdvertising fast=1
[ADV] APP_BLE_AdvStart entry (IPSR=0)
[ADV] aci_gap_set_discoverable -> 0x00
[ADV] aci_gap_update_adv_data(len=15) -> 0x00
[ADV] payload: 02 01 06 0B 16 F6 FF 00 00 0F F1 FF 04 80 00
[MATTER] Init complete
[RTOS] Matter init OK

Any guidance on what Alexa expects at the BLE discovery stage for STM32WBA + X-CUBE-MATTER would be very helpful.

Thank you.

Terms & ConditionsAccessibility statement