From Daikin-Development perspective the ratelimiting is a logical implementation.
You don;t want to overload your platform, every modern (open)API platform has rate limiting implemtation.
But 150 calls a day should be more then engough for daily use according to daikin.
The only thing i can do is look at te code and make it more effecient. but i do not thing this will be the solution.
Let see what happens and in the meantime i going to try to raise the limits by daikin (no garantee!)
Are these numbers for each Daikin device, each Homey user or the whole Homey community?
Edit: I think these numbers are per Daikin user.
First they force you to use their cloud to access your device rather than allowing a LAN access, then they put a limit rate on how much you can access your own device.
Iād understand a minute/hourly limit to avoid an overload of the cloud but a daily limit is unacceptable imho
btw, is this limit for each split, each multisplit, each account ??
For the time being you could use Daikin-AC-Airconditioning app; less flexible because of the IR usage, but it is a temporary alternative not using an api.
I have 6 splits and 5 out of IR reach
Well, there new API looks far from stable imo. Connecting the app works for now, but one device gives an OAuth error.
Another thing, what is seen as one call. Since in a single action like below I set the temperature, the swing, the mode and the fan speed. Is this one call or 4 calls? Because in that case monitoring the temp and steering the units accordingly will be hard, because each unit will eat up like 4 calls an hour.
Also repairing all the flows is impossible due to this unstable connection because for every action it is triggering the API it seems.
oRepair ALL your devices and also restart app most users (4000+) having no problems.
Could happen because of the Oath2 multisession that you need to repair sereval device multiple times.
If all devices are available you flows will be also there.
Well, strange thing is that the Homey Pro (connected to the same Daikin account, other location) is working fine after just one repair. So I think it could be because of the Homey Cloud, which is now overloading the servers of Daikin with requests from 1 (or a couple) IP addresses.
Sounds like the same thing as with Hue, which is why Hue support for Homey Cloud is so extremely limited.
Try to repair Homey Pro again (which was working fine) to compare, but again no issue there.
Reinstalled the app on the Homey Bridge and error after error keeps appearing, so it seems isolated to the Homey Cloud environment. I think that more people will experience this issue soon.
PS: Could it have something to do that I use two locations in 1 Daikin account, an that my Daikin account is therefor linked to 2 Homey IDās?
Here Homey pro early 2018. My Daikin app is also not working properly. Temperature outsite is not updated for a day now. Yesterday I did a repair. Also change in settings is not synchronized. Daikin Airco Perfera.
same here. Not only am I unable to command my AC but I am also prevented from modifying the flows due to a failure to connect to Daikinās cloud.
Does the new rate limit imply that checking if the AC is ON counts as 1/200 ?
No. Flowtrigger(when) & flow condition(and/or) do not make a API call. Only flowactions(then).
Only during setup/configuration in some flows there are some so called autocomplete field that result in a API call but that only during configuration of those flows.
The rate limiting is set by Daikin to max 20 per minute a max 200 per 24hour
But every 30 minutes the app does do a full update api call.
This results that a users has aprox 150 calls left.
Some INFO from Daikin
Sending commands
Users should be mindful of the impact of sending rapid commands to heat pumps, especially those involving the start or stop of the compressor (e.g.onOffMode). To maintain reliability and durability, itās advisable to avoid initiating compressor start and stop operations more frequently than once every 10 minutes.
Itās essential to consider that the startup behaviour of the compressor consumes more energy than during steady-state operation.
Be aware that the focus of the Daikin Onecta Cloud API is mainly on home comfort control. The API is not suitable for reactive control algorithms, like PV solar optimisation, due to the rate limitation. For reactive applications, the Daikin HomeHub provides you with a local interface.
Rate limitation
A rate limitation is applied to every application that is created through this developer portal. All applications will have the following default rate limit:
rate limit per day: 200
rate limit per minute: 20
This rate limit configuration allows you to send a maximum of 200 requests per 24 hour window to the ONECTA Cloud API. Furthermore, per minute, a maximum of 20 requests can be sent. This rate limitation gives you the possibility to query the state of your devices periodically while keeping the flexibility to perform sufficient actions on your devices.
For example, if your application would fetch the state of your devices every 10 minutes, this would take up 144 API requests over a window of 24 hours. Note that you can request the state from all devices with only one API request. You then still have 56 requests that you can use for other actions such as changing the operation mode or room temperature setpoint during this window. However, you canāt perform these actions too quickly after each other because you only have a budget of 20 requests per minute.
The API rate limit algorithm is implemented using a sliding window policy, which dynamically tracks and manages the number of requests made within specific time intervals.
In a sliding window approach, time is divided into consecutive intervals, often referred to as windows. Unlike a fixed window where the limit resets at regular intervals, the sliding window maintains a moving time frame that continuously shifts forward.
For example, if we consider the rate limit of 20 requests per minute, the sliding window constantly tracks the requests made within the last minute. Each time an API call is made, only those requests are taken into account to calculate the remaining budget. This dynamic shifting ensures that the rate limit is calculated over a rolling time period rather than a fixed reset point.
Those drastic restriction implies that one should create one daikin account per device since it seems that the 2OO/day limit applies to the daikin account
So I Monitor my DHW tank temperature using Homey, so it only turns on when itās below a threshold, and the sun shines or the power is cheapā¦ So the basic if DHW tank is below X would explain my polling of the Daikin api every 10-15minā¦ And that is why I cannot repair? Iāve passed my limit on api calls so I cannot use the renew api callā¦
I have the same problem since I monitor every room temperature each hour and/or open windows.
I wonāt be able to go under the 200/day leonine threshold.
One pays 30Kā¬ for a Daikin pump just to be hampered by asinine policies afterwords 
File a formal complaint, they are consciously removing features and blocking usageā¦ while advertising connectedā¦
