Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Factory reset not actually resetting node. #4007

Open
madeofstown opened this issue May 31, 2024 · 4 comments
Open

[Bug]: Factory reset not actually resetting node. #4007

madeofstown opened this issue May 31, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@madeofstown
Copy link

madeofstown commented May 31, 2024

Category

Other

Hardware

Heltec Wireless Tracker

Firmware Version

2.3.10.d19670b

Description

Performing a factory reset from the Android app on Heltec Wireless Tracker v1.1 appears to leave old messages and nodes (now all unknown name) on the device.

Steps to reproduce:

  1. Be connected to node via Bluetooth to your Android device.
  2. Go to settings and select the Factory Reset option. Confirm. Whatch node reboot.
  3. Re-pair and reconnect to same Android device.
  4. See message on node screen. It's from ??? 2 hours ago.(I did receive the message 2 hours ago before driving to a different city on different side of mountain range and factory resetting. Pretty sure it's not being retransmitted.)
  5. Scroll through screen and see a bunch of Unknown Name nodes.
    (This is without setting a region from the Android app)

Update:
The Node now also displays on screen that it is connected to other nodes. I still haven't set up a region since the factory reset.
Update:

Relevant log output

No response

@madeofstown madeofstown added the bug Something isn't working label May 31, 2024
@clwgh
Copy link

clwgh commented Jun 1, 2024

It may be that you're seeing those nodes and messages stored on the Android app (now unknown since the node has indeed factory reset). There may well be a separate option in the Android app to clear the node database from the app.

To be sure, you can check the nodes on the device directly using the Python CLI, with the command meshtastic --nodes. If you see none (or a handful in the seconds since the factory reset) then it is resetting as expected. If you see them all still there then it's not.

@madeofstown
Copy link
Author

Clearing the node database before or after factory reset doesn't seem to make any difference.

@djripcord
Copy link
Sponsor

djripcord commented Jun 16, 2024

It may be that you're seeing those nodes and messages stored on the Android app (now unknown since the node has indeed factory reset).

I don't believe the android app perpetually stores nodes. They seem to be stored in a volatile fashion. They will stick around when disconnected from a device. But when reconnecting it pulls down a fresh copy of the node DB stored on the device. Regardless, it's not possible to narrow down the issue to app or node unless @madeofstown provides the output from the CLI on a node query.

@madeofstown
Copy link
Author

Sorry, I've been working on other projects. I'll try to get around to capturing CLI output from the node this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants