logan/node-26
1
0
Fork 0
Code Issues 14 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Edge dashboard can't tell 'broker refused' from 'broker unreachable' — mqtt_manager exposes no last connect error #21

New Issue
Closed
opened 2026-10-04 01:21:28 -04:00 by logan · 1 comment
logan commented 2026-10-04 01:21:28 -04:00
Owner
Copy Link
Copy Source

Found 2026-10-04 (branch feat/local-ui-usable, new /api/health checklist).

mqtt_manager exposes only is_connected. The refusal reason code from _on_connect and the TCP failure in _connect_with_retry are only logged. So the dashboard's MQTT row has to guess from whether an API key is on disk (key present + disconnected => 'restart edge-node / key may be stale'). For Toughny-type failures (node-26#14) the exact distinction — 'not authorised' vs 'can't reach mqtt.drb.cusano.net:8883' — is what the owner needs.

Ask: add mqtt_manager.last_error (str + epoch), set in _on_connect (reason_code != 0), _on_disconnect and _connect_with_retry; cleared on connect. Then app/internal/health.py MQTT check reads it. mqtt_manager.py is being edited by the install/OTA work (#14/#15), so sequence after that lands.

Found 2026-10-04 (branch feat/local-ui-usable, new /api/health checklist). `mqtt_manager` exposes only `is_connected`. The refusal reason code from `_on_connect` and the TCP failure in `_connect_with_retry` are only logged. So the dashboard's MQTT row has to guess from whether an API key is on disk (key present + disconnected => 'restart edge-node / key may be stale'). For Toughny-type failures (node-26#14) the exact distinction — 'not authorised' vs 'can't reach mqtt.drb.cusano.net:8883' — is what the owner needs. Ask: add `mqtt_manager.last_error` (str + epoch), set in `_on_connect` (reason_code != 0), `_on_disconnect` and `_connect_with_retry`; cleared on connect. Then `app/internal/health.py` MQTT check reads it. mqtt_manager.py is being edited by the install/OTA work (#14/#15), so sequence after that lands.
logan added the area/frontendarea/mqtt
priority
p3
type
feature
 labels 2026-10-05 02:05:10 -04:00
logan commented 2026-11-01 06:39:51 -05:00
Author
Owner
Copy Link
Copy Source

Fixed in 1b4fcef, merged as c57a5b9 (PR #47).

Fixed in 1b4fcef, merged as c57a5b9 (PR #47).
logan removed the
priority
p3
 label 2026-11-01 06:39:52 -05:00
logan closed this issue 2026-11-01 06:39:52 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ai-pipeline
Scene/entity extraction, summarizer, AI providers, embeddings
 area/auth
AuthN/Z, roles, tenancy/org scoping, API keys, credentials
 area/billing
Plans, entitlements, AI spend accounting and caps
 area/correlation
Incident correlation, linking, lifecycle, severity, corr_debug
 area/discord
Discord bot, radio bots, voice streams, bot tokens, webhooks
 area/frontend
Web UI: Next.js app and the edge-node local dashboard
 area/governance
Board process, minutes, unattended runner, agent tooling
 area/growth
Go-to-market, outreach, cold email, discovery conversations
 area/infra-deploy
CI/CD, VM, registry, Firestore rules/indexes deploy, Terraform/Caddy
 area/legal
ToS, retention, licences/DAAs, CAN-SPAM, E&O, name suppression
 area/map
Live map: pins, paths, tiles, legend, geocoding
 area/mqtt
Node-C2 MQTT, checkins, commands, node sweeper, dynsec
 area/node-ota
Node install, enrollment, OTA updater, image skew
 area/osint
External feeds: cameras, 511, ADS-B, AIS, outages, and their licences
 area/recording-audio
Call capture, boundaries, PulseAudio, ring buffer, trimming, attribution
 area/sdr-radio
OP25 decode, SDR hardware/tuning, conventional, second SDR, mesh radio
 area/transcription
STT, transcript correction, place verification, name accuracy
 board
Board process: minutes and board-filed items
 board:agenda
Needs board scoping at the next sitting; CEO removes the label once scoped
kind
behavior-bug
Wrong product behavior; the instrument reads it correctly
kind
measurement-bug
Corrupts the recording/instrument (debug data, evals, health checks), not behavior
priority
p0
Drop everything: prod broken, live exposure, or owner-ruled P0
priority
p1
Next up: blocks a gate, a customer, or core incident quality
priority
p2
Normal: real defect or planned work, schedule in turn
priority
p3
Low: minor, cosmetic, or someday
status
blocked
Waiting on an external party, spend, or another issue
status
in-progress
Branch or PR open against it
status
needs-decision
Waiting on an owner or board ruling before work
status
needs-info
Root cause or repro unknown; needs a reading first
type
bug
Something built is wrong: code, data, or a measurement
type
chore
Maintenance, refactor, tests, pinning, cleanup: no user-visible change
type
decision
A ruling to make or record: board minutes, owner calls, legal reviews
type
docs
Docs, runbooks, CLAUDE.md, skills, SOPs
type
feature
New capability or an extension of an existing one
type
security
Security, privacy, credential or tenant-isolation exposure
type
tracking
Tracker, checklist, initiative or punch-list spanning several changes
No labels area/frontend area/mqtt
type
feature
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
logan
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: logan/node-26#21