Yale/August devices with large numbers of access codes (150+) can fail to confirm access codes - Githubissues

seamapi / public-tracker

0 stars 0 forks source link

Yale/August devices with large numbers of access codes (150+) can fail to confirm access codes #51

Open mc2147 opened 8 months ago

mc2147 commented 8 months ago

Slack thread: https://hello-seam.slack.com/archives/C05FXN0QYH0/p1699381089578719

Summary

Code is set successfully with the initial timebound settings
User updates code with new timestamps
When applying update, Seam deletes original code but during deletion there is an error about the lock being temporarily offline (common error)
On the next iteration, Seam creates a new August user for the code which succeeds but we fail to update the August provider entry for the code with a link to the new ext August user

Possibly Different Issue (on the same device)

An access code is created and marked as set on the device
It stops working at some point for the user and later polls to the device show that the access code is back in the created array instead of loaded array from the August API response