Add support for Cosori Turbo Tower Pro Smart Air Fryer / CAF-DC111S-AEU

[xkl]

device is accessible via VeSync mobile app.

Logfile vesync.log of

$ python testing_scripts/vs_test_script.py --email ... --password ...

I can support as tester and try to capture the communication if I can use an alternative to MuMu. I need sth for Linux, neither Win nor Mac machine around.

[webdjoe]

I'll need packet captures to add this. I'm not sure of which emulators work for linux or mac. The emulator just needs to allow you access to root through adb. I have not been able to get Android studio to work because the latest OS releases do not support ARM emulation. You can also share the device temporarily with me. Happy to assist further on discord homefire1608

[KKeXX]

I can provide packet caputure for the Cosori Turbo Tower Pro Smart Air Fryer CAF-DC111S-AEU. Can I send per Mail or what is your preferred method?

[FReichelt]

@KKeXX Could you provide it to me via email as well, please? My email is git@florian-reichelt.de. Thank you in advance.

[KKeXX]

@FReichelt I just sent you the requested file. I hope everything is in there and you can add this device?

[shaarkys]

Hi @KKeXX would you mind to share with me as well ? Would like to look on possibility to integrate CAF-DC123S-DEUR model into other integration, could happen maybe that your capture could provide something useful.
If possible, to email sharkys at email.cz ? Thank you.

[KKeXX]

@shaarkys I sent you my captured files. Hope this helps.

@FReichelt where you successful in adding the CAF-DC111S-AEU into pyvesync?

[shaarkys]

Thank you @KKeXX , with your data, I'm able to add Cosori Turbo Tower Pro Smart into Athom, as part of VeSync integration from another developer, really appreciated.

[sharknoon]

@KKeXX I am trying to control my Cosori Turbo Tower Pro remotely. Would you mind to share your recordings also with me? frank.josua@gmail.com Thank you so much 🙏

[webdjoe]

There is already a branch started with the air fryer module completely refactored and a few other air fryers added. Please base your code off of this. I'm happy to help anyway I can, but my time is going to be very limited for the next month or so.

#503

[KKeXX]

I added my Cosori Turbo Tower™ Pro Smart Air Fryer - CAF-DC111S-AEU configModule: VS_WFON_CAF-DC111S-AEU_EU to the device_map.py:

dev_types=['CAF-TF101S-AEU', 'CAF-TF101S', 'CAF-TF102S', 'CAF-DC111S-AEU'],

Then it Airfryer is recognized. Can you please add this to the library as well?

[Supersimo88]

Hi, I have the same air fryer model (CAF-DC111S-AEU) and can confirm it's also detected via the VeSync API with deviceType: CAF-DC111S-AEU and reports the device image VS_WFON_CAF-DC111S-AEU_EU_240.png. Log excerpt from pyvesync.device_container:

Device type CAF-DC111S-AEU not found in device map

I'd be happy to help as a tester as well. I have Home Assistant (HAOS) running on a Linux VM, so I can run testing_scripts/vs_test_script.py from a Linux environment if that helps capture the device communication. Let me know what logs/output would be most useful (e.g. get_details, getFryerStatus, or similar endpoint responses), and I'll gather them.

If it helps, the device is likely part of the same "Turbo Tower Pro" hardware family as the CAF-DC123S series, so the response schema might be a close match — but happy to confirm with real captured traffic rather than assume.

"I see PR #503 (air fryer refactor) is close to merge and already adds several other Cosori models (CAF-DC601S, TwinFry, Dual Blaze) — would be great to get the CAF-DC111S-AEU / CAF-DC123S series added too, happy to provide test captures if useful."

[Mlhote1971]

Also affected — Cosori Turbo Tower Pro Smart (dual-basket), EU version

Same issue here with the EU model. Login and region handling work fine, the device list is returned by the API, but the device is dropped because its type isn't in the device map.

Device identifiers (from debug logs):

deviceType: CAF-DC111S-AEU
configModule: VS_WFON_CAF-DC111S-AEU_EU
Region: EU — API host smartapi.vesync.eu, country FR (cross-region retry works correctly)

Relevant log lines:

[pyvesync.auth] Cross-region error, retrying with country: FR
[pyvesync.auth] Login successful
[pyvesync.vesync] Requesting device list from VeSync
[pyvesync.device_container] Device type CAF-DC111S-AEU not found in device map
[pyvesync.vesync] No devices to update

Environment: Home Assistant OS, HA Core 2026.8.3, bundled pyvesync.

This is a dual-zone / dual-basket air fryer (two independent chambers, 6.5 L + 4.3 L), so it likely needs a dedicated handler rather than reusing the single-basket air fryer class.

I'm happy to help: I can run the test script, provide full debug logs, and capture the app↔cloud API traffic with mitmproxy on Linux (get_details / set payloads for both baskets). Just tell me what you need.

[Mlhote1971]

Also affected with CAF-DC111S-AEU (EU / France). Region handling works, the device is returned by the API, but dropped:

[pyvesync.device_container] Device type CAF-DC111S-AEU not found in device map
[pyvesync.vesync] No devices to update

deviceType: CAF-DC111S-AEU — configModule: VS_WFON_CAF-DC111S-AEU_EU — host smartapi.vesync.eu.
Env: Home Assistant OS, HA Core 2026.8.3.

I saw PR #503 (air fryer refactor + VeSyncDualAirFryer) already covers CAF-DC111S. Two questions:

Does the branch's dev_types include the -AEU EU suffix specifically (CAF-DC111S-AEU), or only CAF-DC111S?
Anything I can do to help get it merged?

I can test PR #503 against a real CAF-DC111S-AEU. I run HAOS and can also run testing_scripts/vs_test_script.py from a Linux box, and provide get_details / status payloads for both baskets. Just point me at the branch and tell me what output you need. (Confirmed workaround meanwhile: adding CAF-DC111S-AEU to dev_types in device_map.py makes it recognised, per @KKeXX.)