What do you want to add?
A way for a user to compare the radio region their Meshpoint reports with the region Meshradar has on record for that device (fleet / device metadata from upstream). Clear UI when they differ (and short guidance to fix config).
Why is this useful?
Catches misconfiguration and drift (wrong region in local.yaml, old claim, or device moved) before someone spends time debugging “why I see no mesh” or “why cloud stats look wrong.”
Does this affect:
Extra notes
Probably authenticated fleet or device detail on Meshradar plus device heartbeat/API fields for region. May need a defined source of truth if cloud infers region only from packets vs explicit device config. Requested by kendelmccarley re: MR Cloud Map
What do you want to add?
A way for a user to compare the radio region their Meshpoint reports with the region Meshradar has on record for that device (fleet / device metadata from upstream). Clear UI when they differ (and short guidance to fix config).
Why is this useful?
Catches misconfiguration and drift (wrong region in local.yaml, old claim, or device moved) before someone spends time debugging “why I see no mesh” or “why cloud stats look wrong.”
Does this affect:
Extra notes
Probably authenticated fleet or device detail on Meshradar plus device heartbeat/API fields for region. May need a defined source of truth if cloud infers region only from packets vs explicit device config. Requested by kendelmccarley re: MR Cloud Map