Issue with using nRF7002 DK with Matter "Light Bulb Matter" example

[Germain B]

Hello,

I am working with the nRF7002 DK board and attempting to use the "Light Bulb Matter" example from Zephyr. I am encountering issues when trying to connect the board to Wi-Fi using my Google Pixel 8a smartphone and the Home Assistant app. Although I encounter non-blocking errors, the initial connection seems to work.

First, I provision the Wi-Fi via BLE to the board, and everything appears to be functioning correctly except for one error on the COM port:

Here is the error I encounter:

• IPV6_PKTINFO failed: 109

Despite this error, the nRF7002 DK successfully connects to the Wi-Fi. After that, Home Assistant on my smartphone allows me to connect the "Matter device," which I do. However, the system only works for about thirty seconds before the device is marked as "unavailable" in the Home Assistant app. I am unable to turn the lamp on or off. Home Assistant tries to communicate with the board but encounters repeated errors.

My Home Assistant server is running on a Linux virtual machine.

Could you clarify the correct procedure for using the "Light Bulb Matter" example with the nRF7002 DK board and Home Assistant, please?

Thank you very much for your help!

Additional Context:

• Smartphone: Google Pixel 8a
• App: Home Assistant
• Server: Home Assistant running on a Linux virtual machine
• Operating System: Windows 11 Pro
• IDE : Virtual Studio Code

• Board: nrf7002dk_nrf5340

• IDE: Visual Studio Code with nRF Connect extension

• SDK and toolchains : 3.0

[Edvin]

Hello,

Can you please provide the full log from the device (the 7002DK) and the log from HomeAssistant at the time you are trying to add the device?

Does your WiFi router have IPv6? Or IPv4 only?

Best regards,

Edvin

[Germain B]

I use a Raspberry Pi 3 as a Wi-Fi hotspot, but I also tried with a D-Link router, a Iphone X hotspot and at home with a house router, so these options get IPv6 turned ON. Here is the log from Home Assistant and the log from my nRF7002dk (at the moment of Wi-Fi provisioning before adding the devices to the Home Assistant system). 

[Edvin]

Germain B said:

Here is the log from Home Assistant

I was thinking of the log you find in Settings -> System -> Logs, from the time around when you tried to set up the bulb. Can you send that as well?

BR,
Edvin

[Germain B]

Oh, yes sorry. Here are my logs. (Surprisingly, today the bulb worked for several minutes before stopping working fine.) :

[07:47:59] INFO: [32mHome Assistant Core finish process exit code 0[0m
[07:47:59] INFO: [32mHome Assistant Core service shutdown[0m
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
[33m2025-06-23 09:50:55.983 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly[0m
[33m2025-06-23 09:50:56.015 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=39 from 2025-06-23 07:48:20.940479)[0m
[31m2025-06-23 09:54:41.206 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140297573071776] Error during service call to light.turn_on: src/app/CommandSender.cpp:344: CHIP Error 0x00000032: Timeout[0m
[31m2025-06-23 09:56:58.535 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140297201386976] Error during service call to light.turn_off: src/app/CommandSender.cpp:344: CHIP Error 0x00000032: Timeout[0m
[31m2025-06-23 10:01:08.851 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140297573071776] Error during service call to light.turn_on: src/app/CommandSender.cpp:344: CHIP Error 0x00000032: Timeout[0m
[31m2025-06-23 10:01:37.808 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140297573071776] Error during service call to light.turn_on: src/protocols/secure_channel/CASESession.cpp:615: CHIP Error 0x00000032: Timeout[0m
[31m2025-06-23 10:01:59.528 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140297573071776] Error during service call to light.turn_off: src/protocols/secure_channel/CASESession.cpp:615: CHIP Error 0x00000032: Timeout[0m

I also have this error in the card's logs from the beginning that I forgot to mention:

E: 72294 [SWU]No suitable OTA Provider candidate found
I: 72298 [SWU]No provider available

[Edvin]

Thank you.

Well, the timeouts are probably because HA can't reach the bulb.

Someone from our Matter team looked at the HA logs, and said:

"The logs show that the device was correctly commissioned over BLE, then has been connected to the Wi-Fi network, on which it received Commissioning Complete command over Wi-Fi (CASE session)

Then there is no more logs. At this point the Controller (Home Assistant in this case) should start Matter Subscription to learn the capabilities of the accessory, but it doesn not happen. As the CASE session has been established, this is more likely related with the AP. Is there any more logs from the Accessory (the DK/light bulb)?

We have no experience with Home Assistant - however, for me it looks like the problem is related to lack of communication from the controller side, either due to routing issues, or Home Asssistance configuration."

Do you have any other Matter devices on your network? Do they work as expected?

Best regards,

Edvin

[Germain B]

When you say "AP," do you mean my Wi-Fi router (in my case, a Raspberry Pi 3 hotspot)?

Regarding the logs from the nRF7002 DK, the board continues to attempt communication with Home Assistant and generates many logs continuously. I can provide you with hundreds of lines of logs if needed

Concerning the connection of another device to Home Assistant, I cannot try it at the moment because we do not have another Matter device. However, I will buy a simple device for testing within the week. I have connected my Google Pixel to Home Assistant and there is no similar problem; I can see its information

Thank you 

[Edvin]

Germain B said:

When you say "AP," do you mean my Wi-Fi router

Yes. AP = Access Point, which is your WiFi Router. 

The Google Pixel is not strictly a Matter device as seen from Home Assistant, though, is it?

Best regards,

Edvin

[Germain B]

No, my Google Pixel 8a is not a Matter device; it is my personal phone. As mentioned, I currently do not have any Matter devices available to test HA, so I mentioned the only other device connected to HA.