8000 Dyson Purifier Hot+Cool HP1, not able to add · Issue #241 · libdyson-wg/ha-dyson · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Dyson Purifier Hot+Cool HP1, not able to add #241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Mithrox opened this issue Apr 23, 2025 · 16 comments
Open

Dyson Purifier Hot+Cool HP1, not able to add #241

Mithrox opened this issue Apr 23, 2025 · 16 comments

Comments

@Mithrox
Copy link
Mithrox commented Apr 23, 2025

Hi,

I installed the HACS addon, restarted HA, and then installed the addon under Devices & Services. When HA was rebooted, autodiscover found the fan, but when I try to add it, it fails.

Image

The error is the following:

Image

I have also tried with the correct IP as well, but with no change to the outcome.

Is this because this fan is not supported, or is there another reason why it won't connect?
@almiui
Copy link
almiui commented Apr 26, 2025

I have exactly the same problem with Dyson Humidify+Cool Formaldehyde. Tried many times Also removed everything and tried again. Deons't help.

@juanu159
Copy link
juanu159 commented May 4, 2025

I'm also having the same issue, when adding the IP address that is assigned to that device on my router it does not connect. Do anyone know what to do? What would be the correct IP address to input if it's not the one that can be found at the DHCP section in the router config?

@almiui
Copy link
almiui commented May 4, 2025

Suddenly it connected, the inly thing I know I did was correcting postal address in Dyson account.

@dotvezz
Copy link
Member
dotvezz commented May 6, 2025

Hi all, unfortunately the Dyson devices can be a bit flakey when connecting. Please feel free to share debug logs and we can investigate as needed, though!

@Mithrox
Copy link
Author
Mithrox commented May 6, 2025

I enabled debug logging and took out what looked to be the Dyson entries. Let me know if this makes sense or not. I updated to the latest version this morning and tried again, but same result.

home-assistant_dyson_local_2025-05-06T08-07-09.543Z.log

@evilbobbins
Copy link

