Skip to content

fix(meshcore): WS feeder prefix and channel scan diagnostics#108

Merged
pskillen merged 2 commits into
mainfrom
bot/paddy/log-mc-channels-on-connect
May 21, 2026
Merged

fix(meshcore): WS feeder prefix and channel scan diagnostics#108
pskillen merged 2 commits into
mainfrom
bot/paddy/log-mc-channels-on-connect

Conversation

@pskillen

Copy link
Copy Markdown
Owner

Summary

Follow-up to #106 / #107 for MC channel apply and empty-channel debugging:

  • Append feeder_pubkey_prefix to feeder WebSocket URL so API node_mc_{id} group matches the correct feeder when multiple MC nodes share a constellation API key.
  • Log device channel table on connect; WARNING with per-slot get_channel scan when no named channels are found.
  • Short delay before read_device_channels after connect.
  • MESHFLOW_WS_URL can be omitted when STORAGE_API_ROOT is set (derived automatically).

Depends on meshflow-api#335 for WS group + apply dispatch fixes.

Related #295

Testing performed

  • pytest test/meshcore/test_channels.py test/meshcore/test_channel_sync.py -v
  • Staging: connect, channel sync POST, UI apply returns 202

Pass feeder_pubkey_prefix on ws/nodes/ so apply-mc-channel-config reaches
the connected bot; log per-slot get_channel results when empty; brief
delay before channel read after connect.
@pskillen pskillen merged commit 44e595f into main May 21, 2026
3 checks passed
@pskillen pskillen deleted the bot/paddy/log-mc-channels-on-connect branch May 21, 2026 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants