pylips
Control Philips TVs (2015+) and Ambilight (+ Hue) through their reverse-engineered API (+ MQTT support!)
Runs with mockssource: GitHubPythonMITcommit b6af4cc14d7e
Python, MIT licensed. The project labels itself: ambilight, home automation, philips, philips hue, philips tv and tv.
pylips runs, with stand-ins for the services it depends on. An Argusic agent installed it in 33 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Pylips installs into a .venv and, after two code fixes, runs end to end against a schema-correct mock Philips TV API: API discovery, digest-auth pairing, GET/POST built-in commands, and MQTT listen+update modes with status publishing, all verified by direct command output and mock request logs.
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
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- MQTT listen mode (MQTT_update=False) crashed: AttributeError 'Pylips' object has no attribute 'last_status'14 minutes
- is_online() crashed with FileNotFoundError: 'ping' when host unreachable (ping not installed in container)8 minutes
- pip3 install -r requirements.txt blocked: externally-managed-environment (PEP 668)3 minutes
- Install time
- 33 minutes
- Cold machine to finish
- 35 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- timeout 12 .venv/bin/python pylips.py --host 127.0.0.1 --user mockuser --pass mockpass --command powerstate returned {'powerstate': 'On'} (exit 0); MQTT listen-only mode: publishing {'command':'volume'},{'command':'powerstate'},{'command':'get','path':'system'} on pylips/in each triggered exactly the matching mock GET (/6/audio/volume,/6/powerstate,/6/system); publishing {'status':{...}} on pylips/in produced pylips/out {'powerstate':'On','volume':21,'muted':true,'cur_app':null,'ambilight':null,'ambihue':false}
- Model tokens used
- 2,539,827
- Exact commit tested
- b6af4cc14d7e
- 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.
**What I did**
- Read `README.md` and `docs/`.
- Installed `requirements.txt` in a `.venv` (system `pip3` is blocked by PEP 668); pinned `paho-mqt…
- Exercised the app: manual GET/POST commands, built-in commands, discovery, digest-auth pairing (v…
**Two bugs found and fixed in `pylips.py`**
1. `is_online()` crashed with `FileNotFoundError: 'ping'` on an unreachable host (no `ping` in this…
2. `MQTT_listen=True` + `MQTT_update=False` crashed with `AttributeError: 'Pylips' object has no at…
**Observed verification**
- `... --command powerstate` → `{"powerstate": "On"}` (exit 0).
- `--command volume` → volume object; `--command get --path system` → system JSON; POST commands hi…
- MQTT: publishing `{"command":"volume"}`, `{"command":"powerstate"}`, `{"command":"get","path":"sy…
The one-line result: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 33 minutes.
- Recovered from all 3 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.70 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/pylips)Questions
- Does pylips run?
- pylips runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 33 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test pylips?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b6af4cc14d7e. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test pylips?
- The run that produced this verdict cost $0.70: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does pylips take to install?
- 33 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 pylips need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing pylips?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for pylips?
- 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.