I get the same issue on the Purifier Cool PC1 (shows as a TP11 in opendyson
tried via mydyson and manually :(

@petykowski
Copy link

I experienced this issue with Dyson Purifier Hot+Cool™ Formaldehyde HP09 earlier in the week, it randomly connected after rebooting home assistant and just continuously attempting to connect. Wish I could share a pattern.

Still trying to get my Purifier Cool PC1 to pair.

@petykowski
Copy link

I've found a fix and it appears to be related to the discoverability/dyson account method of installation.

  1. Remove Dyson Account Device from Home Assistant
  2. Reboot Home Assistant
  3. Follow instructions from this comment to get device password, serial, and ip: Dyson TP11 (new model released in March) unable to connect #238 (comment)
  4. On Home Assistant, add new entry from Dyson integration and choose to configure manually with details obtained from step 3.

Good luck!

@Mithrox
Copy link
Author
Mithrox commented May 17, 2025 •
edited
Loading

I tried the method linked, I used opendyson and got all the info, but I am still not getting connect. This is the setup when adding manual (some of the info is redacted with some xxx).

Image

I am curious if I am choosing the right Credential, I am using the info from the mqtt: password section, and when I do it works for 10+ seconds before it comes back with this message. When I try with anything else, it just instant fails.

Am I misunderstanding something here? When I used listen --iot it catch all the mqtt when I change status, turn on/off etc.

HA is running HAOS on bare metal btw, so there is no container or VM involved.

@petykowski
Copy link

I've just reviewed my configuration based on your comment and unfortunately I cannot say you've done anything wrong. All of the information required for the manual linking method is found in the mqtt section of the opendyson output, with password=credentials.

Image

Other suggestions have been to power cycle the device by unplugging so it clears the MQTT server on the Dyson device, but that doesn't seem to be your issue based on the logs you uploaded previously (for what its worth, I unplugged/plugged mine before manually connecting). Also my logs previously had the same repeating message you observed.

2025-05-16 10:07:04.720 DEBUG (paho-mqtt-client-xxx)  Connected with result code 0
2025-05-16 10:07:04.729 DEBUG (paho-mqtt-client-xxx)  Disconnected with result code 7

@mrtnkhl
Copy link
mrtnkhl commented May 17, 2025 •
edited
Loading

I have the same issue with Purifier Cool PC1 running v1.5.3 on Home Assistant Yellow HA 2025.5.2 OS 15.2. Network configuration is not an issue.

2025-05-17 12:02:18.455 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:18.457 INFO (MainThread) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected to device 9HC-EU-xxxxxxxxxxx 2025-05-17 12:02:18.461 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:19.480 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:19.486 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:20.495 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:20.501 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:21.513 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:21.519 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:22.533 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:22.540 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:23.551 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:23.558 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:24.568 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:24.573 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:25.583 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:25.588 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:26.603 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:26.610 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:27.621 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:27.626 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:28.636 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:28.643 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:29.658 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:29.665 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:30.680 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:30.687 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:31.700 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:31.705 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:32.720 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:32.729 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:33.744 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:33.752 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:34.767 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:34.774 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:35.784 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:35.789 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:36.801 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:36.806 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:37.821 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Connected with result code 0 2025-05-17 12:02:37.828 DEBUG (paho-mqtt-client-5yolJquTTmbU2khdqBtMek) [custom_components.dyson_local.vendor.libdyson.dyson_device] Disconnected with result code 7 2025-05-17 12:02:38.830 DEBUG (MainThread) [custom_components.dyson_local.config_flow] Failed to connect to device: DysonConnectTimeout,

@mrtnkhl
Copy link
mrtnkhl commented May 17, 2025 •
edited
Loading

I've found a fix and it appears to be related to the discoverability/dyson account method of installation.

  1. Remove Dyson Account Device from Home Assistant
  2. Reboot Home Assistant
  3. Follow instructions from this comment to get device password, serial, and ip: Dyson TP11 (new model released in March) unable to connect #238 (comment)
  4. On Home Assistant, add new entry from Dyson integration and choose to configure manually with details obtained from step 3.

Good luck!

These steps work, but when adding the Purifier Cool PC1 device manually, there are three times the same entries for a Purifier Cool but not Purifier Cool PC1. Also, the Purifier Cool PC1 did an update an hour ago which added a feature to precisely direct the airflow via the Dyson app. You can tell it which direction to blow its air. This is not available via Home Assistant and it is unclear which of the three Purifier Cool entries in the device type selection during manual setup is the right one for the PC1. Only the THIRD entry works, for whatever reason, but does not provide any pan control, cannot even turn on or off oscillation via HA.

Image

Image

@mrtnkhl mrtnkhl mentioned this issue May 17, 2025
Closed
@petykowski
Copy link

@mrtnkhl I think this integration could benefit from a better naming convention that is used to display the Dyson device name. If you look at the most recent commit c321eb8, support for the TP11 was added but they used the same name "Purifier Cool" to represent the TP07, TP09, and TP11 models. Likely the third works because it follows the same order listed in the init file.

    DEVICE_TYPE_PURIFIER_COOL_K = "438K"  # TP07 AND TP09
    DEVICE_TYPE_PURIFIER_COOL_E = "438E"  # TP07 AND TP09
    DEVICE_TYPE_PURIFIER_COOL_M = "438M"  # TP11
...
    DEVICE_TYPE_PURIFIER_COOL_K: "Purifier Cool",
    DEVICE_TYPE_PURIFIER_COOL_E: "Purifier Cool",
    DEVICE_TYPE_PURIFIER_COOL_M: "Purifier Cool",

@mrtnkhl
Copy link
mrtnkhl commented May 17, 2025 •
edited
Loading

@mrtnkhl I think this integration could benefit from a better naming convention that is used to display the Dyson device name. If you look at the most recent commit c321eb8, support for the TP11 was added but they used the same name "Purifier Cool" to represent the TP07, TP09, and TP11 models. Likely the third works because it follows the same order listed in the init file.

    DEVICE_TYPE_PURIFIER_COOL_K = "438K"  # TP07 AND TP09
    DEVICE_TYPE_PURIFIER_COOL_E = "438E"  # TP07 AND TP09
    DEVICE_TYPE_PURIFIER_COOL_M = "438M"  # TP11
...
    DEVICE_TYPE_PURIFIER_COOL_K: "Purifier Cool",
    DEVICE_TYPE_PURIFIER_COOL_E: "Purifier Cool",
    DEVICE_TYPE_PURIFIER_COOL_M: "Purifier Cool",

@petykowski I agree, trial and error solved that issue, but other people might have less fun. Still wondering if the inoperative oscillation feature is a bug or if the firmware update has changed the way the API works.

Overall just thankful that this integration exists and that Dyson is having an "open" API.

@cmgrayb
Copy link
cmgrayb commented May 26, 2025

I have introduced a PR (libdyson-wg/libdyson-neon#28) to update the display names of the Purifier Cool devices to include the model names. While I am not a maintainer of this project, I do hope they will consider including the changes.

@mrtnkhl
Copy link
mrtnkhl commented May 29, 2025

I have introduced a PR (libdyson-wg/libdyson-neon#28) to update the display names of the Purifier Cool devices to include the model names. While I am not a maintainer of this project, I do hope they will consider including the changes.

Thanks for doing that. I hope they consider the changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@mrtnkhl @dotvezz @petykowski @evilbobbins @Mithrox @cmgrayb @juanu159 @almiui
0