Skip to content

v0.2.1 — the radio hears

Choose a tag to compare

@Resilum-owner Resilum-owner released this 07 Sep 13:21
· 29 commits to main since this release

BLE

  • The driver read nothing back from the radio. It wrote commands and never
    collected events, so a scan started but its results were dropped, a peer that
    dialled us was never noticed, and GATT writes and notifications went nowhere —
    two nodes could not find each other over the radio at all. Discovery,
    disconnects, incoming subscriptions, incoming writes and notifications now
    reach the engine, and a node that dials a peer subscribes to its notify
    characteristic.
  • The beacon moved into service data, keyed by the service UUID, and is read
    from there in preference to the advertised name. A peer still announcing in
    its name is heard as before.
  • A failed handover to the radio no longer costs the session. It ran inside
    a Once, which a panic poisons for the life of the process, so the next
    attempt failed on the poison rather than on anything real.

Wi-Fi group

  • A group is raised only when there is a neighbour to raise it for. A node
    that heard nobody won the election against itself and hosted for an empty room.
  • The profile is deleted rather than left behind. One was created per
    activation and nothing removed it; a failure on the step after the radio came
    up dropped the teardown unrun, and the next tick tried again.

Covert

  • An acknowledgement for something never sent is refused — a peer could hang
    the engine with one out-of-range ack.

Deployment

  • Compose pulls the published images instead of building from source, and the
    README says plainly whether a node interoperates with a Python RNS network.