shenxn / ha-dyson

HomeAssitant custom integration for dyson
MIT License
307 stars 59 forks source link

Dyson Local "failed to connect" Device Type: 438K #160

Open cark0765 opened 2 years ago

cark0765 commented 2 years ago

Dyson TP07 (Dyson Purifier Cool)

Run get_devices.py, get the appropriate information: Serial: W9W-XX-XXXXXX1A Name: XXXX Device Type: 438K Credential: /VPCXVgS8XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX2EVFoLQ==

image

javempt commented 1 year ago

Heya, I am also having no luck with 438K - I have tried both 438 and 438E options to no avail. Multiple restarts of HA & device, uninstalling and reinstalling integrations, etc - still no luck. @shenxn are you able to add compatibility for 438K models? my log:

2022-12-09 13:54:13.267 INFO (MainThread) [libdyson.dyson_device] Connected to device X1Y-AU-XXXXXXXX 2022-12-09 13:54:13.293 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Disconnected with result code 7 2022-12-09 13:54:14.345 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Connected with result code 0 2022-12-09 13:54:14.373 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Disconnected with result code 7 2022-12-09 13:54:15.426 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Connected with result code 0 2022-12-09 13:54:15.454 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Disconnected with result code 7 2022-12-09 13:54:20.198 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Connected with result code 0 2022-12-09 13:54:20.226 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Disconnected with result code 7 2022-12-09 13:54:21.279 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Connected with result code 0 2022-12-09 13:54:21.307 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Disconnected with result code 7 2022-12-09 13:54:22.360 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Connected with result code 0 2022-12-09 13:54:22.387 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Disconnected with result code 7 2022-12-09 13:54:23.441 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Connected with result code 0 2022-12-09 13:54:23.468 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Disconnected with result code 7 2022-12-09 13:54:24.521 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Connected with result code 0 2022-12-09 13:54:24.549 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Disconnected with result code 7 2022-12-09 13:54:25.604 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Connected with result code 0 2022-12-09 13:54:25.634 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Disconnected with result code 7 2022-12-09 13:54:30.213 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Connected with result code 0 2022-12-09 13:54:30.238 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Disconnected with result code 7 2022-12-09 13:54:31.294 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Connected with result code 0 2022-12-09 13:54:31.320 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Disconnected with result code 7 2022-12-09 13:54:32.373 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Connected with result code 0 2022-12-09 13:54:32.400 DEBUG (Thread-17 (_thread_main)) [libdyson.dyson_device] Disconnected with result code 7 2022-12-09 13:54:33.402 DEBUG (MainThread) [custom_components.dyson_local.config_flow] Failed to connect to device:

mattdevo1 commented 1 year ago

I am having the same problem with the 438K. I guess this is a new version of the Dyson Purifier Cool Formaldehyde TP09? I have another machine with a "438E" device type, which is working perfectly.

Are you able to add support for the new 438K @shenxn? Thanks in advance.

niemtec commented 1 year ago

@mattdevo1 having exactly the same issue here. 438E added fine but 438K did not 😢

BeHappy2021 commented 1 year ago

Same issue for me.

niemtec commented 1 year ago

I found this workaround to work. However, it's annoying given that it won't report the formaldehyde values thinking it's a whole different version of the fan. Does work though if that doesn't bother you.

BeHappy2021 commented 1 year ago

Excellent find. @niemtec. I didn't uninstall the integration though. I just made the edit to manifest.json and restarted HA and it worked. I've got all the same values on the purifier cool as I get from my pure cool formaldehyde.

mattdevo1 commented 1 year ago

Excellent find. @niemtec. I didn't uninstall the integration though. I just made the edit to manifest.json and restarted HA and it worked. I've got all the same values on the purifier cool as I get from my pure cool formaldehyde.

Thank you!! This worked for me too (I didn't uninstall the integration either, just edited the manifest.json and restarted HA like you suggested).

I just realized also that I was never getting formaldehyde values from my 438E anyway. My primary goal was to automate on/of/speed etc. versus monitoring air quality, so this hack works fine for me.

Would be nice to get official support, but this will work for now.

bgalakazam commented 1 year ago

No workaround to get formaldehyde values then? My device is listed as 438E. It's the pure cool formal fan TP09.

Snapicek commented 1 year ago

Unfortunately similar issue here as well. Model TP09 which is formaldehyde. get_devices.py shows me model 438K. When adding manually throw local, I will all required with formaldehyde option and error occurs. When I chose the Cool Pure then it was able to add the device (lot of functions are missing). I changed manifest but only in the local version.