Unable to complete the registration process of my Dyson Pure Cool purifier

[brianqtb]

Can you help me understand where I went wrong?

[dotvezz]

Hi @brianqtb! Sorry you're running into this. One thing that often works is if you power-cycle the purifier. You can unplug it and plug it back in, then make sure its IP address hasn't changed and try to connect again.

If that doesn't work, are you able to enable debug logs and retry? The logs might help us understand what's going on.

[dotvezz]

Hi @brianqtb. It's been quite a while since my last message. I'm hoping you were able to get it resolved and am closing this issue. Please feel free to reply if you're still having a problem!

[brianqtb]

How do you enable the logs?

[dotvezz]

@brianqtb https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics

[ewimshurst]

Were you able to resolve this as I am getting the same error with my Dyson Purifier Cool?

[brianqtb]

No I couldn't resolve the problem. On Tuesday, 17 September 2024 at 04:30:15 pm MYT, ewimshurst ***@***.***> wrote: Were you able to resolve this as I am getting the same error with my Dyson Purifier Cool? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[dotvezz]

@ewimshurst I see you mentioned the device "Dyson Purifier Cool" - have you checked the troubleshooting steps specific to that device on this project's readme? https://github.com/libdyson-wg/ha-dyson?tab=readme-ov-file#troubleshooting

[dotvezz]

@brianqtb are you able to provide logs by any chance? Additionally, can you confirm whether the suggested power-cycle step was able to do anything?

[brianqtb]

I will try again today On Wednesday, 18 September 2024 at 01:48:00 am MYT, Ben Vezzani ***@***.***> wrote: @brianqtb are you able to provide logs by any chance? Additionally, can you confirm whether the suggested power-cycle step was able to do anything? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ewimshurst]

@ewimshurst I see you mentioned the device "Dyson Purifier Cool" - have you checked the troubleshooting steps specific to that device on this project's readme? https://github.com/libdyson-wg/ha-dyson?tab=readme-ov-file#troubleshooting

@brianqtb, thanks i have tried the troubleshooting steps unfortunately no luck.

These are the logs:

2024-09-18 20:17:01.626 DEBUG (MainThread) [custom_components.dyson_local.config_flow] Discovery timed out
2024-09-18 20:17:46.317 DEBUG (MainThread) [custom_components.dyson_local.config_flow] Failed to connect to device: DysonConnectTimeout,

Note i tried to connect first with out the IP and then with the IP address.

[dotvezz]

2024-09-18 20:17:01.626 DEBUG (MainThread) [custom_components.dyson_local.config_flow] Discovery timed out
2024-09-18 20:17:46.317 DEBUG (MainThread) [custom_components.dyson_local.config_flow] Failed to connect to device: DysonConnectTimeout,

Thanks for the logs! Unfortunately this is a network/connectivity issue, not a registration issue. I'm happy to try and troubleshoot your home network, but unfortunately it's out of control of this integration specifically.

I have a separate tool that might help. It's called opendyson, and can be run from a command line. Feel free to download the version that fits your OS/CPU over here: https://github.com/libdyson-wg/opendyson/releases.

Once you have it:

1. Run it with the devices argument. You'll be prompted through the login process and it will display all the information it's able to find about your devices.
   • For example, if you're on linux, it'd be ./opendyson devices.
2. After you've identified your device, use its serial number with the listen argument. It will then try to connect to your device and show information about it. If it looks like it's hanging, just give it some time to listen for MQTT messages.
   • On linux, that'd be ./opendyson listen YOUR-SERIAL-NUMBER

[l3arcf]

FYI folks, I have been plagued by this issue for a few weeks. Convinced this would be something to do with my docker setup, I skipped to the comment above, downloaded the tool and followed that process. Interestingly enough, the tool notified me that it was 'unable to get ip address' immediately, and then proceeded to provide other details.

Notably the mqtt _> address field was a null string.

An unplug/replug of the fan proved to clear that issue and also solved the connection from HA.

Moral of the story for me is to follow the advice provided earlier in this thread as that was the first step suggested in the initial response! Thanks dotvezz.