Dyson
cmgrayb/hass-dyson · vv0.38.0
Unofficial Home Assistant integration for Dyson fans, vacuums, and lights
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
light | Light | |
switch | Switch or outlet | |
climate | Thermostat | |
fan | Fan | |
humidifier | Humidifier or dehumidifier | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
vacuum | Vacuum (as a switch) | |
button | Button (as a switch) | |
select | Mode picker (as switches) |
What people report
Dyson purifiers and fans work with local MQTT and cloud discovery, but heater control is limited. Weak Wi-Fi or stuck local MQTT causes dropouts. BLE-only vacuums are now supported.
- Works1
- Partly works3
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Dyson V16 Piston Animal floor-care vacuum | Works Local | BLE-only floor-care support addedSaved copyAdd support for BLE-only Dyson floor-care vacuums (V16 Piston Animal) Adds support for Dyson's LEC floor-care vacuums, device category `flrc`, connection category `lecOnly`, using the V16 Piston Animal as the reference machine. Fixes #434. ## Why These vacuums have no Wi-Fi and no MQTT. They talk exclusively over Bluetooth Low Energy, and after the same LTK handshake the BLE light already uses they speak a completely different protocol: Dyson's binary attribute protocol rather than the lamp's command set. Before this change every `lecOnly` device was routed to the BLE Light configure flow, … Excerpt saved from GitHub on 2026-10-23. | PR #467 · 2026-09 | |
| Dyson HP09 Pure Hot+Cool | Partly works | Entities discovered; heater control not available yetSaved copyHi, I have a Dyson HP09 and the integration correctly discovers sensors and control entities. However, no matter which communication mode I use on the device, nothing gets triggered in or by Home Assistant. For example, the fan entity shows up, but after a refresh it switches to off, even though the physical fan is still running. This means the entity states do not reflect the actual device state. Happy to provide more logs if needed – thanks for your work on this integration! Here is the sanitized output from the *Get Cloud Devices* action: ```yaml account_email: "*HIDDEN*" total_devices: 1 … Excerpt saved from GitHub on 2026-10-23. | Issue #46 · 2025-09 | |
| Dyson HP11 Pure Hot+Cool | Partly works | Works with this integration only; no heating control yetSaved copy… hook my device up to HA is to automate where it is pointing. The only thing stopping it from being perfect is heater control! Hope this helps. Using a Dyson Pure Hot+Cool HP04. Let me know if there's any more info or testing you need. ```yaml account_email: "*HIDDEN*" total_devices: 1 devices: - serial_number: "*HIDDEN*" name: Bedroom product_type: "527" device_category: - ec capabilities: - AdvanceOscillationDay1 - Scheduling - EnvironmentalData - ExtendedAQ - ChangeWifi model: HP04 m Excerpt saved from GitHub on 2026-10-23. | Issue #46 · 2025-09 | |
| Dyson Pure Hot+Cool HP04 | Partly works Local | Worked after Wi-Fi fix; heating climate and extended AQ sensors missingSaved copyDevice - Model: Dyson Pure Hot+Cool (HP04) - Firmware: ECG2PF.30.06.003.0002 - Serial prefix: ZZ7 (Canada region) ### Integration - Version: 0.35.0 (installed via HACS) - Setup method: Dyson Cloud Account (Cloud Discovery) ### Issue After setup via Cloud Discovery, the device comes online fully and creates 33 entities, but is missing both the Heating capability (climate platform / heat control) and the detailed ExtendedAQ sensors (PM2.5, PM10, VOC, NOx, carbon filter). Only basic entities appear: - fan: 1 fan entity - sensor: air quality category, air quality index, indoor AQI (15-min), … Excerpt saved from GitHub on 2026-10-23. | Issue #430 · 2026-08 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Found automatically over
- DHCP
Details
| Installs (analytics) | 1,953 (0.28%) |
|---|---|
| GitHub stars | 119 |
| Latest version | v0.38.0 (2026-10-20) |
| Set up in the UI | Yes |
| Maintainers | @cmgrayb |
| License | MIT |
Devices listed in its README
- Cloud Discovery - Automatic device detection via Dyson API
- Manual Setup - Sticker-based or network-isolated configuration for local devices
- Static IP Configuration - Bypass mDNS with static IP/hostname for reliable connectivity
- Capability Based Detection - Automatic platform setup based on device features
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/cmgrayb/hass-dyson
- Source code: https://github.com/cmgrayb/hass-dyson
- Issues: https://github.com/cmgrayb/hass-dyson/issues
- HACS: https://hacs.xyz