simultaneous.logins

[fezzz]

Hi,

for some weeks I am facing the problem, that the gardena API seems to have introduced a rate limit regarding the logins.
Is there way to handle the frequency of the webcalls or even use the developer API that gardena offers?

Thanks,
Felix

[30.12.2020, 09:15:33] [Cryptor] getToken Successful login
[30.12.2020, 09:15:33] [Cryptor] Cannot get Token {
options: {
method: 'POST',
uri: 'https://smart.gardena.com/v1/auth/token',
body: { data: [Object] },
json: true
}
} 400 undefined
(node:20250) UnhandledPromiseRejectionWarning: StatusCodeError: 400 - {"errors":[{"code":"simultaneous.logins","status":400,"title":"Bad request","detail":"Simultaneous logins detected for client[id=iam-password-client], user[id=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx, email=xxx@xxx.xxx}]"}]}
at new StatusCodeError (/usr/local/lib/node_modules/homebridge-gardena-mower/node_modules/request-promise-core/lib/errors.js:32:15)
at Request.plumbing.callback (/usr/local/lib/node_modules/homebridge-gardena-mower/node_modules/request-promise-core/lib/plumbing.js:104:33)
at Request.RP$callback [as _callback] (/usr/local/lib/node_modules/homebridge-gardena-mower/node_modules/request-promise-core/lib/plumbing.js:46:31)
at Request.self.callback (/usr/local/lib/node_modules/homebridge-gardena-mower/node_modules/request/request.js:185:22)
at Request.emit (events.js:315:20)
at Request. (/usr/local/lib/node_modules/homebridge-gardena-mower/node_modules/request/request.js:1154:10)
at Request.emit (events.js:315:20)
at IncomingMessage. (/usr/local/lib/node_modules/homebridge-gardena-mower/node_modules/request/request.js:1076:12)
at Object.onceWrapper (events.js:421:28)
at IncomingMessage.emit (events.js:327:22)
at endReadableNT (internal/streams/readable.js:1327:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
(Use node --trace-warnings ... to show where the warning was created)
(node:20250) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:20250) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[30.12.2020, 09:15:33] [Cryptor] Cannot get Token {
options: {
method: 'POST',
uri: 'https://smart.gardena.com/v1/auth/token',
body: { data: [Object] },
json: true
}
} 400 undefined