[ST Edge] Fujitsu FGLair air conditioners: on/off, mode, setpoint, fan and swing via a small bridge (Windows or Docker)

Fujitsu air conditioners with an FGLair wifi adapter are not in SmartThings. This brings them in, with control and status.

What you get

  • On and off
  • Mode: auto, cool, dry, fan only, heat (labels follow your phone language, English or Dutch)
  • Set temperature 16 to 30 °C in half degrees, in every mode
  • Fan: quiet, low, medium, high, auto
  • Swing: fixed or vertical (horizontal and both on units that have it)
  • Airflow direction: louver position when swing is fixed, on units that have it (since bridge 2026-11-06f)
  • Room temperature and outdoor temperature (outdoor only on units with an outdoor sensor; a unit without one switches to a layout without it by itself, since driver 2026-11-06T22:05)
  • Minimum Heat as an extra mode, on units that have it, like in the FGLair app (since bridge 2026-11-06e)
  • Changes from the FGLair app or the remote show up within a minute

How it works
FGLair adapters only talk to the Fujitsu cloud and Edge drivers can not reach the internet. So a small Python bridge on a pc that is always on (Windows or Docker) polls the cloud every 60 s, and the Edge driver on the hub reads the bridge over your LAN.

Before you start

  • A pc that is always on with a fixed IP: Windows (installer included, network set to Private) or any Docker host (Linux, NAS, Raspberry Pi)
  • The email and password of your FGLair app

