Gardena: Error 429 Limit Exceeded

[AndrewFG (Andrew Fiddian-Green)]

@sirupflex

Maybe Gardena is messing around with the mechanism as well, which would make it a moving target.

Yes that is also my opinion.

@sirupflex

rule that re-enables the Gardena Account Thing if it goes offline, after 30 minutes. Sometimes it works, sometimes it runs into the “limit exceeded” still. Funny thing is, however, that it seems like the behavior seems to change again a bit over time

Just to clarify what is going on here…

• If the server thinks the client has made too many calls, it will fail the current call with ‘429 limit exceed’. This ‘server thinks’ may be because the client did actually make too many calls. Or it may be because Gardena has been fiddling with the server.
• The only way to recover from this issue is to wait until the server no longer thinks the client has made too many calls. This ‘server thinks’ may be because the time window for ‘too many calls’ has rolled over. I don’t know the exact time when the server window rolls over, but it may be (say) midnight California time (or something like that). Or it may be because Gardena stopped fiddling with the server again.
• When the binding detects an ‘429 limit exceed’ error, it starts a timer to wait for 24 hours, and then retry to connect to the server.
• If you disable and re-enable the account thing, it cancels the above mentioned timer, and it retries to connect to the server immediately.
• This immediate reconnect attempt might either succeed or fail (see ‘server thinks’ above). If it succeeds, then all is good, but if it fails the process will have a) added one more call that might cause the server to trigger its call limit exceeded count, and b) it will restart the above mentioned 24 hour timer.