@All users with local storage:
A suggestion for a fine tuning of your setup regarding the motion alert recognition based on local storage (SyncModule)…
With local storage, the videolists of all SyncModules are needed to check for new videos (which represents a motion).
So your video reading interval deoends on the number of used SyncModules.
For cloud storage, only one API call is nedded for the whole account. With local storage, 2 API calls are needed fo each SyncModule. If you have installed 2 SyncModules, you need 4 calls. That results in a read interval 4 times longer than a possible cloud access.
A good way for optimization is to start with 15 seconds interval.
In addition you can set the wait time for API errors to 0 (zero). That way, every API error will show you the ! icon on the tile. This way you can check if 15 seconds is ok.
If you periodically get http 403 errors, your rate is too high. Adjust to 20 seconds and check some hours. Increase the interval if still http 403 errors are shown.
The SyncModule access has another disadvantage:
It will show an unspecific http 409 error. In that case, another request is processed by the SyncModule. That can be caused by yourself (reading video list or playing videos in Blik app) or by another reason (cloud sync, cameras connecting to or writing video data…). These errors are difficult to avoid. The only way would be to inrease the interval to avoid overlapping requests. It’s a kind of try&error to find a good interval.
