purifier-card

Air Purifier card for Home Assistant Lovelace UI

Runssource: GitHubTypeScriptMITcommit 353874df2598

TypeScript, MIT licensed. The project labels itself: air purifier, custom cards, hacs, hass, home assistant, homeassistant, lovelace and purifier.

purifier-card runs. An Argusic agent installed it in 9 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm install, npm test, the browser card render/service-call test, and the npm start dev server all succeed, and dist/purifier-card.js serves over HTTP 200.

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.12 (measured)
recorded runs
1
last tested
stars
345
forks
120
open issues
14
watchers
4
size
8 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 purifier-card, 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.

  • script scripts/validate-i18n (ES module) failed: Cannot use import statement outside a module because package.json lacked "type": "module"3 minutes
  • Rollup build failed: ReferenceError: crypto is not defined ([email protected] via @rollup/[email protected] requires Node >= 20; container has Node 18)3 minutes
Install time
9 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npm test exited 0 (eslint clean, translation keys consistent, rollup 'created dist'); headless Chromium loaded dist/purifier-card.js and returned all 9 render assertions true and service calls [fan.set_preset_mode{entity_id,preset_mode:Silent}, fan.toggle{entity_id}] with 0 page errors; curl returned HTTP 200 for the npm start dev server
Model tokens used
515,039
Exact commit tested
353874df2598
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

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.

- `npm test` exit 0: ESLint clean, `Translation keys are consistent with en.json.`, `created dist i…
- Real artifact exercised in headless Chromium: all render assertions true, `fan.set_preset_mode`/`…
- `npm start` watch server answers HTTP 200 on `/purifier-card.js`.
- Reproduced both fixes from a deleted `node_modules`; the working tree contains exactly `package.j…
tokens used
515,039
Final checks hold:
- `npm install` from scratch: 986 packages, no errors (only Node-18 engine warnings, which don't bl…
- `npm test` exit 0: ESLint clean, `Translation keys are consistent with en.json.`, `created dist i…
- Real artifact exercised in headless Chromium: all render assertions true, `fan.set_preset_mode`/`…
- `npm start` watch server answers HTTP 200 on `/purifier-card.js`.
- Reproduced both fixes from a deleted `node_modules`; the working tree contains exactly `package.j…

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

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 9 minutes.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 9 minutes after the clone.

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/3Runs100.000.12

Topics (from GitHub)

air-purifiercustom-cardshacshasshome-assistanthomeassistantlovelacepurifiersmart-home

Embed the badge

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

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

Questions

Does purifier-card run?
Yes. purifier-card runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test purifier-card?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 353874df2598. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test purifier-card?
The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does purifier-card 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 purifier-card need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing purifier-card?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for purifier-card?
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