# \[APP\]\[Pro and Cloud\] Daikin ONECTA

**URL:** <https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088>\
**Category:** Apps\
**Tags:** app, homey-pro, homey-service\
**Created:** [November 1, 2021, 1:43pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088 "2021-11-01T13:43:11Z")\
**Posts on this page:** 20\
**Page:** 22

<div class="post-metadata">

**Author:** ![WillemG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/willemg/32/37114_2.png) [@WillemG](https://community.homey.app/u/WillemG)\
**Post date:** [November 10, 2024, 1:55pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/424 "2024-11-10T13:55:02Z")

</div>

It has nothing to do with flows…

After the update the devices were unresponsive. I just wanted to reconnect them to homey.

---

<div class="post-metadata">

**Author:** ![ricercar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ricercar/32/101928_2.png) [@ricercar](https://community.homey.app/u/ricercar)\
**Post date:** [November 10, 2024, 3:13pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/425 "2024-11-10T15:13:58Z")

</div>

Daikin has limited the use of its api to 200 requests/day since its last update.  
I have had to rewrite all my flows to limit the requests and I reverted to use ZXT-120 IR remotes to command some of my devices.  
Those changes of rules after you pay tens of thousands euros is unbearable though

---

<div class="post-metadata">

**Author:** ![Mickel\_Luiten](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mickel_luiten/32/12404_2.png) [@Mickel\_Luiten](https://community.homey.app/u/Mickel_Luiten)\
**Post date:** [November 10, 2024, 4:08pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/426 "2024-11-10T16:08:16Z")

</div>

> [@\[APP\]\[Pro and Cloud\] Daikin ONECTA](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/338):
>
> 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 th…

And its has to do with some flows your using…Also these can be API Calls.  
2488 minutes = 41 hours. Stop all API calls(flows) for 41 hours, if you still send API-call these number is only increasing!

Adjust your flows!

---

<div class="post-metadata">

**Author:** ![WillemG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/willemg/32/37114_2.png) [@WillemG](https://community.homey.app/u/WillemG)\
**Post date:** [November 10, 2024, 4:32pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/427 "2024-11-10T16:32:22Z")

</div>

Unacceptable @Diakin !!

I have a hotel with 10 rooms.  
One of my flows is : “Ventilate rooms”  
It:

- starts 10 of the units
- Changes mode to ventilation only
- Swing Horizontal on
- Swing Vertical on
- Set Speed for FanOnly to 5
- Set Clean On  
This flow is started by house keeping when they start cleaning rooms. That is 60 API request.

Then after clean up all units are stopped. An other 10 API calls.

One hour prior to check in the rooms are heated or cooled depending on the weather.

- starts units
- Changes mode to heat/cool only
- Set Speed for heat (or cool) to automatic
- After one hour put unit in Silent mode.

So the 200 API calls are not sufficient for 10 units in my setup

---

<div class="post-metadata">

**Author:** ![WillemG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/willemg/32/37114_2.png) [@WillemG](https://community.homey.app/u/WillemG)\
**Post date:** [November 10, 2024, 4:34pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/428 "2024-11-10T16:34:27Z")

</div>

I have a NSPanel setup to show all of my Daikin Units (10) per room. So I can see the status of my (hotel)rooms in a glance behind the reception desk.

The panel polls every 5 seconds to homey… Will this cause API-request to Daikin ??

---

<div class="post-metadata">

**Author:** ![Mickel\_Luiten](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mickel_luiten/32/12404_2.png) [@Mickel\_Luiten](https://community.homey.app/u/Mickel_Luiten)\
**Post date:** [November 10, 2024, 4:59pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/429 "2024-11-10T16:59:34Z")

</div>

Depends on your flows, but if nspanel only receive the status from devices in homey I do not think this results in a API call to the Daikin platform.

But without a deep dive in to your flows I cant say it for sure

---

<div class="post-metadata">

**Author:** ![Mickel\_Luiten](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mickel_luiten/32/12404_2.png) [@Mickel\_Luiten](https://community.homey.app/u/Mickel_Luiten)\
**Post date:** [November 10, 2024, 5:04pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/430 "2024-11-10T17:04:59Z")

</div>

Take your complains to Daikin, there is nothing I (developer Homey Daikin app) can do about it.

But most modern APIs has these kind of protection measurements in there platform.  
And from technical perspective I totally understand and agree with Daikin to implement this kind of protection.

---

<div class="post-metadata">

**Author:** ![ricercar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ricercar/32/101928_2.png) [@ricercar](https://community.homey.app/u/ricercar)\
**Post date:** [November 10, 2024, 5:23pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/431 "2024-11-10T17:23:58Z")

</div>

The 200 call/day is connected to the daikin account. There is always the possibility to create 10 accounts for your 10 rooms…

---

<div class="post-metadata">

**Author:** ![WillemG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/willemg/32/37114_2.png) [@WillemG](https://community.homey.app/u/WillemG)\
**Post date:** [November 11, 2024, 10:57am UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/432 "2024-11-11T10:57:30Z")

</div>

Creating individual accounts is a no go for me.  
That is not what I call smart home integration. That is what I call separation. The beautiful thing about home automation is that the Daikin app can have multiple locations in one app. I don’t want to maintain email addresses for my home (2 units) and my hotel (10 units).

I don’t blame you guys, you have to work with what Daikin provides. Probably they have validated their reasons to do so.

From my users point of view a missed opportunity.

The year is 2024, we shoot satellites in to space to have everything connected and be smart. But a simple 2 location, 12 rooms airconditioner setup is too many API calls.

I think it is a design flaw in the Daikin system that every status change to the unit are 6 calls. Switch on, put in FanOnly, Set FanSpeed to 5, Set Horizontalon, Set VerticalOn, Set CleanOn.

For now I am deleting the app from my homey.

Thank you for the 1,5 half years I have been able to use the app happily and to my complete satisfaction without any problems or limitations.

saying farewell to my beloved Airco Screen in my NSPanel 😪 😪 😔

 ![nspanelDaikin klein](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/c/dccb9fb75baccf84a9dd837f05ec2bc084fcdbe2.jpeg)

---

<div class="post-metadata">

**Author:** ![ricercar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ricercar/32/101928_2.png) [@ricercar](https://community.homey.app/u/ricercar)\
**Post date:** [November 11, 2024, 11:47am UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/433 "2024-11-11T11:47:13Z")

</div>

Before resorting to extremes you could try the [DaikinAI app](https://homey.app/fr-fr/app/nl.climate.daikin/)…works like a charm for me 😇

---

<div class="post-metadata">

**Author:** ![holgerr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/holgerr/32/44451_2.png) [@holgerr](https://community.homey.app/u/holgerr)\
**Post date:** [November 20, 2024, 2:27pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/435 "2024-11-20T14:27:12Z")

</div>

never mind, after the restart, it was the Onecta app that was showing the status wrong…

---

<div class="post-metadata">

**Author:** ![Ria\_Banis](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ria_banis/32/7966_2.png) [@Ria\_Banis](https://community.homey.app/u/Ria_Banis)\
**Post date:** [November 21, 2024, 12:39pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/436 "2024-11-21T12:39:51Z")

</div>

@Mickel_Luiten  
Since a few days I have troubles again with the connection with Daikin.

 ![IMG_1045](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/6/c6bc9c992b0c3f37ab8b562bd78a073de47da566.png)

This is the diagnoses report: bcbc662c-2d86-434e-821c-a172582f72d9

Thanks for your help in advance

 ![IMG_1046](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/2/62d64590576cfa2decd21446bfcdbe8e369911fd.jpeg)

This is what I get when I want to repair:

 ![IMG_1047](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/c/bc088dc159f7c8c70e236f804082607933328356.jpeg)  
(This time it is the correct account, I removed the wrong account before).

---

<div class="post-metadata">

**Author:** ![Mickel\_Luiten](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mickel_luiten/32/12404_2.png) [@Mickel\_Luiten](https://community.homey.app/u/Mickel_Luiten)\
**Post date:** [November 21, 2024, 3:50pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/437 "2024-11-21T15:50:16Z")

</div>

Looks like daikin had revokes als access\_tokens.  
simple repair all you daikin devices in homey and to be sure also restart the homey daikin ONECTA app.

Me also has this yesterday and i have received a few reports/mails with same issue.

---

<div class="post-metadata">

**Author:** ![Antoine\_K](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/antoine_k/32/77985_2.png) [@Antoine\_K](https://community.homey.app/u/Antoine_K)\
**Post date:** [November 21, 2024, 5:53pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/438 "2024-11-21T17:53:59Z")

</div>

For the first time today, repairing did not work and token were still invalid. Had to remove and reinstall the app with all the associated work and pain…

---

<div class="post-metadata">

**Author:** ![eirikh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eirikh/32/80427_2.png) [@eirikh](https://community.homey.app/u/eirikh)\
**Post date:** [November 25, 2024, 4:53pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/439 "2024-11-25T16:53:30Z")

</div>

Thanks for creating this, I will be sure to send you a few bucks when I get it to work!

I have the FVXTM30A model (floor), what driver/device would you recommend to use for it? Couldn’t see one with that specific model no. in the list.

---

<div class="post-metadata">

**Author:** ![Mickel\_Luiten](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mickel_luiten/32/12404_2.png) [@Mickel\_Luiten](https://community.homey.app/u/Mickel_Luiten)\
**Post date:** [November 25, 2024, 5:04pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/440 "2024-11-25T17:04:50Z")

</div>

Use the Perfera ,these driver is also used for floomodels.

Or to be sure use the general(all functionalities are implemented)  
Note that some functionalities will not work…this depend on you model

---

<div class="post-metadata">

**Author:** ![eirikh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eirikh/32/80427_2.png) [@eirikh](https://community.homey.app/u/eirikh)\
**Post date:** [November 25, 2024, 5:53pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/441 "2024-11-25T17:53:49Z")

</div>

Thanks, worked like a charm! Got the «no ouath2 client» error after adding, but restarted the Onecta-app in Homey which made it go away.

---

<div class="post-metadata">

**Author:** ![Max\_K](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/max_k/32/113290_2.png) [@Max\_K](https://community.homey.app/u/Max_K)\
**Post date:** [November 29, 2024, 1:44pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/442 "2024-11-29T13:44:36Z")

</div>

Hey, i’ve got a multisplit-system with 2 units in my home.

The unit in the first floor now says “Diese Art von Gerät wird in Zukunft vielleicht nicht unterstützt.” whats translated to “This kind of device may be not supported in the furutre”.

Is’s an floorstanding unit FVXM25A3V1B9. Can anyone tell me whats the problem and how to deal with it? Thanks.

---

<div class="post-metadata">

**Author:** ![JST](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jst/32/80641_2.png) [@JST](https://community.homey.app/u/JST)\
**Post date:** [November 29, 2024, 2:34pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/443 "2024-11-29T14:34:41Z")

</div>

What’s up, everyone? It seems like Daikin is losing support now that Homey has been acquired by LG.

I can’t fix the connection anymore; I’ve tried deleting and re-adding the device, but it won’t let me choose the operation mode.

It’s really frustrating because Daikin was the only device that worked well with Homey, and I rely on it heavily.

The rest of Honey is just useless for my needs as nothing works.

I’m hoping it gets sorted out soon!

---

<div class="post-metadata">

**Author:** ![HansS](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hanss/32/7076_2.png) [@HansS](https://community.homey.app/u/HansS)\
**Post date:** [November 29, 2024, 2:52pm UTC](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088/444 "2024-11-29T14:52:16Z")

</div>

Since a few days I can only switch my daikin on and off with my voice via Google Nest (home). At first I could set the temperature, etc., but now Google responds that it does not support that functionality. for now I can only turn daikin on and off, while in the homey app I can set everything…

[Previous page](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088.md?page=21)

[Next page](https://community.homey.app/t/app-pro-and-cloud-daikin-onecta/54088.md?page=23)
