DP04 Formaldehyde sensor problem

[vincemulhollon]

I have quantity two, older DP04 fans, works great, and after a recent HACS upgrade to 0.16.4-4 now I get the following error:

Setup failed for custom integration dyson_local: Unable to import component: cannot import name 'DysonPurifierHumidifyCoolFormaldehyde' from 'libdyson' (/usr/local/lib/python3.9/site-packages/libdyson/init.py)

AFAIK only model TP09 are supposed to have formaldehyde sensors? I definitely have two DP04 fans not TP09, but whatever.

HACS will only let me downgrade as far as 0.16.3 Unfortunately that results in the same error message. (old library, old integration)

I went into portainer for my homeassistant and "pip list | grep libdyson" shows I have 0.8.7 installed. A "pip install --upgrade libdyson" resulted in the installation of 0.8.11

Restarted HA and obtained same error message. (new library, old integration)

Used HACS to re-download 0.16.4-4 and restarted, that works. (new library, new integration)

It seems the way to make an old DP04 work is to manually upgrade the libdyson version in the Docker container for home-assistant and then make sure to use a local dyson integration of 0.16.4-4. Any combination of older integrations or older libraries do not work.

The way I fixed it is probably the "wrong" way to fix it, and I think perhaps your integration should have a dependency on libdyson being newer than 0.8.7 or perhaps minimum dependency level of 0.8.11, or you may have some other suggestion.

[phoniclynx]

I'm still getting the same problem here.. Sometimes it connects sometimes it doesn't connect and shows the errors:

Logger: homeassistant.setup
Source: setup.py:162
First occurred: 11:55:02 (2 occurrences)
Last logged: 11:55:31

Setup failed for custom integration dyson_cloud: Unable to import component: cannot import name 'DysonPurifierHumidifyCoolFormaldehyde' from 'libdyson' (/usr/local/lib/python3.9/site-packages/libdyson/__init__.py)
Setup failed for custom integration dyson_local: Unable to import component: cannot import name 'DysonPurifierHumidifyCoolFormaldehyde' from 'libdyson' (/usr/local/lib/python3.9/site-packages/libdyson/__init__.py)

This happens on a reboot of HA and doesn't always happen, but does happen about 90% of the time on both cloud and local. I have a DP04 too

[phoniclynx]

so I've totally uninstalled the Dyson Local and the Dyson Cloud from my HA system. It took A LOT of work to remove it from the system as it didn't want to be removed due to some kind of miss-configuration because of this error. I am running HA Core 22.7.2 and I've downloaded the image afresh.

According to the above-mentioned links, it should fix the issues by downloading a new libdyson version which fixes the errors. But to no avail:

Logger: homeassistant.config_entries
Source: config_entries.py:784
First occurred: 21:03:43 (2 occurrences)
Last logged: 21:04:12

Error occurred loading configuration flow for integration dyson_cloud: cannot import name 'DysonPurifierHumidifyCoolFormaldehyde' from 'libdyson' (/usr/local/lib/python3.10/site-packages/libdyson/__init__.py)
Error occurred loading configuration flow for integration dyson_local: cannot import name 'DysonPurifierHumidifyCoolFormaldehyde' from 'libdyson' (/usr/local/lib/python3.10/site-packages/libdyson/__init__.py)

[Anto79-ops]

if it helps, I was never able to ever add my 2 Pure+Cool Formaldehyde machine (they are 2 years old), so I added it as a Pure+Cool machine and it works very well (minus formaldehyde information).

[snigehere]

I guess you installed the package in an earlier ha version.. most comments, and my experience as well, relate to not being able to install the integration so never get near adding a device.. don't uninstall!!

[vincemulhollon]

I run homeassistant and HACS in Docker.

Today I did and update of the HA docker container AND upgraded the HACS for this integration to the latest 0.16.4-4

Something is reinstalling 0.8.7 every time I restart homeassistant using the UI (web interface, developer tools, check configuration, restart)

docker exec -it homeassistant /bin/bash

cd /usr/local/lib/python3.10/site-packages

look around and its definitely libdyson 0.8.7 which is why the integration cannot run, it requires 0.8.11

pip list | grep libdyson

shows 0.8.7 is installed, yes that is why its not working.

pip install --upgrade libdyson

Seems to leave 0.8.7 partially installed when looking in /usr/local/lib/python3.10/site-packages, weird whatever. Restarting HA errors integration out as 0.8.7 is installed.

pip uninstall libdyson

OK now every trace of 0.8.7 is totally gone

pip install libdyson

pip list | grep libdyson

Shows 0.8.11 is now installed. Every directory looks like 0.8.11. We totally have 0.8.11 installed at this time.

Go into web browser, developer tools, check config, restart. Integration WORKS cool reports temperature and I can turn my fan on and off and all is well.

Go back to bash session inside homeassistant

pip list | grep libdyson

Shows 0.8.7 is installed again. How is this possible all I did was restart HA using the web interface (NOT restart or redeploy the docker container)

Seems like I can install 0.8.11, then restart HA using the web UI, libdyson 0.8.11 works and connects and I can control my fan etc, then "something" in the HA startup process removes 0.8.11 and reinstalls 0.8.7, so that on the NEXT restart, it'll fail because the integration requires 0.8.11 to work and 0.8.7 has been installed over the top of 0.8.11

Note the docker container has been up the entire time. I'm well aware what wipe and restart the docker container will do LOL.

Summary: Works with 0.8.11, does not work with 0.8.7. I can log into the innards of the docker container and remove 0.8.7 and force the installation of 0.8.11, then the very next restart of HA will work. But something in the startup process for HA pulls in 0.8.7 over the top of my fresh install of 0.8.11, so the NEXT time I restart HA the integration will fail as it cannot work with 0.8.7 only 0.8.11

Maybe because I have cloud and local Dyson integrations installed and one demands 0.8.7 and the other demands 0.8.11 but I do not know how to troubleshoot that speculation

[hscissors]

@vincemulhollon Sorry! Just saw the thread here with more info on the error you were seeing.

As you suspected, if you uninstall Dyson Cloud from HACS, manually update libdyson to 0.8.11, and restart the docker image. The Dyson Local integration works.

[avassem85]

I got it working. I uninstalled Dyson cloud. Then reinstalled Dyson Cloud but before restart ha I edited custom_components/dyson_cloud/manifest.json libdyson==0.8.7 -> libdyson==0.8.11. When I restarted both Cloud and local were working.

[kolafson777]

@avassem85 This worked for me too - uninstalled both, restarted, installed Dyson Local and Dyson Cloud, changed manifest.json as you said for Dyson Cloud, restarted and I got the set up prompt when adding the integration.

I then ran into another issue (#59) but got that one sorted following a suggestion in the linked comments. Phew!

[vincemulhollon]

My solution from July 13 linked here Jul 13 no longer works. It did work "a couple weeks ago" but after a docker image upgrade today something in the startup process of homeassistant was re-ordered such that version 0.8.7 of libdyson is being installed over 0.8.11 before loading the dyson integration every time.

My solution was to 'docker exec -it homeassistant /bin/sh' or however you log into your docker image command line, then I reload the config using the web UI, then immediately while its reloading I repeatedly run "pip install --upgrade libdyson" using uparrow and enter many times, perhaps 10 times, while homeassistant is restarting, at some point I see the "upgrade" stopped failing and it had to install 0.8.11 over the mis-installed 0.8.7, and the integration now works and I can control my fans. Cool!