homebridge-daikin-local

Supports Daikin Air Conditioners on HomeBridge by connecting to the optional Daikin Wifi Controller

or the alternative Faikout WIFI Controller. You can find information on how to buy that alternative controller on the Github page.

WARNING

Daikin has removed their local API in newer products. They offer a cloud API accessible only under NDA, which is incompatible with open source. This affects units fitted with the BRP069C4x wifi adapter.

The Daikin App will most likely ask you to update the devices firmware. If you want to continue to use this plugin, DO NOT UPDATE THE FIRMWARE.

In case you already updated the firmware or you bought a new device, you may want to have a look at this plugin instead: https://github.com/tasict/homebridge-daikin-local-platform.

About this plugin

This plugin retrieves sensor and mode data from a Daikin WIFI controller in your local network and allows you to set operation modes and target temperatures. As it is a plugin for HomeBridge you will have access to these features using Apple Home.

It is recommended to configure your DHCP server to reserve a fixed IP for the wifi controller.

This plugin can be installed using Homebridge UI.

Configuration

This screenshot shows the configuration in Homebridge UI:

Features

The FAN: The FAN allows you to turn on the fan of your Daikin AC. You can also set the speed of the fan. Apple HomeKit allows you to set a speed percentage from 0% to 100%. This plugin translates this percentage value as follows: 0% to 9%: SILENT mode 10% to 20%: AUTO mode 21% to 30%: Level 3 31% to 40%: Level 4 41% to 60%: Level 5 61% to 80%: Level 6 81% to 100%: Level 7 (max)

The AC: Apple HomeKit settings allow you to enable or disable the swing aka oscillation mode. As HomeKit is limited to a true or false value, the plugin's configuration allows you to configure the type of swing mode. Available modes are "horizontal swing", "vertical swing" and "3D".

Swing / oscillate configuration (swingMode):

• 1 — vertical swing when Oscillate is on in HomeKit
• 2 — horizontal swing when Oscillate is on
• 3 — 3D swing (both directions) when Oscillate is on

Turning swing off is done with the Oscillate toggle in the Home app, not via swingMode.

Oscillate visibility in the Home app: Where the Oscillate control appears depends on how HomeKit groups the AC and Fan accessories:

• Combined tile: fan speed may appear when scrolling the tile; Oscillate is often hidden.
• Separate tiles: Oscillate usually appears in the Settings view (gear icon) on the AC tile and/or the Fan tile.

Recommended workaround if Oscillate is missing: leave disableFan as false (default), then in the Home app long-press the accessory → Settings → Show as Separate Tiles, and use Oscillate from Settings on either tile. Setting disableFan to true hides the Fan tile but does not reliably surface fan speed or oscillate in the Home app on all iOS versions.

Econo Mode: When enabled in the configuration, a switch will appear in HomeKit to toggle the AC's Econo mode. This energy-saving mode reduces power consumption by moderating the cooling/heating output.

Powerful Mode: When enabled in the configuration, a switch will appear in HomeKit to toggle the AC's Powerful mode. This mode provides maximum cooling or heating output for rapid temperature change.

Important: Econo mode and Powerful mode are mutually exclusive - they cannot both be active simultaneously. Turning on one will automatically turn off the other, as they have opposite effects on power consumption and performance.

Night Quiet Mode: When enabled in the configuration, a switch will appear in HomeKit to toggle the AC's Night Quiet mode. This mode reduces noise for silent operation during nighttime.

AC Modes (Dry/Fan): When enabled in the configuration, a fan slider will appear in HomeKit to switch between special AC modes:

• 0-20%: Off
• 21-49%: Dry mode (dehumidification)
• 50-79%: Fan-only mode
• 80-100%: Return to normal operation (Cool/Heat/Auto)

Note: Night Quiet Mode can be used independently with either Econo or Powerful modes.

Technical background information on the API used

The apiroute is used for two main calls: Get info such as current activity and sensor readings from the thermostat and set the target temperature and modes. The Aircon LAN adapter provides two directories for these settings and data:

1. /common uses the GET method for control and system information about the Aircon (e.g software version, MAC address, Reboot System, Region)

2. /aircon uses the GET method to set Aircon related information (e.g Target Temperature, Modes like Heat and Cool, Temperature Sensor Readings, Timers)

Supported devices

Currently, this plugin supports:

• Daikin wifi controllers supporting the "aircon" URLs (System: Default)
• Skyfi controllers supporting the "skyfi" URLs (System: Skyfi)
• ESP32-Faikout chipset (System: Faikout) - An open-source alternative WiFi controller for Daikin units

Testing Standard Daikin/Skyfi Controllers

To test http connectivity, use your browser to connect to your device using one of these URLs:

http://192.168.1.88/aircon/get_model_info
http://192.168.1.88/skyfi/aircon/get_model_info

replace the IP (192.168.1.88) with the IP of your device.

Your browser should return a line like this:

