Describe the bug
The Opensky API integration doesn't handle the response case 429 (Too Many Requests) correctly. This can occur due to the rate limit depending on how the API is used: https://openskynetwork.github.io/opensky-api/rest.html#limitations
To Reproduce
Steps to reproduce the behavior:
- Enable the Opensky integration
- With standard settings of 1 request every 20 seconds the limit should be reached after around 30 min
Expected behavior
The Opensky API calls should stop or back-off and not do any additional request to the API until x seconds mentioned in header pass.
Additionally to allow users to use the live Opensky API longer it would be good to allow authenticated requests to the Opensky API. For this the username and password needs to be configurable in the settings and should be passed in the request as auth header. This would allow the API to be user 10x longer for registered Opensky users.
Describe the bug
The Opensky API integration doesn't handle the response case 429 (Too Many Requests) correctly. This can occur due to the rate limit depending on how the API is used: https://openskynetwork.github.io/opensky-api/rest.html#limitations
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The Opensky API calls should stop or back-off and not do any additional request to the API until x seconds mentioned in header pass.
Additionally to allow users to use the live Opensky API longer it would be good to allow authenticated requests to the Opensky API. For this the username and password needs to be configurable in the settings and should be passed in the request as auth header. This would allow the API to be user 10x longer for registered Opensky users.