pyvesync

pyvesync is a python library to manage Etekcity & Levoit smart devices

Runs with mockssource: GitHubPythonMITcommit 58eee3bdbfba

Python, MIT licensed. The project labels itself: smart home and smarthome.

pyvesync runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

In the .venv, pyvesync 3.4.2 installs editable and its pytest suite passes 380/3; a real library run against a local schema-correct mock of the VeSync API logs in, retrieves devices, instantiates VeSyncOutlet15A, and turns it on and off.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.18 (measured)
recorded runs
1
last tested
stars
252
forks
155
open issues
65
watchers
17
size
14 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing pyvesync, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • My first API mock compared the plain-text password while the library sends MD5(password) (RequestGetTokenModel.hash_password), so login failed with the library's real VeSyncLoginError - mock-schema mismatch6 minutes
  • My device-list fixture lacked the required 'type' field, so mashumaro raised MissingField('type') in ResponseDeviceDetailsModel - mock-schema mismatch5 minutes
  • Mock server process was SIGHUP-killed when launched with '&' in the non-interactive shell (connection refused on 127.0.0.1:8931), an environment/harness artifact, not a repo bug4 minutes
  • My device-status endpoint path was wrong for the ESW15-USA outlet (library posts to /cloud/v1/deviceManaged/deviceStatus) - mock-schema mismatch4 minutes
  • My harness script used dev.state.device_status and indexing, but the library exposes state status via dev.state.device_status/is_on and DeviceContainer is a set - harness-script mistakes I fixed via next(iter(...))2 minutes
Install time
3 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
.venv/bin/python -m pytest exited 0 with '380 passed, 3 skipped'; e2e_check3.py against the mock printed login: True, get_devices: True, device 'Living Room Plug ESW15-USA VeSyncOutlet15A is_on=True', turn_on: True, turn_off: True, and the mock's request dump showed POST /cloud/v1/deviceManaged/deviceStatus with status 'on' then 'off'
Model tokens used
869,712
Exact commit tested
58eee3bdbfba
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

======================== 380 passed, 3 skipped in 6.61s ========================
Everything verified. Final state: `.venv` with `pyvesync` 3.4.2 installed editable, 380/3 test pass…
 exited 1 in 31525ms:
======== Running on http://127.0.0.1:8931 ========
(Press CTRL+C to quit)
exec
/bin/sh -lc 'pkill -f vesync_mock.py; sleep 1; ps aux | grep vesync_mock.py | grep -v grep; echo "m…
 exited 143 in 0ms:
All work complete and verified. Final report:
tokens used
869,712
All work complete and verified. Final report:

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 3 minutes.
  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.18

Topics (from GitHub)

smart-homesmarthome

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/pyvesync.svg)](https://argusic.com/subject/pyvesync)

Questions

Does pyvesync run?
pyvesync runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test pyvesync?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 58eee3bdbfba. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test pyvesync?
The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does pyvesync take to install?
3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does pyvesync need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing pyvesync?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for pyvesync?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion