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

Diagnostics displaying wrong hotspot name after card swap #84

Open
smeakles79 opened this issue Jan 29, 2022 · 1 comment
Open

Diagnostics displaying wrong hotspot name after card swap #84

smeakles79 opened this issue Jan 29, 2022 · 1 comment

Comments

@smeakles79
Copy link

I have a couple hotspots on and that I keep running (unasserted) to keep the cards synced and up to date. When a field installed hotspot dies, for whatever reason, I've been swapping cards to get them back online rather than wait to resync 10k blocks. With the most recent firmware at latest 2022.01.24. When you swap the cards and run diagnostics on the hotspot, the diagnostics will now show the name of the hotspot and the address from the hotspot the card came from, not the information from the hotspot the card was in. I swapped 2 units, and all 4 had the name/ address swap in diagnostics. Hard closing the app doesn't seem to resolve. I've got the cards from the deployed units back in the donor units. Will update if I see the name/address resolve on those donor units. At least one of the deployed units is earning again, other may still have internet issues)

@ke6jjj ke6jjj transferred this issue from helium/miner Jan 30, 2022
@ke6jjj
Copy link

ke6jjj commented Jan 30, 2022

@Sneak85, I've transferred this issue over to the component that actually performs the Bluetooth diagnostics function. I also suspect that the code here is using a quick shortcut to determine the miner name rather than querying the miner directly. The reason for doing so is likely historical, but it's important enough that this issue might likely not be solved to your liking, because accidentally swapping out SD-cards is a very rare feature, and trying to fix things to support such a swap will likely require dropping a key feature that this code relies on: being able to determine the hotspot name even when the miner itself is broken or not running.

If this issue is truly what I think it is then it's simply a display issue in the diagnostics output. The hotspot itself will know its proper name and will continue to function on the blockchain as normal, under its proper, ECC chip derived identity.

I see a possible mechanism that can be improved, but it will still allow the wrong name to appear in the diagnostics for up to a few minutes after the hotspot reboots and regains its bearings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants