-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
Cannot Import Name 'DysonPurifierHumidifyCoolFormaldehyde' #164
Comments
I'm having the same issue and no changes to my previously working fan setup, so don't believe this is related to your new Dyson model.
|
Probably worth checking which libdyson version(s) you have in your HA. At least some time back Dyson cloud installed older libdyson than Dyson local. See #103 (comment) |
Thanks, @GitPetri. I was able to install both local and cloud. I have modified manifest.json
However, got another obstacle. Local was able to pull all information from the cloud, however, when I try to configure local it asks me for the host (I know this should be ignored) and when I press submit I got an In the logs, I have found below.
|
Same issue here |
Unfortunately this integration is no longer maintained, but I've created a new fork and am actively working on the new Formaldehyde models. Have a look at #185 for more information, and let me know if you have any questions. |
I have recently installed both the Dyson_local and Dyson_cloud integrations on my HASS OS VM, and they were working great until the system rebooted. Now they are both failing to load and giving the following error in the logs:
Setup failed for custom integration dyson_cloud: Unable to import component: cannot import name 'DysonPurifierHumidifyCoolFormaldehyde' from 'libdyson'
(/usr/local/lib/python3.10/site-packages/libdyson/init.py`I suspect this is related to my newer Dyson fan, an HP07 Purify Hot+Cool, since I had zero issues previously with my older two Pure Cool Link fans.
Please advise on any additional logs or information required and I can provide as needed.
The text was updated successfully, but these errors were encountered: