[APP][Pro and Cloud] Daikin ONECTA

We are now in 2026 have these been added by Daikin ?

Not in de basic API the Homey Daikin App supports.

There is a premium (paid) api the has more features.

I have ask Daikin if this can be enabled.

Should be added, as this is considered the official app. Also I would love for the heatpump to show up correctly in HomeKit using HomeKitty. Another heatpump I have works fine in HomeKit as well

any update about the premium features?

@Mickel_Luiten picking this up again because we never closed it, and post 877 looks like the same problem (Daikin ACs showing as “Not Supported” in Apple Home via Matter Bridge).

I looked into how Homey core handles the default thermostat_mode cards, and you’re right: renaming the values on existing devices would break flows. But there’s a way to do it that breaks nothing.

Why a plain rename breaks flows
The flow saves the value id (e.g. heating), and Homey core compares it as plain text:

  • “The thermostat mode changed to …” and “The thermostat mode is …” only match when the saved id is exactly the device’s current value, so after a rename they silently stop matching.
  • “Set the thermostat mode to …” is checked against the device’s current list of values before your app even sees it, so a saved heating would fail with an “Invalid enum value” error.
  • Keeping both heating and heat in the list would keep old flows working, but both would then show up in the device picker and the flow dropdowns. There’s no way to hide a value.

Proposal: choose the ids when a device is paired

  1. Store the format per device. In each driver’s onPairListDevices, add store: { thermostatModeScheme: 'standard' } (homey-oauth2app merges this with its own session data). In onOAuth2Init, set it to 'legacy' when it’s missing. That covers every device that exists today, and a repair keeps it.
  2. Map in one place. Only heating/cooling get renamed. Every other mode still comes straight from the Daikin API per model, like now: auto already is a Homey id, and dry/fanonly stay as they are. The app already does this kind of mapping for the lowercase ids in resolveOperationModeFromHomey, so it’s a small extension:
const STANDARD_IDS = { heating: 'heat', cooling: 'cool' };

toHomeyMode(daikinMode) {
  const id = String(daikinMode).toLowerCase();
  return this.getStoreValue('thermostatModeScheme') === 'standard' ? (STANDARD_IDS[id] ?? id) : id;
}

async resolveOperationModeFromHomey(value) {
  return this.operationModes?.find(mode => this.toHomeyMode(mode) === value) ?? value;
}

Use toHomeyMode wherever the thermostat_mode values and current value are set.

  1. Optional: a device setting like “Use Homey standard thermostat modes (heat/cool)” for existing users who want to switch without re-pairing. It should warn that flows using the default thermostat-mode cards with heating/cooling need the value picked again. setCapabilityOptions applies the change immediately.

One change is needed either way: the app’s own “for operation-mode …” condition cards (fan mode/speed, swing, offset) compare the thermostat_mode value with the Daikin mode name. They should compare the device’s internal operationMode instead, and so should the dry/fanOnly checks in the AC driver. Then your own cards behave the same with either set of ids.

What this means for users

  • Existing devices: nothing changes, and all flows keep working.
  • Newly added devices, or removed and re-added ones: get heat/cool. Removing a device already breaks every flow that used it, so there’s nothing extra to fix.
  • Matter Bridge (and other integrations): work for those devices. Matter Bridge handles the airconditioning class now, but only recognises the ids heat/cool/auto/off. With today’s ids an AC only exposes auto, and a heating-only Altherma has no recognised mode at all, so Matter Bridge skips it. That’s most likely what post 877 is running into.

Happy to help test a build.

I have implemented your proposal.

Please test with test version 7.13.0 Daikin ONECTA | Homey

Be aware that u need to remove the device and pair it again.
This wil break the flows for that device.

Repair doesn’t work to get the correct values

There is also no settings page because that is not supported on Homey(cloud)

let me know if this works for you.

Tested 7.13.0 after re-pairing my AC: everything works, and it’s exposed correctly via Matter Bridge. Thanks a lot!

Small follow-up: the picker shows the raw ids as names (“heat”, “fanonly”, header “OPERATIONMODE”), and only in English. The titles can be translation objects where you build the list:

