Request for Supporting Device Levoit Vital Pet Pro

[daviddesmet]

Brand: Levoit
Device: Vital Pet Pro
Model: LAP-P501S-WUSR

Link to product page: https://levoit.com/pages/vital-pet-pro
Amazon: https://www.amazon.com/LEVOIT-Purifier-Large-Vital-White/dp/B0GXKSC38S

I can share the device temporarily if needed.

[webdjoe]

I'll need packet captures outlined here: https://webdjoe.github.io/pyvesync/latest/development/capturing/. If you are able to share tonight, I will try to get to it or it will have to wait until the following weekend. Message me on discord homefire1608

[daviddesmet]

I'll need packet captures outlined here: https://webdjoe.github.io/pyvesync/latest/development/capturing/. If you are able to share tonight, I will try to get to it or it will have to wait until the following weekend. Message me on discord homefire1608

If you can take a look tonight that will be great, otherwise I can wait. I just sent a friend request on Discord so I can message you.

[theiam79]

Really funny timing, I was just looking around after getting one of these today. I had Claude doing some testing, and this is what it returned if it's of any use:

• deviceType LAP-P501S-WUSR / LAP-P501S-AUSR, configModule VS_WFON_APR_LAP-P501S-AUSR_US, uses /cloud/v2/deviceManaged/bypassV2 (same style as Vital 100S/200S).
• Reads work fully. getPurifierStatus returns power, workMode, fan level, PM2.5, VOC, odorLevel, AQLevel, child lock, screen, buzzer, filter life + days, filter-open, and screenPreference/childLockPreference/autoCleanPreference. Modes: sleep, manual, odorShieldQuiet/Balanced/Performance; fan levels 1–3.
• Control is blocked by the _packfilesignature header on this device (unlike the air fryers in Cosori Dual Blaze 6.8-Quart Smart Air Fryer CAF-P583S #477). Sending the byte-identical control payload from pyvesync without the signature returns code:0/result.code:0 but the device never applies it; the app's identical payload with the _packfilesignature: v0001-… header works. Reads aren't gated on it. I ruled out payload keys, subDeviceNo, appVersion, HTTP/2, and traceId; the signature is computed in obfuscated native code.

So read-only support looks easy; control needs the signature reproduced. Glad to share the full captures, command payloads, and test transcripts in whatever format is most useful.

[rocord01]

I have reverse-engineered the signature function and successfully implemented full control and read support for the Vital Pet Pro (LAP-P501S-WUSR / LAP-P501S-AUSR) in pure Python.

The VeSync servers gate control traffic using the _packFileSignature HTTP header. Static analysis of the APK revealed that the backend verifies this signature using the default AOSP test key certificate fingerprint (2CA4647FA8C5C9475B13FBD47984E525F38AD3B8).

Because of this, we can easily generate valid signatures natively using hashlib.sha256.

See PR #532

[daviddesmet]

@rocord01 wow, that was fast! Thanks a lot for investing time into it 🙂