iot-inspector-client

IoT Inspector: capturing and analyzing your smart home network traffic

Runs with mockssource: GitHubhomepagePythonApache-2.0commit cae56e6e890f

Python, Apache-2.0 licensed. The project labels itself: internet of things, iot, network analysis and smart home.

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

In this container: uv sync --locked success, pytest 7/7, Streamlit dashboard HTTP 200 with health ok, anonymize/time_series/event_inference work, and the packet-collector POST saved a valid pcap against the Mongo mock; checkout is clean.

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.09 (measured)
recorded runs
1
last tested
stars
483
forks
69
open issues
14
watchers
26
size
218 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 iot-inspector-client, 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.

  • packet_collector exits unless MongoDB is reachable (no mongod in container)10 minutes
  • iot_inspector console script fails: ModuleNotFoundError No module named 'page_manager'2 minutes
  • pytest not declared in pyproject.toml/uv.lock1 minute
Install time
28 minutes
Cold machine to finish
10 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
pytest -q src/tests -> 7 passed; streamlit run src/iot_inspector/dashboard.py -> health ok HTTP 200 on / and _stcore/health, stayed up; anonymize and time_series produced decodable pcap/PNG; event_inference exit 0 with packet/burst counts; POST /label_packets with real TLS frames -> HTTP 200 success and pcap saved via mongomock
Model tokens used
390,819
Exact commit tested
cae56e6e890f
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.

- CLIs: `anonymize -h`, `time_series -h`, `event_inference -h` all printed usage, exit 0. `anonymiz…
- Real-data pipeline: `event_inference -p src/tests/data/application_data.pcap -m aa:bb:cc:dd:ee:ff…
- Flask collector: `GET /label_packets` → 200; `POST /label_packets` with real TLS app-data frames …
- The failure notes above (repeated process that vanished after the shell exits) were misdiagnoses:…
**Issues recorded**
- `packet_collector` requires a reachable MongoDB at startup; without one its `init_db` calls `sys.…
- The `iot_inspector` console script fails with `ModuleNotFoundError: No module named 'page_manager…
- The repo vendorless `pip install pytest` is not in `pyproject.toml`; added pragmatically to the v…
**Notes**
- Read-only success criteria are the most honest for this kind of repo; I checked both the mocked f…
**Final state**
- `.venv` is fully synced at the lockfile; `anonymize`/`time_series`/`event_inference`/`packet_coll…

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 28 minutes.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, 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.09

Topics (from GitHub)

internet-of-thingsiotnetwork-analysissmart-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/iot-inspector-client.svg)](https://argusic.com/subject/iot-inspector-client)

Questions

Does iot-inspector-client run?
iot-inspector-client runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 28 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test iot-inspector-client?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit cae56e6e890f. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test iot-inspector-client?
The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does iot-inspector-client take to install?
28 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 iot-inspector-client need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing iot-inspector-client?
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 iot-inspector-client?
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