const MODE_TITLES = {
  auto: { en: 'Automatic', nl: 'Automatisch', de: 'Automatisch' },
  heating: { en: 'Heat', nl: 'Verhitten', de: 'Heizen' },
  cooling: { en: 'Cool', nl: 'Koelen', de: 'Kühlen' },
  dry: { en: 'Dry', nl: 'Drogen', de: 'Entfeuchten' },
  fanonly: { en: 'Fan only', nl: 'Alleen ventilator', de: 'Nur Lüfter' },
};

const values = this.operationModes.map(mode => ({
  id: this.toHomeyMode(mode), // your existing mapping
  title: MODE_TITLES[mode.toLowerCase()] ?? { en: mode },
}));
await this.setCapabilityOptions('thermostat_mode', { values });

Only the titles change, so no flows are affected. Dropping title: { en: 'operationmode' } gives Homey’s translated “Thermostat mode” header (if that makes sense for an AC maybe is a different question).

PS: Homey Cloud only rules out custom app settings pages. Device settings should still work if existing users ever want to switch without re-pairing. But personally I don’t need it.

Thanks for testing…i will publish it to live.

Some of the values still comes from the Daikin API and this is only in english.
If i only translate some values it wil be a mesh.

If the users want to use Matter bridge the know now they need to update the app and pair the device again.

In did not get any response from the emails I have send so I send another email.

In the meantime I have checked if the subscription is already enabled, which it not.

So hopefully Daikin will send me a response asap and grant my request to enable the premium ferures

