Skip to content

feat(meshcore): send flood advert on first device connect#117

Merged
pskillen merged 1 commit into
mainfrom
bot-116/pskillen/initial-flood-advert
May 25, 2026
Merged

feat(meshcore): send flood advert on first device connect#117
pskillen merged 1 commit into
mainfrom
bot-116/pskillen/initial-flood-advert

Conversation

@pskillen

Copy link
Copy Markdown
Owner

Summary

Stop-gap for #116: when a MeshCore radio session connects for the first time, the bot sends one flood-routed advert via send_advert(flood=True) so the feeder is visible on the mesh without waiting for firmware timing.

Does not close #116 (API-driven interval and WebSocket refresh still planned).

Changes

  • MeshCoreRadio.schedule_initial_flood_advert() — asyncio task on the radio loop after first SELF_INFO connect
  • Unit tests in test/meshcore/test_initial_flood_advert.py
  • Note in docs/MESHCORE.md

Test plan

  • pytest test/meshcore/test_initial_flood_advert.py test/meshcore/test_radio_channel_sync.py -v (project venv)
  • Manual: RADIO_PROTOCOL=meshcore, confirm log MeshCore sent initial flood advert after connect

Stop-gap until API-driven periodic adverts (#116): schedule
send_advert(flood=True) once when the radio session first connects.
@pskillen pskillen merged commit aebc745 into main May 25, 2026
8 checks passed
@pskillen pskillen deleted the bot-116/pskillen/initial-flood-advert branch May 25, 2026 15:43
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.

MeshCore: periodic flood advert (fetch ManagedNode config from API)

2 participants