MerossIot tested by Argusic Runner

What the test found

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.

Install: Created venv, pip install -e .[speedups] succeeded (25 packages). Dependencies: paho-mqtt 2.1.0, requests 2.34.2, aiohttp 3.12.13, pycryptodomex 3.24.1. Dev deps: pytest 6.2.5, pytest-aiohttp 0.3.0. Library: 6988 Python LOC. Tests: 2398 Python LOC (61 test cases). Utilities: 591 LOC. CLI entry points (meross_sniffer, meross_api_cli) import and display help text. All 15+ library modules import cleanly. A schema-correct mock Meross HTTP API server was built on aiohttp. Verification: cached-creds login/logout/device-listing, email-password login/logout/device-listing, and bad-login detection all passed end-to-end against the mock. The remaining 22 test files (57 of 61 test cases) cannot run without a real Meross cloud account with physical devices, since they send MQTT commands to real hardware and listen for push notifications.

Argusic installed MerossIot in 0.25 minutes and launched it; verification reached Verified with mock services. 2 of 2 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of MerossIot

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.