It has nothing to do with flows…
After the update the devices were unresponsive. I just wanted to reconnect them to homey.
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
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!
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
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 ??
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
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.
1 Like
The 200 call/day is connected to the daikin account. There is always the possibility to create 10 accounts for your 10 rooms…
3 Likes
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 
Before resorting to extremes you could try the DaikinAI app…works like a charm for me 
1 Like
never mind, after the restart, it was the Onecta app that was showing the status wrong…
@Mickel_Luiten
Since a few days I have troubles again with the connection with Daikin.
This is the diagnoses report: bcbc662c-2d86-434e-821c-a172582f72d9
Thanks for your help in advance
This is what I get when I want to repair:
(This time it is the correct account, I removed the wrong account before).
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.
1 Like
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…
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.
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
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.
1 Like
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.
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!
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…
