Flair smart home integration, free and open source

Control Flair Smart Vents, room set points and Home/Away, read the Flair Pucks.
Control your Flair Smart Vents from Gladys, follow the temperature of every room, and switch your home between Home and Away.
What you get
After the configuration, the Discovery tab lists one device per Flair item:
| Flair item | In Gladys |
|---|---|
| Home | Home switch (off = Away), Auto mode switch (off = Manual) |
| Room | Set point (thermostat), Temperature, Humidity, Active |
| Smart Vent | Opening (0 % closed to 100 % open) and the open / close buttons |
| Puck | Temperature, Humidity |
Each device shows a cloud badge: Flair is reached through its cloud only. The badge turns unreachable when Flair does not answer, or when a vent or a puck stops reporting (empty battery, out of range).
Before you start: get your API credentials
Flair gives API access on request: write to Flair support (from the Flair website or the Flair app) and ask for API credentials for your account. You receive a client ID and a client secret.
Configuration
- Open the Configuration tab of the integration.
- Paste the Client ID and the Client secret.
- Optionally change the Refresh interval: the integration reads your Flair account every 2 minutes by default (one minute minimum).
- Save, then press Test the connection: the answer lists the homes, rooms, vents and pucks found.
- Open the Discovery tab and add the devices you want.
Good to know
- In Auto mode, Flair opens and closes the vents itself to reach the set point of each room. A vent opening set from Gladys holds until Flair's next decision. To keep the vents where you put them, switch the home to Manual (the Auto mode switch).
- An inactive room is left aside by Flair: its vents stay closed.
- A change made in the Flair app shows in Gladys at the next refresh.
Scenes
The integration adds its own cards to the scene editor, in the Integrations category.
Triggers:
- Flair home or away changed — a home switched between Home and Away
(Flair app, geofencing or Gladys itself... except a change made by the same
scene). Optionally pick the home and the new mode. The next actions can
read
{{triggerEvent.data.mode}}(homeoraway) and{{triggerEvent.data.home_name}}. - Flair device online or offline — a vent or a puck stopped reporting,
or came back. Optionally pick the device and the status. Variables:
{{triggerEvent.data.status}}(offlineoronline) and{{triggerEvent.data.device_name}}.
Actions:
- Set a Flair vent opening — 0 to 100 %. Returns the opening and whether the home is in Auto mode (Flair may then move the vent again).
- Set a Flair room set point — 10 to 32 °C. Returns the set point.
- Set a Flair home to Home or Away — returns whether the home is Home.
- Set a Flair home to Auto or Manual — returns whether Auto is on.
Dashboard
Add the Flair overview widget to a dashboard. It shows the average room temperature, the number of open vents, the devices offline, then each home (Home / Away, Auto / Manual) and each room (temperature → set point, green when close, orange or red when far). Its buttons switch the first home between Home and Away, between Auto and Manual, and refresh the data now.
Troubleshooting
- "Flair refused the API credentials" — check the client ID and the client secret, with no space around them. Ask Flair support if they still fail.
- "The Flair cloud does not answer" — Flair or your Internet connection is down. The integration tries again at every refresh.
- A device stays unreachable — check its battery and its distance to the Flair bridge in the Flair app.
- More detail in the integration logs (Gladys interface, or
docker logson the host), withLOG_LEVEL=debug.
Configuration settings
These are the settings Flair asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| Getting started | section | No | Flair is reached through its cloud API, with OAuth 2.0 credentials (a client ID and a client secret) that Flair support gives on request. Enter them below, save, then press "Test the connection": your homes, rooms, vents and pucks appear in the Discovery tab. |
| Client ID | string | Yes | OAuth 2.0 client ID of the Flair API. |
| Client secret | secret | Yes | OAuth 2.0 client secret of the Flair API. Stored as a secret, never logged. |
| Refresh interval (s) | number | No | How often the Flair account is read, in seconds (one minute minimum). |
How to install Flair in Gladys
- In Gladys, open Integrations: Flair appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/prohand/gladys-flair:1.0.1), 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-flair.
Flair requires Gladys >=5.3.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
Flair 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 integrations, native and community
- Build and publish your own external integration
- Source code on GitHub — source of this documentation