Too many requests when trying to login to Kress account

[jellyneck84]

Describe the issue

A few days ago i changed the RTK Head of my Kress RTKn and it seems since then i have no cloud connection anymore. I'm getting "too many requests" even if i do not try it for more than 24 hrs.

What version of Home Assistant Core has the issue?

core-2024.7.2

What was the last working version of Home Assistant Core?

No response

What version of the Landroid Cloud integration do you have installed

5.0.5

What type of installation are you running?

Home Assistant OS

Which make and model is the mower used for this integration?

Kress KR174E

Diagnostics information (NOT log entries!)

I would love to get these data, but i cannot even add the integration because setup of the integration is already failing. How can i get the debug logs then?

Relevant log entries

I cannot find any entry in the logs, i don't even know if the integration is trying to connect....

Additional information

No response

[jellyneck84]

@MTrab do you think you can help here? how can i get a debug log?

[MTrab]

Not at the moment - everything is shutdown for moving. Will be a month or more before I have the opportunity

[jellyneck84]

Not at the moment - everything is shutdown for moving. Will be a month or more before I have the opportunity

Hello MTrab. Any news here or are you still in moving process?
Currently i can't get this integration to signin to kress, i talked with some positec guys and my account is fine. If you let me know how to create the debug logs, i can help.

Is there any way to workaround this maybe?

[MTrab]

Nothing new here, sorry

[jellyneck84]

Nothing new here, sorry

ok, keep me updated. I'm currently trying to avoid re-installing Home Assistant....

[jellyneck84]

@MTrab for any reason, i figured it out to get it back working. As i have another account also for Worx, i tried to add this account. After adding the Worx account, i was then also able to add the KRESS account again in the integration.

Not sure if this is really the workaround or any of the latest HomeAssistant updates fixed it, but it's working again.