Faikout smart home integration, free and open source

Control your Daikin air conditioners locally through their Faikout module.
This integration connects Gladys to your Daikin air conditioners fitted with a Faikout module (formerly Faikin). The Faikout replaces the original Wi-Fi module and is driven locally, on your own network: no cloud, no account, no Internet needed.
In Gladys, each air conditioner becomes a device with:
- power, mode (auto, cooling, heating, dry, fan only), set point and fan speed;
- horizontal and vertical swing (on or off: no fixed position), and the Econo, Powerful, Comfort, Streamer and quiet outdoor unit modes, when your unit has them;
- the readings: room temperature, outside temperature, inlet and refrigerant temperatures, humidity, power consumption and the energy meter (kWh).
The integration only creates what your air conditioner actually reports: a function your model lacks does not show up.
Before you start
- Fit the Faikout module in the air conditioner (see the Faikout setup manual).
- Join it to your Wi-Fi: on first start it opens its own access point, with a setup page.
- Check that you can open its web page (
http://<module address>/) from your network and drive the air conditioner from it. - Give it a fixed IP address (a DHCP reservation in your router). That is the address Gladys will use.
Gladys talks to the module the way its own web page does: keep the Faikout
web controls on (webcontrol, on by default).
Configuration
In Integrations → Faikout → Configuration:
| Field | Role |
|---|---|
| Faikout units | The address of each module, separated by commas. A name followed by = in front of the address names the device. |
| Web password | Only if a web password is set in the Faikout settings (the same one for every unit). Leave empty otherwise. The settings password is not needed. |
| Refresh interval | How often each air conditioner is read, in seconds (30 by default, 5 to 600). A change made with the remote shows in Gladys within this delay. |
Example:
Living room=192.168.1.50, Bedroom=192.168.1.51, 192.168.1.52
- Without a name, the device takes the module's own name (its hostname).
- A name ending in
.local(e.g.guestac.local) is often not resolved inside the integration container: prefer the IP address. - A port other than 80 is written
192.168.1.50:8080. - With a web password, Gladys sends it the way the Faikout page does once logged in (a cookie, in clear on your network, as the Faikout settings warn). The settings password stays unknown to Gladys: it never needs it.
Then click Test the connection: for each unit, the message says whether it answers, its model, its protocol (S21, X50A…), its mode and the room temperature.
Finally, open the integration's Discover tab and create the devices it offers.
What each device badge means
| Badge | Meaning |
|---|---|
| Local | The Faikout answers, so does the air conditioner. |
| Local + orange dot | The Faikout answers, but not the air conditioner: check the S21/X50 cable. |
| Unreachable | The Faikout does not answer: switched off, off the Wi-Fi, or a new address. |
Scenes
Triggers
| Trigger | When |
|---|---|
| An air conditioner goes offline or comes back | The Faikout stops answering (reason unreachable), the air conditioner stops answering the Faikout (reason aircon), then when all answers again. |
| An air conditioner is changed outside Gladys | Power, mode, set point or fan changed with the IR remote, the Faikout web page or a Faikout timer. Never by Gladys itself. |
| An air conditioner starts or ends defrosting | While heating in the cold, the outdoor unit stops for a few minutes to melt its frost. |
Each trigger can be filtered by air conditioner, and by state (or by what
changed). The values are available in the scene, e.g.
{{triggerEvent.data.mode}} or {{triggerEvent.data.temperature}}.
Changes made by Faikout auto (which moves the set point and the mode by itself) do not fire "changed outside Gladys".
Actions
| Action | Role |
|---|---|
| Set an air conditioner | Power, mode, set point and fan in one go. A field left empty keeps its value. |
| Set Faikout auto | The Faikout heats or cools by itself to keep the room between target − range and target + range. A range of 0 stops it. |
| Read an air conditioner | A fresh reading: online, power, mode, set point, room and outside temperature, humidity. Never fails: test the Online output. |
Their outputs can be used by the next actions of the scene (conditions, messages…).
For a single command (switch on, change the set point), Gladys' standard Set device value action works too.
Energy monitoring
When the air conditioner reports its energy meter (Faikout field
Whoutside, usually with the S21 protocol), the device gets an Energy
meter feature, in kWh. It is an index: Gladys derives the 30-minute
consumption and its cost from it by itself, and shows them in the Energy Monitoring
integration.
- Once the device is created, open Integrations → Energy Monitoring in Gladys: the air conditioner is listed there, attached to your main meter if you have one.
- The meter moves by steps of 100 Wh: over a short period, the consumption shows as steps.
- The power consumption (in W) stays available for live values.
- An air conditioner that does not report this meter does not get the feature.
- Multi-split (several indoor units on one outdoor unit): the meter is the outdoor unit's, so each Faikout may report the same one: check in Energy Monitoring that it is not counted twice.
Dashboard widgets
- Faikout air conditioner: one unit. Live tiles (room, set point, outside, power), a chart of the room, set point and outside temperatures over 24 h, then state, mode, fan, flaps, comfort modes, and Faikout auto or defrost while they run. An On or Off button (the opposite of the current state) and Refresh. Pick the unit in the widget settings.
- Faikout overview: all your air conditioners on one card, with their mode and room temperature.
Troubleshooting
- "no answer" in the connection test: open
http://<address>/from a computer on the same network as Gladys. If the page does not open, the problem is the network (address, Wi-Fi, VLAN), not Gladys. - "web password missing or wrong": a web password is set on the Faikout. Type the same one in Web password (copy it from the Faikout settings).
- A command fails with "did not apply": the air conditioner does not have that function, or the Faikout cannot drive it.
- Faikout auto does not apply: the Faikout is driven by an external
controller (EnvMon, MQTT
controlcommand), which takes priority. - A device stays unreachable after an address change: put the new address in Faikout units. The Gladys device is tied to the module's MAC address: it keeps its history and its scenes.
Privacy
Everything stays on your network: the integration only talks to the addresses
you give it, over local HTTP and WebSocket. The web password, if any, is kept by Gladys
with the configuration and only sent to the units. It only keeps, in its /data
volume, the MAC address, name, model and feature list of each unit, to find
its devices again even when an air conditioner is off at start-up.
Configuration settings
These are the settings Faikout asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| Getting started | section | No | Faikout replaces the Wi-Fi module of a Daikin air conditioner and is driven on your network, with no cloud. Join each unit to your Wi-Fi first (see the Faikout setup manual), keep its web controls on (they are by default), then list the units below. Gladys finds their features by itself. |
| Faikout units | string | No | The address of each unit, separated by commas. Prefer a fixed IP address: names ending in .local are often not resolved inside the integration. Put a name and = in front to name the device, e.g. Living room=192.168.1.50. |
| Web password | secret | No | Only if a web password is set in the Faikout settings: the same one for every unit. Leave empty otherwise. The settings password is not needed. |
| Refresh interval (s) | number | No | How often each unit is read, in seconds. A change made with the remote control shows up in Gladys after at most this delay. |
How to install Faikout in Gladys
- In Gladys, open Integrations: Faikout appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/prohand/gladys-faikout:1.1.0), starts it in a sandbox isolated from the core, and generates the integration's interface (devices, discovery and configuration). - Open the Configuration screen of the integration, fill in the settings, and save.
- You can also install it directly from its repository URL: https://github.com/prohand/gladys-faikout.
Faikout requires Gladys >=5.1.0. The catalog inside Gladys refreshes every hour, so a new version becomes available at most one hour after its release.
Not running Gladys yet? It is free and open source: follow the installation guide to get started.
About external integrations
Faikout is an external integration: a community integration packaged as a Docker container and published on GitHub, that Gladys installs in one click and runs in a sandbox isolated from its core. It is published and maintained by prohand, not by the Gladys core team.
- Browse all external integrations
- Discover the native integrations built into Gladys
- Build and publish your own external integration
- Source code on GitHub — source of this documentation