MerossIot
Async Python library for controlling Meross devices
Runs with mockssource: GitHubhomepagePythonMITcommit 4fc819384086
Python, MIT licensed. The project labels itself: automation, domotic, home automation, iot, meross, meross cloud, meross devices and python.
MerossIot runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.3 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
meross_iot 0.4.10.4 installed in venv with all dependencies; HTTP API layer (login, logout, device listing, hub subdevice listing, error handling) verified end-to-end against a schema-correct mock Meross API server; the remaining 57 of 61 test cases cannot execute without real cloud credentials and physical Meross hardware.
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.
- All 24 test files require real Meross cloud credentials and real Meross IoT hardware — MEROSS_EMAIL, MEROSS_PASSWORD, and devices like smart plugs/bulbs must exist on the account
- Tests use AioHTTPTestCase with @unittest_run_loop decorators that are deprecated in aiohttp 3.12+ (63 deprecation warnings)
- Install time
- under a minute
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- Installed in venv, all modules import. Built and started a schema-correct mock Meross HTTP API (aiohttp web server) on port 48888 that implements /v1/Auth/signIn, /v1/log/user, /v1/Device/devList, /v1/Hub/getSubDevices, /v1/Profile/logout. Set MEROSS_API_URL, MEROSS_EMAIL, MEROSS_PASSWORD, __MEROSS_CREDS to point at mock. async_get_client() -> async_list_devices() returned 1 device (Mock Smart Plug), async_logout() succeeded. async_from_user_password(email=test, password=testpass) -> async_list_devices() returned 1 device, async_logout() succeeded. async_from_user_password with wrong password raised BadLoginException. All verified through actual HTTP request/response cycles against the mock with real signature computation.
- Model tokens used
- 569,972
- Exact commit tested
- 4fc819384086
- 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.
Everything is verified. Here is the final result:
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 0…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 0.25, "errors": [{"msg": "…
exec
/bin/sh -lc "# Validate JSON
echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 0.25, \"errors…
succeeded in 0ms:
Valid JSON
tokens used
569,972Replay 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 0.3 minutes, faster than the median of the 38 comparable projects Argusic has measured.
- Recovered from all 2 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.
Of the 39 automation projects Argusic has installed and timed, MerossIot was the 6th fastest to reach a running state, and 27 of 39 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.06 |
Topics (from GitHub)
automationdomotichome-automationiotmerossmeross-cloudmeross-devicespython
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/merossiot)Questions
- Does MerossIot run?
- MerossIot runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test MerossIot?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4fc819384086. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test MerossIot?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does MerossIot take to install?
- 0.3 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 MerossIot need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing MerossIot?
- 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.
- How does MerossIot compare with the alternatives?
- Of the 39 automation projects Argusic has installed and timed, MerossIot was the 6th fastest to reach a running state, and 27 of 39 reached one at all.
- Where is the evidence for MerossIot?
- 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.