core: Dyson Integration Fails to setup.

The problem

When HA restarts the Dyson integration fails to connect.

Environment

Home Assistant 0.104.3 running on hyper-v

Home Assistant release with the issue:
Last working Home Assistant release (if known): 0.104.3
Operating environment (Hass.io/Docker/Windows/etc.): Windows Hyper-v hassio install
Integration causing this issue: Dyson
Link to integration documentation on our website: https://www.home-assistant.io/integrations/dyson/

Problem-relevant `configuration.yaml`

dyson:
  username: xxx
  password: xxxx
  language: US
  devices:
    - device_id: NM7-US-xxxxx # eg. Serial number: XXX-XX-XXXXXXXX
      device_ip: 10.0.0.13

Traceback/Error logs

Log Details (ERROR)
Mon Feb 03 2020 12:09:50 GMT-0800 (Pacific Standard Time)
Not connected to Dyson account. Unable to add devices'

Log Details (ERROR)
Mon Feb 03 2020 12:09:50 GMT-0800 (Pacific Standard Time)
Setup failed for dyson: Integration failed to initialize.

Additional information

I haven’t restarted my HA in a few weeks and I noticed that someone updated the dyson integration about 3 weeks ago, also I see that it’s failed some checks on github so maybe that’s the issue?

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 2
Comments: 99 (15 by maintainers)

Most upvoted comments

Here are the steps to replace the dyson.py on Pi4 running Home Assistant OS:

install Portainer Addon, disable protection mode, start addon and open web-ui. in Portainer settings remove core and homeassistant from the disabled devices now from the containr list select homeassistant, clic the console button and enter the three lines below one after the other: cd /usr/local/lib/python3.8/site-packages/libpurecool/ rm dyson.py curl -O https://raw.githubusercontent.com/bfayers/libpurecool/auth_customdeps/libpurecool/dyson.py

+10

motarek17 on Feb 13, 2021

Got exactly the same issue since yesterday. I restarted HA many times last week w/o any issue, and I’m running 0.104.3. Since today or yesterday I got the same error message (without more logs). Maybe an issue on Dyson Cloud infrastructure.

benaisn on Feb 3, 2020

I’ve been using this custom integration for the last couple of weeks. It has both a cloud and local option. Setup is a bit non-intuitive. The standard path (or at least what I did) is to install both the cloud integration and the local integration (above), and use the cloud integration to set things up (you can choose to use the local integration when setting up a device). There’s also a way to setup the local integration directly without using the cloud integration, but I haven’t tried that.

This is a very good substitute for built-in dyson integration, if you just want to turn on and off. But I’m using all the services that built-in integration provides.(night mode, flow direction…) This integration provide just two services.(set speed and set auto mode)

It has everything for me, even more than what I had with the built-in integration (i.e. night mode switch that I have never seen before)!

motarek17 on Mar 6, 2021

Having the same issue after last upgrade.

efaul on Feb 10, 2021

Hello again Jason,

after the last supervisor version seems to have 2021.02.6 and the Dyson integration fails again. I have again worked off your steps in order to identify whether my config or libpurecool is causing the issue. Unfortunately I am not able to connect to my Dyson account, getting the integration to work again.

your help is very appreciated, Ben

Benekification on Feb 10, 2021

I have always had issues with Dyson on HA, I am using a workaround to automate it using virtual motion sensors and Alexa at the moment, it is working well!

motarek17 on Feb 10, 2021

It’s been broken for me today, too, but I haven’t had a chance to look into it yet. Hopefully this evening.

jason0x43 on Feb 10, 2021

Hello again Jason,

after the last supervisor version seems to have 2021.02.6 and the Dyson integration fails again. I have again worked off your steps in order to identify whether my config or libpurecool is causing the issue. Unfortunately I am not able to connect to my Dyson account, getting the integration to work again.

your help is very appreciated, Ben Getting the same this morning myself, rebooted to finish an upgrade and now dyson says it’s not connected to my account. App still works on my phone.

monsieurlatte on Feb 10, 2021

FINALLY FOUND THE ISSUE!!!

I have been using EU as Region, which seems to have been removed/deprecated. US and DE (am living in Germany) both work.

Thanks again mate!

Benekification on Oct 29, 2020

Dark. I just copied all the files and made folder called Dyson under custom components for now. It’s working.

monsieurlatte on Feb 5, 2020

@monsieurlatte please add any relevant logs from home-assistant.log to this issue 😃

springstan on Feb 3, 2020