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?
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?
@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)
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 @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.