Dyson

The original text was already deleted or overwritten when we archived it.

Dyson integrates with HA. https://preview.redd.it/fv5dyib9wp2c1.jpeg?width=1290&format=pjpg&auto=webp&s=07e7ec6baf074caa50ed5bd751209b52b6d0bf2f

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

Having the same problem, I have and old Dyson pure cool (`438`) that I've been able to add locally. I also have a regular Purifier Humidify+Cool that I can't add. The `get_devices.py` out put is as follows: [code] Is there already some workaround to add the device while it's fixed properly?

Excerpt saved from GitHub on 2026-10-23.

Hi there! Supporting Formaldehyde fans is definitely something we are working on adding soon. You can check my comment on a pull request for more information: https://github.com/libdyson-wg/libdyson-neon/pull/7#issuecomment-1501923127 But the short version, copied from that comment: > Properly supporting Formaldehyde models actually happens to be one of the things I want to solve with a light refactor I'm working on right now. The challenge here is this: Dyson dealt us a tricky hand with their product codes for Formaldehyde models. The code 527K is correct for BOTH the Formaldehyde and …

Excerpt saved from GitHub on 2026-10-23.

The original text was already deleted or overwritten when we archived it.

The original text was already deleted or overwritten when we archived it.

The problem Last 2025.5 Home Assistant release introduced the possibility to expose fans as air purifiers through the HomeKit bridge. My Dyson purifiers are exposed as switches, with multiple sub accessories inside HomeKit, instead of Air Purifiers. ### What version of Home Assistant Core has the issue? 2025.5.0 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue HomeKit Bridge ### Link to integration documentation on our website _No response_ ### Diagnostics information …

Excerpt saved from GitHub on 2026-10-23.

The problem I see an error in the logs when HomeKit attempts to load the `ha-dyson` custom component. Logging here in case the issue lies with core; if it's determined that this is a problem with the custom component, let me know and I'll log with that author. ### What version of Home Assistant Core has the issue? core-2021.12.3 ### What was the last working version of Home Assistant Core? ? ### What type of installation are you running? Home Assistant Container ### Integration causing the issue HomeKit ### Link to integration documentation on our website …

Excerpt saved from GitHub on 2026-10-23.

… (Hass.io/Docker/Windows/etc.): Manual install on Raspberry Pi Component/platform: https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/dyson Description of problem: When starting up Home Assistant my two Dyson DP04 are detected but it throws the following error: `[homeassistant.components.homekit.util] ['low', 'medium', 'high'] does not contain the speed setting off as its first element. Assuming that low is equivalent to 'off'.` Actually it should be off and speeds 1 to 10 (which I can later see in the speed list of my Dyson fan, still the dev tool doesn't allow …

Excerpt saved from GitHub on 2026-10-23.

… Core release (if known): - Operating environment (Home Assistant/Supervised/Docker/venv): Docker, Supervised - Integration causing this issue: Homekit/Dyson fan/Xiaomi air purifier - Link to integration documentation on our website: HomeKit: https://www.home-assistant.io/integrations/homekit/ Dyson fan: https://www.home-assistant.io/integrations/dyson/ Xiaomi air purifier: https://www.home-assistant.io/integrations/fan.xiaomi_miio/ ## Problem-relevant `configuration.yaml` [code] ## Traceback/Error logs ```txt Logger: homeassistant.components.homekit.util Source: components/homekit/util.py:234 …

Excerpt saved from GitHub on 2026-10-23.

Unable to add Dyson Hot+Cool Link sensors on Homekit I have configured the bridge by the Integration UI to add the Dyson Hot+Cool Link control on the Home App. The fan works well and I am able to switch to hot/cool, oscillate, set the fan speed. But I can't add the dyson sensors like humidity or air quality to homekit even if I check the 'sensors' checkbox on the bridge setup UI... ## Environment - Home Assistant Core release with the issue: HassOS 4.10 - Last working Home Assistant Core release (if known): N/A - Operating environment (OS/Container/Supervised/Core): N/A - Integration causing …

Excerpt saved from GitHub on 2026-10-23.

The problem Dyson integration does not expose humidity or air quality (pm25) to homekit by default ## Environment - Home Assistant Core release with the issue: 2020.12.1 - Last working Home Assistant Core release (if known): - Operating environment (OS/Container/Supervised/Core): Mac OSX Catalina 10.15.7 - Integration causing this issue: Dyson - Link to integration documentation on our website: https://www.home-assistant.io/integrations/dyson/ ## Problem-relevant `configuration.yaml` [code] ## Traceback/Error logs [code] ## Additional information The dyson integration works perfectly within …

Excerpt saved from GitHub on 2026-10-23.

Summary Adds support for the Dyson HushJet Purifier Compact HJ10 (cloud ProductType `897`, model prefix `M4P`). - Maps `897` / `HJ10` / `M4P` to a `DysonPureCool` instance via a local `get_device` wrapper, so this works without changes to libdyson-neon - Custom fan entity with speed and preset mode only, no oscillation or direction, as the HJ10 doesn't support either - Sensors limited to PM 2.5, PM 10, and filter life, the HJ10 has no humidity, temperature, VOC, or NO₂ sensors - Speed commands sent as a single MQTT message to avoid the device resetting to max speed Tested on a real HJ10 …

Excerpt saved from GitHub on 2026-10-23.

Hi @moonmelon1. Unfortunately Vis Nav was supported until Dyson disabled the connection method we use in a firmware update. This integration uses MQTT to communicate directly with the device over LAN. After a firmware update last year, the Vis Nav stopped accepting MQTT Connections and now only seems to work via the cloud connection, which is not used in this integration. I don't currently have plans to add cloud connectivity features unless it becomes required for more devices. I'll mark this topic as closed, but please feel free to follow up if you have any questions. You can also check out …

Excerpt saved from GitHub on 2026-10-23.