ret=OK,model=0AB9,type=N,pv=2,cpv=2,cpv_minor=00,mid=NA,humd=0,s_humd=0,acled=0,land=0,elec=0,temp=1,temp_rng=0,m_dtct=1,ac_dst=--,disp_dry=0,dmnd=0,en_scdltmr=1,en_frate=1,en_fdir=1,s_fdir=3,en_rtemp_a=0,en_spmode=0,en_ipw_sep=0,en_mompow=0

If it does not, your device is not yet supported.

ESP32-Faikout Support

If you're using the ESP32-Faikout open-source WiFi controller, select "Faikout" as the system type in the configuration. The Faikout system provides:

• Local control without cloud dependencies
• MQTT and Home Assistant integration
• Enhanced features and faster response times
• Full compatibility with this plugin's special modes (Econo, Powerful, Night Quiet)

For Faikout devices, the plugin automatically uses the JSON-based control API. The special modes work as follows:

• Econo Mode: Controlled via the econo parameter (boolean)
• Powerful Mode: Controlled via the powerful parameter (boolean)
• Night Quiet Mode: Controlled via the fan parameter set to 'Q' (Quiet mode)
• Swing Mode: Controlled via swingh and swingv parameters (separate horizontal and vertical swing booleans)

For traditional Daikin controllers, the special modes work as follows:

• Econo Mode: Controlled via the en_economode parameter
• Powerful Mode: Controlled via the en_powerful parameter
• Night Quiet Mode: Controlled via the f_rate parameter set to 'B' (Silent/Night mode)
• Swing Mode: Controlled via the f_dir parameter (0=No swing, 1=Vertical, 2=Horizontal, 3=3D)

Faikout Attribute Support: The plugin currently supports these Faikout control attributes:

• power (boolean) - AC on/off state
• mode (H/C/A/D/F) - Heat, Cool, Auto, Dry, Fan modes
• temp (number) - Target temperature in Celsius
• fan (A/Q/1-5) - Auto, Quiet, or manual fan levels 1-5
• swingh (boolean) - Horizontal louvre swing
• swingv (boolean) - Vertical louvre swing
• powerful (boolean) - Powerful mode
• econo (boolean) - Economy mode

Not yet implemented:

• target - Single temp or min/max array for Faikout auto mode
• env - Temperature reference for Faikout auto mode
• streamer - Air purifier/ionizer boolean

To test Faikout connectivity, access your Faikout device's web interface at http://<Faikout-ip>.local or check the /aircon/get_control_info endpoint.

To test https connectivity see HTTPS/Registered client support

The response of an unsupported device will look like this:

ret=PARAM NG,msg=404 Not Found

Tested devices are documented here: (https://github.com/cbrandlehner/homebridge-daikin-local/wiki/Tested-devices,-reported-to-work)

If you have other devices or firmware versions working, please update the wiki.

HTTPS/Registered client support

Some models require requests via https containing a registered client token.

TLS / OpenSSL 3: No configuration is required. On Node.js 18+ (linked against OpenSSL 3.x), the plugin automatically selects a legacy TLS agent for HTTPS connections to Daikin controllers (legacy renegotiation support). At startup, Homebridge logs a line such as TLS: HTTPS apiroute — using legacy TLS agent when this applies. There is no OpenSSL3 setting in the plugin config.

It is necessary to register a client token with each device. The same token may be registered with multiple devices.

These instructions are based on comments in GitHub Project ael-code/daikin-control Issue #27

1. Generate a UUID4 (https://www.uuidgenerator.net can be used), e.g. 7b9c9a47-c9c6-4ee1-9063-848e67cc7edd
2. Strip the - from the UUID, i.e. 7b9c9a47c9c64ee19063848e67cc7edd
3. Grab the 13-digit key from the sticker on the back of the controller. e.g. 0123456789012
4. Register the UUID as a client token

curl --insecure -H "X-Daikin-uuid: 7b9c9a47c9c64ee19063848e67cc7edd" -v "https://<controller-ip>/common/register_terminal?key=0123456789012"

This UUID must be used in client requests to the device.

Test your registered token using the above requests but using https instead of http, e.g.

curl --insecure -H "X-Daikin-uuid: 7b9c9a47c9c64ee19063848e67cc7edd" -v "https://192.168.1.88/aircon/get_model_info"
curl --insecure -H "X-Daikin-uuid: 7b9c9a47c9c64ee19063848e67cc7edd" -v "https://192.168.1.88/skifi/aircon/get_model_info"

In the configuration file, make sure you specify https in the apiroute option and add the registered token as the value of uuid in the configuration for each device, e.g.

        "accessories": [
            {
                "accessory": "Daikin-Local",
                "name": "Living room",
                "apiroute": "https://192.168.1.50",
                "uuid": "7b9c9a47c9c64ee19063848e67cc7edd",
                "system": "Default",
                "swingMode": "2",
                "defaultMode": "0",
                "fanMode": "FAN",
                "fanName": "Living room FAN"
            }
        ],

Make sure to use the correct token if a different token has been registered with each device.

Debugging and Testing

The code of this plugins generates debug output. Normally, this debug output is not visible on the homebridge console.

Before reporting any issue or bug, enable debugging and restart.