[Bug]: Duplicate repeater even when using hybrid

[MeshMapperBot]

Platform: Map/Website

Description:
Someone brought up a node in IAD with the same id as mine so I followed your suggestion of driving with hybrid on to resolve the issue, but it doesn't appear to be working. I started hybrid wardriving yesterday around 4pm and 12 hours later its still marked as duplicate.

Thanks

Submitted by: Eldoon

[EldoonNemar]

Apologies. Didn't realize this would create a git issue when submitted from the site.
The duplicate id in IAD is FE

[CSP-Tom]

Hey there.

Driving in hybrid mode won't clear the duplicate ID, unfortunately, and apologies for the misunderstanding. What it will do, though, is use Discovery pings, which when heard by a repeater (must be running up-to-date firmware), will have it reply with its full public key/ID. Unlike other repeater replies that only identify themselves with the first 2 characters (1 byte) of their public ID, we can use the full ID to tie that DISC ping to the proper repeater.

So in other words, using hybrid mode won't change the status of a repeater in collision, but it will tie DISC pings with the correct repeater regardless of that fact that it shares a 1 byte ID with another repeater.

The repeater with a colliding ID will remain on the map as long as it's still sending adverts. This unfortunately is a MeshCore limitation (though efforts for multi-byte paths are very much in the works), and not a MeshMapper one. That said, there are tips and tricks and ways to adjust a regions settings to best suit needs...you can read about those here:
https://wiki.meshmapper.net/duplicaterepeaterid/

I'm closing this one as is isn't a bug, but please feel free to reopen if needed!