My VeSync 400S power Controls are still present but the Sensors (Air Quality and PM2.5) have become Unavailable after the upgrade. When you click on a sensor, you get the message:
This entity is no longer being provided by the vesync integration. If the entity is no longer in use, delete it in settings.
Does anyone have a suggestion on how to bring these sensors back online after the 2025.11 update?
I have seen restarting the integration after pulling the plug on the vesync clear this type of thing. Also try restarting HA.
My 400 loses stuff periodically and it eventually just comes back if I wait.
I have restarted HA a couple of times (which BTW caused my Amazon Media Player to start asking for authentication now) with no changes to the 400S. I have also reset the Frontend cache.
So are you also suggesting that I physically unplug the VeSync 400S to see if that resets it?
Just for completeness, this is the warnings I am getting in the system logfile:
Logger: pyvesync.devices.vesyncpurifier
Source: runner.py:289
First occurred: 10:26:32 AM (38 occurrences)
Last logged: 11:04:11 AM
Bedroom Cleaner for Core400S API from get_details returned error code: 11802000, message: device_error - BYPASS_AIRPURIFIER_MOTOR_ABNORMAL Air Purifier motor error - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success
Bedroom Cleaner for Core400S API from get_details returned error code: 11802000, message: device_error - BYPASS_AIRPURIFIER_MOTOR_ABNORMAL Air Purifier motor error - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success
Bedroom Cleaner for Core400S API from get_details returned error code: 11802000, message: device_error - BYPASS_AIRPURIFIER_MOTOR_ABNORMAL Air Purifier motor error - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success
Bedroom Cleaner for Core400S API from get_details returned error code: 11802000, message: device_error - BYPASS_AIRPURIFIER_MOTOR_ABNORMAL Air Purifier motor error - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success
Bedroom Cleaner for Core400S API from get_details returned error code: 11802000, message: device_error - BYPASS_AIRPURIFIER_MOTOR_ABNORMAL Air Purifier motor error - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success - request success
Is your motor working? Is the filter clean? That is a lot of successes in that log!
Everything on the machine is working. It was working great up until i rebooted to update to 2025.11. I have sense unplugged the machine and still nothing. HA allows me to turn the machine on/off but no longer see the PM or air quality.
Is the device showing up in the VeSync app?
I’ve had it happen occasionally that, after restarting Home Assistant, the entities didn’t show up and finally realized that the device itself had dropped off the VeSync network.
The only thing that I could do was to wait until the device showed up in the VeSync app and reload the HA integration.
Yes, i thought the same. It does appear in the app though the app has been updated since i last used it.
Ok, I uninstalled the VeSync integration and reinstalled it. However when I did that only the power on/off entity appeared. All the sensor entities are now missing. Totally useless without the air quality sensors. If anyone has any suggestions, i am open to them.
I got round this by cloning the home assistant repo:
git cone https://github.com/home-assistant/core.git homeassistant-core
cd homeassistant-core
git checkout 2025.9.4
cd homeassistant/components/
tar czf ~/vesync.tgz vesync/
Which creates a tarball with the previous version of the vesync integration from release 2025.9.4 in your home directory.
Then get that tarball over to home assistant and extrace it into the config/custom_components directory where it should create a vesync directory.
Edit manifest.json and add a version so it’ll get picked up and override the built in one, so it’s like:
{
"domain": "vesync",
"name": "VeSync",
"codeowners": [
"@markperdue",
"@webdjoe",
"@thegardenmonkey",
"@cdnninja",
"@iprak"
],
"config_flow": true,
"documentation": "https://www.home-assistant.io/integrations/vesync",
"iot_class": "cloud_polling",
"loggers": ["pyvesync.vesync"],
"requirements": ["pyvesync==2.1.18"],
"version": "1.1.0"
}
Then restart home assistant.
Not sure why I picked 2025.9.4 and not 2025.10.4 - probably a typo but that should work as well.
Only thing that’s changed in 2025.11 is the pyvesync version I think.
You lost me at cloning and repo. I guess i should of mentioned that i am very new/amateur at home assistant and yaml programming. If yhe fix is more than simply reinstalling or restarting, it is way above me.
I get:
2025-11-07 15:54:37.806 WARNING (MainThread) [pyvesync.devices.vesyncpurifier] Lounge for Core400S API from get_details returned error code: 11802000, message: device_error - BYPASS_AIRPURIFIER_MOTOR_ABNORMAL Air Purifier motor error - request success - request success - request success - request success - request success - request success - request success
But with the older vesync integration extracted that goes, and it’s back to how it was.
Edit: Turns out it just the version of pyvesync - 3.1.2 works fine, 3.1.4 not so much.
I hadn’t thought of unplugging them all and restarting home assistant as the older version worked - but may give it ago.
If it helps anyone else (or can someone help me lol) - with the current version of the vesync integration if I change the version of pyvesync to 3.1.2 it also brings back all the sensors like PM2.5, filter life etc.
With 3.1.4 all I get is on/off - however I can change presets through the main entity and change the fan speed.
@gingermist i am glad you found a workaround by going back a version. I am going to hope they fix the integration soon so that i do not have to do workarounds. Since my Core 400s was my only Vesync device, i have uninstalled the integration to keep from getting so many system errors.
Hopefully someone will post when the integration gets fixed so that i can reinstall
Having the EXACT same issue with my 400S. I have other vesync devices that still work. Just after I updated to 2025.11
The way to backout to an early known working version without using the inbuilt HomeAssistant Restore functionality???
Will a future update/fix transparently overwrite the “patch” without user intervention, or will expert editing assistance be required to bring everything back to normal?
[Asking for the ever-present AI Bot that will be offering it forever as the ideal solution slop for this most-likely short term issue]
Is it not yet recommended to use the built in restore functionality? (Or am I missing your intention here) I’m looking at doing it… But tbh have yet to do it once and not sure what to expect if I do a full restore, add ons and all back to backup on 10.4
That, or wait to pyvesync 3.2.1 which looks to be coming 11.2 (Bump pyvesync to 3.2.1 by cdnninja · Pull Request #156195 · home-assistant/core · GitHub)
@MikeScottCAD Oh those coming updates sound promising. Thank you for sharing that link.
When I used the restore functionality, the DB schema (in MariaDB) was not rolled back - which left a mismatch.
Restore works well with third-party integrations/components, but not so much when it’s in the core.
Edit: To be honest, I didn’t spend much time looking into why the restore/rollback in home assistant didn’t work - I had only selected the core to restore.
Doing it this way does mean you are responsible for removing it to go back to the core integration. I rename manifest.json to manifest.json.bak then restart home assistant to switch between them.
As for the confused AI bot - I think the onus is on the bot’s creators than forum contents to give better results.
Reasons above for not using the restore functionality with the home assistant core.
Thanks also for posting that link - there’s hope.
Edit: Updated the manifest to use pyvesync 3.2.1:
"requirements": ["pyvesync==3.2.1"],
And can confirm this fixes all the issues I had with 3.1.4. This is using the 2025.11 version of the vesync core integration