Update pyvesync to 3.4.0+ to support LV600S (LUH-A603S-WUS) humidifier

[threesquare]

Integration name

Vesync/Levoit

Link to integration documentation on our website

https://www.home-assistant.io/integrations/vesync/

Describe the enhancement

The problem

The VeSync integration is using pyvesync 3.3.3, which doesn't support the Levoit LV600S humidifier (model LUH-A603S-WUS).

Support for this model was added in pyvesync 3.4.0 with the VeSyncLV600S class:
https://github.com/webdjoe/pyvesync/blob/master/src/pyvesync/devices/vesynchumidifier.py

What version of Home Assistant Core has the issue?

2026.1.0

What was the last working version of Home Assistant Core?

N/A - This is a new device model

What type of installation are you running?

Home Assistant OS

Integration causing the issue

VeSync

Link to integration documentation on our website

https://www.home-assistant.io/integrations/vesync/

Diagnostics information

The device appears in the VeSync API response but is skipped due to missing device map entry:

DEBUG (MainThread) [pyvesync.device_container] Device type LUH-A603S-WUS not found in device map

The VeSync API shows the device:

• Device Name: LV600S
• Device Type: LUH-A603S-WUS
• Config Module: VS_WFON_AHM_LUH-A603S-WUS_US
• Connection Status: online

Example YAML snippet

N/A

Anything in the logs that might be useful for us?

2026-01-07 18:47:21.944 DEBUG (MainThread) [pyvesync.device_container] Device type LUH-A603S-WUS not found in device map
2026-01-07 18:47:21.944 DEBUG (MainThread) [pyvesync.device_container] Added device Classic 200S - Classic200S to container.
2026-01-07 18:47:21.944 DEBUG (MainThread) [pyvesync.device_container] Added device Dual 200S - Dual200S to container.
2026-01-07 18:47:21.945 DEBUG (MainThread) [pyvesync.vesync] Added 2 devices

Additional information

Manually upgrading pyvesync to 3.4.0 via pip install --upgrade pyvesync allows the device to be detected, but Home Assistant reverts to 3.3.3 on restart.

Proposed Solution:
Update the pyvesync dependency in homeassistant/components/vesync/manifest.json from version 3.3.3 to >=3.4.0

Use cases

use the newer Levoit model

Anything else?

No response

[github-actions[bot]]

🏷️ I've automatically added the integration: vesync label to help categorize this feature request.

[CloCkWeRX]

home-assistant/core#160573

[fpgirard]

I also saw the 3.4.1 release as well - super naive question - besides submitting this request via git issues, what is the normal process to incorporate this feature into HAOS?

[CloCkWeRX]

Requesting here is fine; or if you feel like contributing...

For library version bumps; basically, do the kind of same kind of PR as a stand alone item and wait for it to get through the review/merge process.

If the library supports new functionality ontop of the version bump; submitting a subsequent PR to take advantage of it (or a draft one, referencing the version bump one).

[CloCkWeRX]

This one is now merged, so will likely be in the next release.

Nice job @cdnninja :)

[cdnninja]

I also saw the 3.4.1 release as well - super naive question - besides submitting this request via git issues, what is the normal process to incorporate this feature into HAOS?

I typically am running in lock step with the library. This one was a larger change since we are working toward strict typing, it took a bit longer to be bumped compared to normal. Here works - feel free to ping me on discord or submit PRs too.

[fpgirard]

Wow! I wasn't expecting this speed and efficiency! Great job @cdnninja - thank you!