-
Notifications
You must be signed in to change notification settings - Fork 28
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.
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
Can't connect to Dyson Pure Cool Link TP02 purifying fan (White/Silver) #86
Comments
Hi @Agile-Travel! Sorry for the slow reply. The TP02 is supported, but you're not the only person who has reported issues with it in the past few weeks. Are you able to enable debug logging for the integration, then re-attempt connection to the device? That would be awesome! Let me know if you would like any more info for debug logging. |
I believe I may have the same issue with a HP04, the debug logs just show:
|
I have a similar issue with my HP04, while the error message shows "unknown error occurred" and the debug logs are as follow:
|
Just tried again and it worked... 🤷♂️ No idea why though |
I have the same issue with my Dyson Pure Hot+Cold ( Device model 527 ). Dyson app works and I can ping the address but it looks like setup times out. I have tried config flow and manual setup as well as moving the device in different subnets to no avail. Thanks |
It feels like something has changed. The past few weeks people have been having difficult-to-reproduce errors with a wide variety of Dyson Fan devices. One thing clear to me is this: I need to improve the error logging to make this easier to reproduce. I'll get a release out that improves logging, hopefully we can find an answer for you all soon! |
Okay, better logging is still forthcoming, but in the meantime I wonder if the new release happens to have improved the situation. @ufu- @SungFeng-Huang @Agile-Travel any changes after updating? |
I've also released the logging improvement in v1.3.4. If you happen to have time, please update then enable debug logging so we can get a clearer picture of what's happening. Thanks! |
Thanks so much for working on this plugin and this issue. Here is the updated error when on 1.3.4: 2023-12-02 20:01:37.471 ERROR (MainThread) [aiohttp.server] Error handling request |
@Agile-Travel wow I could have sworn I'd already replied here. I owe you an apology. In your logs, you're getting DysonConnectTimeout with a whole bunch of noise. The noise is my fault for trying to log the error incorrectly (I fixed that in 1.3.5 lol). DysonConnectTimeout means that the fan is not acknowledging the connection attempt. This is the first time I've seen that behavior for the TP02, which is frustrating. There isn't much we can do unfortunately. Can you unplug and plug-in your device, then try to connect again? |
Problem solved in v1.3.6! Thanks @dotvezz! |
It still was not able to connect. On mobile so can’t grab logs atm
…On Mon, Dec 18, 2023, at 7:51 PM, Sung-Feng Huang wrote:
> Okay, better logging is still forthcoming, but in the meantime I wonder if the new release happens to have improved the situation. @ufu- <https://github.com/ufu-> @SungFeng-Huang <https://github.com/SungFeng-Huang> @Agile-Travel <https://github.com/Agile-Travel> any changes after updating?
>
Problem solved in v1.3.6! Thanks @dotvezz <https://github.com/dotvezz>!
—
Reply to this email directly, view it on GitHub <#86 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQGLNLA2G7FRLHNKZCMVSW3YKEFMVAVCNFSM6AAAAAA655F3H2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRSGA3TGNJWGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
How did you get on with this? |
I hope this will help some of you; I had the issue for quite a long time and nothing seemed to solve it: I kept getting time out errors, and if I checked the IP address it would respond to pings, but the MQTT port seemed close or unavailable ( 1883/TCP ). |
Hi, I can't connect my HP04 too. It worked fine two month ago.... I treid to factory reset and re-add the HP04 on my mobile app several times but can't detect on homeassitant. Logger: homeassistant.config_entries Traceback (most recent call last): Thanks for some help. |
It is discovered using my cloud account, and I've identified the IP address via an IP Scanner (has name matching serial # so sure that is correct IP).
I get the error:
Failed to connect. The IP Address may be required if your Home Assistant installation is running in a Container or a VM.
No complicated networking or firewalls in between.
I've also tried getting my credentials manually and using manual setup, but still can't connect.
Is the Dyson Pure Cool Link TP02 supported?
The text was updated successfully, but these errors were encountered: