Installer report, deeper non-invasive monitoring, no games in emails

[MSabacreationslab]

What

Installer report: a technical report for whoever installed or services the eero system. It's available from a dashboard card, at /installer-report?days=7|14, and as python -m hogwatch installer-report [--days N] [--note "..."], which also writes a PDF with headless Edge or Chrome.

• Summary with numbers: which link drops and how often (per monitored hour), eero reconnects, whether the Ethernet run between eeros ever links, the band and width on each hop and whether it overlaps radar-shared DFS channels, mesh route changes, double NAT behind the ISP gateway, internet-line health, and whether the PC's own cable ever dropped.
• Requested work, generated from the findings.
• Evidence: layout table; per-hop typical, p95, jitter and loss; dropouts by day and by time of day (rate per monitored hour); the longest dropouts; reconnects; Ethernet port link checks; radios, channel changes and backhaul changes; speed tests; an appendix of every dropout; and the method.
• Privacy: it reads no device names, people, programs or games. A test seeds all of those and checks that none appear. Homeowner notes are escaped.

Deeper monitoring (still non-invasive: timing and eero status only):

• Each eero's backhaul, signal bars, radios (channel, width, utilization, clients, tx power), firmware and Ethernet ports, every 2 minutes (unit_sample).
• Pings to every eero, so each eero-to-eero link has its own record.
• Jitter per 10-second bucket (new latency.jitter_ms column, added automatically to existing databases).
• This PC's network-card link going down or up (link_event), and eero speed-test history.
• gzip on eero API calls, which cuts HogWatch's own eero traffic by about 90%.

Daily email: games are left out, since the email may be forwarded.

Fixes found while checking the report against real data

• Sleep: a dropout or slowdown that was open when the PC went to sleep closed on wake with the sleep counted, giving a "2,275-minute dropout". Now any open record closes at the last ping before a pause of 30 s or more, and older records are capped by their bad-ping count everywhere they're shown.
• Startup before the network: if HogWatch started at boot before the network was up, it never found the main eero or ISP gateway and never retried, so eero-link dropouts were read as AT&T-side. Discovery now retries every 30 s and falls back to the main eero's address from eero's data. The report labels dropouts from unmeasured periods instead of guessing.

Testing

• 63 tests pass locally, 12 of them new in tests/test_installer.py: privacy, every finding, DFS channel math, route labels, unit parsing, gzip, the sleep fix, the database migration, and the "location not measured" relabeling.
• Generated against 8 days of real data. A grep for device, person, program and game names in the output came back empty.

🤖 Generated with Claude Code