Summary

A custom component to interact with Winix air purifiers and dehumidifiers.

Air purifiers: confirmed on C545 and C610, and reported to work on AM90, HR1000, C909, T800, T810, 5510, 5520, 9800 — functionality may vary by model.

Dehumidifiers: confirmed on DXWE210 (Korean page). Other models in the DXW*21* family are likely compatible.

Installation

This can be installed by copying all the files from custom_components/winix/ to <config directory>/custom_components/winix/. Next add Winix integration from Add Integration and use your credentials from Winix mobile app.

Air Purifier

• C545 will generate 4 entities.
• C610 will generate 6 entities.

• The Air QValue sensor reports the qValue reported by Winix purifier. This value is related to air quality although I am not exactly sure what it represents.

• The AQI sensor matches the led light on the purifier.

  • Good (Blue) = 1
  • Fair (Amber) = 2
  • Poor (Red) = 3

• The Filter Life sensor represents the left filter life and is based on an initial life of 9 months.

• The PM 2.5 sensor is exposed only on devices that report particulate readings (e.g., T800).

• The fan entity supports speed and preset modes

• The Child Lock switch toggles the device's child lock, exposed only on devices that report support for the feature.

• The device data is fetched every 30 seconds.
• There are 4 services winix.plasmawave_off, winix.plasmawave_on, plasmawave_toggle and remove_stale_entities in addition to the default fan services fan.speed, fan.toggle, fan.turn_off, fan.turn_on, fan.set_preset_mode.
  • remove_stale_entities can be used to remove entities which appear unavaialble when the associated device is removed from the account.

Brightness Level

If the purifiers support this feature, then you will see a selection list under the device.

• Winix only supports updating the brightness level when the purifier is running.
• The last brightness level is exposed as the attribute last_brightness_level on the fan.

Dehumidifier

• DXWE210 will generate 7 entities.

• The humidifier entity is the primary control for the dehumidifier device.
  • Powers the device on or off.
    • Treats the auto-dry power state as off. It is represented by the Auto Dry binary sensor.
  • Sets the operating mode: Auto, Manual, Clothes, Shoes, Quiet, or Continuous.
  • Sets the target humidity, in the 35–70 % range with 5 % steps.
  • Reports the current humidity from the device's sensor.
• The Fan Speed select sets the fan to low, high, or turbo.
• The Auto Dry binary sensor reflects the internal drying cycle, which runs while the device is powered off.
• The Water Tank binary sensor reports a problem state when the tank is full or detached.
• The Timer number entity sets an off-timer between 0 and 24 hours.
• The Child Lock switch toggles the device's child lock, exposed only on devices that report support for the feature.
• The UV Sanitize switch toggles UV sanitization, exposed only on devices that report support for the feature.

Note

• If devices are added/removed, then you would have to reload the integration.

• Winix does not support simultaneous login from multiple devices. If you logged into the mobile app after configuring HomeAssistant, then the HomeAssistant session gets flagged as invalid and vice-versa.

  • To maintain access to both the app and Home Assistant, you can set up a second account. Use this second account for Home Assistant while keeping your main account logged in on your mobile app.

    Create a second Winix account with no devices linked. Then from your main account, navigate to Device Settings > Device Sharing > Add a user and invite the second account.

Language Support

Entity names and states are displayed in the language configured in Home Assistant. English and Korean are verified; German, French, Dutch, and Japanese are machine-translated. Corrections are welcome via pull request.

Breaking Changes

• 1.1.0 changed the sensor implementation. The aqi sensor id might be different now.

• 1.0.0 introduces config flow and previous yaml based setup is no longer supported. You would want to delete that setup and proceed to setup the intgeration as mentioned in Installation section.