[APP][Pro] Philips Air Purifiers & Humidifier app - Healthy air, always

Apps
284

you need to use > 2020 devices . that uses coap. , before on 2019 they used some other protocol.

try to fix ip dhcp address and wifi 2.1 ghz , not shared with 5ghz.

285

Thank you very much, that helped!

286

Update: did some edits to improve the comment.

Hi Edwin,

I’m having trouble getting my Philips 4000i fully working in Homey.

The purifier can be added successfully via its IP address, but most of the device capabilities remain empty or null, including:

  • PM2.5
  • IAI
  • TVOC
  • filter values
  • purifier mode
  • fan speed
  • product/model information

I also notice that the Philips Air app crashes relatively often.

To rule out a network or purifier issue, I tested the device directly from my Mac using philips-airctrl.

The purifier identifies itself as:

  • Type: AC4236
  • Model: AC4236/14
  • DeviceVersion: 4.1.8
  • Firmware: Ms4418

The local CoAP connection itself appears to work correctly. philips-airctrl is able to:

  • complete the sync/key exchange
  • retrieve the full device status
  • subscribe to the status observer
  • receive live status updates
  • send control commands successfully

The returned status includes valid values for fields such as:
pwr, mode, om, pm25, iaql, tvoc, fltsts0, fltsts1, fltsts2, etc.

I have restarted the Philips Air app, removed and re-added the purifier after installing the newer app version, and changed the purifier state afterwards, but the missing Homey capabilities remain empty.

I then tested the power control more specifically while keeping a direct CoAP status observer running.

When I switch the purifier OFF through Homey:

  • Homey changes its own onoff capability to false
  • the physical purifier remains on
  • the purifier continues to report pwr: "1" over CoAP

I then compared the registers directly using philips-airctrl.

With the purifier switched off: D03102=1 does not turn it on. The purifier remains off and continues to report: pwr: "0"

However: pwr=1 immediately turns the purifier on, after which its status reports: pwr: "1"

Likewise: pwr=0 successfully turns it off again.

So on this AC4236/14, power control definitely uses the classic pwr register rather than D03102.

Since the device also reports the classic fields such as pwr, mode, om, pm25, iaql and tvoc, I’m wondering whether the AC4236/14 is currently being handled using the wrong register/device mapping in the Homey app.

That could potentially explain both:

  1. the outgoing Homey commands not reaching the purifier correctly; and
  2. the incoming purifier status not being mapped to the Homey capabilities.

Diagnostics report ID: ae6bbe7e-4ccb-4515-b1a2-e90b7bb61c88

287

thanks

1st I see a lot of Error: catch: No response received for sync call. Cannot proceed, is coap://192.168.1.76:5683 up or don’t use philips-airctrl , pull the plug for some minutes, restartt the homey app.

also is your network/ firewall ok ? like 2.4 only wifi , no wifi restriction between wifi devices

I did not see any response but looks like you have a firmware where philips did not know what definition they want to have like D03-02, D03102 or pwr

can you try again to send me a report

288

Thanks Edwin.

I’ve done another clean test, this time on the test version v1.0.80.

Before restarting the Homey app, I power-cycled the purifier and tested it directly once more with philips-airctrl.

Directly from my Mac, the purifier responded immediately:

  • CoAP sync completed successfully
  • status-observe connected successfully
  • the full status payload was returned
  • values such as pm25, iaql, tvoc, pwr, mode, filter status, model information, etc. were all present

For example, the purifier reported:

modelid: "AC4236/14"
DeviceVersion: "4.1.8"
pwr: "1"
mode: "S"
pm25: 1
iaql: 1
tvoc: 1

I then completely stopped philips-airctrl, so there was no other CoAP client connected.

After that I restarted the Philips Air app in Homey.

Unfortunately, Homey still does not populate most of the capabilities. It currently only seems to know values such as:

onoff: true
purifier_mode: "S"

while the following remain null:

  • PM2.5
  • IAI
  • TVOC
  • filter values
  • fan speed
  • product/model information
  • latest retrieval date
  • most other capabilities

So the purifier itself is definitely responding to CoAP sync/status requests immediately after a reboot, but Homey still does not retrieve/map the same status even when no other CoAP client is active.

I created a fresh diagnostics report directly after this test on v1.0.80:

5c41c86a-156e-4350-a6b9-42cd23402ebc

Separately, the register behaviour I mentioned before is still reproducible as well:

  • pwr=1 turns the purifier on
  • pwr=0 turns it off
  • D03102=1 does nothing

So this AC4236/14 appears to use the classic register set (pwr, mode, om, pm25, iaql, tvoc, etc.).

Hopefully the new v1.0.80 diagnostics show where the Homey CoAP connection is failing.