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]: NodeID Changed after Update #3641

Closed
daniel-hofer opened this issue Apr 16, 2024 · 6 comments · Fixed by #3651
Closed

[Bug]: NodeID Changed after Update #3641

daniel-hofer opened this issue Apr 16, 2024 · 6 comments · Fixed by #3651
Assignees
Labels
bug Something isn't working

Comments

@daniel-hofer
Copy link

daniel-hofer commented Apr 16, 2024

Category

BLE

Hardware

T-Echo

Firmware Version

2.3.5.2f9b68e

Description

The NodeID changed after Update to latest alpha 2.3.5 on t-echo to !7c3b4eeb. Did nrf reset and resetted android app. Noticed, that my node was shown twice in the app and noticed, that the mac-address nodeID changed. Noticed that the pairing started with 000_xxxx new node ID.
Did a restore of the settings via app. reinstalled android app and reflashed node.

Relevant log output

No response

@daniel-hofer daniel-hofer added the bug Something isn't working label Apr 16, 2024
@GUVWAF
Copy link
Member

GUVWAF commented Apr 16, 2024

So your initial flash was without full erase, right?
Might it be that there was another node with this node number on your mesh?
If you now reboot, I assume the node number stays the same. If you fully reset it again, will it have the original one or yet another new one?

@daniel-hofer
Copy link
Author

daniel-hofer commented Apr 16, 2024

2024-04-16 21_31_44-Meshtastic Web
Node is showing zero as MAC-Address
I will reset it and write a summary with the needed information.

@GUVWAF
Copy link
Member

GUVWAF commented Apr 16, 2024

Ah, so it's only the MAC address and thus BLE name, but not actually the node number that changed?

@daniel-hofer
Copy link
Author

daniel-hofer commented Apr 16, 2024

Steps:
Save Node-Config via Android App Version 2.3.4
Full erase node with Meshtastic_nRF52_factory_erase_v2.uf2
Serial console and confirm factory reset with any key -> Formatting done -> node restart
Copy firmware-t-echo-2.3.5.2f9b68e.uf2 to node -> node restart
Delete local appdata on Android App.
Delete Bluetooth pairing
Search for node, node shows up with correct ble name Meshtastic_b561 after + Symbol.
Pairing with pin on display
Pairing done
Device Name Meshtastic b561 Region unset.
Device config -> factory reset from menu of android app -> reboot node
Now the Device Name changed to Meshtastic 0000 region unset.
Region set to EU_868 -> node reboot
Other Node hast now this node shown up as Meshtastic 0000 T_ECHO wit 00:00... MAC Address
Node ID is !4162b561 in Settings, correct node.
Import config via Andorid app cfg file -> node reboot
After this, all went correct, but the shown mac-address in the nodelist from the webview of the other node still sowes zeroes for this node.
After delete the nodelist of the webview node, my device showed up with zeroes in the MAC Address section again.
Finally I couldn't manage it to show me a wrong nodeID in the App like after updating without formatting. Maybe it was a misconfiguration regarding to another node, wich was connected earlier by bluetooth bot not recognized in the app anymore after deleting the cache of the app.

@daniel-hofer
Copy link
Author

daniel-hofer commented Apr 16, 2024

I made all steps again WITHOUT radioconfiguration/factory reset from android app 2.3.4 and the mac address is shown correctrly again
image
So it is an issue with the radioconfiguration/factory reset part of the implementation, I suggest

@GUVWAF
Copy link
Member

GUVWAF commented Apr 17, 2024

Thanks for the elaborate explanation, I now understand what happened and it should not happen anymore with the above PR.

thebentern added a commit that referenced this issue Apr 17, 2024
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

Successfully merging a pull request may close this issue.

2 participants