I am begging - please continue to maintain and don’t ever let it die like betaboon did… THANKS! <3
Or you can update the card using the new entities…
entity.attribute.filter_pre_remaining is now a sensor
Mine is: sensor.ac3829_living_room_filter_pre 
Thank you 
vote changed
If I get to, I’ll update the frontend as well. Need to do it anyhow for myself 
1 Like
Well, I guess we have to be really grateful to betaboon and all his work. It’s the foundation of the current implementation. The tricky bit will be to debug all the different models and situations as I don’t have access to those devices. And it is double painful with the connectivity being so bad. Hopefully, we find some more people to support this.
My purifier MAC starts with e8:C1:D7 which points to a Philips WiFi chip.
I filled in the poll.
Model: 3829/10
I changed my host name manually. No clue what it said right after installation.
I am pretty sure it is an http device. I am using a repository from marlub.
@kongo09 will my http device work reliably with your new integration?
You can’t demand that from a dev…
I already have my own repository in hacs, and it is really hard to find time for development and support when having a family with 2 young kids… (not to mention my full time job)
I would like to step in the Coap issues, but it will really take a lot of debug hours…
And after that is fixed, there will be loads of other stuff that people want to have fixed (or maybe Philips changes something what’ll cause us to start from scratch…who knows🤔)
I totally understand when something gets too much and someone want to move on….it should be a pleasant challenge, not a hard burden!!
We just should be happy betaboon left the repository for someone to pick it up 
4 Likes
No. The integration supports only encrypted CoAP
I already suspected that but I was not sure.
Thx for confirming this and thx for the fast response.
As a workaround for the quite cumbersome selection of modes and fan levels I created a Dropdown Helper combined with three automations:
My air purifier is an AC2889/10 called Sauron
The Helper is configured like this:
Sauron Mode (input_select.sauron_mode)
Options:
Off
Auto
Allergen
Bacteria
Level 1
Level 2
Level 3
Turbo
Sleep
The Automations
For the four level Settings:
alias: Sauron Set Level
description: ''
trigger:
- platform: state
entity_id: input_select.sauron_mode
to: Level 1
- platform: state
entity_id: input_select.sauron_mode
to: Level 2
- platform: state
entity_id: input_select.sauron_mode
to: Level 3
- platform: state
entity_id: input_select.sauron_mode
to: Turbo
condition: []
action:
- service: fan.set_percentage
data:
percentage: |
{% if is_state('input_select.sauron_mode', 'Level 1') %}
25
{% elif is_state('input_select.sauron_mode', 'Level 2') %}
50
{% elif is_state('input_select.sauron_mode', 'Level 3') %}
75
{% else %}
100
{% endif %}
target:
entity_id: fan.sauron
mode: restart
For the automatic modes / presets:
alias: Sauron Set Preset Mode
description: ''
trigger:
- platform: state
entity_id: input_select.sauron_mode
to: Auto
- platform: state
entity_id: input_select.sauron_mode
to: Allergen
- platform: state
entity_id: input_select.sauron_mode
to: Bacteria
- platform: state
entity_id: input_select.sauron_mode
to: Sleep
condition: []
action:
- service: fan.set_preset_mode
data:
preset_mode: '{{ states(''input_select.sauron_mode'') | lower }}'
target:
entity_id: fan.sauron
mode: restart
And last but not least an automation to turn it off:
lias: Sauron Turn Off
description: ''
trigger:
- platform: state
entity_id: input_select.sauron_mode
to: 'Off'
condition: []
action:
- service: fan.turn_off
data: {}
target:
entity_id: fan.sauron
mode: restart
Finally
Add the input_select entity to your UI and your done with the controls. Not as pretty as betaboons but does the job in a minimalistic way.
1 Like
Hello!
First of all, thanks for the improved integration, it mainly works with my ac3858 too.
The first few characters of the mac address defines only the vendor of the wifi chip in the device. It does mean that philips probably made a contract with mxchip, but not all mxchip wifi chip was delivered to philips. That way there can be false positives. I changed the hostname too, but it was mxchip IIRC.
After a while the connection is lost to my purifier, I’ve tried to check why but have no idea. But when I choose to send diagnostic information in the application in the email I can see that sometimes local connection is set to “no”. IDK why it says that but it would be good to debug I think.
My wifi mac is in the 04:78:63 pool
Yes. That’s the downside of dhcp discovery. The idea would be to listen to these mxchip devices and try to get some data from them. If it doesn’t work, than discard them.
Waiting for it!
Probably due to Coap issues, but good finding!!
I’ve tried to do autodetect in a beta v0.9.6-beta.1 but honestly, I’m not really sure about it. You can give it a try and see how it works for you. In the worst case, you can always go back to the normal version.
Hrmmm strange just installed via HACS and rebooted but can’t find the integration? Am I missing something? No errors in the log.
Which version?
Version V0.9.5 using Hassos 2022.4.4
Did you go to Configuration, Devices, Add Integration and selected Philips?
Ah another reboot and it has shown up. Strange why it didn’t appear previously. Thanks!