Thanks for explaining. It was that the usage doesn’t seem to be correct though even if reported through the Onecta API. Would it be possible to build in some compensation for this behavior through a setting? It won’t help for past days.
My app was just updated to v5.1.0. I do have an Altherma III Air 2 Water heatpump.
I got the attached message:
I did remove the air2water heatpump, but there are no other options for me, except the device I already used.
When I add that again, I get the same warning as above. Anything I do wrong?
1 Like
Sorry this is prep work for the universal Altherma driver and domestic hot water tank.
Check message (air 2 water)!
You can safely ignore this message…
1 Like
Thank you for clearing this up. 
I have same problem. I’m clueless about how to fix this. Where am I supposed to find this air-2-air driver? Should I just remove my unit from the ONECTA app and add it again?
Yes, remove and add them again…
I you have taking a moment to read some previous posta in this topic the answer was multiple time already given!
1 Like
I used several moments for that. Would have been easier if the explanation given in the app had been clearer.
Thanks
My units are shut off (totally) during winter and with the new driver and app version the log is filled:
I’ve now disabled the app or is there a better solution for not spamming?
1 Like
I changed to the new air driver a few weeks back and recreated all flows. Today the card for setting the temperature from a variable is missing and those flows are broken. Can’t find a card for setting the temperatute from a variable now.
The default capability target_temperature comes also with the default flows that are generated automaticly by Athom SDK.
There is not much I can do about this without braking some general coding rules made by Athom.
I know it was posible in the previous versions but that versions broke more functionalities users used then a temperature variable set. So thats is a reasons some coding choices are made undone.
Sorry
I see, now a new card appeared setting temperature via a slider and that one seems to be able to take a variable value as well. Is this an auto generated by athom-card? Can I just use that instead of the old one?
Yes this is the auto generated temperature flow card.
You can use that one
1 Like
Hi. I’ve only ability to turn on/off water tank and on/off powerful mode. I can’t set temperature directly (I’ve disabled schedule in the daikin settings, but it wont work). Any suggestions?
Thanks
That is correct , work in progress.
Wait for the upcoming 6.x.x release
If you also send the diagnostic report the answer is in the reply mail.
Your account is 429 rate limited.
Be sure you do a maximum request of 20 calls per minute and 150 calls the day.
Check your flows to make sure you don’t exceed these limts
Interestingly, the flows have been running without problems for half a year so far. How long will it take for access to be restored?
Something triggers the rate limiter on the Daikin cloud. Can’t tell what that should be.
Best way is to disable the app for 24h.
After 24h enable the app. It could happen that you need to repair all you Daikin devices in Homey.
1 Like
This is very relevant to me right now, because the temperature outside is -11 degrees, and electricity prices are jumping like grasshoppers.
Price fluctuations are likely related to the Baltic states’ disconnection from Russian power grids a week ago.
BRR that’s cold 
. Can’t do much about it.
Daikin has build in the rate limiting on the new API cloud platform. And I totally agree with them.
All modern API have these kind of protection.
If you use e.g. home assistant the same rate limiting is implemented.
If it so important for you maybe your setup needs to be under consideration…
Btw if your creating a diagnostic report and post a message here please add the diagnostic ID so I don’t have to guess for which user it is
1 Like
