Can this issue be reproduced in a sandbox workspace? No
Does this issue represent a regression? Did it previously work? No
Description
If access code creation is delayed on a SmartThings device and an external integration or the device user manually creates a code on the device, Seam may assume the externally created code is the code Seam was trying to set. This results in the access code appearing to be in the set status, but the device actually has an incorrect pin programmed for the access code.
Steps to Reproduce
Create an access code through Seam Connect on a SmartThings device and delay code loading
Manually create a new access code on the device
Allow Seam Connect to sync to the device
Seam Connect sees the externally created code and assumes it's the code Seam was attempting to program
Prerequisites
Description
If access code creation is delayed on a SmartThings device and an external integration or the device user manually creates a code on the device, Seam may assume the externally created code is the code Seam was trying to set. This results in the access code appearing to be in the
set
status, but the device actually has an incorrect pin programmed for the access code.Steps to Reproduce