For a connection to a security system, I need timely information whether a user has gained access via keypad. I don’t get any reliable information about this via the local callbacks, because it is not possible to distinguish whether the user has gained access normally or via the keypad (I have already read the reasons for this in other threads, I hope that this will change soon).
Now I query in parallel every 5 seconds the logs of the Web-API to look there for entries, because the Web-API does not offer a callback. (Except the extended API, for which I have already applied).
There would be theoretically also the access by keypad recognizable. But in some cases it takes up to 10 minutes until the log is up to date. Therefore, this is not yet the all-encompassing solution.
Therefore, I now also trigger a sync of the smartlock every 5 seconds. This gives me a delay after the input that is at least only in the minute range. Unfortunately, it is not quite recognizable from when a sync makes sense. To reduce spam on the API I tried before to trigger a sync when receiving a local callback as well, but that didn’t solve the problem, even with 5 seconds pause before the sync. In the web log some entries were still not visible. So something seems to happen in the background before a sync makes sense.
So now to my real question: How many API requests am I allowed to make per minute? Currently there are 2 requests every 5 seconds by querying the logs + sync, so 24 requests per minute.