search

rgerganov / py-air-control

Command line app for controlling Philips air purifiers
MIT License
264 stars 53 forks source link

Add 'a'uto Option to 'om' Field #48

Closed Sunoo closed 4 years ago

Sunoo commented 4 years ago

One of the users of my Homebridge plugin reported that at least some COAP-based models use a setting of 'a' in the 'om' field to indicate auto mode, instead of using the 'mode' field.

https://github.com/Sunoo/homebridge-philips-air/issues/9

Sunoo commented 4 years ago

Sidenote: It would be very helpful to my project to know whether all COAP-based units work this way, or if it's just some subset. If anyone here has any information, I'd love to hear it.

Cyber1000 commented 4 years ago

At least for my coap-based device AC2889/10 it doesn't work this way, I'm getting a success message if I send --om a, but nothing happens. Only --mode A (and other mode-switches) work for me. "Om" only shows the fanspeed for me.

If I want to switch from Auto to manual I need to use a nasty workaround (switch to manual {speed-not-equal-to-current-autospeed} and then to manual speed {what-I-want} - that's the task you have mentioned here.

But there seems to be a lot of different devices ...

Sunoo commented 4 years ago

@Cyber1000 That’s what I was afraid of, guess it’s gonna be yet another configuration option in my project that people need to determine with trial and error. It would have been nice if Philips had any consistency in their devices. I guess the official app must have some sort of lookup table to determine how to interface with each model or something...