Skip to content

Feature request: keep automatically adding contacts by removing oldest ones unless they are favorite #1227

Closed

Description

@sigram

Companion nodes can be set up to automatically add new contacts, or not. When this is turned on the newly discovered contacts are added until the list reaches device-specific limit (e.g. 350) and after that new contacts are only available in the Discovered list, they are not being automatically added because the list is full. Turning this function off means that you have to add any new contacts manually, which is tedious.

Someone (OS556) suggested a better approach (or maybe an option): when automatic adding is turned on the node would only keep the Favorite contacts intact, and replace other contacts by discarding the oldest ones. It would be elegant if this was handled in the firmware but if not then the companion app could do this whenever it's connected.

Activity

  1. mrlmuk commented on Dec 17, 2025

    @mrlmuk

    I made a feature request #931 for this a while ago which correctly describes the FIFO based on advertisement method I am imagining used because its not always clear to people.

    I don't think this is the best place for it to be noticed though, that would be discord probably. People are asking the same thing on here without searching and there are now a lot of issues open which don't seem to be being looked at effectively.

  2. liamcottle commented on Jan 18, 2026

    @liamcottle
    Member

    This has been implemented in #1379. Closing as completed :)

  3. bmweller commented on Mar 15, 2026

    @bmweller

    seeing a different version where after updating to companion release 1.14 favorite contacts are lost automatically after a number of days sat at 350 -- contact count resets and grows again. Has happened twice since updating the Heltec v4 on March 8th. Using iOS app v1.41.0 set to auto add chat users / repeaters / sensors only. and Overwrite Oldest is enabled.

  4. weebl2000 commented on Mar 15, 2026

    @weebl2000
    Contributor

    @bmweller try flashing this build one time #1601

    Then look at before and after storage size.

  5. bmweller commented on Mar 16, 2026

    @bmweller

    thanks for the direction. I've not stood up a build env, is there a way to access a prebuilt image?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions