mqtt-diagnosis
Diagnose MQTT publishing issues between CaptureLora.py and mqtt_grid_web.py. Check topic distribution, connection stability, and cross-reference with web app logs. Use when messages aren't reaching the web interface.
npx skills add majiayu000/claude-skill-registry --skill mqtt-diagnosis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# MQTT Diagnosis Investigate why MQTT messages may not be reaching the web interface. ## Step 1: MQTT Publish Success Rate Count in `logs/IQRight_Daemon.debug`: - Pattern `MQTT-TX.*SUCCESS` = successful publishes - Pattern `MQTT-TX.*FAILED` = failed publishes Calculate success rate. Baseline: >95% is healthy. ## Step 2: Topic Distribution Search for all `Topic=` values in MQTT-TX lines. Extract and count unique topics. **Correct topics**: - `Class{number}` (e.g., `Class96`, `Class89`) = student data routed to teacher's class - `IQRSend` = commands (break/release/cleanup) **Malformed topics (known bugs)**: - `Class['cmd', 'ack', 'break']` = BUG-001, command list stringified as topic suffix (FIXED Feb 2026) - `Classcmd|ack|cleanup}` = raw payload leaking into topic name (FIXED Feb 2026) If malformed topics found: the server code needs updating to the latest version. ## Step 3: Connection Stability Search for `Connected to MQTT` and `Disconnected from MQTT` patterns. Analyze: - Connect/disconnect ratio (healthy: few disconnects) - Clustering (many rapid reconnects = broker unstable) - Gaps between disconnect and reconnect (long gaps = extended outage) ## Step 4: MQTT Error Codes Searc
- Step 1: MQTT Publish Success Rate
- Step 2: Topic Distribution
- Step 3: Connection Stability
- Step 4: MQTT Error Codes
- Step 5: Cross-Reference with Web App Logs
- Diagnosis Flow
What does the mqtt-diagnosis skill do?
Diagnose MQTT publishing issues between CaptureLora.py and mqtt_grid_web.py. Check topic distribution, connection stability, and cross-reference with web app logs. Use when messages aren't reaching the web interface.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill mqtt-diagnosis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.