Edit

Frequently Asked Questions and Troubleshooting for Matter over Wi-Fi#

Troubleshooting#

1. Bluetooth connection fails when trying to commission the system through the chip-tool#

Command leading to error:

$ out/standalone/chip-tool pairing ble-wifi 1122 mySSID myPassword 20202021 3840

Where mySSID is your AP's SSID and mypassword is your AP's password.

Error example:

[1659464425.856025][34818:34823] CHIP:DL: HandlePlatformSpecificBLEEvent 16386
[1659464425.856035][34818:34823] CHIP:IN: Clearing BLE pending packets.
[1659464425.856055][34818:34823] CHIP:IN: BleConnection Error: ../../examples/chip-tool/third_party/connectedhomeip/src/platform/Linux/bluez/Helper.cpp:1775: CHIP Error 0x000000AC: Internal error

This error indicates that the Bluetooth connection between your system and laptop is failing. Follow the given procedure and then retry the chip-tool commissioning command.

Procedure:

  1. Stop Bluetooth service:

    $ systemctl stop bluetooth.service

  2. Wait 20 seconds

  3. Restart Bluetooth service:

    $ sudo service bluetooth restart

  4. Unblock Bluetooth service:

    $ rfkill unblock all

  5. Enable Bluetooth service:

    $ sudo systemctl enable bluetooth

  6. Issue the pairing command:

    $ out/standalone/chip-tool pairing ble-wifi 1122 mySSID mypassword 20202021 3840

    Where mySSID is your AP's SSID and mypassword is your AP's password.

2. Unsupported certificate format error#

When trying to commission the system, if an Unsupported certificate format error (example below) is encountered, follow the procedure stated below.

Error example:

[1659631352.672826][5076:5076] CHIP:TOO: Run command failure: ../../examples/chip-tool/third_party/connectedhomeip/src/controller/CHIPDeviceController.cpp:1275: CHIP Error 0x00000050: Unsupported certificate format

Procedure:

  • Delete the existing certificates on your laptop with the following command run from the /connectedhomeip directory:

    $ /bin/rm /tmp/chip_*

  • Issue the commissioning command

3. Apple HomePod associated failures#

If there is an Apple HomePod on the network paired with a Thread device, and a commissioning failure is seen with error 3000001:

  • Remove the Apple HomePod from the network or unpair it from all Thread devices.

  • Retry commissioning

4. Commissioning failure at step 18#

  1. Verify router configuration specifically related to IPV6 SLAAC, Internet Group Management Protocol (IGMP) snooping.

  2. Delete all the files of chip-tool /tmp folder. (rm -rf /tmp/chip_*)

  3. After checking the router configuration, factory-reset your access point.

5. Commissioning failure at step 16#

Verify the access point settings, SSID, PSK, security type, REGION, CHANNEL.

6. To enable different security options on AP/Router#

  1. Get the router address by entering route -n or ifconfig of ipconfig.

  2. Enter the router address in the browser and enter the appropriate username and password.

  3. Select the appropriate band.

  4. In security, select type (WPA / WPA2 / WPA3).

7. CHIP Logs are not available on MG12 + WF200 due to image size constraints#

Due to apps taking up more space than available flash on the MG12 + WF200 device combination, chip_logging=false needs to be included on the command line while building the app image, to disable CHIP logs and thereby reduce the image size.

This prevents debugging the code on the MG12 + WF200 device combination.

In order to work around this constraint, disable either the LCD or the use of QR codes, depending on your debugging needs. Disabling one of these will sufficiently reduce the image size to allow CHIP Logging to be enabled.

If you disabled QR Codes, you may use the chip-tool for commissioning the device.

If you disabled the LCD and need to debug with QR Codes, the URL to display the QR Code will be printed in the device logs.

Disable LCD and enable CHIP Logging: ./scripts/examples/gn_efr32_example.sh examples/lock-app/efr32 out/wf200_lock_app BRD4161A is_debug=false disable_lcd=true --wifi wf200 |& tee out/wf200_lock_app.log

Disable QR Code and enable CHIP Logging: ./scripts/examples/gn_efr32_example.sh examples/lock-app/efr32 out/wf200_lock_app BRD4161A is_debug=false show_qr_code=false --wifi wf200 |& tee out/wf200_lock.log

8. MG24 device sometimes fails to bootload with the new image during OTA Update with WF200#

While performing an OTA Update with the EFR32MG24 + WF200 device combination using the external flash, when the device is reset and bootloading begins with the new image, the device sometimes starts up with the existing image instead of the newly downloaded one.

When this happens, perform the following steps to run the OTA Update successfully:

  1. Disconnect the WF200 Expansion Board from the EFR32MG24.

  2. Go to the Simplicity Commander's folder path in the command prompt and run this command:

    commander.exe extflash read --range 0x00:+<total size to read>

  3. Reconnect the WF200 Expansion Board to the EFR32MG24 and reset the device.

  4. Re-run the OTA Update process from the beginning.

9. Connectivity Issues with SiWX917 SoC with Low-Power Applications while flashing firmware/application image#

Sometimes, firmware/application updates fail while flashing, and the logs display "Could not connect debugger. Could not connect to target device," indicating that the application processor is in a low power state with no flash access. Try one of the following solutions, then retry the firmware/application update:

Toggle the power switch towards AEM (Advanced Energy Monitoring) on the WPK/WSTK board, or

Perform the following sequence of steps:

  1. Press and hold the ISP button on the radio board and the RESET button on the WPK/WSTK board simultaneously.

  2. Release the RESET button on the WPK/WSTK board.

  3. Release the ISP button on the radio board.

  4. Click Erase chip to erase the flash.

  5. Press the RESET button on the WPK/WSTK board again.

  6. Retry flashing the firmware/application.