[Bug]: App-provided nodes appear in list with spurious 0SNR 0RSSI 0HOPS

[NomDeTom]

Contact Details

I'm not giving my details to a machine

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.8.0 CLOSED9

Affected Android version

?

Affected phone model

Galaxy S10

Affected node model

promicro diy

Affected node firmware version

2.8.0

Steps to reproduce the bug

reconnect to previously used node with wiped nodeDB and some nodeDB entries
check nodelist
Note that some nodes are shown with spurious heard/hops/etc.

Actual behavior

several nodes are listed in the app that are not in the node's own node db, nor are they transmitted over the bluetooth connection. Therefore they exist in the app only.

Expected behavior

nodes don't keep coming back as last heard now, 0 hops, 0snr, 0rssi, etc.

Screenshots/Screen recordings

Relevant log output

Nothing relevant in the log - the nodes are coming from inside the building.

Additional information

No response

[jamesarich]

Logs? Expected behavior/logic?
It seems like this might have been an underscoped feature.

[NomDeTom]

Logs? Expected behavior/logic? It seems like this might have been an underscoped feature.

Updated. I ruled out firmware-side effects and have a potential improvement there, but this is almost certainly app-side.