Philips Air Purifier

Installation Home Assistant OS
387

Oh, there is a reply, how wonderful. That means, we can try to interpret the data and then try to also send data to the device to change settings.

Please go to the github repo and file an issue, posting the data as well.

It will take some time and fiddling around to interpret the meaning of the data. Take a look at this old issue to get a feel of what’s needed. You would have to help to create a similar table and play around with your app while recording the settings as above. Support request Model AC1715/11 · Issue #42 · kongo09/philips-airpurifier-coap · GitHub

I’m happy to help to get it going.

1 Like
388

Guys I am sorry but I need your lights please. Is it possible to force update the firmware to these units except the default guide with unplugged for some seconds? It seems on my end firmware cannot update at all

389

Not to my knowledge, Philips pushes them out. But why would you want a Fw update? The Philip updates continue to break the integration. Personally I set my purifiers up on a no internet vlan to avoid further fw updates

390

Side question, where is the Philips AC1715 available for purchase in the USA? I can’t find a retailer upper NY state.

391

Dear all, I own an AC1214/10 model. I installed the integration provided by @kongo09. As auto discovery failed, I did a manual setup and entered the IP. Unfortunately, I got timeouts in 10/10 trials. Restarts of the purifier did not help. Is there any advise? Should I enable debugging and post the result?

Thanks,
Tobias

392

Hmm…I use a AC1214/10, and I don’t have issues (except for the occasional drop)

2023-03-05 18:09:29.968 ERROR (MainThread) [coap] Connection loss was not expected.
2023-03-05 18:09:44.987 ERROR (MainThread) [coap] Connection loss was not expected.
2023-03-05 18:10:10.670 ERROR (MainThread) [coap] Connection loss was not expected.

But these are inmedeately resolved…

GitHub - kongo09/philips-airpurifier-coap: 💨 Philips AirPurifier custom component for Home Assistant. Supports local CoAP protocol. mentiones:

Due to a bug in the Philips devices, this integration is rather instable. It might or might not work. Even if it seems ok at first, it might stop working after a while. Sometimes, a power cycle of the Philips device helps. Sometimes, only a power cycle and a Home Assistant restart together help. It is frustrating. Do not report this as an issue here. Nobody can help right now. @mhetzi contributed timer code to attempt reconnects if the device is not responsive. Sometimes, that helps. But not always. You’ve been warned.

393

It’s a pain that is beyond my expertise to fix. Some people report that switching devices off and on makes them available. Some the mobile app for power on/off and that seems to work. Some need to unplug. For some it never works and for some it works most of the time and then out of the blue fails. For myself, it is totally random. Right now it works. A week ago it wasn’t. I don’t know.

394

Yes, I already fail in the very first setup…

