GitPetri

> Same here with a PH03 (device type 358E, sadly the same as PH04). If I enable the debug log in HA for this integration, I managed to configure my...

> I am having the issue with a PH02 and two PH04's @LunchboxNYC did you test the steps linked to my previous comment?

I do know that selecting incorrect machine type will end up in fail. So picking up the correct based on [https://github.com/shenxn/libdyson/blob/7b19d1c96c151eb876d8d8fbb3a4d5f2917b86b3/libdyson/const.py#L4](https://github.com/shenxn/libdyson/blob/7b19d1c96c151eb876d8d8fbb3a4d5f2917b86b3/libdyson/const.py#L4) is crucial too

> No change for me using latest Dyson Local (I did have Dyson Cloud installed, so I removed both and only reinstalled Dyson Local). I still have the debug logs...

Umm, @Ekman little help? I updated the PureI integration via HACS, integration is showing release now as 1.4.0 but I can't see any new entities for my vacuum. Do I...

> Weird @GitPetri ! > > Please add this to your `configuration.yaml` and then send me your logs `Settings -> System -> Logs`: > > ```yaml > logger: > default:...

> Yup, that was it. I had old vacuum: - platform: purei9 email: !secret electrolux_user password: !secret electrolux_password in my configuration.yaml. Commented those out, re-integrated the vacuum via integration UI...

Uh, good to know. Which version of HACS broke the integration? Running 1.28.0 at the moment and HA shows 1.30.0 as available one

> I'm on 1.29. 1 Thanks, staying in 1.28 for now then.

> Google integration is busted too... Might be a change in Dyson's end? I am running 1.28.0 and my integration seems to be working at the moment