Philips Air Binding improved coap connectivity [4.0.0.0;5.0.0.0)

Philips Air Binding
logo

Binding to support the integration with Philips Air Purifiers including the models based on COAP communication protocol (most >2019 models)

Note may require to (manually) install coap and upnp transport

feature:install openhab-transport-coap
feature:install openhab-transport-upnp

Changelog

2021-11-04 Initial market place version.

2022-12-15 Minor update

2023-09-24 Version bump oh4 - Minor update

2024-01-29 Version bump oh4 - Alpha version with new connectivity approach for Coap based devices

  • Use observeAndWait to keep better connectivity
  • Extra verbose logging (needs to be removed later)

2024-05-05 Version bump oh4 - beta version with new connectivity approach for Coap based devices

Notes:

Philips Air Binding is developed by Michał Boroński
(GitHub - michalboronski/openhab-addons: Add-ons for openHAB 2.x
Coap protocol support (this version) contributed by [Marcel Verpaalen] (Profile - marcel_verpaalen - openHAB Community)
Discussion topic in this forum: Binding request: Philips air purifier
Market place topic for 3.x version: Philips Air Binding [3.0.0.0;4.0.0.0)
Alternative installation jar (you must manually install coap and upnp transport): https://verpaalen.com/openhab/org.openhab.binding.philipsair-4.1.2.jar

Resources

https://verpaalen.com/openhab/org.openhab.binding.philipsair-4.1.2.kar

Hey, i got myself an AC0850/11 Air purifier. Unfortunately it seems it uses a different data format but also via COAP and the decryption also works. I might wanna try and add that to the binding but the link to the Github for Version 4.2 is dead. Can you maybe update that? Maybe you just forgot to push that branch. I occasionally see Data from in the logs with that version, the older versions do not seem to work as reliably with my purifier.
Thanks a lot

yes, seems I have missed that.
pushed it now

new version pushed.

I manage to build a .kar version with the latest, but still needed to manually
install coap and upnp transport

feature:install openhab-transport-coap
feature:install openhab-transport-upnp

Hello Marcel
I am a bit blind to find your philips binding latest vers. for OH 4.2. Can you please show me the way.
regards
Wolf

Strange, in the marketplace only the version from last year can be found “2023-09-24 Version bump oh4”.

The links to the new .jar or .kar are not working. Should we use the old version?

Let me check what happened to the links/server.

I think I did something wrong indeed when last time updating the files.
Suggest to use this one https://www.verpaalen.com/openhab/org.openhab.binding.philipsair-4.1.2.jar it is the version I also use in my openhab instance.

If you need different version:
These are the files I have on the server (https://www.verpaalen.com/openhab/ ):
The most up2date version is the .jar And normally when I update I rename the existing .jar to [some number].jar

Feb 26  2021 org.openhab.binding.philipsair-3.1.0-SNAPSHOT.jar
Aug 10  2021 org.openhab.binding.philipsair-3.2.0-SNAPSHOT2.jar
Aug 11  2021 org.openhab.binding.philipsair-3.2.0-SNAPSHOT3.jar
Nov  4  2021 org.openhab.binding.philipsair-3.2.0-SNAPSHOT.jar
Nov  5  2021 org.openhab.binding.philipsair-3.2.0-SNAPSHOT.kar
Dec 17  2022 org.openhab.binding.philipsair-3.4.0-SNAPSHOT.jar
Dec 17  2022 org.openhab.binding.philipsair-3.4.0-SNAPSHOT.kar
Dec 17  2022 org.openhab.binding.philipsair-3.4.0-SNAPSHOT-sources.jar
Sep 24  2023 org.openhab.binding.philipsair-4.0.4-SNAPSHOT.jar
Sep 24  2023 org.openhab.binding.philipsair-4.0.4-SNAPSHOT.kar
Sep 24  2023 org.openhab.binding.philipsair-4.0.4-SNAPSHOT-sources.jar
Sep 24  2023 org.openhab.binding.philipsair-4.1.0-SNAPSHOT1.kar
Sep 24  2023 org.openhab.binding.philipsair-4.1.0-SNAPSHOT.jar
Sep 24  2023 org.openhab.binding.philipsair-4.1.0-SNAPSHOT.kar
Sep 24  2023 org.openhab.binding.philipsair-4.1.0-SNAPSHOT-sources.jar
May  6 16:13 org.openhab.binding.philipsair-4.1.2.jar
May  6 16:13 org.openhab.binding.philipsair-4.1.2.kar
May  6 16:13 org.openhab.binding.philipsair-4.1.2-sources.jar
Jan 14  2024 org.openhab.binding.philipsair-4.2.0-SNAPSHOT1.jar
Jan 30 00:25 org.openhab.binding.philipsair-4.2.0-SNAPSHOT2.jar
Jan 30 00:26 org.openhab.binding.philipsair-4.2.0-SNAPSHOT.kar
Jan 30 00:25 org.openhab.binding.philipsair-4.2.0-SNAPSHOT-sources.jar
Jun 10  2021 org.openhab.binding.philipsairC2-3.1.0-SNAPSHOT.jar
Apr  6  2021 org.openhab.binding.philipsairC-3.1.0-SNAPSHOT.jar

Thanks for the quick fix :+1:

Hi Marcel,
fist of all thank you for you work maintaining this binding.
Since my device is not discovered with the marketplace version, I tried installing the 4.1.2 Version manually.
Sady I run into this error message:

2024-09-10 17:33:36.252 [ERROR] [Events.Framework                    ] - FrameworkEvent ERROR
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.philipsair [337]
  Unresolved requirement: Import-Package: com.google.gson; version="[2.10.0,3.0.0)"
	at org.eclipse.osgi.container.Module.start(Module.java:463) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1847) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1840) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1745) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1667) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345) ~[org.eclipse.osgi-3.18.0.jar:?]
2024-09-10 17:33:37.194 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.philipsair-4.1.2.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.philipsair [337]
  Unresolved requirement: Import-Package: com.google.gson; version="[2.10.0,3.0.0)"
	at org.eclipse.osgi.container.Module.start(Module.java:463) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:445) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) ~[?:?]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) ~[?:?]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) ~[?:?]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) ~[?:?]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) ~[?:?]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) ~[?:?]

Do you have any clue how to fix it?

Thank you
Martijn

What version openhab are you running

Hi Marcel,
thank you for the hint, I got rid of this error with an update to 4.2.1.
When installing the marketplace version, it still lists 4.0.4 in the sources.
I installed the Package with
bundle:install https://www.verpaalen.com/openhab/org.openhab.binding.philipsair-4.1.2.jar
Now I have the 4.1.2 version, clean logs and can also see some COAP activity on DEBUG.
Last thing I’m missing, is seeing the manually installed binding in the UI to create things with it. But I will search some more regarding that.

I just wanted to give an update/feedback that it the initial problem is gone.

1 Like