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
The sequence in this test is as follows:
e1-admin adds e2-bridge (using fabricsync add-bridge command)
e2-admin pairs device which becomes available on an endpoint of e2-bridge ()
e1-admin syncs e2-bridge (using fabricsync sync-device command)
e1-admin pairs the device using payload returned from OCW request made in [3]
If we does not specify the setupPIN, SDK should generate a random one, but this does not work on my home setup when try to sync a example Matter device.
Reproduction steps
The sequence in this test is as follows:
e1-admin adds e2-bridge (using fabricsync add-bridge command)
e2-admin pairs device which becomes available on an endpoint of e2-bridge ()
e1-admin syncs e2-bridge (using fabricsync sync-device command)
e1-admin pairs the device using payload returned from OCW request made in [3]
If we does not specify the setupPIN, SDK should generate a random one, but this does not work on my home setup when try to sync a example Matter device.
Bug prevalence
Always
GitHub hash of the SDK that was being used
681f951
Platform
raspi
Platform Version(s)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: