Contact Details

ryanclose@ymail.com

Checklist

• I am able to reproduce the bug with the latest version.

• I have updated to the latest Alpha firmware, and am able to reproduce the bug. Many issues are fixed quickly in alpha before the general beta release.

• I made sure that there are no existing OPEN or CLOSED issues which I could contribute my information to.

• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.

• This issue contains only one bug.

• I have read and understood the Contribution Guidelines.

• I agree to follow this project's Code of Conduct

• I actually read this list, and should be taken seriously.

Affected app version

2.7.9

Affected Android version

Android 16

Affected phone model

Google Pixel 9 Pro

Affected node model

Seeed T1000-E, Seeed NRF52840/sx1262 kit.

Affected node firmware version

2.7.16

Steps to reproduce the bug

1. Notice that one (now at least 2 missing have been discovered) of my reliable solar nodes is missing my node list. Tried all communications of filters and sort, including manual search.
2. Ask friend when they last saw it, responds that it's currently in their list and responding to traceroutes.
3. Attempt to import node from URL sent by them. Still does not appear. No error messages or other events after hitting "import", as shown in video below.
4. Send traceroutes to other nodes in the general area, the missing node shows up in the traceroute with it's NodeID.
5. Force stop app, try again. Nothing.
6. Restart phone, still nothing.
7. Check Wismesh Tap V2, missing node indeed appears in it's list.

Actual behavior

Node never appears in node list, despite appearing in traceroutes and in the log while importing the contact. Have not reset nodedb, as I'm monitoring some sensors for trends and don't want to lose the data for those at this time.

Expected behavior

I expected the node to self populate as they normally do. I'm not sure if this is the only missing one, but it's one that has been reliable for the last 2 years so was quickly observed when it went missing.

Screenshots/Screen recordings

Relevant log output

to: 1984577019 (!764a3dfb)
id: 3752095286
hop_limit: 7
want_ack: true
priority: RELIABLE
decoded {
  portnum: ADMIN_APP
  payload: "\222\004V\b\232\275\355\356\t\022L\n\t!9ddb5e9a\022\vSt. Michael\032\004\360\237\252\275\"\006\377\347\235\333^\232(\tB \177.\340\033VI\224\334\220!\277\370_(\313\004\344r\216W\223\203\t\275\333\315;\315\201\271h~H\001 \001\252\006\b\037\220\227yC\206 \251"
}

Decoded Payload:
{
add_contact {
  node_num: 2648399514
  user {
    id: "!9ddb5e9a"
    long_name: "St. Michael"
    short_name: "\360\237\252\275"
    macaddr: "\377\347\235\333^\232"
    hw_model: RAK4631
    public_key: "\177.\340\033VI\224\334\220!\277\370_(\313\004\344r\216W\223\203\t\275\333\315;\315\201\271h~"
    is_unmessagable: true
  }
  manually_verified: true
}
session_passkey: "\037\220\227yC\206 \251"

}

Additional information

No response