Here you find some logs filtered on “coap”; does it give some insights?

  33519,83: 2023-03-07 16:09:49.525 DEBUG (MainThread) [custom_components.philips_airpurifier_coap.config_flow] trying to configure host: 192.168.178.72
  33520,56: 2023-03-07 16:09:49.657 DEBUG (MainThread) [aioairctrl.coap.client] syncing
  33521,45: 2023-03-07 16:09:49.668 DEBUG (MainThread) [coap] Sending request - Token: ab51, Remote: <UDP6EndpointAddress 192.168.178.72>
  33522,45: 2023-03-07 16:09:49.669 DEBUG (MainThread) [coap] Sending message <aiocoap.Message at 0x7f7d8c7070: NON POST (MID 53513, token ab51) remote <UDP6EndpointAddress 192.168.178.72>, 1 option(s), 8 byte(s) payload>
  33522,71: 2023-03-07 16:09:49.669 DEBUG (MainThread) [coap] Sending message <aiocoap.Message at 0x7f7d8c7070: NON POST (MID 53513, token ab51) remote <UDP6EndpointAddress 192.168.178.72>, 1 option(s), 8 byte(s) payload>
   33526,45: 2023-03-07 16:09:50.088 DEBUG (MainThread) [coap] Sending request - Token: 09cd, Remote: <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>
  33526,94: 2023-03-07 16:09:50.088 DEBUG (MainThread) [coap] Sending request - Token: 09cd, Remote: <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>
  33527,45: 2023-03-07 16:09:50.089 DEBUG (MainThread) [coap] Sending message <aiocoap.Message at 0x7f8e2afbe0: CON GET (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 1 option(s)>
  33527,71: 2023-03-07 16:09:50.089 DEBUG (MainThread) [coap] Sending message <aiocoap.Message at 0x7f8e2afbe0: CON GET (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 1 option(s)>
  33527,144: 2023-03-07 16:09:50.089 DEBUG (MainThread) [coap] Sending message <aiocoap.Message at 0x7f8e2afbe0: CON GET (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 1 option(s)>
  33528,45: 2023-03-07 16:09:50.090 DEBUG (MainThread) [coap] Exchange added, message ID: 61289.
  33545,45: 2023-03-07 16:09:50.989 DEBUG (MainThread) [coap] Incoming message <aiocoap.Message at 0x7fa9023430: ACK 2.05 Content (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 2 option(s), 612 byte(s) payload>
  33545,72: 2023-03-07 16:09:50.989 DEBUG (MainThread) [coap] Incoming message <aiocoap.Message at 0x7fa9023430: ACK 2.05 Content (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 2 option(s), 612 byte(s) payload>
  33545,154: 2023-03-07 16:09:50.989 DEBUG (MainThread) [coap] Incoming message <aiocoap.Message at 0x7fa9023430: ACK 2.05 Content (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 2 option(s), 612 byte(s) payload>
  33546,45: 2023-03-07 16:09:50.990 DEBUG (MainThread) [coap] Exchange removed, message ID: 61289.
  33547,45: 2023-03-07 16:09:50.990 DEBUG (MainThread) [coap] Received Response: <aiocoap.Message at 0x7fa9023430: ACK 2.05 Content (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 2 option(s), 612 byte(s) payload>
  33547,74: 2023-03-07 16:09:50.990 DEBUG (MainThread) [coap] Received Response: <aiocoap.Message at 0x7fa9023430: ACK 2.05 Content (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 2 option(s), 612 byte(s) payload>
  33547,156: 2023-03-07 16:09:50.990 DEBUG (MainThread) [coap] Received Response: <aiocoap.Message at 0x7fa9023430: ACK 2.05 Content (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 2 option(s), 612 byte(s) payload>
  33548,45: 2023-03-07 16:09:50.991 DEBUG (MainThread) [coap] Response <aiocoap.Message at 0x7fa9023430: ACK 2.05 Content (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 2 option(s), 612 byte(s) payload> matched to request <Pipe at 0x7f8e2ae4a0 around <aiocoap.Message at 0x7f8e2afbe0: CON GET (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 1 option(s)> with 2 callbacks>
  33548,64: 2023-03-07 16:09:50.991 DEBUG (MainThread) [coap] Response <aiocoap.Message at 0x7fa9023430: ACK 2.05 Content (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 2 option(s), 612 byte(s) payload> matched to request <Pipe at 0x7f8e2ae4a0 around <aiocoap.Message at 0x7f8e2afbe0: CON GET (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 1 option(s)> with 2 callbacks>
  33548,146: 2023-03-07 16:09:50.991 DEBUG (MainThread) [coap] Response <aiocoap.Message at 0x7fa9023430: ACK 2.05 Content (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 2 option(s), 612 byte(s) payload> matched to request <Pipe at 0x7f8e2ae4a0 around <aiocoap.Message at 0x7f8e2afbe0: CON GET (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 1 option(s)> with 2 callbacks>
  33548,303: 2023-03-07 16:09:50.991 DEBUG (MainThread) [coap] Response <aiocoap.Message at 0x7fa9023430: ACK 2.05 Content (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 2 option(s), 612 byte(s) payload> matched to request <Pipe at 0x7f8e2ae4a0 around <aiocoap.Message at 0x7f8e2afbe0: CON GET (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 1 option(s)> with 2 callbacks>
  33548,376: 2023-03-07 16:09:50.991 DEBUG (MainThread) [coap] Response <aiocoap.Message at 0x7fa9023430: ACK 2.05 Content (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 2 option(s), 612 byte(s) payload> matched to request <Pipe at 0x7f8e2ae4a0 around <aiocoap.Message at 0x7f8e2afbe0: CON GET (MID 61289, token 09cd) remote <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f92aa3490>, 1 option(s)> with 2 callbacks>  
  33914,85: 2023-03-07 16:10:19.528 WARNING (MainThread) [custom_components.philips_airpurifier_coap.config_flow] Timeout, host 192.168.178.72 doesn't answer, aborting
395

What year was yours bought? The ac2889 for example comes in multiple versions, some are coap, others (pre2021?) http. It might be worthwhile to check if the Philips Air purifier http integration works for you?

https://github.com/GeorgeSG/philips_airpurifier_http

1 Like
396

Hello Fellow Philips Filter Users
A quick heads up. About 6 months ago I had to completly reset my whole HA (Supervised) installation. I didn’t bother to include the filters right away becaus the connection was never stable and restarting the filters and integration was just not worth it.
Now I readded both AC2889 filters which received firmware updates due to me not paying attention when setting up the new router.
But all the problems of the past seem to be solved now. The filters connect to the 2,4GHz even though the router provides a 5GHz Network with the same name. This didn’t work before and was a known limitation.
Also the connection to HA seems to be stable for about a month now.

This combination works for me. As we all know results will vary widely! So be careful with Philips provided updates.

Firmware on my devices:

software_version: 1.0.7
wifi_version: [email protected]

Thanks for the ongoing development of this integration!
-jutonium

1 Like
397

Hi, i can’t see the integration in home assistant search. I only see Philips hue, Dynalite and Philips tv. Am I doing something wrong?

398

Yes, you need to install the custom component first (e.g. via HACS)

399

Thank you. What is the correct one to install?

400
401

Hello
Have you found a way how to interg the Philips AMF765 in ioBroker? Or with HomeAssistant or Homebridge or …?
Thanks a lot

402

Hi
I implemeted the new integration from kong09. It works fine.
Thank you :grinning:

Is there an update of the card from kongo09 with the new sensors?
Thank you

403

Been using the HACS version for Philips Air Purier now for a while from: Release v0.15.0 · kongo09/philips-airpurifier-coap · GitHub

Works pretty oke. When i’ts going down I just reboot HA or turn the AC3829 off/on and the connection is restored. Too bad it’s not an “official” integration without HACS.

404

If the sensor is available as an attribute you could also create a sensor template to expose the value in Lovelace.

My configuration.yaml contains the following lines:

template:
  - sensor: !include template_sensors.yaml

And in the template_sensors.yaml are a few sensors defined like this:

- unique_id: living_room_t_ref
  attributes:
    friendly_name: "Living Room Reference Temperture"
  unit_of_measurement: °C
  state: "{{ state_attr('climate.living_room_heating', 'temperature') | default(0.0) }}"
  device_class: temperature
  state_class: measurement
  availability: "{{ states('climate.living_room_heating') != 'unavailable' }}"
405

As part of my search for a working card, I found the following solution: https://github.com/EvisHome/Home-Assistant/tree/main/examples/air-purifier.
Only small adjustments are required. It works fine without the “animation: rotation”.

One problem with this is that the integration for AC2889/10 in “Auto mode” does not provide any values for ‘percentage’.

406

Hi, I have one AC3829/10 which works well with Philips Air+ app. But it failed to connect to the kongo09’s integration . The strange thing is that I cannot ping it from other hosts in the same Wifi network. I even tried arping its mac address directly. I am sure the IP address is right because I checked the mac address in the wifi router’s GUI. Also I used the ‘ping’ function provided by the router, and also cannot ping it. I also tried to use aioairctrl and aircntrl, which also falied to connect. Any hint?