majordomo

Home automation platform

Runssource: GitHubPHPMITcommit d1283ab64ae9

PHP, MIT licensed. The project labels itself: diy, home automation, javascript, majordomo, php and smarthome.

majordomo runs. An Argusic agent installed it in 41 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

PHP 8.1.31 + MariaDB 11.4.3 running: index/diagnostic/admin pages all return HTTP 200, default admin/admin login works, REST API returns real room data from database, main cycle launches sub-cycle daemons

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

At a glance

verdict
Runs
Argusic Score
90 / 100
cost of the verifying run
$0.59 (measured)
recorded runs
2
last tested
stars
407
forks
155
open issues
80
watchers
47
size
37 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 majordomo, 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.

  • No MySQL/MariaDB server available10 minutes
  • No PHP binary in container5 minutes
  • Invalid HTTP status headers in index.php and admin.php (#1 header malformed with colon and trailing newline)3 minutes
  • MariaDB client requires libncurses.so.5, only libncursesw.so.6 is present2 minutes
  • Missing cached_cycles table needed by caching.class.php2 minutes
  • DB_PORT not wired into mysqldb constructor1 minute
Install time
41 minutes
Cold machine to finish
42 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
curl hits: index.php 200 (42KB), diagnostic.php 200 (55KB), admin.php 200 (104KB), POST admin/admin login returns 200 with Control Panel, GET /api/rooms returns 200 with 7 rooms from DB, GET /api/devices returns 200 with empty array, cycle.php starts all sub-cycle threads
Model tokens used
2,839,326
Exact commit tested
d1283ab64ae9
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 2, 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.

API devices: 200 (104 bytes)
Login: 200
Panel after login: 200 (103601 bytes)
--- CYCLE ---
73
cycle scripts launched
Now I have all the verification data. Let me assemble the final report.
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":41,"errors"…
tokens used
2,839,326
Now I have all the verification data. Let me assemble the final report.
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":41,"errors"…

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 41 minutes.
  • Recovered from all 6 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.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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 Runner2/3Runs100.000.59
Argusic Runner1/3Unverified80.000.35

Topics (from GitHub)

diyhome-automationjavascriptmajordomophpsmarthome

Embed the badge

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

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

Questions

Does majordomo run?
Yes. majordomo runs. Argusic installed and launched it on a clean machine in 41 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test majordomo?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d1283ab64ae9. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test majordomo?
The run that produced this verdict cost $0.59: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does majordomo take to install?
41 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 majordomo need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing majordomo?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for majordomo?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion