You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add another fabric over CASE of the first commissioned fabric
Open a new CASE session over the new fabric
Complete commissioning of the new fabric
Platform
esp32
Platform Version(s)
No response
Type
Manually tested with SDK
(Optional) If manually tested please explain why this is only manually tested
The steps above were exercised.
Anything else?
On M5 log, there were lots of Failed to post event to CHIP Platform event queue messages and one after receiving the Sigma3 message as well. So suspecting resource issue.
I (59199) chip[EM]: <<< [E:13002r S:0 M:38815149 (Ack:13084043)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (59219) chip[IN]: (U) Sending msg 38815149 to IP address 'UDP:[FE80::18DD:660:1490:E11A%st1]:51277'
I (59219) chip[SC]: Received Sigma3 msg
E (59229) chip[SC]: The device does not support GetClock_RealTimeMS() API: 6c. Falling back to Last Known Good UTC Time
E (60179) chip[DL]: Failed to post event to CHIP Platform event queue
E (60179) chip[CSL]: Failed to queue CHIP System Layer lambda event: 1000000
E (60199) chip[DL]: Failed to post event to CHIP Platform event queue
E (60199) chip[CSL]: Failed to queue CHIP System Layer lambda event: 1000000
...
I (75569) chip[FS]: Fail-safe timer expired
E (75569) chip[SVR]: Failsafe timer expired
E (75569) chip[SVR]: Commissioning failed (attempt 1): 32
This could also be similar to #25833 (note the lower-memory non-default configuration file that was added in #25935), and is likely the same as #24418 and #23258
Reproduction steps
Platform
esp32
Platform Version(s)
No response
Type
Manually tested with SDK
(Optional) If manually tested please explain why this is only manually tested
The steps above were exercised.
Anything else?
On M5 log, there were lots of
Failed to post event to CHIP Platform event queue
messages and one after receiving the Sigma3 message as well. So suspecting resource issue.M5_pairing_failed_accessory_log_21A220a.txt
The text was updated successfully, but these errors were encountered: