Skip to content

add: remote reassociation request #25

@Bilchreis

Description

@Bilchreis

Problem

1) Sticky association to a non-optimal coordinator

A levelmeter may remain associated with a coordinator even when other coordinators are closer and provide better signal strength.

2) Reported location can become wrong after moving a device

If a levelmeter is moved, its position is inferred from the coordinator it’s connected to.
When the levelmeter stays connected to the old coordinator, the physical vessel location and the reported location no longer match.


Proposed solution

Add a reassociation request message

  • Introduce a new message code: Reassociation Request
  • When received, it triggers the levelmeter to reassociate and select the coordinator with the best signal (e.g., highest RSSI / link quality).

Expected outcome

  • Levelmeters can be prompted to switch to the best available coordinator
  • Reported vessel location stays accurate after device relocation

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions