We are using the API to retrieve, add, and modify the TRB256 device configuration from an application.
After adding a configuration, we’ve observed that we need to call the Status API to check the configuration status and wait at least 10 seconds per configuration. When handling multiple configurations, the total waiting time increases accordingly. What is the best approach to minimize or avoid this delay?
In the first instance, I would recommend upgrading the device to the newest firmware.
Configuration changes often require the internal configuration daemon to reload services, which may take up to 10 seconds before a new API change becomes visible in the status system.
I would recommend trying to push all configuration changes, wait a single delay interval, and then make concurrent status API calls for each configuration.