Install

  1. Download GitHub - Stoeckie/smartthings-stoeckie-bridge: Stoeckie Bridge: cloud appliances (AEG/Electrolux, Fujitsu FGLair, Škoda, iRobot favorites) in SmartThings. Bridge for Windows or Docker plus Edge driver · GitHub. Windows: copy the bridge folder to the pc and run install.bat (installs Python if needed, firewall rule, autostart). Docker: docker compose up -d --build in the bridge folder
  2. Enter your FGLair email and password on the setup page (http://localhost:8787/setup, only reachable on that pc)
  3. Enroll your hub: SmartThings. Add a little smartness to your things. (Stoeckie Edge Drivers) and install Stoeckie Bridge (local)
  4. Add device > Scan nearby. A “Stoeckie Bridge” device appears, the air conditioners at the next poll with their FGLair names

Code (bridge and driver, one repository for all brands): GitHub - Stoeckie/smartthings-stoeckie-bridge: Stoeckie Bridge: cloud appliances (AEG/Electrolux, Fujitsu FGLair, Škoda, iRobot favorites) in SmartThings. Bridge for Windows or Docker plus Edge driver · GitHub
Page for this brand: GitHub - Stoeckie/smartthings-fujitsu-fglair: Fujitsu FGLair air conditioners in SmartThings: small bridge (Windows or Docker) plus Edge driver · GitHub

Developer notes

Running here with two units (adapters AP-WF2E and AP-WD1E). Feedback welcome, especially from other models.

Thanks for sharing. Could have used this years ago when I did my first install. Ended up substituting the Cielo Breez for the built-in wifi connection on the Fujitsu since there was not a great pathway between ST and the Fujitsu.

Update (bridge 2026-11-02c): FGLair app works normally again

The library writes a “refresh” to the wifi adapter on every update so it reads the room temperature again. With a poll every minute that kept the adapter busy: the FGLair app then showed “Air conditioner information acquisition not completed” and a setpoint changed in the app jumped back. The bridge now only reads the cloud values on each poll and asks the adapter for a fresh room temperature at most every 15 minutes. Control from SmartThings was not affected. Update the bridge to get it.

Tip: also a “back online” notification

If you made the Offline routine (Stoeckie Bridge (FGLair air conditioners) device, Connection is Offline, send notification), duplicate it in the app and change the condition to Connection is Connected, with a text like “Stoeckie Bridge (FGLair air conditioners) is back online”. Then you know the problem is over without opening the app. The device also shows Last drop (when, how long, why).

README updated with the same tip.

Wow! Thank you…this is just what I needed, as Samsung is about to kill API access for free. I have been using Homebridge to connect virtual switches to actions on the mini split.

A few things…I decided to go the Docker route and it was tedious but possible, especially with help of CoPilot AI. AI instructed me to add lynx and then open the Setup page in Lynx. That worked. The Dutch page for the bridge was a bit tough to consume, but AI helped again by seeing things that I could not.

Any chance of providing support for the mode “Minimum Heat”? It’s a mode that keeps the room at a bare minimum temperature. It’s great for vacation homes, cabins, etc…

@danhvos thanks, great feedback. All three points are in now.

Update (bridge 2026-11-06d, driver 2026-11-06c)

Setup page in English. Everything on the setup page is English now.

Docker: no lynx needed. Open http://localhost:8787/setup in a normal browser on the Docker host itself. With host networking that just works. Without host networking (port mapping, Docker Desktop, many NAS) the bridge now sees it runs in a container and also allows the Docker network gateway, so localhost on the host works there too. From another computer: add its address to STBRIDGE_SETUP_ALLOW in docker-compose.yml, for example STBRIDGE_SETUP_ALLOW: "192.168.1.20/32", then open https://(docker host ip):8443/setup (https only, the certificate is self signed). Details in the README, section 1b.

Minimum Heat. Units that report the min_heat property now get Minimum Heat as an extra mode in the mode list, just like the FGLair app shows it (edit: first version had a separate switch, changed to a mode in bridge 2026-11-06d). Choosing another mode or switching off ends Minimum Heat. Changes from the FGLair app or remote show up too. Units without it look the same as before. You can also pick the mode in routines, for example when the house is empty for a few days.

To update: Docker git pull then docker compose up -d --build in the bridge folder; Windows: copy the new files and run install.bat again (config.json stays). The driver updates on the hub by itself (or reinstall it from the channel). After the update the mode shows up within a minute.

Both of my units have the property. Please let me know how it works on yours.

Update (bridge 2026-11-06e, driver 2026-11-06d): clearer controls

  • Minimum Heat is now a normal entry in the mode list, like in the FGLair app, instead of the raw minHeat text. Choosing another mode or switching off ends it.
  • The target temperature is now called Set temperature instead of “Cooling setpoint”, which was confusing in heat mode.
  • Both follow the language of your phone (English and Dutch for now).

This uses two small custom capabilities and a custom device view. The standard mode and cooling setpoint stay on the device, so Google Home, Alexa and existing routines keep working; they are just no longer shown twice. Update the bridge as before; the driver updates on the hub by itself and the air conditioners switch to the new view within a minute (close and reopen the SmartThings app if you still see the old one).

Update (bridge 2026-11-06f, driver 2026-11-06e): airflow direction

With swing on Fixed you can now pick the louver position in SmartThings: Airflow direction, position 1 to the number your unit supports (both of my units have 4). Choosing a position switches vertical swing off. It works in routines too, for example a lower position when heating. Units that do not report positions do not get the control.

Update the bridge as before; the driver updates on the hub by itself.

Bridge 2026-11-06g for FGLair users: please update, Python 3.13 required

The bridge moved to Python 3.13 (needed for the new local Home Connect support, [ST Edge] Home Connect (Bosch, Siemens, Neff) dishwasher and oven, local without cloud: status, door, temperature, stop (small bridge)). On Windows run install.bat once more: it installs Python 3.13, rebuilds its environment and keeps your config.json and FGLair login. Docker users rebuild the image (python:3.13-slim). Minimum Heat, set temperature and airflow direction work as before.

A few things…

  1. I Did the git pull and got the minheat button in SmartThings app. I did not get the latest update. That may be a timing thing on the ST side. I’ll try it again later. However, when I tap the minheat button, it errors out, “A network or server error occurred. Try again later.”
  2. AC-UTY note. I am not sure which WLAN card I have, but the name is AC-UTY under “Air conditioner setting” in the FGLair app, although I do not have an external thermostat. It works except for the minheat issue.

@danhvos thanks for testing.

1. Getting the latest driver
The channel has the new version, but a hub picks it up on its own schedule (that can take up to a day). To get it right away: open the channel link SmartThings. Add a little smartness to your things., Available drivers, Stoeckie Bridge (local), Install. Your devices stay as they are. From driver 2026-11-06c Minimum Heat is one of the modes in the mode list, not a separate button.

2. The error on Minimum Heat
That message means the bridge refused the command. My guess: on your unit the FGLair cloud only reports the min_heat property and does not let you set it (US units can differ from my EU ones). Bridge 2026-11-06h (just pushed) checks this: when min_heat is read only it no longer offers Minimum Heat, so you get no button that cannot work, and the log says why.

Could you:

  1. Update the bridge. For Docker, in the folder where you cloned the repo:
    git pull
    cd bridge
    docker compose up -d --build
    
    The --build matters: the image is now based on python:3.13-slim (the bridge needs Python 3.13). Your settings in bridge/data stay. Check the version on the setup page or with docker compose logs --tail 50
  2. Post the log line that starts with [fglair] unit (docker compose logs | grep "fglair] unit"). It lists the property names of your unit (no values) and says whether min_heat is writable. You can leave out the serial number
  3. If you still see Minimum Heat: tap it and post the bridge log lines that follow (docker compose logs --tail 50)

If your unit uses another property for Minimum Heat, that line shows it and I can add it.

3. AC-UTY
Thanks. The bridge does not depend on the adapter model; it uses what the FGLair cloud reports for the unit.

Took a while to get all of the updates. The “minHeat” mode is now working! OMG! However, it is still named “minHeat”. The version I see attached to the device is: 2026-11-06T17:25:27.3852…

I’m assuming that is not the latest ST Edge driver.

@danhvos great that Minimum Heat works now!

2026-11-06T17:25:27 is the latest driver, so you have everything. With it the device page uses its own mode list, which shows Minimum Heat (and “Set temperature” instead of “Cooling setpoint”). The raw “minHeat” comes from the standard mode list that the older driver showed. The driver switches each air conditioner to the new layout when it starts, but the app keeps the old layout in its cache for a while.

Could you:

  1. Fully close the SmartThings app (swipe it away) and open it again
  2. If it still says minHeat: tell me where you see it (device page, the tile on the dashboard, or in a routine) or post a screenshot

Routines made before the update still point at the standard mode list; those keep showing minHeat until you pick the mode again in the routine.

I am seeing the mode listed as “minHeat”, and still seeing “Cooling temperature” even though I’m on that release. When I open the device, I receive the message, "This device hasn’t updated all of it status information yet. Check again later.

Should I delete this device and rediscover?

@danhvos thanks, that message explains it. “This device hasn’t updated all of its status information yet” means the new mode list and Set temperature (they replace “Cooling setpoint”) never got their first value on your hub, so the app falls back to the old view with minHeat and Cooling temperature.

Cause: when the driver switched your air conditioner to the new layout, the very first update of the mode list arrived before the switch was done, was refused, and the driver remembered it as sent. I fixed that in driver 2026-11-06T18:41 (it now sends a refused update again at the next poll). Please don’t delete the device, that would break your routines.

  1. Get the new driver now: open SmartThings. Add a little smartness to your things., Available drivers, Stoeckie Bridge (local), Install
  2. Wait a minute, then fully close the SmartThings app (swipe it away) and open it again; do that twice, the app keeps the old layout in its cache for a while
  3. Open the air conditioner: the mode list should show Minimum Heat and the warning should be gone

If it still shows the warning after that, tell me and I’ll look further.

I installed that update a few hours ago, and followed your instructions but am still getting the same error message, and no change to the labels. “This device hasn’t updated all of it status information yet. Check again later.”

Do you know how often that info gets polled?

@danhvos found it, thanks for your patience. I could reproduce it on my own second unit: when an air conditioner is switched off, the bridge reports its mode as “off”, which is not one of the modes in the new list, so the driver never filled in the new mode list. That empty value is what triggers “This device hasn’t updated all of its status information yet”, and the app then falls back to the old view (minHeat, Cooling temperature).

Fixed in driver 2026-11-06T21:56: while the unit is off the mode list keeps the last mode (so routines and the view always have a value). It also retries the switch to the new layout if a device somehow still has the old one.

  1. Install it now from the channel link (Available drivers, Stoeckie Bridge (local), Install), or wait for the hub to pick it up
  2. Check the version: open the air conditioner, menu (3 dots), Driver; it should say 2026-11-06T21:56 or later
  3. Wait a minute, close the app fully and open it again

To answer your question: the bridge reads the FGLair cloud every 60 s and the hub asks the bridge every 10 s, so after the update it should be right within a minute.

One more possible cause of that warning: if your unit has no outdoor temperature sensor, the “outdoor” temperature stays empty. That does not change the labels, but tell me if the warning stays after the update, then I’ll make that part optional.

@danhvos a small addition to my last post: the outdoor part is now optional automatically. Since driver 2026-11-06T22:05 an air conditioner that reports no outdoor temperature for 3 polls in a row switches to a layout without the outdoor temperature, so an empty value can’t cause “hasn’t updated all of its status information” anymore. My attic unit had the same and switched by itself.

Nothing to do for you besides installing the driver from the channel (or waiting for the hub to pick it up). If the warning is still there after that, please let me know which driver version the device shows.

@danhvos one more for Docker users: bridge 2026-11-07a moves to Python 3.14, because Python 3.13 no longer gets security releases as Windows installers. For Docker this means a new base image (python:3.14-slim), so please update with git pull and then docker compose up -d --build in the bridge folder (the --build matters). Your settings in bridge/data stay. Nothing changes for the air conditioners themselves.

I tried it last evening (US East) and again today. Still the error and misnamed labels. Not complaining! Just glad you are working on it. I’m not at home this weekend, but can test further after the weekend.

And I did update the bridge and SmartThings driver. 2026-11-06T22:22:30 release