CarConnectivity

Python API to retrieve telemetry data from various car brands

Runs with mockssource: GitHubPythonMITcommit 1e5c1736108d

Python, MIT licensed. The project labels itself: api, api client, api rest, carnet, myskoda, skoda, skoda connect and telemetry.

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

In /work/repo/.venv, carconnectivity 0.11.12.dev4+g1e5c17361 with all official connectors and plugins is installed and importable, pip check passes, the CLI runs, and with a local mock connector the library loads, fetches a vehicle into the garage, reports healthy, persists an encrypted tokenstore/cache, and answers --version.

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.25 (measured)
recorded runs
1
last tested
stars
216
forks
19
open issues
28
watchers
19
size
0 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 CarConnectivity, 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.

  • initial pip install -e .[all] failed: ResolutionImpossible, plugin/connector pins require carconnectivity>=0.11.10 while repo tree resolves dev versions5 minutes
  • pip install refused: externally-managed-environment (PEP 668), no root available1 minute
  • mock connector AttributeError: Connector has no attribute log1 minute
  • TypeError: You cannot set this attribute. Attribute is not mutable.1 minute
  • mock connector TypeError: BaseConnector.__init__ missing log and api_log
  • first mock fetch did not populate garage (new vehicle each call)
Install time
9 minutes
Cold machine to finish
13 minutes
Errors hit and fixed
7 hit, 7 fixed with no human help
How the result was proved
PYTHONPATH=/tmp/mockconn-4585 .venv/bin/python /tmp/mockconn-4585/exercise.py printed 'EXERCISE_PASSED'; carconnectivity --version printed 'carconnectivity 0.11.12.dev4+g1e5c17361'; CLI with testconn mock wrote healthcheck 'healthy', stayed up, exited 0 on SIGTERM; database plugin created /tmp/mockconn-4585/cc.db with 23 tables; pytest exited 5 (collected 0 items); pylint 10.00/10 exit 0; flake8 --exclude=.venv exit 0; bandit 0 issues; sdist installed in fresh venv and its carconnectivity --version ran
Model tokens used
1,165,980
Exact commit tested
1e5c1736108d
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

The end of the recording

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

## Verified
- `pip list`: `carconnectivity 0.11.12.dev4+g1e5c17361 /work/repo` plus all 4 official connectors, …
- `pytest`: exited 5 with `collected 0 items` (no tests in repo); exit code 5 is pytest's documente…
- `pylint ./examples ./src ./tests`: rated 10.00/10, exit 0. `flake8 --exclude=.venv`: exit 0. `ban…
- `PYTHONPATH=/tmp/mockconn-4585 .venv/bin/python /tmp/mockconn-4585/exercise.py`: printed `EXERCIS…
- Persistence: `exercise2.py` wrote an encrypted tokenstore (Fernet `format_version 1.0`) and an en…
- CLI with mock connector: process stayed up, wrote `healthy` to the healthcheck file, `cli_exit=0`…
- Real database plugin: `{"type": "database"}` with `sqlite://` ran 15s under the CLI (exit 0), cre…
- Real car-brand connectors (volkswagen/skoda/seatcupra/tronity) were not exercised end-to-end beca…
## Output
```
```

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

  • Recovered from all 7 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.
  • Took 9 minutes to install, slower than the median of the 61 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 62 api projects Argusic has installed and timed, CarConnectivity was the 44th fastest to reach a running state, and 39 of 62 reached one at all.

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.25

Topics (from GitHub)

apiapi-clientapi-restcarnetmyskodaskodaskoda-connecttelemetrytelemetry-collectiontelemetry-datavehiclevolkswagenvolkswagen-weconnectweconnectweconnect-pythonweconnect-users

Embed the badge

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

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

Questions

Does CarConnectivity run?
CarConnectivity runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 9 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test CarConnectivity?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1e5c1736108d. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test CarConnectivity?
The run that produced this verdict cost $0.25: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does CarConnectivity take to install?
9 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 CarConnectivity need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing CarConnectivity?
7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does CarConnectivity compare with the alternatives?
Of the 62 api projects Argusic has installed and timed, CarConnectivity was the 44th fastest to reach a running state, and 39 of 62 reached one at all.
Where is the evidence for CarConnectivity?
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