Stylish
Description
DAIKIN Stylish – ONECTA
This DDF enables the integration of a DAIKIN Stylish air conditioning unit via the DAIKIN ONECTA Cloud API into the system.
The air conditioning unit can be visualized and switched on and off via the system. The connection is established through the DAIKIN ONECTA Cloud and requires one-time authentication.
Requirements
The following requirements must be met to use this DDF:
- a compatible DAIKIN Stylish air conditioning unit
- a DAIKIN ONECTA account with access to the air conditioning unit
- an application registered in the DAIKIN Developer Portal
- the Client ID and Client Secret provided by DAIKIN
- Internet access for communication with the DAIKIN ONECTA Cloud
Application Registration with DAIKIN
To connect to the ONECTA Cloud, an application must first be created in the DAIKIN Developer Portal:
Under My Apps (top right, next to the email address), create a new application.
The following address must be entered as the Redirect URI:
https://devicelib.my-gekko.com/OAuth.php
After creating the application, DAIKIN provides a Client ID and a Client Secret. The Client Secret is displayed only once and should therefore be stored securely.
These credentials are required to authenticate the system with the DAIKIN ONECTA Cloud.
Device Station Configuration
The credentials are entered in the Device Station:
| Parameter | Description | Value |
|---|---|---|
| Domain | Address of the DAIKIN ONECTA Identity Provider used for login and authentication. | https://idp.onecta.daikineurope.com/ |
| Client ID | The identifier provided by DAIKIN when creating the application. | Your Client ID |
| Client Secret | The secret key of the application registered with DAIKIN. This is displayed by DAIKIN only once. | Your Client Secret |
| Redirect URI | Address to which DAIKIN redirects after successful authentication. | https://devicelib.my-gekko.com/OAuth.php |
After entering the data, execute the AUTHORIZE command. Then open the displayed URL and log in with the DAIKIN ONECTA account.
After successful login, the connection to the ONECTA Cloud is authorized and the access token required for communication is created.
System Device Configuration
After successful authentication, the system devices must be created and assigned to the corresponding IO groups.
-
Under Settings > More, enable BETA features.
-
Add the system device "Daikin Onecta" and select the INFO group under IO Config.
-
Add the system device for the air conditioning unit, for example "Living Room", and select the DEVICE group under IO Config.
Usage
After successful setup, the available information from the DAIKIN air conditioning unit is provided via the ONECTA Cloud and can be visualized in the system.
The air conditioning unit can be switched on and off via the system. The current information is retrieved from the ONECTA Cloud at regular intervals.
Update Interval and Limitations
The data is updated approximately every 10 minutes by default.
The DAIKIN ONECTA Cloud API is limited to a maximum of 200 requests or commands per day. This limit must be taken into account when using the DDF, particularly when performing frequent queries or switching operations.
General Info
| Manufacturer | Type | Protocol | Model | Version | ID |
|---|---|---|---|---|---|
| Daikin | Air conditioner | REST-API (DDF) | 1 | 1 | 0x0D00000D00010100 |
Documents
DDF Items
| ID | Name | Unit | Type | Direction |
|---|---|---|---|---|
| 2 | ID | |||
| 10 | Name | |||
| 11 | Model | |||
| 13 | Cloud | |||
| 14 | Fehler | |||
| 15 | Fehlercode | |||
| 16 | Zeit | |||
| 17 | IP | |||
| 18 | MAC | |||
| 20 | Raumtemp | C | ||
| 21 | Aussentemp | C | ||
| 22 | Betrieb | on, off | ||
| 23 | Modus | auto, dry, cooling, heating, fanOnly | ||
| 28 | Boost | on, off | ||
| 40 | Solltemp_aktuell | C | ||
| 41 | Ventilator_aktuell | fixed, auto, quiet | ||
| 42 | Stufe_aktuell | von 5 | ||
| 43 | Horiz_Luft_aktuell | stop, swing | ||
| 44 | Vert_Luft_aktuell | stop, swing | ||
| 46 | Raumtemp_10 | C / 10 | ||
| 48 | Solltemp_aktuell_10 | C / 10 | ||
| 50 | Abfragemeldung | |||
| 51 | Letzte_Abfrage_vor | s | ||
| 52 | Abfragefehler | 0, 1 = Fehler | ||
| 60 | Ein_Aus | |||
| 61 | Abfrage | |||
| 62 | url | |||
| 100 | POLLTOKEN | |||
| 101 | REFRESHTOKEN | |||
| 150 | EXPIRES_IN | |||
| 151 | EXPIRES_DATE | |||
| 152 | EXPIRES_REST | |||
| 153 | SLAVE |
Note
Last Commit: 77b48879 | 2026-02-26 10:11:54
*2026-04-21 09:59:43 (hw) ******************************
Last Commit: f873754c | 2026-04-21 07:56:56
*2026-04-24 06:50:07 (hw) ******************************
Last Commit: f873754c | 2026-04-21 07:56:56