Hi,
I have difficulties commissioning / pairing matter enabled ESP32 test device with Nest Hub (2nd gen) firmware 1.56.324896. The pairing process was working for my test device prior to the Nest Hub (2nd gen) firmware 1.56.324896 upgrade.
My steps to reproduce:
- I have followed the codelab to build and commission a matter enabled device as per the build guide for ESP32
- I have successfully built and flashed my ESP32 based device
- I have restarted my Google Nest Hub (2nd gen) running latest preview programme firmware 1.56.324896
- I have set up my google home developer console project and added the matter integration as instructed in the codelabs
- I try to add a new matter device using the Google Home app on my Google Pixel 4a mobile.
- The BLE commissioning seems to work fine but I pairing comes to a complete stop at the Certificate Signing stage as per the log entries from the ESP32 device:
I (42462) chip[EM]: >>> [E:55844r M:219460464] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (42472) chip[ZCL]: OpCreds: Received a CSRRequest command
I (43172) chip[ZCL]: OpCreds: AllocatePendingOperationalKey succeeded
I (43522) chip[ZCL]: OpCreds: CSRRequest successful.
I (43532) chip[EM]: <<< [E:55844r M:179577212] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
The pairing/commissioning process comes to a halt at the point and an error appears on my Home app. I am using the Test Product Id (0x8001) and Test Vendor Id (0xfff1) and the associated digital certificates.
The pairing process was working for this test device prior to the Nest Hub (2nd gen) firmware 1.56.324896 upgrade.
Has the ability to commission devices with test certificates been taken away ? Or am I missing or overlooking something?
Many thanks in advance
Bovis
P.S. Apologies to moderators if you see this as a double post. My first post was marked as spam for some unexplained and despite my communication attempts with the moderation team the original post wasnt released.
