Add support for Levoit Classic 300S Smart Ultrasonic Top-Fill Cool Mist Humidifier in the VeSync integration

To make it clearer, what I meant was:
1- remove any core integration instance
2- reboot
3- install HACS version
4- reboot
5- add integration searching for “vesync” in the integration panel

Then as they share the same domain, the custom integration will be added in place of the core one.
This can be confirmed after installation with the small orange icon:
image

1 Like

Unfortunately I don’t have the time to keep maintaining the custom integration… I’m looking for someone to take it from here. In the meantime, the integration will stay as is without any further development…
Sorry for the inconvenience…
If anyone is interested in taking over, please contact me so I can transfer ownership of the repo!

Cheers.

2 Likes

That’s why I prefer using custom names for custom integrations…

@chuckdeal97 Is it okay if I take another crack at using your code to create a core PR? Would you be interested in assisting if I can make progress on getting approvals?

My plan is try to take code owner of the core integration and submit just test coverages to start. If this gets accepted I will do small improvements over time. Using your large PR as a base.

The start of this: Add codeowner to vesync by cdnninja · Pull Request #104809 · home-assistant/core (github.com)

1 Like

Has anyone been able to set child lock on 300S Air Purifier? My cats love to stand on the thing and keep turning it off :scream_cat:

Hi @formatBCE
I have a Levoit Core 300s which is suppose to be supported by pyvesync & Vesync integration but after i take a look at the repo
(pyvesync/src/pyvesync/vesyncfan.py at 7f49c643d703d37755da41295a4f7a9c8ec456c9 · webdjoe/pyvesync · GitHub)
i managed to get the models from vesycn cloud: LAP-C301S-WAAA
seem like the models that i have is not yet added to the list of regconized models for Core300s, could you help me support it on your repo ? i also attach the api call

Hello!
It looks like same old 300 model, but with slightly different model version.
If you push pyvesync devs to all your model into Core300s section, it will become supported automatically in next pyvesync. Then it will be as easy as update pyvesync version in my repo to bring it into HA. At least it looks like it.

I’m away from keyboard for next week, will check it closer when return home.

1 Like

Hi @formatBCE !
I downloaded the folder from your GitHub and extracted to custom_components and after that I installed the integration and logged in. My task is to make my new dual 200s available in the HA, but it didn’t work, the devices list is empty in the integration and on the logs there only one warning. What am I missing?


Hello!

Are you sure you didn’t have original Vesync installed before doing all this?
The support for LUH-D301S-WEU was added in 2022: Added support for Dual200S, LUH-D301S-WEU · formatBCE/HA_VeSync_Classic300s@361e85f · GitHub, and there’s no reports on it not working…

Try deleting everything (start with integration, then reboot, then files in custom_components, then reboot), and re-downloading please.

Yes I reaady had original installed too. So I deleted intergration, rebooted, deleted folder from custom_components, rebooted, then re-added folder to custom_components and rebooted, added integration, logged in, and still nothing =(

In the full logs I can see following

2024-11-05 20:47:34.507 INFO (MainThread) [custom_components.vesync_formatbce.common] 1 VeSync fans found
2024-11-05 20:47:34.507 WARNING (MainThread) [custom_components.vesync_formatbce.fan] Humidifier - Unknown device type - LUH-D301S-WEU

That’s really strange…

Can you check if your local files contain this line?

Yes it has, I have the latest github code, I just downloaded it yesterday. I thin log warning comes from this line

but I am not sure why the code invokes in fan.py instead of humidifier.py

I think I fixed it locally by adding this line, works for me now. PR for fix:

I just was writing this to you :slight_smile:
Thanks for fix, it should work now. Curious why it wasn’t reported by others…

1 Like

For some reason just to test, I tried installing this custom component

And unfortunatelly after that, yours stopped loading my humidifier. I tried deleting integration, solder, rebooting HA etc but to no help.

The only message in logs that I can see is

2024-11-06 03:36:04.683 WARNING (SyncWorker_5) [pyvesync.vesync] Error retrieving device list

Uh-oh, something got broken in config entries probably?
Things to try:

  • check leftover files in custom_components;
  • check config entries file in .storage folder and clean it up.

I honestly don’t know what could happen…

P.S. that integration looks very good, not the crap I made just for myself, and then extended as was asked. :slight_smile: Doesn’t it work?

I actually just double-checked that installed version of pyvesync is correct 1.4.3 and tried manually in container consolu through the python shell to login but got the same message. Maybe smth on the server, idk. Will look tomorrow.

>>> manager.login()
True
>>> manager.update()
2024-11-06 03:59:16,862 - WARNING - Error retrieving device list

Yeal looks like server.