It has been a while since I posted. The troubles I had before were caused by the setting “Vraagbesturing” in the ONECTA app. Because of the power save options the units did not heat the room powerful enough. So that problem solved. After weeks of investigation by my installer and Diakin. They first ruled out all hardware problems (all units got new gas, new connectors etc etc). Software setting none of them all thought about ;-(

Changing of seasons, so I am preparing my 10 Daikin units for the winter.
Situation: I have 10 hotel rooms with Daiking Onecta’s installed in every room. All connected to ONE diking account so I can control them all from the Daikin Onecta app on my phone.

Every morning house keeping gets in the rooms the units are set to “FAN ONLY, high speed”. So the rooms get ventilated. (Housekeeper has to: click MODE several times to get to FAN ONLY and hit HIGHSPEED and POWER–>3 clicks)

After cleaning is done the house keeping has to hit mode until AUTO is selected. Hit FAN until quiet is selected and click Horizontal fan and Vertical fan and OFF.
So the remote is ready for the next guest to arrive in the room.

So I created some FLOWS to have this automated, so the housekeeper doesn’t have to click several times before she starts working. And cannot forget to put the AC in my default mode.

Unfortunately because of the 10 units there are to many requests :frowning: and the whole thing goes offline in homey. (restarting the app helps until the flow is triggerd again)..

Can someone think of an (easy) solution for this ??? Does anyone of you have connections at Daikin to have the number of requests extended (depending on the amount of units)?

Gemini AI says:
"The official Daikin Developer Portal (for the cloud API, as used with systems running the Daikin Onecta app) applies the following standard rate limits for individual developers and standard applications:

• Per day: Maximum of 200 API calls per user/application
• Per minute: Maximum of 20 API calls per minute

For business partners or specialized development environments, this limit can sometimes be increased (up to a maximum of 1,000 calls per day upon request for development applications), but the standard production limit usually remains strictly capped at 200 requests per 24 hours."

So using several Wait commands >= 1 minute before activating some units could be a solution. Or you could define multiple Daikin accounts.

Thnx for you quick reply…

Multiple Diakin accounts is no option, for now I have all my units in one screen in the daikin onecta app on my phone.
Multiple accounts would mean logging in and out every time I want to activate or control a single unit.
How will homey react to 10 different Daikin accounts??
Showing 10 units from 10 different accounts on 1 dashboard. I expect that to be messy
Logging in to 10 different accounts when calling one single flow. :face_with_raised_eyebrow:

For now I will alter my flows :frowning:
Putting 10 units on FAN ONLY - HIGH SPEED - VERT FAN - HORZ FAN - SWITCH ON, requires 5 API calls per unit = 50 calls. Let’s make 15 calls just to be safe, means 3 waits for 1 minute. means 4 minutes, just to have a (professional??) system ventilating my rooms.

I sounds as a big flaw in the Daikin API design to me. It makes total sense to have this limitation when there is one unit connected. But in my case there are 10.
-Doing 5 different calls on 10 different Daikon accounts will mean a lot more traffic on their servers-

Can anyone help me to get contact information for the correct Daikin development department to notify them for my business case?
(I can imagine that there are more cases to think of just like mine? Small schools that want to ventilate classrooms in one action, hotels, small offices etc etc)

I have the same problem with my Altherma III PAC, Daikin ONECTA in v7.13.2

@WillemG , here some explantions.

About the Rate-limiting :
When somebody requesting API-Credentials by daikin they get a client-id and secret to use in a application. By default the ratelimiting is bounded to the client-ID.
With Rate-limiting :
• Per day: Maximum of 200 API calls per application
• Per minute: Maximum of 20 API calls per minute

The Homey Daikin Onecta APP used 1 client_id for all +/- 10.000 users(and growiing)
So for that reason Daikin has created a separated rate-limiting rule:
• Per day: Maximum of 200 API calls per user
• Per minute: Maximum of 20 API calls per minute

The Homey Daikin Onecta app uses some api-call for sync so in real live 150 api-call we be left to be used in flows and on devices.

Daikin state that this should be enough for “normal” users.
There’s no way Daikin will raise the rate-limiting for maybe 50 users that hits the limits.

Rate-limiting is there to protect the backendservers of Daikin.
Every modern (REST) api has this rate-limiting in there platform.
Basicly if you send a lot of reqeust you doing some kind of DDOS attack, but now this will be blocked.

REST-API is the modern way to send (HTTPS) reqeust to Daikin with Oauth2 Authentication and Autorization. Most (REST) API suppliers creates for every “feature” (e.g. temperature) a seperared endpoint that needs to be called. This is most common and therefor also Daikin using this method.

The only way to to tackle your issue is with multiple account.
I current investigate what possible ( gemini says it should be possible)

But you need to change your setup if the multi-account is going to work.

Official Daikin ONECTA app:
-Remove all units from your main account.
-Created 10 account and pair each unit to that account.
-Share these 10 account with your main accounts.
-Now you have all 10 units in your main account and in the offcial daikin account you can switch easily between these units/rooms/accounts.

Homey Daikin App.
-Remove all units.
-Pair unit with there own account.
-repair flows.
-All units are in homey without switching.

Its a lot of administrative work but theoraticly this should work but let me test it and come back to you.
Beacuse of the separted accounts every units has its own rate limit with:
• Per day: Maximum of 200 API calls per user
• Per minute: Maximum of 20 API calls per minute

Checkout Daikin ONECTA | Homey

Version 8.0.1 adds support for multiple Daikin Accounts.
See my previous post howto handle.

If have tested it with my 2 Daikin AC units, created 2 seperated account @daikindaikin, pair the 2 units in this 2 accounts, shared the to main account to have then you have them all in official daikin app

Removed them from homey, and pair them with the 2 new accounts.
Please test if there any bugs send me a PM.

The heating season just started, I noticed the same problem from last winter persisted, even with all Homey and Daikin updates installed.

When setting the room temperature with Homey, the Daikin app follows. So the temp setting in both apps is equal. OK.

However, when setting the room temperature with the Daikin app or room thermostat, Homey does not follow. Not OK:

Homey then displays the old value set previously (e.g. the day before) from within the Homey app. The value set with the room thermostat or Daikin app is leading for the Altherma, it responds to that value. In this situation, lowering the room temperature with a Homey flow to 18°, when going to sleep, does not work since Homey’s setting is already at 18°. And lowering the device’s target temperature with Homey also has no effect. One has to lower the temperature with the Daikin app or home thermostat before going to sleep, easy to forget…

This is very annoying, help to solve this is highly appreciated!

Homey Pro 13.5.3

Daikin Onecta Homey app 7.13.2

Daikin UI 7.11.0

Daikin indoor unit software 0793

Daikin outdoor unit software 802B

Thanks for reading! :grinning_face:

André

Hi, I just tried to use in Apple home with matter bridge, the pump appese with all his features, but it doesn’t work. It does not turn on or off, anything change.

Am i doing something wrong?

Hi there, Some Daikin AC and Altherma didn’t work any more. Repairing opens the correct connection window and allows homey to connect, aftera uto closing the window nothing happens any more… Homey reboot and new ip and so one doesn’t work. Try to chose a new account that doesn’t work either (screenshot). Has so a great idea? :slight_smile: Do you know that bug @Mickel_Luiten ?

:white_check_mark: solved (12 hours off then on again).

Interesting that this came with the update yesterday :thinking: