All looks good now. Thanks for the speedy responses 
Hi, recently my levoit 200s humidifier keeps disconnecting in my homey. However, the other oasismist 1000s humidifier works normally. Could you look at it? Thanx
@spkesDE are you planning to add support for the Levoit Superior 6000s model?
Hi,
I’m having trouble adding my Core 400S air purifier.
The purifier is powered on and connected to Wi-Fi. The VeSync Android app works correctly, I can see the purifier and control it without issues. I also do not have 2FA enabled on my VeSync account.
During the setup process, I select the correct model (Core 400S) and am prompted to enter my credentials. The credentials are successfully verified (I receive an email from VeSync notifying me of a new login). However, after this step, the setup fails with the message “No new devices have been found.”
I’ve tried both the current production app and the test version you linked, but the issue occurs in both.
Help?
Thanks,
Alex
Hi.
Is it possible to add a flow card for when mode changes for humidifiers that supports different modes?
Rgds.
Using VeSync app with 2FA (Workaround)
There is no 2FA support available yet.
But you can get it work using a workaround
Please take into consideration that the VeSync Homey app will appear as SM-9005N in your device list (different than the HA integration)
Work fine for me (even after reactivate 2FA)
Hi,
I am using the VeSync app on Homey with a Levoit Dual 200S humidifier, and I’m still experiencing persistent connectivity issues.
The device frequently goes “Offline” in Homey, even though it remains reachable and stable in the official VeSync smartphone app. To get it working again, I have to either use the “Repair” function or completely remove and re-add the device. This happens quite regularly and makes automation unreliable.
Could you please look into this? If you need a diagnostic report or specific logs to investigate the communication between the Homey app and the VeSync API for this model, please let me know how I can best provide them.
Thank you for your help and for maintaining this app!
In the meantime, I also set up the Vital 100S, and it connected to Homey immediately with zero issues, even though it’s marked as experimental in the Homey app. It’s on the same Wi-Fi, using the same VeSync credentials and region as Core 400S, yet the Core 400S still won’t connect and always returns “No new devices have been found.”
It’s quite frustrating, I’d really appreciate any assistance you can provide.
Thanks.
Can you add core mini?
Check out the latest test build
This is possibly the issue
// Update target humidity setting (configuration may be absent in some modes/firmware; newer APIs use targetHumidity on the result object)
const currentSettingHumidity = this.getSetting("humidity");
const r = status.result.result as {
configuration?: { auto_target_humidity?: number };
targetHumidity?: number;
target_humidity?: number;
};
const deviceHumidity =
r.configuration?.auto_target_humidity ??
r.targetHumidity ??
r.target_humidity ??
0;
if (currentSettingHumidity != null && Number(currentSettingHumidity) !== deviceHumidity) {
await this.setSettings({humidity: deviceHumidity}).catch(this.error);
}
}
Currently reworking some parts of the app to make it more stable.
Can you give me a diag report?
Restart the app, then create a report since I need to get the status json of the device?
Version 1.0.22 Device Compatibility & Diagnostics 
Hey,
This update focuses on making the app more reliable and future-proof for newer and regional VeSync devices.
VeSync keeps changing API responses between models, so this version improves how the app handles missing or changed status fields.
What’s New in Version 1.0.22:
- Improved device compatibility for newer and regional VeSync models.
- Added additional model aliases based on pyvesync.
- Includes LV600/LV603 refresh variants and more Core, Vital, Oasis, and Superior models.
- Added better diagnostics for unsupported devices.
- Virtual/non-smart devices are now ignored where possible.
- Unsupported real devices are collected in a diagnostic report to make future support easier.
- Improved pairing categories in Homey.
- Air purifiers now show as Air Purifiers.
- Humidifiers now show as Humidifiers.
- Tower fans remain Fans.
- Made VeSync status handling more robust against changed or missing API fields.
Your feedback and diagnostic reports are incredibly valuable for making this app more reliable and supporting more devices over time!
How to Create a Diagnostic Report
If you have an unsupported VeSync device or something does not work as expected, you can now create a diagnostic report.
- Open Homey Flows and run the new “Create VeSync diagnostic report” action card.
- Immediately after running the Flow card, go to the VeSync app settings in Homey.
- Send a diagnostic report from there.
Please send the diagnostic report right after running the Flow card, because Homey only includes the last few log lines in the report.
The diagnostic data is cleaned and does not include personal login data, tokens, passwords, MAC addresses, or similar sensitive information.
Support My Development:
If you appreciate my work and want to help out, consider buying me an energy drink 
or a beer 
. Donations are a great way to support and motivate me!
You can donate via PayPal. Your generosity helps keep this solo project moving forward!
Calling All Developers!
Are you a developer? Want to contribute to this project? I’d love to collaborate! Feel free to send a pull request on GitHub and join me in making this app even better.
Thank you for your support!
Edit: Does someone have Sprout Air, Sprout Humidifier or a Pedestal Fan from Levoit?
Also does someone have Etekcity devices or Aura Thermostat?
Everything works now, I have tested all functions on the LV603S and all works fine so no diagnostic report needed.
Version 1.0.26 Bug Fixes & Dual Blaze Support
Hey,
This update focuses on improving reliability when controlling VeSync devices from Homey and adds experimental support for the Cosori Dual Blaze Air Fryer.
Some VeSync devices report their old status for a short moment after a command has already been accepted.
This version improves how the app handles that delay, so Homey should no longer jump back to the previous state as often.
Fun fact: this is my 100th build
What’s New in Version 1.0.26:
- Added experimental support for the Cosori Dual Blaze Air Fryer.
- Improved command handling for VeSync devices.
- Improved Air Fryer status handling.
- Updated npm dependencies.
The Cosori Dual Blaze support is marked as experimental for now. If you own this device, feedback and diagnostic reports are very welcome so support can be improved further.
Support My Development:
If you appreciate my work and want to help out, consider buying me an energy drink or a beer .
You can donate via PayPal. Your generosity helps keep this solo project moving forward!
Calling All Developers!
Are you a developer? Want to contribute to this project? I’d love to collaborate! Feel free to send a pull request on GitHub and join me in making this app even better.
Thank you for your support!
@spkesDE Just trying my luck again in hope of some support… The issue persists with new versions of the app (was hoping one of the updates will fix it), Vital 100S connected to Homey immediately but when trying to connect Core 400S all I get is "No new devices have been found.” Both 100S and 400S work fine it the VeSync app, both using the same credentials and both are on the same WiFi network.
Thanks.
Thanks for fixing it for me!
