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]: Suspected duplicate device identifier #3746

Closed
grinco opened this issue Apr 28, 2024 · 2 comments
Closed

[Bug]: Suspected duplicate device identifier #3746

grinco opened this issue Apr 28, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@grinco
Copy link

grinco commented Apr 28, 2024

Category

Other

Hardware

Other

Firmware Version

2.3.6.7a3570a

Description

My device has been heard on another continent. See screenshots. I suspect that it's an ID overlap.
Screenshot_20240428_154514_Meshtastic
MeshMap - Meshtastic Node Map (28 04 2024 16_38)
MeshMap - Meshtastic Node Map (28 04 2024 16_36)

Relevant log output

No response

@grinco grinco added the bug Something isn't working label Apr 28, 2024
@GUVWAF
Copy link
Member

GUVWAF commented May 1, 2024

According to Meshmap it's not the same Node ID. It shows different user IDs (!327b23ca and !da575630), which is derived from this. But I assume you don't have it set to US region when you're in Czech Republic? So then something else is wrong.

I see you run the Linux Native application (it says PORTDUINO) which uses a random ID if it doesn't has Bluetooth, but you can specify it with --hwid.

@thebentern
Copy link
Contributor

Meshmap is also not an official meshtastic source, though I do believe much of the data comes from our mqtt.

@thebentern thebentern closed this as not planned Won't fix, can't repro, duplicate, stale May 1, 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

No branches or pull requests

3 participants