[philipsair] New binding for Philips Air Purifiers

Hello community,

I would like to share with you a new binding for Philips Air Purifiers device family.
The OpenHAB binding provides readings and control of Philips Air Purifier devices.

Based on the project at py-air-control
by rgerganov and this binding is an adaptation to OpenHAB project. Thanks for researching the whole communication with those devices!

Any feedback welcome!

Supported Things

Supported Philips Air Purifiers (hardware testes) devices are

  • AC2889/10
  • AC2729/50


  • first OpenHAB 2 binding poviding support for Phlips Air Purifiers devices
  • auto discovery via UPNP
  • power off/on,
  • fan speed control,
  • purification mode control,
  • lights control,
  • sensor readings (air quality, temperature, humidity)


Source code

Draft build

Hi Michal,

thanks a lot for your hard work, just because of the binding i decided to choose the app connected air purifier instead of the dumb one!

I will gladly test your binding next week. Do you have a paypal account or something to buy you a coffee, beer or something in that category?

Thanks again



Thank you for your work.
Do you know if new Philips models DualScan are supported
for example this model Philips Dual Scan AC3858/50 ?
Asking based on comments here:

There is an experimental support for newer models (after end of 2019) which communicate over the CoAP protocol. So this binding support CoAP protocol also?

Yeah, i got one of the new ones which have every port closed. So no smart air purifier for me.

If you want to follow up, there is an issue for that on github:



Hi @regnets,

Yes, I’m aware of the recent switch to CoAP but as it’s already noted here - yes, looks like it won’t be easie to provide support as the communication is encrypted and ports are closed :confused:

Hi @michalboronski,
First of all many thanks for your work!
I have a problem with the binding, it does not discover my AC2889/10 automatically.
Currently I am running openHAB 2.5.6-2 and I have tried the following versions:
The manual installation was successful, it is shown as active in the console and I can see it in Paper UI.
In the Philips app the AC2889/10 is also shown and I can control it without problems.
Is there anything else special to do, what else can I check?
Or does the binding generally not work correctly with openHAB 2.5.6?

Is anyone still working on this @michalboronski ?
As far as I understand the coap connection is „hacked“ and working with the newer devices again.

But I have no idea how to adapt the changes from the actual python version to a an openhab binding.

Maybe someone is interested in updating the bindung?


Maybe someone can help me how I can the get the actual powerstate to sync it with openhab?

This is what I’ve done so far…I installed the phyton script and I am able to control my device via command line.
I created a simple rule so when I switch a item to on or off a script with the command line code will be started to power on or off the device.
This is working fine, also the control via „Fan“ in HomeKit works nice.

My only problem is when the powerstate is changed on the device itself (physical button) or via the Philips app the powerstate is no longer synchronized.

How can I fetch the powerstate and show it correct in openhab no matter how the state is changed?

Thank you!


will there be an update to 3.0? Am very interested in it!

best regards

Me too :wink:

Best regards

@michalboronski or whoever finds it useful:
In anticipation of my Philips air to arrive I made this port to OH3:

UnfortunatelyPhilips cancelled my order, so I’ll not have one on short notice to actually test it with a device.
But you may find it useful. It compiles again against the OH3.1 (disabled few of the tests though)

1 Like

Hi Guys,

After beeing on a long hiatus as a developer over last months (it’s all covid’s fault;)) I’m planning to get back to coding beginning of March and try to add what is needed for most recent FW. First I need to upgrade my OH from 2.5 to 3 :wink:
@marcel_verpaalen I will definitely take a look at your port to see what has changed in terms of OH3
We can open a new PR once it is verified it works against newer FW.


any news here?