Programming Tutorials

  If you are developing a Matter-over-Wi-Fi device on the ESP32, you have likely encountered the specific problem that is the Apple Home "Commissioning Failed" error. Android devices commission instantly. The   chip-tool   on Linux works perfectly. Yet, when you scan the QR code with an iPhone, the Home app spins on "Connecting..." for 30 seconds before unceremoniously dropping the connection. Apple provides zero logs to the user. However, the issue almost always boils down to two factors specific to the ESP32 implementation:  BLE Advertisement intervals violating Apple's strict accessory design guidelines  and  Memory exhaustion during the PASE (Passcode Authenticated Session Establishment) handshake . Here is the root cause analysis and the production-grade fix to stabilize your Matter commissioning. The Root Cause: Timing and Fragmentation Matter commissioning (specifically PASE) begins over Bluetooth Low Energy (BLE). The Commissioner (the iPhone) must ...

  You have successfully compiled the   lighting-app   example from the   esp-matter   SDK. You flash the ESP32, monitor the UART, and see the QR code URL. You pull out your iPhone, scan the code in Apple Home, and wait. The spinner rotates for 30 seconds, followed by the dreaded, non-descript error:   "Unable to Add Accessory." The UART logs on the ESP32 side show a BLE connection, a brief exchange, and then a sudden disconnect with an error like  SecureChannel: error 0  or  CASESession: error . This is the most common hurdle in professional Matter development. It is rarely a code syntax error; it is almost always a failure in the  Device Attestation Procedure  or  Storage Partitioning . The Root Cause: Device Attestation and Factory Data Matter relies on a rigorous security handshake known as PASE (Passcode Authenticated Session Establishment). During commissioning, the Commissioner (the phone/hub) challenges the Accessory (ES...