Hi Lionell, thank you for your prompt and clarifying reply.
We understand the necessity for the rate limits from a technical perspective, but are afraid it will create a bad user experience on first app launch. To explain, here is our use case:
Although eventually a user will change Nest Thermostat settings on rare occasions, a user who opens the app for the very first time will start clicking around, quickly changing the mode from Eco to Off to Heat, and changing the temperature multiple times within a short time frame, just to see if the app works as expected.
As it stands now, the user will, after only a few clicks, be confronted with a blocked call.
That’s a bad user experience, making them think the app doesn’t work very well, because it is not as responsive as the official Nest app and the Nest web interface, which are, as I understand now, not rate limited.
What is considered best practice in dealing with this?