@formatBCE, @Derex @kelstar I was contacted recently - @gdgib seems keen to get it moving and looking for support to maintain it.
2 Likes
Thought I would chime in hear. Really great progress is being made on the native core vesync integration.
- A key bug that was causing an unloading error was fixed in 2025.1
- Another bug that would cause disconnects due to too aggressive polling has been merged and will be in 2025.2 (iprak)
- A humidifier support pull request is in final stages. It may make the cutoff for 2025.2 (iprak)
- A binary sensor pull request that add some states to humidifiers is in the final stages and may also make 2025.2
More to come as well.
3 Likes
Great news!
Thanks @cdnninja. So does that mean that at some point in the near future we should switch from the custom integration to the native one?
The core integration simply needs to be able to handle all the devices lists in the Python Library!
Up to you! Potentially. Humidifier is merged and will be in 2025.2. You will need to decide if features are adequate. A hand full of other items are coming.
While I agree with what you are saying the tone is demanding - you are welcome to volunteer and help us get to that. We are volunteers working on this. It is the direction the PRs are going.
1 Like
You may have read it that way, but it wasn’t intended to be. Simply a statement of fact. If the underlying Python Library can handle a device, it makes sense for the HA component to do so.
I have contributed to the custom integration in the past as the previous refactoring PR got stuck for many years. It is good someone is actively working on it and hopefully its coverage will exceed the custom one. My Python is rudimentary at best and my experiences of previous attempts to contribute were not pleasant (attitude of devs), so I tend to avoid it.
I hadn’t noticed anything in the release notes about the Vesync integration getting an update.
Today i archived my repo and moved to this one. It works great!